Privacy Policy

How ProofCall™ collects, uses, protects, and controls access to personal information

Last updated: September 21, 2026

Overview 

This Privacy Policy summary explains what information ProofCall™ may collect, how that information is used, how it is protected, and what choices users may have.

ProofCall™ is built around a simple principle.

Consent comes first. Identity must be verified. Evidence must remain protected.

ProofCall™ is designed to support consent-based, identity-verified, evidence-grade communication. It is not designed for hidden monitoring, public viewing, casual surveillance, or open access to another person’s private life.

ProofCall™ Is Not a Spy App 

ProofCall™ is not a spy app, surveillance app, public-monitoring platform, or social viewing system.

ProofCall™ does not allow the public, unrelated users, or unauthorized parties to view a user’s private communications, daily activity, location, documents, recordings, session records, or ProofVault™ evidence.

Information inside ProofCall™ remains private, encrypted, access-controlled, and limited to the verified user, authorized participants, approved role-based users, or legally authorized reviewers.

  • The user chooses to create, save, flag, share, export, submit, or attach the record;
  • The record is part of a consent-authorized ProofCall™ session;
  • The record is attached to a case, dispute, payment event, document exchange, Evidence Manifest, or Compliance Report;
  • Required participant 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. It verifies consent, identity, timestamps, and evidence integrity. It does not create a public feed, hidden monitoring tool, or open-access record of a user’s everyday life.

Information We May Collect 

ProofCall™ may collect information needed to operate the platform, verify users, support consent-based sessions, and preserve evidence integrity.

This may include:

  • Account details provided by the user, such as name, email address, phone number, and account preferences;
  • Identity verification information, such as KYC/KYB status, role verification, credential verification, or verified enrollment records;
  • Session metadata needed to verify identity, consent, timing, participation, and session status;
  • Consent records, including timestamps, consent selections, session confirmations, and withdrawal or refusal events;
  • Records the user chooses to create, upload, share, store, seal, export, or attach to ProofVault™;
  • Device, network, and security information used to protect the platform and support audit integrity;
  • Optional location-related verification data, depending on user settings, consent, permissions, lawful authorization, and applicable session rules;
  • Support communications and requests submitted through ProofCall™ contact forms, help channels, or administrative workflows.

ProofCall™ does not collect information for public display. Information is collected for platform operation, verification, security, consent documentation, compliance, evidence preservation, and user-authorized workflows.

How We Use Information 

ProofCall™ uses information to operate a secure, consent-first, identity-verified communication and evidence platform.

We may use information:

  • To create and manage user accounts;
  • To verify participant identity, role, authority, or enrollment status;
  • To confirm consent before a session begins;
  • To document session status, timestamps, participants, and consent events;
  • To generate evidence-grade records, Evidence Manifests, Compliance Reports, audit trails, and ProofVault™ records;
  • To secure the ProofCall™ platform against unauthorized access, tampering, impersonation, fraud, or misuse;
  • To support role-based access control, persona/context isolation, and case-scoped permissions;
  • To respond to user support requests;
  • To maintain legal hold, retention, export, and compliance workflows;
  • To comply with lawful orders, court processes, agency requirements, subpoenas, legal holds, or other legally valid requests.

ProofCall™ does not use private records to create a public profile of the user. ProofCall™ does not make private session evidence publicly visible.

Consent-Based Sessions 

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

Before a recorded or evidence-generating session proceeds, ProofCall™ may require one or more consent steps, such as on-screen acknowledgment, participant confirmation, role-based approval, verified enrollment, legal authorization, or administrative review.

If required consent is not provided, the session should not proceed as a recorded, stored, transcribed, exported, or evidence-generating session.

Consent events may be logged as part of the audit trail, including:

  • Who consented;
  • When consent was granted;
  • What session or record the consent applied to;
  • Whether consent was declined, withdrawn, expired, or incomplete;
  • Whether a lawful authorization or court/agency process applied.

Consent is not a decorative label inside ProofCall™. Consent is a gate.

ProofVault™ and Evidence Records 

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

Records stored in ProofVault™ may include session files, uploaded documents, compliance records, consent logs, Evidence Manifests, transaction records, service evidence, certified exports, audit logs, and related verification data.

ProofVault™ records may be protected by:

  • Encryption;
  • Cryptographic hashes;
  • Timestamps;
  • Role-based access controls;
  • Audit logs;
  • Chain-of-custody tracking;
  • Legal hold controls;
  • Retention rules;
  • Certified export workflows.

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

Who Can Access Information

ProofCall™ limits access based on consent, identity, role, authorization, and context.

Depending on the account type, session type, case type, or organization structure, access may be limited to:

  • The verified user;
  • Approved session participants;
  • Authorized account holders;
  • Verified guardians or caregivers;
  • Court, agency, legal, compliance, or administrative users with approved permissions;
  • Authorized business, professional, or organizational users;
  • Records custodians or compliance reviewers;
  • Service providers operating under confidentiality, security, and data-protection obligations;
  • Courts, agencies, or lawful authorities when legally required.

Every material access event should be logged, including actions such as view, create, share, export, revoke, sign, print, release, legal hold, compliance review, administrative access, or certified export.

ProofCall™ is designed so that access is attributable and reviewable.

Location Information and Privacy Modes 

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

Location handling may vary based on the selected mode, user permissions, lawful requirements, and session context. ProofCall™ may support privacy-preserving options such as precise location, approximate location, escrowed location, or location withheld/Safety Mode.

When location is off, withheld, or limited, ProofCall™ may still preserve evidentiary integrity through alternative verification anchors, such as timestamps, device attestation, audit logs, hash chains, session metadata, network artifacts, or other tamper-evident controls.

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

What ProofCall™ Does Not Do 

ProofCall™ does not:

  • Operate as a spy app;
  • Create a public feed of user activity;
  • Allow unrelated people to view private records;
  • Sell personal communications or ProofVault™ evidence;
  • Use private evidence records for public social display;
  • Allow hidden public monitoring of a user’s everyday life;
  • Bypass required consent for recorded sessions;
  • Treat location data as a public tracking feature;
  • Use Integrity Engine outputs to diagnose emotions, mental health, character, intent, or psychological state.

ProofCall™ is designed for verified communication, consent documentation, evidence preservation, and lawful accountability — not unauthorized surveillance.

User Choices

Users may have choices and controls depending on their account type, role, jurisdiction, legal obligations, and session context.

These choices may include:

  • Choosing whether to create a ProofCall™ record;
  • Choosing whether to participate in a consent-based session;
  • Choosing whether to upload, save, share, flag, export, or attach records;
  • Managing certain account information;
  • Requesting access to account information;
  • Requesting export of eligible information;
  • Requesting deletion or restriction of eligible information;
  • Managing certain communication and notification preferences;
  • Selecting available privacy settings, including location-related settings where supported.

Some requests may be limited by legal retention, dual-party consent requirements, court orders, legal holds, compliance obligations, fraud prevention, audit integrity, dispute resolution, or evidence-preservation requirements.

Retention and Legal Hold 

ProofCall™ may retain information for as long as necessary to operate the platform, support user-authorized records, preserve evidence integrity, comply with legal obligations, maintain audit trails, resolve disputes, enforce agreements, or satisfy court/agency requirements.

Certain records may be subject to legal hold, retention rules, certified export requirements, or chain-of-custody obligations.

When a record is sealed, attached to a case, included in an Evidence Manifest, placed under legal hold, or preserved for compliance purposes, it may not be fully deleted merely because one user requests removal from their personal view.

This protects both privacy and evidentiary integrity.

Security 

ProofCall™ is designed to protect information using technical, administrative, and organizational safeguards.

These safeguards may include:

  • Encryption in transit and at rest;
  • Secure authentication;
  • Role-based access control;
  • Persona and context separation;
  • Audit logging;
  • Hashing and tamper-evident verification;
  • Access review;
  • Retention and legal hold controls;
  • Secure export workflows;
  • Monitoring for unauthorized access or misuse.

No platform can guarantee absolute security, but ProofCall™ is designed around privacy, consent, accountability, and evidence-grade integrity.

Children, Protected Persons, and Sensitive Use Cases 

ProofCall™ may be used in sensitive contexts involving families, children, elderly individuals, patients, caregivers, legal matters, agencies, professionals, businesses, or court-related workflows.

Where children, protected persons, patients, or dependent individuals are involved, ProofCall™ may require verified authority, guardian approval, court/agency enrollment, role-based permissions, or other lawful authorization.

Users should not upload, record, share, or submit information they are not legally authorized to handle.

Service Providers 

ProofCall™ may use trusted service providers to help operate the platform, verify identity, secure data, provide hosting, process support requests, maintain infrastructure, or deliver compliance-related functionality.

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

ProofCall™ does not authorize service providers to use ProofCall™ evidence records for unrelated commercial purposes.

Lawful Requests and Compliance 

ProofCall™ may disclose information where required by valid legal process, court order, subpoena, agency requirement, regulatory obligation, legal hold, emergency request, or other lawful authority.

When legally and operationally appropriate, ProofCall™ may limit disclosures to the information necessary for the specific lawful request.

Access to records through lawful process should be documented through audit logs, compliance records, or chain-of-custody workflows where applicable.

Updates to This Policy 

ProofCall™ may update this Privacy Policy as the platform, legal requirements, product features, or compliance obligations evolve.

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

The final production privacy policy may be further refined by ProofCall’s privacy, compliance, legal, or regulatory advisors before launch or deployment.

For privacy questions, user requests, or compliance inquiries, contact ProofCall™ through the official privacy contact method provided on the website.

Contact

For privacy questions, user requests, or compliance inquiries, contact ProofCall™ through the official privacy contact method below.

ProofCall™ Privacy Inquiries

P.O. Box 161
Demopolis, AL 36732

Official privacy contact: privacy@proofcall.com

Users may also submit privacy requests through the ProofCall™ website contact form, if available.

ProofCall™ is not a spy app.

Your private records are not public. ProofCall™ does not allow the public to view your daily life, private communications, location, documents, or evidence records. Records remain private unless you choose to create, share, flag, export, or attach them — or unless access is required by lawful order, legal hold, verified compliance authority, or court/agency process.

Scroll to Top