Prove what happened.

Proof of consent that travels with every lead.

AdPriva records the consent wording displayed, the visitor’s action and whether the submission appears human or automated. It seals them in a tamper-evident record with an Evidence ID designed to travel with the lead, so buyers can examine the evidence.

Evidence Object

Evidence ID

EV-91C2-7F4A

Recorded interactionConsent box ticked, then form sentcompare.example · 28 Oct 2026
Traffic assessmentAssessed as humanProbabilistic, not identity verification
IntegrityDemonstration signatureCheck the sample record in the demo

Lead · home insurance quote

Evidence ID attached

To the marketplace →

Example

The lead travels. The proof often doesn’t.

When a lead changes hands, the consent evidence often stays with the original seller. If a buyer needs to prove what happened, a CRM field that says “yes” doesn’t tell the whole story.

EXAMPLE · HOME INSURANCE LEAD

  1. A consumer requests a home insurance quote on a comparison site and agrees to a call from Example Insurance.

  2. The lead passes through a marketplace and a broker before reaching the insurer.

  3. Weeks later, the consumer disputes having agreed to the call.

What the lead file says

Name
contact details
Phone
contact details
Product
Home insurance
Consent
yes

The lead says “yes”. But the evidence behind that answer may still be with the original seller.

What the evidence shows

Consent wording displayed
“I agree to be called by Example Insurance about my home insurance quote.”
Choice and time
Initially unticked, then ticked and submitted.28 Oct 2026, 09:41:05 UTC
Traffic assessment
Assessed as humanProbabilistic, not identity verification
Evidence ID
EV-91C2-7F4AOne reference to the recorded interaction and traffic assessment.

From one choice to checkable evidence.

Follow how a consent interaction is captured, assessed, sealed and made available for review.

  1. 1. Capture

    Recorded as it happens.

    On the seller’s form, the AdPriva tag records the consent wording displayed, the choice made and when the form was submitted. It does not read the contents of the visitor’s contact fields.

  2. 2. Assess

    Human, AI agent or bot?

    AdPriva analyses interaction signals to assess whether a form was submitted by a human, AI agent or bot, or whether the result is uncertain. Each assessment is probabilistic, not proof of identity or consent validity.

  3. 3. Seal

    Sealed into one Evidence Object.

    AdPriva seals the recorded interaction and its traffic assessment into one signed evidence record, linked to an Evidence ID. If the signed record is changed, its integrity check fails.

  4. 4. Verify

    The ID travels. The buyer checks.

    The Evidence ID is designed to travel with the lead, from the comparison site to the marketplace, broker and insurer. It gives buyers a way to examine the consent evidence and traffic assessment without relying solely on the seller’s records.

    Try the integrity check ↓

Explore the evidence. Check its integrity.

Explore the recorded interaction, traffic assessment and integrity of an Evidence Object. Run the integrity check directly in your browser.

Evidence ObjectExample

Evidence ID

EV-91C2-7F4A

What happened on the form

Consent request in view
“I agree to be called by Example Insurance about my home insurance quote.”Observed by AdPriva
Business named in the request
Example InsuranceSupplied by the seller
Purpose
Phone call about a home insurance quoteSupplied by the seller
Recorded action
Consent box ticked by the visitor, then form sentObserved by AdPriva
Action observed at
28 Oct 2026, 09:41:05.902 UTCObserved by AdPriva
Form fields read by the tag
NoneObserved by AdPriva
View all evidence details ↓
Evidence ID
EV-91C2-7F4A
Site and page
compare.example/home-insurance/quoteObserved by AdPriva
Consent box when observation began
Unticked · 28 Oct 2026, 09:41:02.118 UTCObserved by AdPriva
In view before the tick
4.2 sObserved by AdPriva
Received by AdPriva
28 Oct 2026, 09:41:07.010 UTCObserved by AdPriva
Wording reference (SHA-256)
01b71a85 975bfaa2 c921accb f87c3192 b88963a7 a44da31d e383bbf3 e922ddafObserved by AdPriva

Who or what submitted it

Why it matters: automated submissions can lower a lead’s quality, or raise questions about where an interaction came from.

Assessment
HumanWorked out by AdPriva
Main reason
R-101 · Varied pointer movement and typing rhythmTiming of pointer movements and keystrokes, never the keys typedWorked out by AdPriva
Nature
A technical assessment of how the interaction happened, not a legal finding.Worked out by AdPriva
Model
None: no model ran for this demonstrationWorked out by AdPriva
  • HumanR-101
  • AI agentR-211
  • BotR-304
  • UncertainR-002

What this layer doesn’t show: A probabilistic technical assessment: not a legal finding, and not an identity. Recognising AI agents is in preview. Evidence of whether an agent had a person’s authority to act is a separate capability, and it is planned.

Can anyone check it?

If anyone changes even one word of a record after it is signed, this check fails.

This demonstration

  • A record made for this page
  • Signed once with a throwaway key generated for the demonstration
  • No public anchor, batch or transaction
  • Checked in your browser by code on this page

A real AdPriva record

  • Made when a consumer sends a real form
  • Signed with AdPriva’s signing key
  • Grouped into a batch, with a receipt; public anchoring of new records is paused
  • Checked against AdPriva’s published key and its batch receipt

No real record is shown on this site yet.

Demonstration

Runs in your browser. Nothing is sent anywhere.

Not checked yet. Press Check integrity.

Record format
adpriva-website-demo/0
Signature algorithm
ECDSA P-256 with SHA-256
Signing key
Demonstration key made for this page, not AdPriva’s
Signature
v2lfzFdtkEFIQ4qorXksL_…8qjvp1ajoA
Public anchor
None for this demonstrationProduction records are grouped into batches, and each record gets a receipt for its batch. Public anchoring of new records is paused while replacement infrastructure is being evaluated. This demonstration has no batch, so no anchor is shown.
Show the record (JSON)
{
  "record": {
    "assessment": {
      "class": "human",
      "kind": "technical assessment, not a legal finding",
      "model": "none",
      "reason": "Varied pointer movement and typing rhythm",
      "reason_code": "R-101"
    },
    "evidence_id": "EV-DEMO-91C2",
    "format": "adpriva-website-demo/0",
    "interaction": {
      "action": "consent box ticked by the visitor, then form sent",
      "consent_box_when_observation_began": "unticked",
      "form_fields_read": "none",
      "observation_began": "2026-10-28T09:41:02.118Z",
      "observed_at": "2026-10-28T09:41:05.902Z",
      "page": "/home-insurance/quote",
      "purpose": "Phone call about a home insurance quote",
      "received_at": "2026-10-28T09:41:07.010Z",
      "recipient": "Example Insurance",
      "site": "compare.example",
      "wording": "I agree to be called by Example Insurance about my home insurance quote.",
      "wording_in_view_ms": 4200,
      "wording_sha256": "01b71a85975bfaa2c921accbf87c3192b88963a7a44da31de383bbf3e922ddaf"
    }
  },
  "signature": "v2lfzFdtkEFIQ4qorXksL_cfaS5g_72_xbCCFOqUwsrv9ITR9GL8TSBL_wHtJbrLooTfsjw3V3AX8qjvp1ajoA",
  "public_key": {
    "kty": "EC",
    "crv": "P-256",
    "x": "InqPmS3csIpNWPqLCRbXqDC7ceEpmnApoX1ukZuXI78",
    "y": "cZPOdvEQxofEWwF6TU2Oo9zFc88QyUifR_EtMcAsnlY"
  }
}

What this layer doesn’t show: A passing check shows the record is unchanged since it was signed, against the key it was signed with. It doesn’t show who acted, what they understood, whether everything recorded was accurate, or that the consent was legally valid.

Evidence both sides of the sale can use.

Sell leads that carry their own evidence.

For lead sellers · Publishers, comparison sites and affiliates

  • Provide an Evidence ID alongside each lead
  • Connect each lead to the consent interaction that produced it
  • Access consent wording, recorded actions and timestamps under one reference
  • Give buyers evidence they can examine when questions arise

For lead sellers

Check the evidence before you call.

For lead buyers · Insurers, brokers and marketplaces

  • Review the consent wording displayed on the form and the recorded action
  • See whether the submission was assessed as human, AI agent, bot or uncertain
  • Examine the record associated with an Evidence ID
  • Keep the evidence reference for audits and disputes

For lead buyers

Why AdPriva

Evidence built to be checked, not just stored.

AdPriva brings the recorded consent interaction, traffic assessment and integrity information together, so buyers can examine more than a consent flag.

Checkable integrity.

A signed evidence record allows changes to the record to be detected through an integrity check.

Consent and traffic. Together.

The recorded consent interaction and assessment of human or automated activity are linked under one Evidence ID.

Evidence without contact-field contents.

Designed to record consent choices and technical signals without reading names, email addresses or phone numbers entered into form fields.

What sellers and buyers ask first

Practical answers about evidence, integrations, privacy and working with AdPriva.

We already have consent logs. Why do we need AdPriva?

Your CRM records what your systems stored. AdPriva brings the consent wording displayed, the visitor’s action, timestamp and traffic assessment together in a signed evidence record. One Evidence ID provides a common reference, making it easier to examine what happened without piecing together separate logs and screenshots.

Why a CRM consent timestamp may not be enough →

What exactly can a lead buyer check?

An Evidence ID is designed to accompany each lead. The associated record contains the consent wording displayed, recorded actions, timestamps and traffic assessment. Buyers can examine the available evidence, subject to access permissions, and use supported integrity checks to detect changes to signed records. Production buyer verification and access arrangements are still being validated.

What buyers can examine →

Does AdPriva work with our existing forms and consent platform?

AdPriva is designed to work alongside your existing forms and consent-management platform, without replacing them. Its tag records permitted interactions while respecting the applicable consent controls. Integration depends on your setup, which we review with you during the pilot.

How does AdPriva distinguish humans, AI agents and bots?

AdPriva analyses technical interaction signals to assess whether a submission appears to come from a human, AI agent or bot, or whether the result is uncertain. The assessment is probabilistic, not proof of identity or a legal determination.

Can AdPriva prove that consent is legally valid?

No. AdPriva provides evidence of the recorded interaction, including the consent wording displayed, the action taken and when it occurred. An integrity check can help establish whether a signed record has changed, but it cannot establish that consent was legally valid. That determination remains with the responsible business and relevant authorities.

What happens when a consumer disputes consent?

The business can retrieve the evidence associated with the lead and review the consent wording, recorded action, timestamp and traffic assessment. This provides a common record for investigating the dispute rather than relying solely on CRM entries or screenshots. Matching the complaint to the consumer remains within the business’s own systems.

Does AdPriva collect personal information?

AdPriva is designed to capture consent interactions and technical signals without reading the contents of contact fields such as names, email addresses or phone numbers. Some technical information may still qualify as personal data. Our privacy documentation explains the applicable data handling and protections.

Privacy by design →

What does an AdPriva pilot involve?

We work with your team to understand your lead-generation workflow, consent platform and evidence requirements. Together, we agree on a suitable test, explore the evidence and verification experience, and assess integration options for your forms. Design partners receive direct access to our team and help shape the product. Pilot terms are agreed before testing.

Explore a pilot →

Shape it with us.

We’re inviting lead sellers and buyers in France to help shape how consent evidence is captured, shared and checked.

Or email us at hello@adpriva.com

Who it’s for
  • Lead sellers, publishers, marketplaces, brokers and insurers.
What you get
  • Pilot access, direct collaboration with our team and a voice in product development.
What happens next
  • We’ll discuss your workflow, identify a suitable test and agree on the next steps together.