Terms of Service

The terms that govern your use of ProofCall™ products, services, records, and verification tools.
Last updated: September 21, 2026

1. Acceptance of Terms 

By creating an account, accessing the website, using ProofCall™, participating in a ProofCall™ session, uploading records, using ProofVault™, or using any ProofCall™ product or service, you agree to follow these Terms and any policies referenced within them.

These referenced policies may include, where applicable:

  • Privacy Policy;
  • Consent Disclosures;
  • Recording Consent Terms;
  • ProofVault™ Retention Policy;
  • ProofCall Pay™ Terms;
  • Evidence Manifest Rules;
  • Compliance Report Rules;
  • Court, agency, organization, or business account terms;
  • Any additional notices presented during signup, verified enrollment, or session creation.

If you do not agree with the applicable terms, you should not use ProofCall™.

Consent is required. Records are protected. Access is controlled.

ProofCall™ is designed for lawful, consent-based, identity-verified documentation. It is not a spy app, public-monitoring system, or open-access feed. Records remain private unless authorized by the user, required by consent-based workflow, attached to a verified case or record, or accessed through lawful order, legal hold, court/agency process, or approved role-based compliance review.

2. Purpose of ProofCall™ 

ProofCall™ is designed as a consent-first, identity-verified, evidence-grade communication and trust-infrastructure platform.

ProofCall™ supports verified communication, consent documentation, record preservation, ProofVault™ storage, Evidence Manifests, Compliance Reports, audit trails, certified exports, service evidence, transaction evidence, and lawful accountability workflows.

ProofCall™ is not a general-purpose spy app, hidden surveillance tool, public-monitoring platform, casual social platform, or open-access viewing system.

ProofCall™ is intended to help users document communications and records in a lawful, transparent, consent-based, and verifiable manner.

Your existing legal framework already identifies ProofCall™ as a secure communication platform for verified, consent-based video and audio sessions and states that it is not a surveillance tool.

3. Consent Comes First 

ProofCall™ sessions are designed to begin only after required consent or lawful authorization is captured.

Before a recorded, stored, transcribed, exported, shared, or evidence-generating session proceeds, ProofCall™ may require consent or authorization steps, such as:

  • On-screen acknowledgment;
  • Participant confirmation;
  • Voice or video confirmation;
  • Verified enrollment;
  • Role-based approval;
  • Court, agency, or organization authorization;
  • Guardian, caregiver, professional, or administrative approval where legally required.
If required consent is declined, incomplete, expired, withdrawn, or legally insufficient, the session should not proceed as a recorded, stored, transcribed, exported, or evidence-generating session.
Consent is a gate, not a label.

4. Lawful Use of the Platform

ProofCall™ may only be used for lawful purposes and in accordance with all applicable consent, recording, privacy, evidence, communications, payment, court, agency, and data-protection requirements.

Users agree not to use ProofCall™ to:

  • Harass, intimidate, stalk, threaten, exploit, impersonate, or deceive another person;
  • Record, document, monitor, or share another person without required consent or lawful authority;
  • Upload false, altered, misleading, or unlawfully obtained records;
  • Tamper with ProofVault™, hash records, timestamps, audit trails, Evidence Manifests, or Compliance Reports;
  • Bypass identity verification, role verification, KYC/KYB, credential validation, or authority checks;
  • Use ProofCall™ for unlawful surveillance;
  • Misrepresent a record as court-certified, agency-approved, notarized, or legally conclusive unless that status has actually been granted;
  • Abuse ProofCall Pay™, release-code governance, payment evidence, or transaction evidence workflows;
  • Interfere with the security, availability, or integrity of the platform.

Accounts or sessions found to violate these Terms may be restricted,
suspended, terminated, placed under review, or preserved for compliance
purposes where legally required.

5. Verified Identity, Roles, and Authority

ProofCall™ may require users, organizations, professionals, agencies, businesses, or other participants to complete identity or authority verification before using certain features.

Verification may include:

  • KYC identity verification;
  • KYB business verification;
  • Role verification;
  • Credential validation;
  • Court or agency enrollment;
  • Professional license verification;
  • Guardian or caregiver authority review;
  • Organization administrator approval;
  • Device or account security checks.

A user may hold more than one verified role or persona, but each role may operate within its own permissions, context, evidence namespace, and audit boundary.

Users may not claim a role, credential, title, agency status, business authority, court authority, professional status, or legal authority they do not actually possess.

6. No Public Visibility / No Spy-App Use

ProofCall™ does not create a public feed, public viewing channel, or open-access record of a user’s everyday life.

Private ProofCall™ records are not available to the public.

A record may only become viewable outside a user’s private account, session, case, or authorized context when one or more of the following applies:

  • The user chooses to create, save, flag, share, export, submit, or attach the record;
  • The record is part of a consent-authorized session;
  • The record is attached to a case, dispute, transaction, document exchange, Evidence Manifest, service record, or Compliance Report;
  • Required consent or lawful authorization has been captured;
  • A court, judge, agency, subpoena, legal hold, compliance process, or other lawful order requires access;
  • A verified role-based reviewer is permitted to access the record under ProofCall™ access-control and audit rules.
ProofCall™ is designed to protect privacy while preserving accountability.

7. ProofVault™ and Evidence Records 

ProofVault™ is designed to store records in a secure, controlled, and tamper-evident environment.

ProofVault™ may support:

  • Session records;
  • Uploaded documents;
  • Audio/video records;
  • Consent logs;
  • Evidence Manifests;
  • Compliance Reports;
  • Payment evidence;
  • Service evidence;
  • Certified exports;
  • Audit logs;
  • Hash records;
  • Legal hold records;
  • Chain-of-custody materials.

ProofVault™ records may be protected by encryption, cryptographic hashes, timestamps, role-based access controls, audit trails, retention rules, legal hold controls, and certified export workflows.

Your framework already states that ProofVault™ files are encrypted, timestamped, protected by chain-of-custody, governed by role-based access, and subject to dual-party retention where applicable.

User-facing deletion may remove or hide information from a user’s view, but sealed records, audit logs, legal-hold materials, compliance records, dispute records, payment evidence, or retention-controlled evidence may remain preserved where required by law, policy, court order, evidentiary integrity, or compliance obligations.

8. Documents, Uploads, and Shared Records 

Users may be able to upload, store, scan, sign, share, export, or attach documents and other records inside ProofCall™. By uploading or submitting content, the user represents that they have the right, authority, consent, or legal basis to upload and process that content.

ProofCall™ may apply:

  • Hashing;
  • Timestamps;
  • Audit logging;
  • ProofVault™ storage;
  • Evidence Manifest attachment;
  • Certified export rules;
  • Access controls;
  • Watermarking;
  • Revocation of future access;
  • Retention and legal-hold control

Revoking access may stop future viewing or sharing, but it may not delete the canonical ProofVault™ copy, audit trail, legal-hold record, or compliance-preserved evidence.

9. ProofCall Pay™ 

ProofCall Pay™ is designed to document payment intent, payment terms, release-code governance, transaction evidence, and compliance-related payment records.

ProofCall Pay™ is not intended to operate as a public banking service or open consumer wallet.

ProofCall™ does not intend to hold or take custody of principal funds transferred between parties unless a final legally approved product model, payment partner structure, licensing analysis, and applicable compliance framework expressly permits it.

ProofCall Pay™ may document:

  • Payment intent;
  • Release-code terms;
  • Transaction confirmation;
  • Service evidence;
  • Delivery confirmation;
  • Dispute records;
  • Compliance events;
  • Audit trails;
  • Evidence Manifest attachments.

Final ProofCall Pay™ terms may be revised by ProofCall’s legal, payments, financial regulatory, and compliance advisors before launch.

10. Location Information and Verification 

ProofCall™ may request or use location-related information only where enabled, consented to, legally authorized, or needed for a specific verification workflow.

Location handling may vary by session type, account type, privacy setting, lawful order, court/agency requirement, device setting, or selected privacy mode.

ProofCall™ may support privacy-preserving location modes such as:

  • Precise location;
  • Approximate location;
  • Escrowed location;
  • Withheld location;
  • Safety Mode.

Location data is not intended to create public tracking or everyday monitoring of a user’s private life.

When location is withheld, limited, or unavailable, ProofCall™ may still preserve evidentiary integrity through other anchors, such as timestamps, device attestation, audit logs, hashes, session metadata, and secure event records.

11. Integrity Engine and Automated Reports 

Certain ProofCall™ features may generate reports, summaries, metrics, or verification records.

If enabled, Integrity Engine features may analyze consent-authorized sessions to generate communication metrics, report artifacts, hashes, and audit records. Existing ProofCall™ Integrity Engine materials state that the feature is limited to consent-authorized sessions and does not assess emotions, mental states, or provide psychological, medical, or legal advice. ProofCall™ — Integrity Engine Legal Addenda (Filled • Sanitized).pdf

Any automated report should be treated as informational, evidence-supporting, and subject to human review.

ProofCall™ does not guarantee that any report, record, transcript, export, or Compliance Report will be accepted by a court, agency, business, insurer, employer, professional board, or other third party.

12. Access, Sharing, and Exports 

Access to ProofCall™ records may be governed by:

  • Consent;
  • Verified identity;
  • Role-based access control;
  • Persona/context boundaries;
  • Case or session permissions;
  • Organization policies;
  • Legal hold rules;
  • Court or agency authority;
  • Export controls;
  • Retention requirements.

Every material access event may be logged, including:

  • Create;
  • View;
  • Edit;
  • Share;
  • Export;
  • Revoke;
  • Sign;
  • Print;
  • Certified export;
  • Legal hold;
  • Release-code action;
  • Administrative review;
  • Compliance review.
Users are responsible for ensuring that any disclosure, export, download, print, submission, or sharing action is lawful and authorized.

13. Retention, Deletion, and Legal Hold 

ProofCall™ may retain records as necessary to operate the platform, provide services, preserve evidence integrity, maintain audit trails, resolve disputes, comply with legal obligations, enforce agreements, or satisfy court/agency requirements.

Certain records may be subject to:

  • Retention schedules;
  • Dual-party retention requirements;
  • Legal hold;
  • Court order;
  • Agency policy;
  • Certified export preservation;
  • Chain-of-custody requirements;
  • Fraud, misuse, or security review.

A deletion request may remove account information or hide user-facing content where legally permitted, but it may not purge records that must be retained for legal, compliance, evidentiary, dispute, audit, security, or retention reasons.

14. User Content and Ownership

Users may retain ownership of content they lawfully upload, create, or submit.

By submitting content to ProofCall™, users grant ProofCall™ the limited authority needed to operate the platform, store the record, secure it, process it, verify it, create hashes, generate audit logs, produce reports, support exports, comply with lawful requests, and maintain ProofVault™ integrity.

ProofCall™ does not claim ownership of user evidence merely because it is stored in ProofVault™.

Users remain responsible for the legality, accuracy, authorization, and appropriateness of content they upload or submit.

15. Service Providers and Third-Party Components 

ProofCall™ may use trusted service providers, vendors, infrastructure providers, identity-verification providers, payment-related partners, hosting providers, analytics-limited service providers, security tools, transcription tools, or other technical systems to operate the platform.

Service providers should only receive information necessary to perform authorized services and should be subject to appropriate confidentiality, security, and data-protection obligations.

ProofCall™ may also use properly licensed third-party or open-source components. Third-party services may have their own terms, policies, and limitations.

16. Security 

ProofCall™ is designed to protect records through technical, administrative, and organizational safeguards.

These safeguards may include:

No platform can guarantee absolute security. Users are responsible for protecting their login credentials, devices, access tokens, release codes, account credentials, and authorized contact methods.

17. Court, Agency, Professional, and Organizational Use

Some ProofCall™ use cases may involve courts, agencies, law enforcement, healthcare, elder care, custody matters, legal professionals, business users, service providers, or other regulated environments.

Those uses may require additional terms, agreements, approvals, authority verification, enrollment steps, retention rules, access restrictions, legal review, compliance workflows, or jurisdiction-specific requirements.

If an organization, court, agency, employer, business, or professional entity provides access to ProofCall™, additional policies may apply.

18. No Legal, Medical, Financial, or Professional Advice 

ProofCall™ may help document communications, evidence, consent, payment intent, service evidence, transaction events, or compliance records.

ProofCall™ does not provide legal, medical, mental health, financial, tax, law enforcement, judicial, or professional advice.

Users should consult qualified professionals for advice regarding legal rights, court procedure, medical issues, financial matters, payment obligations, compliance duties, or regulated activity.

19. No Guaranteed Outcome or Admissibility 

ProofCall™ is designed to support verification, documentation, evidentiary integrity, and accountability.

ProofCall™ does not guarantee:

  • Court admissibility;
  • Court acceptance;
  • Agency acceptance;
  • Case outcome;
  • Payment outcome;
  • Dispute outcome;
  • Business approval;
  • Regulatory approval;
  • Law enforcement action;
  • Professional board action;
  • User credibility findings;
  • Any specific legal or financial result.

Records generated through ProofCall™ may support review, verification, dispute resolution, or legal process, but final determinations belong to courts, agencies, arbitrators if applicable, businesses, regulators, professionals, or other authorized decision-makers.

20. Intellectual Property 

ProofCall™, ProofVault™, ProofCall Pay™, related names, marks, logos, designs, interfaces, workflows, systems, text, graphics, features, technical architecture, documentation, and platform materials may be protected by trademark, copyright, patent, trade secret, contract, or other intellectual-property laws.

Users may not copy, reverse engineer, reproduce, modify, distribute, sell, misuse, or create derivative works from ProofCall™ systems or materials except as expressly authorized.

21. Suspension and Account Termination

ProofCall™ may restrict, suspend, terminate, or review accounts, sessions, records, or access where necessary to protect users, comply with law, enforce these Terms, prevent fraud or misuse, preserve evidence integrity, respond to security concerns, or comply with court/agency requirements.

Reasons may include:

  • Violating consent requirements;
  • Uploading unlawful or unauthorized content;
  • Misrepresenting identity or authority;
  • Tampering with records;
  • Abusing ProofCall Pay™;
  • Attempting unauthorized access;
  • Harassing, threatening, exploiting, or deceiving others;
  • Violating law or platform policy;
  • Creating security, compliance, or legal risk.

Termination of user-facing access does not necessarily require deletion of audit logs, compliance records, sealed records, legal-hold materials, payment evidence, or retention-controlled records.

22. Changes to the Service or Terms 

ProofCall™ may update the platform, features, policies, workflows, or Terms as the product evolves.

When material changes are made, ProofCall™ may update the effective date and may provide additional notice where appropriate.

Continued use of ProofCall™ after updated Terms are posted or presented may indicate acceptance of the updated Terms, subject to applicable law and final legal policy language.

23. Governing Law and Dispute Resolution

Final governing law, venue, dispute-resolution procedures, consumer-rights disclosures, and any required jurisdiction-specific terms should be reviewed and approved by ProofCall’s legal advisors before publication.

Until final legal review is complete, this section should remain marked as pending.

Placeholder: These Terms and any related dispute-resolution provisions will be finalized by ProofCall’s legal and compliance advisors before launch or deployment.

Do not publish final arbitration, venue, class-action waiver, governing-law, or limitation-of-liability language until reviewed and approved by counsel.

Contact

For Terms of Service, legal, compliance, or policy questions, contact ProofCall™ through the official legal/compliance contact method below.

ProofCall™ Legal / Compliance Inquiries

P.O. Box 161
Demopolis, AL 36732

Official legal/compliance contact: legal@proofcall.com

Official privacy contact: privacy@proofcall.com

Legal/Compliance Review Notice:

This Terms of Service page is a plain-language website summary intended to explain ProofCall’s operating principles to visitors and prospective users. It is not the final binding legal Terms of Service. Final terms, payment language, dispute-resolution provisions, consumer disclosures, consent rules, retention requirements, jurisdiction-specific provisions, and compliance obligations may be refined by ProofCall’s legal, privacy, payments, and regulatory advisors before launch or deployment.

Scroll to Top