What You Can Build
- Verified audience segments — Issue demographic and interest credentials on profile completion or KYC; advertisers target against cryptographic proof, not self-reported fields
- Consent-portable targeting — User consents once; that consent credential is verifiable by any publisher in the ecosystem without a consent management platform re-prompt
- Age-verified ad targeting — Gate alcohol, gambling, and adult ad categories behind a ZK age proof — no DOB ever transmitted to the ad server
- Cross-publisher identity — A user’s verified attributes follow them across publisher sites without third-party cookies or device fingerprinting
- Bot and fraud resistance — Issue a “verified human” credential after KYC or passkey authentication; DSPs and SSPs can filter on-credential instead of on-signal
- Brand safety compliance — Verify user age and location at serve time without storing the data, satisfying COPPA, GDPR Article 8, and regional ad regulations
Architecture
Recommended Schemas
Verified Audience Segment
Consent Credential
Implementation
Step 1 — Issue audience credentials on profile completion
Step 2 — Issue consent credential when user accepts CMP
Step 3 — Verify audience attributes at ad-serve time
Step 4 — Cross-publisher audience verification (partner publisher)
Partner publishers integrate AIR Kit as a verifier. One SDK call replaces the cookie sync / data clean room round-trip.Key Patterns
Privacy Guarantee
No raw user data — no DOB, no email, no IP, no browsing history — is transmitted during ad verification. The ZK proof flow means the verifier (DSP, SSP, partner publisher) receives only boolean results.Regulatory Alignment
- GDPR Article 8 — Age verification without storing DOB satisfies child protection obligations
- CCPA / CPRA — Consent credential provides an auditable, user-owned record of opt-in; revocation is instant and on-chain
- COPPA — ZK age gate (isOver18 === false blocks serve) without collecting minor data
- TCF 2.2 — Consent credentials can encode TCF purpose IDs; verifiers check compliance without a centralised CMP dependency
Examples
The repo uses a venue check-in and merch store; the same event-triggered pattern applies to ad engagement (publisher issues, ad server verifies). Adapt via schema and branding — see the README’s “Adapting to Your Vertical” section.Fan Attendance — Issuer
Venue check-in app: issues attendance credential when the fan scans in at the event.
Fan Attendance — Verifier
Merch store app: verifies attendance and unlocks rewards (e.g. discount, exclusive offer).
Next Steps
Direct Issuance — Concepts
Server-side issuance without user presence.
Direct Issuance — API
Full endpoint reference with error codes.
AIR for Fintech & Payments
KYC portability and age verification patterns.
Schema Use Cases
More credential schema examples.