The problem it solves
Every adult platform has minors trying to get in, and a checkbox that asks “are you 18?” protects no one. Guardian Shield replaces the checkbox with a gateway.
How it works
Registration passes through seven independent verification layers before a profile can exist. No single layer decides alone; signals accumulate across the gateway, and ambiguous cases escalate rather than slip through. The gateway sits in the write path — like everything in the Candor architecture, it cannot be skipped.
Verified behaviors
Every claim below maps to a dated behavioral proof against the live production gateway.
The zero-knowledge age-verification layer issues a single-use cryptographic proof of adulthood; the same proof cannot be replayed to verify a second account.
method: a real proof submitted against the live verification endpoint, then the identical proof submitted a second time under a different identity · observed: first submission verified as adult; the same proof submitted again was rejected as already used, enforced consistently across production · VERIFIED July 2, 2026
When the gateway's behavioral signals indicate a probable minor, the profile is soft-paused rather than immediately punished — the account holder is given the chance to prove adulthood via a zero-knowledge age proof before any redirect decision is made.
method: a test account carrying signals consistent with an underage user was evaluated by the live gateway · observed: the account was soft-paused pending age proof; a successful proof lifts the pause, a failed or missing proof redirects the account to Your Voice, the platform’s youth service · VERIFIED July 2, 2026
Honest limitations
- No age-assurance system is perfect; the gateway is built to escalate uncertainty to review rather than pretend certainty.
- Detailed layer mechanics are deliberately not published — describing the checks in full would be a manual for evading them.
Download the white paper (PDF)