What is CAIRL?
CAIRL is identity verification infrastructure built on a different premise than legacy identity verification platforms.
CAIRL is identity verification infrastructure built on a different premise than legacy IDV platforms: the answer crosses the boundary, not the file. Users verify their identity once through CAIRL’s multi-gate verification pipeline — document validation, face matching, liveness detection, and fraud checks — and receive a credential they control. When a platform needs to confirm who they are or how old they are, the user authorizes a verified claim through an OAuth consent boundary. The platform receives confirmation. The personal data that produced it stays on CAIRL’s side of the line. CAIRL delivers digital identity users control and verified claims platforms trust.The Internet Passport
An identity layer that travels with you across the internet — not as a surveillance mechanism, but as a genuine passport. A credential that proves what needs to be proved, shares only what the moment requires, and leaves nothing behind on the other side of the boundary.The phrase "Internet Passport" describes a credential that travels with the person it belongs to. It proves what needs to be proved, it shares only what the moment requires, and it keeps the underlying identity data behind the consent boundary.
How the model works
CAIRL is identity verification infrastructure built on a different architectural premise: the answer crosses the boundary, not the file. Instead of extracting personal data and delivering it to the requesting platform, CAIRL issues a verified claim. The platform receives what it needs to know — age confirmed, identity verified, document authentic — without receiving the underlying data.That means a platform can ask a narrow question like:
- Is this user over 18?
- Has this identity been verified?
- Is the document authentic?
CAIRL returns the answer the platform needs. It does not have to deliver the full document, the full identity record, or an unnecessary dump of personal data.
Verified claims, not raw data
The answer crosses the boundary, not the file.That architecture changes the relationship between the person being verified and the platform that needs the result. Users keep control of identity. Platforms still receive a verification answer they can trust.
What users and platforms each get
Users
People who verify their identity through CAIRL. They hold the credential, authorize sharing, and are the reason the privacy architecture exists.Platforms
Businesses that integrate CAIRL to receive verified claims. They receive outcomes and attestations — not document fields, images, or identity dumps.