🔗 Wire to Live Sync
Paste the userId from Privacy Cockpit Scene 1 to close the loop
Paste the userId shown in the extension after Sync — this wires Scene 1 token directly to the Bouncer evaluation
🎬 Demo Scenarios
Pre-built flows for investor recording
Patent Pending #9128 · Privacy Governance Engine (Component #2) · All decisions logged to tamper-evident ledger
Try Any Request
Enter any combination — the Bouncer evaluates against the live consent ledger in real time
💡 How Advertiser IDs Work
An Advertiser ID is issued by Adworth when an advertiser registers on the platform — the same model as Stripe issuing merchant IDs. It uniquely identifies who is requesting access to a user's data.
When a user grants consent, their token names the specific advertiser they're authorizing. The Bouncer enforces that match cryptographically — no other advertiser can use that token.
Try any advertiser ID below. If a matching consent token exists for that user + advertiser + scope combination, the Bouncer GRANTs. If not, it BLOCKs. Every decision is logged to the tamper-evident ledger.
Issued by Adworth on registration — like a Stripe merchant ID. Must match the advertiserId named in the user's consent token exactly.
The user whose consent ledger is being checked. Paste the live userId from the Wire to Live Sync field above to evaluate the real token.
The category of data access being requested. Must match the scope named in the consent token — scope mismatches are blocked automatically.
What will happen: The Bouncer runs 6 checks against the live ledger in real time. GRANTED means a valid consent token was found for this exact user + advertiser + scope. BLOCKED means no token, wrong scope, revoked, expired, or Minor Shield active. Every evaluation is logged permanently.
🛡️
Connect with your API key and run a scenario.
The Bouncer will evaluate consent in real time.