v0.1 · Design partners wanted

Prove your age.
Keep your identity.

We don't track you — because the architecture won't allow it.

Zero persistent ID storage
No persistent identity data after issuance
Simple verifier API
Designed for minimal platform integration
Initial jurisdiction pilots
Focused U.S. state workflows with design partners
on-device
credential never leaves your wallet
unlinkable proofs
each presentation is
cryptographically distinct
no tracking trail
proofs can't be
correlated across sites
9:41 Wallet · ATVI
AnonTrustVI
Age credential
issuer: AnonTrustVI credential service
Status Verified
Birthdate •• / •• / ••••
Sharing with
example-platform.com
Proof: age ≥ 18
Only this proof leaves your device.
Current state

Core flow working today. Built with design partners in mind.

AnonTrustVI has a working wallet and proof path today. We're looking for design partners to harden the production issuer, verifier deployment model, and jurisdiction-specific artifacts.

Now MVP

Implemented proof path

Android wallet, encrypted local credential storage, BBS+/AnonCreds proof generation, and mock verifier, issuer, and redemption services.

Next production

Production hardening

Real ID and liveness validation, verifier deployment packaging, revocation design, reproducible builds, and third-party review before production rollout.

Open partners

Design partner pilots

Focused U.S. state age-verification workflows, signed verification artifacts, integration planning, and real-world feedback from platforms.

How it works

Three steps. No surveillance.

The process is simple, three pieces: get a credential, keep it with you, share only what the site needs to see.

01 / 03 one-time

Validate your ID once

A user completes ID and liveness checks during issuance. After eligibility is verified, the wallet receives a signed credential for later age proofs.

02 / 03 device-only

Your credential lives on your device

The credential stays in your wallet. Sites receive a proof — not your ID, birthdate, or any persistent identifier.

03 / 03 zero-knowledge

Prove only what's needed

Share an age proof with supported sites — not your ID document. In the default age-check flow, your birthdate is not disclosed; the wallet shows any required metadata before approval.

The privacy difference

This isn't just a privacy policy.
It's the architecture.

Structural unlinkability. Each presentation generates a fresh cryptographic proof — mathematically distinct from every other. Sites can't correlate your visits. Neither can we.

The same credential can be presented to hundreds of sites without those sites being able to determine it's the same user.

No issuer call-home. No correlation. Not by choice. By design.

Zero-knowledge proof
age ≥ 18, nothing else
No identity logs
proofs do not reveal who you are
No issuer call-home
the verifier checks the proof; your credential stays on device
Structurally unlinkable
BBS+ generates a unique proof per presentation — unlinkability is in the math
system topology verified local
Validator (ATVI) issue-once with ATVI
issues your credential. walks away.
offline after issuance
↓ one-time, at onboarding
Your wallet (device) on your phone
generates a zero-knowledge proof locally.
holds credential
↓ proof only — no identifying data
Verifier verify.platform.com
checks proof. never calls home.
customer-controlled verifier
The verifier checks a cryptographic proof. No raw ID, birthdate, or reusable credential is transmitted at presentation time. Self-hosted or managed — the proof model is the same.
For platforms

Compliance without
becoming a data custodian.

Initial build plan is U.S. state and federal age-verification requirements, with legal validation still ahead. We're building to meet these requirements without platforms ever holding the identity data they'd rather not touch.

01
Verifier you control
Self-host or use a managed deployment. Either way, the verifier checks proofs — not raw ID documents. You get a signed compliance artifact, not an identity database.
02
Minimal API for your backend
POST to register a verification. GET the signed result.
03
Signed compliance artifact
A JWS record of what was verified, when, and the result. No identity attributes retained.
Integration

Two endpoints. One container.

Reference Docker deployment. No ATVI egress at verify time.

// request a verification session
POST /verifications
{
"required_claim": "age_ge_18",
"jurisdiction": "US-PILOT",
"callback": "https://you.com/cb"
}
// retrieve signed result
GET /verifications/:id
 
→ 200 OK
{
"verified": true,
"claim": "age_ge_18",
"jws": "eyJhbGciOi..."
}
# self-hosted verifier
services:
atvi-verifier:
image: "atvi-verifier:preview"
ports: ["8080:8080"]
env: ATVI_JURISDICTION="US-PILOT"
Standards & trust signals

Built on what you can audit, not what we can claim.

Every cryptographic assurance here is verifiable by a third party. No proprietary trust-us primitives — just open standards, with a third-party audit planned before production.

spec
W3C Verifiable Credentials
Standards-based credential format
crypto
BBS+ selective disclosure
Prove one claim. Reveal nothing else.
crypto
AnonCreds v2
Pairing-based, privacy-preserving
review
Open cryptographic core
Audit scoped for pre-production
zkp
Zero-knowledge age proof
Birthdate never leaves the device
crypto
Per-presentation unlinkability
Each BBS+ proof is unique — presentations across sites cannot be correlated
compliance
US state AV law coverage
pursuing design partners for pilot coverage
For users

Join the wallet waitlist.

Your age is yours. So is your identity. Join the wallet waitlist and be first when the wallet ships for your platform.

no spam · unsubscribe anytime · we never share
For platforms Design partners open

Become a design partner.

Work with us on an early verifier integration for privacy-preserving age checks. Design partners get direct engineering support, signed verification artifacts, jurisdiction-focused implementation planning, and preferred pricing.