From form fill to evidence, step by step.
- 1RecordThe publisher adds the cValue script to their form. It records the session and the consent moment, with sensitive fields masked.
- 2SealOn submit, the session is sealed into a certificate: hashed, signed and timestamped. Its link travels with the lead.
- 3ClaimWhen you buy the lead, one API call claims the certificate, matches the email and phone, checks consent rules and returns a TrustScore.
- 4KeepClaimed certificates are kept for 5 years, or longer on legal hold. Unclaimed certificates are deleted after 90 days and never billed.
- 5ProveOpen the replay, download the evidence pack, or share a secure link with counsel.
INDEPENDENT VERIFICATION
Verify any certificate yourself.
Each certificate’s hash is timestamped by two independent authorities the moment it is sealed. Anyone can recompute the hash and check those timestamps with standard tools like OpenSSL. If a single byte changed, the check fails. No login and no trust in cValue required.
See a sample certificate page →FOR DEVELOPERS
One script tag. One API call.
Publishers add the script to their form. Buyers claim the certificate when they accept the lead. Webhooks tell you when certificates are about to expire.
Read the docsQuestions
Add one script tag. Tagging the consent text is optional; cValue can find it automatically.
Nothing. You pay only when you claim.
5 years by default, longer on legal hold.
No. Any change would break its signature and timestamp, and anyone can check.
Masked session data, the consent moment, and keyed hashes of email and phone.