Privacy

How 2Fa Live Protects Your Privacy: Encrypted in Your Browser, Not on Our Servers

What 'privacy-first' means for an authenticator in practice: where your secrets live, how they are encrypted, what we do and do not collect, and the limits of the model.

2Fa Live is built so your 2FA secrets stay in your browser. They are encrypted there with a key derived from a passphrase you choose, they are never sent to a server, and we keep no copy. That is what we mean by privacy-first. This post explains what that does and does not guarantee, so you can decide for yourself whether it fits how you use your accounts.

This post replaces an earlier version that described the site as having no analytics of any kind. That wording was too absolute, so we explain the current rules precisely below.

What stays on your device

Your authenticator holds secret keys. Anyone with a key can generate your codes, so those keys are the sensitive part. In 2Fa Live:

  • Account secrets are stored in your browser, not in a database on a server.
  • Before storing, they are encrypted with AES-GCM-256, using a key derived from your passphrase and a fresh random value on each save.
  • The derived key is held in memory only, and the vault auto-locks when idle or when the tab is hidden.
  • Backup files are encrypted too, and checked for a valid structure before restore.

Because the server never receives your secrets, a breach of our servers would not expose them. There is nothing of that kind to take.

Why we chose this design

Many cloud authenticators keep your secrets on their servers so they can sync them. That is convenient, but it creates a single place holding keys for millions of accounts. The OWASP Multifactor Authentication Cheat Sheet advises that seeds be stored encrypted and, ideally, in dedicated key-management infrastructure on the service side, which shows how seriously a central store of secrets has to be treated.

We took a different route. If we never hold the keys, we cannot lose them, leak them or be compelled to hand them over. The trade-off is that you own the responsibility for your passphrase and backups.

What we do and do not collect

Being precise matters here.

  • Secrets and codes: not collected. They are processed in your browser.
  • Account issuer names and labels: not sent to analytics.
  • Analytics: opt-in only. A consent choice controls it, and no analytics script loads on the authenticator page.
  • Advertising on the tool area: none in the secret-entry flow.
  • Contact form messages: if you write to us, we receive what you send, the same as any email.

We replaced the older claim of "no tracking" because a site that uses any analytics should say so plainly. The current approach is consent-based and keeps analytics away from the screen where secrets are handled.

The quick link we removed

An older shortcut let you put a secret in the web address so you could open a code with one click. URLs get copied into server logs, browser history and the referrer information sent to other sites, so a secret there can leak in ways you cannot see. We removed it. If you want to move accounts, use an encrypted backup instead.

The honest limits

No design is magic. Here is where the model stops protecting you.

  1. Your device is the root of trust. Malware on your computer, or a malicious browser extension with access to page content, can read what you can read. Keep your system updated and extensions few.
  2. A shared or unlocked computer is risky. Auto-lock helps, but you should lock the vault, and the computer, when you step away.
  3. You must trust the code you are served. A web app is delivered each time you load it. The protections we use, such as a strict Content-Security-Policy and no third-party CDN scripts, reduce the chance of tampering, but a website is not the same as an app you installed and audited. If you need the highest assurance for a critical account, consider a hardware security key or passkey instead. See is it safe to enter your 2FA secret into a website?
  4. Forgetting your passphrase is final. No server copy means no reset. Use a passphrase you can recover, and keep an encrypted backup.
  5. Clearing browser data deletes the vault. Site data cleared in your browser removes the encrypted store along with it, so export a backup.

How to check the claims yourself

You do not have to take our word for any of this. Open your browser's developer tools, switch to the Network tab and add an account or generate a code. You should see no request that carries your secret. You can also look at the page's response headers for the Content-Security-Policy. The is it safe page walks through these checks step by step.

What this means for you

If you want a free authenticator that works in any modern browser and keeps your secrets off our servers, this design fits. If you want automatic sync across devices through a cloud account, a cloud authenticator suits that need better. Either way, enable 2FA, and for your most important accounts consider a security key or passkey as well.

You can see the current feature set in what's new in 2Fa Live, or try the TOTP generator directly.

Key takeaways

  • Secrets are encrypted in your browser and never sent to a server.
  • We cannot read your secrets or reset your passphrase, by design.
  • Analytics are opt-in and absent from the authenticator page.
  • The remaining risks are your own device, your passphrase and trusting a web app's delivered code.

Tags: privacy, encryption, local storage, aes-gcm, web authenticator

OzoneApps team

The OzoneApps team builds and maintains 2Fa Live.

Frequently asked questions

Where does 2Fa Live store my 2FA secrets?

In your own browser, encrypted with a key derived from a passphrase you choose. They are not sent to a server and we do not hold a copy.

Can OzoneApps see my codes or reset my passphrase?

No. Because secrets are encrypted in your browser and never leave it, we cannot read them and there is no server-side passphrase reset. That is a consequence of the design, so keep your passphrase and backup safe.

Does 2Fa Live use analytics?

Analytics are opt-in through a consent choice, and no analytics script loads on the authenticator page. Account issuer names are not sent to analytics.

What are the limits of this model?

Your secrets are only as safe as the device and browser you use. Malware, a hostile browser extension or an unlocked shared computer can still expose them. A web app is also delivered to you each time you load it, so you rely on the site serving unmodified code.