Proving age without showing your ID

Why new safety mandates make zero-knowledge proofs the new standard for youth regulatory compliance.

Share
Proving age without showing your ID
An abstract visualization of zero-knowledge age verification, where identity flows through a dynamic chrome threshold to yield pristine cryptographic proof without retaining any personal data.

⚡ The Signal

As Meta's massive child safety settlement makes clear, consumer apps are facing unprecedented pressure to keep minors safe. At the same time, a global movement to restrict social media access for children is accelerating rapidly across state legislatures and international governing bodies.

App developers are trapped in a regulatory vise: fail to verify user ages and face crushing legal liability, or force users to upload government IDs and risk catastrophic privacy breaches.

🚧 The Problem

Traditional age verification is fundamentally flawed. Standard approaches rely on uploading driver's licenses, manual document reviews, or invasive facial scanning. These methods destroy user onboarding conversion rates and turn consumer tech startups into targets for identity theft by requiring them to hold vast reservoirs of personally identifiable information (PII).

For engineering teams, building custom compliance flows for ever-changing state mandates—like COPPA 2.0 or California's AADC—requires months of custom development and ongoing legal oversight. Developers need a way to prove a user's age without ever handling or storing the underlying identity documents.

🚀 The Solution

Meet Aevum: a drop-in developer SDK for zero-knowledge age assurance and parental consent.

Aevum enables mobile and web applications to verify age eligibility and handle parental consent flows in under 10 lines of code. By leveraging zero-knowledge proofs directly on the user's device, Aevum generates cryptographic proof that a user meets specific age thresholds (e.g., over 13 or over 18) without raw identity data ever leaving the client. Developers satisfy regulatory mandates instantly while eliminating PII liability entirely.

🎧 Audio Edition

Listen to Ada and Charles discuss today's business idea.

If you're reading this in your email, you may need to open the post in a browser to see the audio player.

💰 The Business Case

Revenue Model

Aevum monetizes through a multi-tiered infrastructure model:

  • Usage-Based Verification Pricing: $0.03 to $0.10 per successful zero-knowledge proof verification, scaling with application volume.
  • Enterprise Platform Subscription: $499/month for dedicated Hardware Security Module key management, custom ID issuer attestations, priority performance SLAs, and automated audit logging.
  • Parental Token Routing Fees: $0.05 per dispatched SMS or email parental consent request processed through the zero-knowledge approval pipeline.

Go-To-Market

  • Interactive Compliance Sandbox: A free developer playground that audits an application's existing onboarding flow against COPPA, KOSA, and state laws, allowing engineers to test local WebAssembly proof generation directly in their browser.
  • Programmatic Regulatory SEO: High-intent integration guides targeted at specific legislation and tech stacks (e.g., "Utah SB 152 Compliance for React Native" or "COPPA Middleware for Supabase").
  • Open-Source Middleware Integration: Submitting turn-key middleware PRs to popular indie starter kits, including Create-T3-App, Expo templates, and standard authentication libraries.

⚔️ The Moat

While incumbents like Persona, Yoti, or Veriff focus on traditional identity scanning—retaining data risk—and Web3 tools like Privado ID lack developer-friendly tooling, Aevum builds a moat around workflow lock-in and reusable network identity.

Once integrated into an app's primary authentication path, replacing Aevum requires re-architecting core onboarding and re-undergoing expensive compliance audits. Furthermore, proofs generated across the Aevum network enable cross-app identity reuse: users verify their age once and enjoy frictionless, privacy-first onboarding across the entire partner ecosystem.

⏳ Why Now

The demand for age verification is no longer optional. As industry observers dissect the broader impact of Meta's legal resolutions, existing verification solutions are proving inefficient and unpopular.

Simultaneously, recent advancements in client-side cryptography allow modern smartphones to execute complex zero-knowledge circuits in milliseconds using standard WebAssembly runtimes. Cryptographic capability and regulatory necessity have finally converged, making privacy-centric compliance the only viable path forward.

🛠️ Builder's Corner

To build an MVP for local age proofs, reach for a lightweight client library combining Circom and SnarkJS compiled to WebAssembly inside a React Native or Expo app shell. This handles local mathematical proof generation on the user's device.

On the backend, deploy a stateless Rust verification microservice on AWS Lambda to validate proof signatures against modern digital credential issuers like mobile driver's licenses. Connect the platform with Supabase for API key management and compliance audit logs, Clerk for developer portal authentication, and Stripe to handle meter-based usage billing.


Legal Disclaimer: GammaVibe is provided for inspiration only. The ideas and names suggested have not been vetted for viability, legality, or intellectual property infringement (including patents and trademarks). This is not financial or legal advice. Always perform your own due diligence and clearance searches before executing on any concept.