Skip to main content
AIR Kit lets publishers issue verified audience credentials and configure programs that check audience eligibility using ZK proofs. Raw source records remain with the issuer. Encrypted credential payloads may be stored in DStorage, while users control decryption and disclosure to partners.

The Problem

Post-cookie advertising has a trust problem that no contextual or cohort-based replacement fully solves: someone still has to hold the raw user data and claim the audience is what they say it is. Data brokers vouch for segments they assembled from sources that are increasingly unverifiable. Advertisers pay for “35-44, high income, tech-interested” and get whatever the intermediary decided that means.

What Changes With AIR Kit

  • Users hold their own verified attributes — Demographic and interest credentials are issued by your platform based on actual KYC and behaviour, not declared preferences. They’re cryptographically signed
  • Advertisers buy proof, not claims — The DSP or SSP verifies the credential at serve time. They get COMPLIANT / NON_COMPLIANT — a ZK proof that the user is 25–34, verified, consented, and located in AU. No raw data in the bid request
  • Consent records are portable — A credential can record consent collected by your CMP. Each publisher must still check that consent covers its purposes and recipients, and users control credential disclosure
  • Age-restricted serving without storing DOB — Prove isOver18 at ad-serve time for gambling, alcohol, or adult categories. No DOB database to create or secure; confirm the setup meets your regulatory obligations

How It Works

1

User completes profile or KYC on your platform

Your existing onboarding. The user verifies their age, confirms their country, or completes interest profiling. Nothing new for the user.
2

AIR Kit issues an audience credential

Your backend fires one API call. A credential encoding the user’s age range, verified country, IAB interest segments, and consent record lands in their AIR Account.
3

Ad server verifies at serve time

When the user visits a publisher page, the publisher’s ad server calls one SDK method. It receives a verified boolean signal: age verified, consent confirmed, segment matched.
4

DSP bids on verified signals

The bid request carries a verified audience flag. DSPs can bid higher on ZK-proven attributes than on unverified self-reported data. The audience segment is now worth more.

What the Ad Server Actually Receives

This example requests limited audience claims with user approval. The Verification Program determines the disclosed fields and whether a ZK proof is required.

What Compliance Will Ask

Does user consent need to be re-obtained? The credential records consent collected by your CMP. A new publisher or purpose may require additional consent; a portable credential does not extend the scope of the original permission. Separately, users approve credential disclosure during verification.Can users withdraw consent? Users can withdraw consent through your consent-management process and deny future disclosure requests. Revoke the consent credential so subsequent checks reject it once the updated status is available. Revocation does not retract data already disclosed; apply withdrawal to the relevant downstream processing as well.Does this replace our CMP? No. Your CMP continues to collect and record consent. AIR Kit converts that consent record into a portable, cryptographically verifiable credential.

Integration at a Glance

Compliance FAQ

Full GDPR, CCPA, and TCF answers.

Partner Economics

Revenue model, fee structure, and rewards.