Proof of Age

Privacy Policy

Last updated: June 12, 2026

This Privacy Policy explains how the Proof of Age application (the "Service") collects, uses, and shares information. The Service is designed to verify that you meet an age requirement — using World ID zero-knowledge proofs today, and on-device passport NFC when available — without revealing your identity to partners.

For a technical description of our data boundaries, see the privacy model in the project documentation at docs/privacy-model.md.

Information We Process

  • World ID verification data such as proof data, nullifier hash, merkle root, and verification level sent to our server for validation.
  • Shareable proof link data including an age-range claim and a timestamp when you generate a proof link.
  • Technical data such as IP address, device and browser information, and log records generated by hosting or infrastructure providers.
  • Any information you choose to provide if you contact support.

How We Use Information

  • Verify age eligibility using World ID and enforce verification levels.
  • Generate and display shareable proof links you request.
  • Prevent fraud, abuse, and security incidents.
  • Operate, maintain, and improve the Service.
  • Respond to support inquiries.

Partner age-check sessions

When a website or app sends you to Proof of Age to verify your age, you see a consent screen before anything is shared. If you approve, the partner receives only whether you meet their requested age threshold — not your name, date of birth, passport details, email or wallet address. Proof tokens are short-lived (typically five minutes) and scoped to that partner and session.

Mobile app local history

The Proof of Age mobile wallet may store a local history of your recent checks on your device only: partner name, age requirement, verification method and status. It does not store proof tokens, names, dates of birth or document numbers. You can clear this history in the app. At most 50 entries are kept.

Retention

Server-side proof records and sessions are deleted automatically after expiry (see docs/compliance/data-retention.md). Audit logs are retained for a limited period for security purposes and contain opaque identifiers only — not personal identity data.

What We Do Not Do

  • We do not store your date of birth or government ID.
  • We do not give partners a stable identifier to track you across sessions.
  • We do not sell personal data.
  • We do not use verification data for advertising.

Sharing and Disclosure

We may share information in the following situations:

  • With World ID services to validate proofs as part of the verification process.
  • With infrastructure, hosting, and security providers who process data on our behalf under appropriate safeguards.
  • When required by law, legal process, or to protect the rights, safety, or security of users or the Service.
  • With relying parties only when you choose to share a proof link with them.

Data Retention

We do not persistently store World ID verification payloads. Proofs are processed to verify your eligibility and then discarded. Server logs and security records may be retained for a limited period as required for operations and compliance.

Security

We use reasonable technical and organizational measures to protect the Service, including encryption in transit and access controls. No method of transmission or storage is fully secure, so we cannot guarantee absolute security.

Children's Privacy

The Service is intended for users who are old enough to meet the applicable age requirements for the content they are trying to access. We do not knowingly collect personal information from children under the age of 13.

International Transfers

We may process information in the United States or other countries where our providers operate. Those locations may have data protection laws different from your jurisdiction.

Your Choices and Rights

Depending on where you live, you may have rights to access, delete, or restrict certain processing of your information. Because we do not maintain user accounts or store verification payloads, our ability to identify data about you may be limited.

Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date indicates when changes were made. Continued use of the Service after changes become effective constitutes acceptance of the revised policy.

Contact

If you have questions about this Privacy Policy, contact us at [email protected].