Technology & compliance

Every consumer, accounted for.

Every consumer comes through our own system first. We check them and save the consent proof before anyone else sees them.

Our record first

Every consumer is saved before anyone else sees it

We keep the original record of every consumer, with the consent proof and the data behind it. Any partner can trace a consumer back to the page and moment they agreed.

  1. 1ValidateEvery field, on the page and on our server
  2. 2ScorePhone and data checks
  3. 3SuppressDuplicates, do-not-contact and opt-outs
  4. 4RecordConsumer, consent text and certificate saved first
  5. 5DeliverPing/post or direct post to partners, in real time
Consent

Proof on every consumer

What we store with every consumer

  • The exact consent wording shown. Each version is saved, never edited.
  • Timestamp, page, brand, IP and browser
  • A third-party consent certificate for the session
  • A raw copy of the submission that never changes

What it looks like to a partner

"consent": { "version": "auto-2026-10-v2", "text": "By clicking..., I agree that...", "brand": "TrustyQuote", "captured_at": "2026-10-01T14:22:09Z", "certificate": "https://cert.example/..." }

Example only. Field names follow your posting spec.

Privacy by design

Personal details only where they're needed

Ping without PII

Partners see a profile with no name, phone or birth date. Contact details come only with the post.

Nothing left in the browser

Our funnels don't store personal details on the consumer's device. Analytics tags don't get them either.

Locked-down tools

Our ops tools sit behind single sign-on. Every config change is logged with who made it and when.

Built to learn

We test what improves quality and conversion

Every funnel has a version number. We test question order, length, wording and where the funnel starts. We read results with confidence intervals and ship the winner. Each consumer record notes the version they saw.

Versioned funnels

Published versions are frozen. Results always match what the consumer saw.

No early calls

We don't call a test early on a small sample. We wait for the data.

Attribution that holds

First-party, server-side attribution helps keep source credit right across return visits and browser privacy changes.

See a sample consumer record.

We'll walk you through a sample record and show how it posts to your system.