Last updated: July 2026
This Privacy Policy explains how LeadOpera LLC, a Colorado limited liability company (“Company,” “we,” “us,” or “our”), collects, uses, and shares information in connection with LeadProof™, TermsProof™, and our related websites and services (the “Services”). It should be read together with our Terms & Conditions.
The Services handle two categories of data that are treated differently:
(a) Account data — information about the businesses and users who sign up for and operate the Services. For this data we act as the controller.
(b) Certified records — the consumer-consent events or agreement acceptances that an integrating business or account captures and asks us to certify and seal on its behalf. For this data the integrating business or account is the controller and the Company acts as a service provider / processor: we process it under the business’s instructions to produce a tamper-evident record, and we do not sell it or use it to build consumer or signer profiles for our own purposes. For an agreement acceptance (TermsProof), the parties’ identifiers (such as a signer’s name and email) and the assent context (timestamp, IP, and intent-to-sign) are processed to produce the sealed record; identity is one-way hashed on the certificate, and no session recording is made. A consumer or signer who wishes to access, correct, or delete their information should contact the business or account that collected it; we will assist that party as its processor. See Your choices & rights.
Account & billing. Company name, contact name, email address, authentication identifiers, API keys, credit balance and transaction history, and support communications. Payments are processed by our payment processor (Stripe); we do not receive or store full payment-card numbers.
Consent records (on behalf of integrating businesses). At the moment a consumer consents on an integrating business’s property, the Services may capture: the consent language and form markup presented, the URL and the documents linked from it, the timestamp, the originating IP address, behavioral signals from the session (for example mouse movement, keyboard interaction, pointer events, and time-to-complete), and an anti-bot / anti-fraud assessment. Phone numbers and email addresses provided for later matching are hashed with a secret salt at capture and the plaintext is discarded — we store only the one-way hash, never the raw number or address.
Agreement records (on behalf of accounts). When a party accepts or executes an agreement, the Services may capture: the exact document and any exhibits presented, the acceptance statement and version, the signer’s name and email, the timestamp, the originating IP address, the recorded intent to sign, and the identity-assurance method and result. Signer identifiers used on the certificate are one-way hashed as above, and no session recording is made.
Technical & usage. Standard server and security logs, and cookies strictly necessary to keep you signed in and to run the anti-bot challenge. We do not use advertising or cross-site tracking cookies. See Cookies.
We use account data to provide, secure, bill for, and support the Services. We process consent and agreement records solely to perform the certification the integrating business or account requested — archiving and hashing what was observed, applying a trusted timestamp, scoring trust and fraud signals, and, on request, running verification, drift analysis, or generating evidence packages and attestations. We also use limited data as needed to detect abuse, comply with law, and enforce our Terms. We do not sell personal information.
We share information with vendors that help us run the Services, each under contractual confidentiality and data-protection obligations, and only as needed for their function:
We may also disclose information to comply with law or valid legal process, to protect the rights, safety, and security of our users and the public, or in connection with a corporate transaction (for example a merger or acquisition), in which case we will require the recipient to honor this Policy.
The Services are designed to seal evidence, not to accumulate personal data. Contact identifiers used for matching are stored only as one-way salted hashes; the certification record is a cryptographic seal over what was observed. Where a field is absent, we record its absence honestly rather than substituting a placeholder.
Account data is retained for the life of the account and as required for legal, tax, and audit purposes. Because a certificate’s value is evidentiary, sealed consent records and evidence are retained as directed by the integrating business (for example, for a chosen retention term) and for so long as they may be needed to demonstrate the integrity of a record. Retention on behalf of an integrating business is governed by our agreement with that business.
We use technical and organizational safeguards including encryption in transit and at rest, scoped access controls, cryptographic integrity hashing, and database-level immutability of sealed fields so a certified record cannot be silently altered after capture. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.
Depending on where you live, you may have rights to access, correct, delete, or port your personal information, or to object to or restrict certain processing. For account data, you may exercise these by contacting us at the address below. For consumer consent records, because the integrating business is the controller, please direct requests to that business; we will support the business in responding as its processor. Note that we may retain information where required by law or where a sealed record must remain intact for its evidentiary purpose, and that hashed identifiers are pseudonymous and not reversible by us.
We use only cookies that are strictly necessary: a session cookie to keep you signed in, and cookies set by our bot- mitigation provider to run the human/bot challenge. We do not use advertising, analytics-profiling, or cross-site tracking cookies. You can block cookies in your browser, but the Services may not function correctly without the necessary ones.
We operate in the United States, and our vendors may process information in the United States and other countries. Where required, transfers of personal data are made under appropriate safeguards. By using the Services you understand your information may be processed in the United States.
The Services are intended for businesses and are not directed to children. We do not knowingly collect personal information from children. If you believe a child’s information has been provided to us, contact us and we will take appropriate steps.
When an advertiser connects their Google Ads account to LeadProof (Setup → Social & hosted lead-ad forms → Google Ads), LeadProof accesses a narrow slice of Google user data under the adwords OAuth scope, strictly to power a user-facing feature. This section describes that data specifically, as required by the Google API Services User Data Policy.
lead_form_asset) via a GAQL query: the lead form’s consent disclosure text and privacy-policy URL, plus the identifiers needed to match a form (form / campaign / customer ids). Via the openid and email scopes we also receive the connecting account’s basic identity, solely to record which Google login was connected. We do not read, create, edit, pause, or delete campaigns, ads, budgets, keywords, audiences, or any other Google Ads data, and we never spend on the advertiser’s behalf.Limited Use. LeadProof’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
We may update this Policy from time to time. Material changes take effect when posted with an updated date; your continued use of the Services constitutes acceptance of the revised Policy.
Questions about this Privacy Policy may be directed to support@leadopera.com.
LeadOpera™ is a trademark of LeadOpera LLC, a Colorado limited liability company. Its products and services — including LeadProof™ and TermsProof™ — are proprietary and operated through their independent websites; LeadProof™ and TermsProof™ are trademarks of LeadOpera LLC. Unauthorized use of these marks is strictly prohibited. The certification method used by LeadOpera’s products is patent pending. A certificate is a tamper-evident technical record — not a determination of legal or regulatory compliance, validity, or enforceability, and not legal advice.
TrustedForm, Jornaya, Boberdoo, Phonexa, LeadsPedia, Google, Meta, Facebook, Instagram, Twilio, DigiCert, and Sectigo are trademarks of their respective owners; their mention describes interoperability only and does not imply any affiliation with, endorsement by, or sponsorship from those companies.
Press, partnership, and general inquiries: inquiry@leadopera.com
© 2026 LeadOpera LLC. All rights reserved.