Privacy Policy
Last updated: November 14, 2026
1Auth is built so that we cannot read what you store. This policy explains the limited data we do hold, why we hold it, and the choices you have.
The short version. Your vault is end-to-end encrypted with keys derived from your master password on your own devices. We store ciphertext we cannot open. We never receive your master password, your vault keys, or anything they unlock. A database dump, backup, or subpoena would yield unreadable blobs, account email addresses, team membership, sizes, and timestamps — nothing more. See our security overview for the technical detail.
1. Who we are
1Auth ("1Auth", "we", "us") provides a password manager and single sign-on service at 1auth.us and through our browser extension and desktop and mobile apps. 1Auth is based in Florida, United States, and acts as the controller of the limited personal data described below. For privacy questions, contact us at [email protected].
Where your organization provides 1Auth to you through a team or business account, your organization is the controller of your team membership and administrative data, and we process that data on its behalf.
2. Data we collect
We collect only what we need to run the service:
Account data
- Email address. Used to identify your account, derive your encryption keys on your device, and send essential service messages.
- Authentication proof. Your master password never reaches us. Your device derives a login proof from it, and we store only a slow one-way hash of that proof so you can sign in. We cannot recover your password from it.
- Multi-factor settings. If you enable an authenticator app, recovery codes, or passkeys (WebAuthn), we store the public credentials and verifiers needed to check them — never a second secret that could open your vault.
Your encrypted vault
- Encrypted items. Your logins, passkeys, verification-code seeds, and notes are encrypted on your device and stored with us as opaque ciphertext. We also hold the public halves of your encryption identity and a record of which vaults you may open.
- Website icons. To show site icons in your vault, we keep a cache of public website icons by site. This cache is not linked to any account or to who requested which icon.
Billing data
- Subscription details. If you buy a paid plan, our payment processor (Stripe) handles your card details directly; we receive your plan, status, and a customer reference, not your full card number.
Operational data
- Service logs. Standard logs such as IP address, timestamps, device/client type, and request metadata, kept to operate the service, keep it secure, and diagnose problems.
- Error reports. When something fails, we record a reference and technical context to fix it. These reports are scrubbed of secrets and do not include your vault contents.
- Support messages. If you email us, we keep your message and our reply.
3. What we cannot see
Because 1Auth is zero-knowledge, there are things we structurally cannot access, no matter who asks:
- Your master password.
- Your vault key or the private half of your encryption identity — these are derived on your device and never leave it.
- The contents of your vault: the usernames, passwords, passkeys, codes, and notes inside your encrypted items.
Decryption happens only on your devices — in the browser extension, the Apple and Windows apps, and the web vault. We cannot decrypt your data for you, for law enforcement, or for anyone else. If you lose your master password and your recovery options, your vault cannot be recovered.
4. How we use data
We use the data above to:
- Provide and sync your vault across your devices;
- Authenticate you and protect your account with MFA and passkeys;
- Operate team accounts, roles, invitations, and single sign-on;
- Process payments and manage subscriptions;
- Keep the service secure, prevent abuse, and diagnose and fix problems;
- Send essential service and security notices; and
- Meet our legal obligations.
We do not sell your personal data, and we do not use it for advertising or behavioral profiling.
5. Legal bases
Where the GDPR or similar laws apply, we rely on: performance of a contract (to provide the service you signed up for), legitimate interests (to secure and improve the service), consent (where we ask for it, such as optional communications), and legal obligation (to comply with applicable law).
7. Teams & single sign-on
If you use 1Auth through an organization, your administrators can see and manage your membership, role, and status in the company console, and can invite or remove you. Because vault keys never reach our servers, administrators cannot read your personal vault; team vault access is managed by sharing keys between members' devices, and removals are enforced without us ever seeing the keys.
For single sign-on, we store your organization's SSO configuration (SAML or OIDC settings) and verified domains so we can authenticate your team. Sign-in events may be logged for security.
9. Retention
We keep your account and encrypted vault data for as long as your account is active. When you delete your account, we delete your account record and encrypted vault data; backups containing them are purged on our normal backup rotation. We keep limited records longer where we must for legal, tax, security, or fraud-prevention reasons. Logs are retained for a limited period and then deleted or aggregated.
10. Your rights
Depending on where you live, you may have the right to access, correct, delete, or export your personal data, to object to or restrict certain processing, and to withdraw consent. Residents of California (CCPA/CPRA), the EEA/UK (GDPR), and similar jurisdictions have these rights. We do not sell or "share" personal information for cross-context behavioral advertising, and we do not discriminate against you for exercising your rights.
You can access and export much of your vault directly from the apps. To make any other request, email [email protected]; we will verify your request and respond within the time required by law. Note that we cannot produce the contents of your encrypted vault, because we cannot decrypt it.
11. Security
Encryption keys are derived on your device from your master password (PBKDF2-SHA256, 600,000 rounds), items are sealed with AES-256-GCM, and vault keys are shared between your devices using ECDH over P-256 — all without the keys ever reaching us. We hash your login proof before storage, serve the web vault under a strict Content-Security-Policy, and ship the extension and native apps separately from the server. No system is perfectly secure, but our design limits what any breach of our servers could expose. For the full model, see how our encryption works.
12. International transfers
1Auth operates from the United States, and your data is processed there and in the regions where our infrastructure providers operate. Where we transfer data internationally, we rely on appropriate safeguards (such as standard contractual clauses) where required by law.
13. Children
1Auth is not directed to children under 13 (or the minimum age in your jurisdiction), and we do not knowingly collect their personal data. If you believe a child has provided us data, contact us and we will delete it.
14. Changes to this policy
We may update this policy from time to time. When we make material changes, we will update the date above and, where appropriate, notify you. Your continued use of 1Auth after an update means you accept the revised policy.
15. Contact
Questions about this policy or your data? Email [email protected]. For terms and legal notices, see our Terms of Service or write to [email protected].
This Privacy Policy is provided for general information and should be reviewed by qualified counsel before you rely on it for your jurisdiction.