THE INTERNET PASSPORT
Built for proof.
Engineered for privacy.™
Privacy-first identity infrastructure for businesses, platforms, developers, and institutions.
People stay in control through CAIRL's dedicated identity surface.
Built on infrastructure you trust
Verified claims at launch
Accepted document types
Average verification time
Biometric confidence threshold
SECURITY & COMPLIANCE
Enterprise-grade from day one
Privacy-first identity infrastructure
Every layer of CAIRL is built to protect user data — from encrypted storage to claims-only delivery. Security is not a feature. It is the architecture.
End-to-End Encryption
AES-256 encryption at rest with TLS 1.3 in transit. Documents remain encrypted in storage and in transit.
Privacy by Design
Claims-based delivery keeps partner responses focused on verified answers without sharing raw PII, selfies, or government documents.
Regulatory Compliance
HIPAA-ready infrastructure, COPPA compliant for age-gated flows, and GDPR-ready data handling across the pipeline.
Secure Authentication
OAuth 2.0 with PKCE enforcement for partner integrations, secretless public-client flows, and authorization-code-first routing.
SOC 2 Type I
ISO 27001
Security and Scalability
Pursuing SOC 2 Type I and ISO 27001 certifications. Built on AWS infrastructure with HIPAA-eligible services.
AUDIENCE MODEL
Three core markets. Four business paths.
At board level, CAIRL serves people, businesses, and institutions. On the infrastructure surface, business breaks into distinct motions so each page speaks to the right buyer, builder, or collaborator.
Partner is not a synonym for B2B customer. A dating app using CAIRL is a platform. A consulting firm, reseller, implementation shop, identity vendor, nonprofit, or infrastructure collaborator can be a partner.
People
Individuals, professionals, creators, and families who need to prove facts about themselves without handing over raw identity files.
Businesses
Companies that use, embed, integrate, or extend CAIRL across onboarding, trust, safety, compliance, and verification flows.
Institutions
Government, public-sector, and regulated organizations that need verifiable identity signals with strong privacy controls.
Business paths
Business users
Teams use CAIRL directly to run verification and compliance checks without storing raw IDs.
Platforms
Apps embed CAIRL inside signup, access, trust, safety, or age-gated user flows.
Developers
Builders integrate APIs, OAuth, hosted verification, webhooks, and claims delivery.
Partners / collaborators
Ecosystem allies help deliver, sell, implement, bundle, or improve CAIRL-adjacent services.
HOW IT WORKS
Verification that respects both sides
Verify once, share on your terms
One verification. You choose who receives it. Share with as many or as few connected platforms as you want — or none at all. Your credential travels with you, not ahead of you.
Claims, not copies
When you approve a connection, the platform gets a verified answer — age confirmed, identity checked. They never see your ID, your selfie, or your biometric data. You shared an answer, not a file.
You hold the keys
Every connection requires your explicit consent. Every permission is visible and revocable. CAIRL brokers the claim — you decide who receives it, and when to cut them off.
THE GOLDEN FLOW
What happens when a user verifies with your platform
One transaction. Both perspectives. The moment identity changes hands — without the documents ever leaving.
“[Platform] wants to verify your identity.”
- →You see exactly which claims they’re requesting
- →age_18_plus, identity_verified, freshness_current
- →No data has moved yet
User is redirected to CAIRL consent screen.
- →Your app triggered the OAuth flow
- →You specified the claims you need
- →You wait for the user’s decision
You approve or deny. That’s it.
- →You see every claim in the list
- →Nothing moves without your explicit yes
- →You can deny and walk away — no penalty
You receive only what the user approved.
- →Verified claims delivered via OAuth token
- →No document, no selfie, no biometric data
- →Just the answers: true/false
The connection appears in your dashboard.
- →See who has access and what they can check
- →Revoke any permission, any time
- →Your identity, your call
Claims available via API. You’re live.
- →Check freshness on every auth
- →Claims-based delivery — no raw PII shared with partners
- →Metered billing only for what you use
// What you receive after consent
{
"claims": {
"age_18_plus": true,
"identity_verified": true,
"freshness_current": true
},
"consent_granted_at": "2026-03-23T...",
"revocable": true
}PRODUCT SURFACE
One identity layer for every business path.
Business teams run checks directly. Platforms embed verification in their flows. Developers integrate claims delivery. Partners extend the ecosystem without being mislabeled as customers.
CAIRL:verify
Core verification pipeline
CAIRL/vault
Document and credential storage
CAIRL:connect
OAuth + claims delivery
PLATFORM CAPABILITIES
Built for depth, not just breadth
Forty verified claims at launch. Four verification depth levels. One privacy-first pipeline underneath.
Standard claims
6
age_18_plus, age_21_plus, identity_verified, unique_per_partner, document_active, freshness_current
Comparison claims
3
name_match, dob_match, address_match
Total claim catalog
40+
Standard, comparison, and extended claims across identity, age, document, and freshness domains
Document types
55+
Driver’s licenses, state IDs, US passports, passport cards, green cards, tribal IDs
Verification depth levels
4
From automated binary checks to human-supervised authentication
Freshness model
Event-driven
Triggered by high-sensitivity actions, not arbitrary cadences
PRICING
Sandbox in minutes. Live with $50.
Start metered, scale into commitments, and route governed deployments through sales. Personal identity plans stay on the identity surface.
FOR BUSINESSES
$0.05
Per verified attribute event
- Start with a $50 wallet minimum
- $0.50 enrollment event
- Direct verification workflows
FOR PLATFORMS
Contract
From $500/mo
- Embedded user verification
- OAuth and hosted verification
- Volume commitments as usage grows
FOR INSTITUTIONS
Custom
Governed rollout
- Security review support
- Procurement and DPA routing
- Implementation planning
PRIVACY PROMISE
Built on privacy. Not on your data.
- We verify — we don’t monetize.
- We share claims, not documents.
- You control what’s shared and with whom.
- We don't sell user data and don't use it to train third-party AI models.
Built for proof. Engineered for privacy.™
Businesses, platforms, developers, and institutions get verified claims. People keep control of the documents and disclosures behind those claims.
Looking for personal identity? Visit cairl-identity.com →