Pangram verdict · v3.3
We believe that this text is a mix of AI and human-written content.
AI likelihood · overall
MixedArticle text · 605 words · 5 segments analyzed
Login With One Privacy, rebuilt for a strange new world. Passkey-first authentication. Universal Identity. Private by design. Private by design Only you hold the keys to your data. Sensitive data stays encrypted at rest. No readable Personal Identifiable Information (PII) is stored. 01 User device holds key 02 Encrypted data protected at rest 03 ONE cannot decrypt it Anonymous age verification Verify once. Prove your age anywhere. User-held encryption keys unlock reusable, one-tap age verification without exposing sensitive data. Verified once Age 18+ Yes Name — Birth date — Government ID — Proof of personhood Know there's a human behind the account. One-tap, anonymous confirmation that an account belongs to a verified person. Designed for AI platforms working to limit bot accounts and prevent automated model distillation, but useful anywhere an application needs frictionless proof of personhood. Verified once Verified person Yes Name — Birth date — Government ID — Passkey first Skip the password. Skip the inbox. Passwords can be guessed or phished. Email login flows are slow and vulnerable to phishing. Passkeys are fast and phishing-resistant. Password Phishable Email login Slow + phishable Passkey Fast + phishing-resistant FAQ Frequently asked questions. Why One for businesses? Some applications need to know that a user is old enough to use their product. Others want confirmation that there is a verified person behind an account. One returns the required identity proof in one tap, helping businesses meet their requirements without collecting personal data or putting users through a long and invasive verification flow. Why One for users?
Users verify their identity once, then reuse it across any application that uses One. No repeated ID uploads, and no new processor to trust with sensitive data. Applications receive only the proof a user approves, not their PII. Their data stays encrypted with a key only they hold, so even a breach of One would not expose readable identity data. Is One only for age verification? No. Age verification is simply the first privacy challenge that One was built around. The same infrastructure can confirm that an account belongs to a verified person without revealing who they are. At its core, One is a new primitive for persisting sensitive data under user-held encryption. It can power reusable identity presentation for KYC, private AI chat transcripts, and other applications that require persistence of sensitive data without surrendering custody to the platform.
How does One store personal data? One stores ciphertext: encrypted blobs created with a key held by the user. Never the underlying identity data. This includes government ID data, as well as the verified email associated with the account. What does my application receive?
Only the requested proof and an audit record. For example, that a user is a verified person or is at least 18 years of age, and when the check was completed. No name, birth date, address, selfie, or ID image. Why was One created? Applications increasingly need to verify aspects of their users’ identities, but traditional verification methods create a new privacy problem. Users upload IDs, selfies, and other PII to providers that can read and retain it, then repeat the process across multiple applications. That creates friction and spreads sensitive data across more databases and attack vectors. One was built around a new primitive to resolve that conflict: reusable identity data encrypted with keys only the user holds. Businesses get the proof they require, while users maintain their privacy and custody of their data.
Read more: The Internet Should Be More Like a Liquor Store How can I find out more? Email [email protected] to ask a question, discuss an integration, or request access.