About CAGE
Age verification should not create a new identity database.
CAGE exists because the internet needs stronger age gates, but users should not have to upload government IDs to every website that asks.
The Problem
The current model is invasive for users and liability-heavy for platforms.
Every site that asks for a government ID becomes another place where sensitive documents can be retained, breached, mishandled, or reused. That is bad privacy design and bad operational design.
Verify the minimum
CAGE is built to answer a narrow question: does this user meet an age threshold? The system does not need a full identity profile to do that.
Keep partners out of ID storage
Partner platforms receive signed age claims, not documents, selfies, names, or dates of birth.
Prevent cross-site correlation
Per-partner anonymous subjects make CAGE useful without creating a shared tracking identifier.
The Idea
Verify once. Use everywhere. Share almost nothing.
CAGE uses a trusted third party, Veriff, to process the document verification step. CAGE stores only the result: an age floor and an expiration window.
When a partner site needs to confirm age, CAGE issues a signed token confirming that result through a standard OAuth/OIDC flow. The partner never sees the document and cannot correlate a user across other CAGE partners.
The long-term goal is simple: make responsible age gates feel like modern infrastructure, not a repeated personal-data handoff.
Built In The Open
Interested in partnering or contributing?
CAGE is an early-stage project moving quickly. Partner teams, privacy-minded builders, and contributors can reach us through the access flow or inspect the open-source repository.