Most people know that storing passwords in a plain text file is a bad idea. Fewer people know that their two-factor authentication app may be doing something similar: uploading the cryptographic seeds behind every 2FA code they generate — without end-to-end encryption — to a cloud account they share with an email service, an ad platform, and years of other personal data.
Two-factor authentication is supposed to add a layer of security that a password alone can’t provide. Understanding how the most popular 2FA apps handle cloud backup is essential to knowing whether that layer is as strong as you assume.
What a 2FA “Seed” Actually Is
When you set up two-factor authentication for an account — say, your email, your bank, or a social media service — the service generates a cryptographic secret called a TOTP seed (Time-based One-Time Password seed). Your authenticator app stores this seed. Every 30 seconds, the app performs a calculation using the seed and the current time, producing the six-digit code you enter.
The security model depends on the seed remaining secret. If someone obtains your password AND your TOTP seed, they can generate valid codes for your account indefinitely — without your phone, without your authenticator app, and without any notification to you.
Backup mechanisms that upload TOTP seeds to cloud storage carry a specific risk: if the cloud account is compromised, the attacker gets not just the backup, but the ability to generate 2FA codes for every account that seed covers.
The Google Authenticator Situation
Google Authenticator added cloud sync in 2023, and a Play Store update in July 2026 made cloud sync a core feature of the app. The appeal is obvious: if you lose your phone, your 2FA codes are recoverable from your Google account rather than permanently lost.
The privacy concern is equally obvious to those who looked closely: Google Authenticator’s cloud sync is not end-to-end encrypted.
Security researchers at Mysk flagged this when sync first launched. The uploaded TOTP seeds are tied to your Google account, but they are not encrypted in a way that prevents Google — or anyone who compromises your Google account — from reading them. Google acknowledged at the time that end-to-end encryption was on the roadmap but not yet implemented.
What this means practically: your Google account is now also the master key to every 2FA code in your Google Authenticator. A phishing attack, credential stuffing, or breach that compromises your Google password — assuming 2FA protects it, unless it’s the account whose 2FA codes are in the app — could expose all your other TOTP seeds at once.
Google’s July 2026 update added a Privacy Screen feature (biometric or PIN lock on top of account protection), which protects against physical access to the device. It does not change the encryption status of the cloud backup.
How Other Major Authenticator Apps Compare
Authy (Twilio)
Authy offers encrypted cloud backup, but the encryption uses a backup password you set. If you forget the backup password, the backup is unrecoverable — it is not tied to your Twilio/Authy account credentials. The seeds are encrypted before they leave your device.
The limitation: Authy is a closed-source product owned by Twilio, a corporate communications company. You are trusting that the encryption is implemented as described without the ability to verify the code.
A concern: if your backup password is weak or reused, the backup encryption may not be as protective as it appears.
Microsoft Authenticator
Microsoft Authenticator backs up to iCloud (on iOS) or your Microsoft account (on Android). The encryption status of this backup follows the backing service — iCloud backup is not end-to-end encrypted by default unless you have Advanced Data Protection enabled on your Apple account. If you have iCloud Advanced Data Protection on, the Authenticator backup benefits from it.
Ente Auth
Ente Auth is an open-source authenticator app that uses fully end-to-end encrypted cloud backup — the same encryption model as Ente Photos. Because it is open-source, the encryption claims can be independently audited. It stores data on Ente’s servers, which are independently verifiable.
For users who want cloud backup with genuine end-to-end encryption, Ente Auth is the most auditable option among widely-used apps.
Aegis (Android only)
Aegis is an open-source authenticator for Android that stores everything locally. There is no cloud sync at all. Backups are encrypted files you can store wherever you choose. This eliminates the cloud account compromise vector entirely, at the cost of needing to manage backups yourself.
2FAS
2FAS offers cloud backup with synchronization through Google Drive or iCloud. The encryption model depends on the backing service. The app is open-source and has been audited.
The Specific Risk: Account Compromise Cascade
The threat model worth understanding isn’t just “will someone hack Google and get my seeds.” It is:
- Your Google password is phished, guessed from a data breach, or obtained through credential stuffing
- The attacker logs into your Google account
- They access the synced Google Authenticator seeds from that account
- They can now generate valid 2FA codes for every account whose TOTP seed is in your Google Authenticator
If your Google account itself is protected by Google Authenticator, there’s an obvious circularity problem: either you use a different 2FA method for your Google account, or compromising your Google account by other means immediately unlocks the seeds.
This is not a hypothetical cascade. Credential stuffing — using leaked passwords from other breaches to log into Google accounts — is one of the most common attack vectors. The combination of an exposed password from an old data breach and a Google account with unencrypted 2FA backups is a meaningful vulnerability.
Storing 2FA Recovery Information Privately
Regardless of which authenticator app you use, there’s a category of related files you should be storing securely: recovery codes.
When you set up 2FA, most services generate backup codes — typically 8-10 alphanumeric strings — for use if your authenticator app is unavailable. These are just as powerful as TOTP access. If they’re sitting in a screenshot in your camera roll, they’re being backed up to your cloud photo library (which, as covered elsewhere on this blog, may be subject to AI indexing and content analysis).
A more private approach: store recovery codes in a dedicated, encrypted notes app that isn’t synced to your primary email provider’s cloud. Or store them in private file storage under a name that doesn’t signal their contents.
daftei works well for this use case. Files stored in daftei are encrypted in transit with TLS 1.3 and at rest with AES-256. The service doesn’t analyze file contents, doesn’t show ads, and doesn’t use uploaded content to train AI models. A file of backup codes stored there is encrypted at rest and not subject to AI content analysis — which is more than can be said for a screenshot in a Google Photos library.
What to Do If You’re Currently Using Google Authenticator
You don’t necessarily need to switch apps. The practical response depends on your threat model:
If you’re using Google Authenticator with cloud sync enabled and your Google account is a high-value target (financial services, primary email, sensitive work accounts backed up there), consider:
- Enabling 2FA on your Google account using a method other than Google Authenticator — a hardware key (YubiKey) or a separate authenticator app adds a layer that breaks the circular dependency.
- Migrating your highest-sensitivity accounts to an app with end-to-end encrypted backup (Ente Auth) or a local-only backup (Aegis).
- Ensuring your Google password is unique and not used anywhere else.
If your Google account is less sensitive, the cloud sync risk is lower but still worth knowing about.
If you’re setting up 2FA for the first time, Ente Auth (open-source, E2EE backup) or Aegis (open-source, local-only) are defensible choices that don’t carry the non-E2EE cloud sync concern.
The Broader Pattern
Two-factor authentication was designed to add a second independent factor to account security — something attackers couldn’t get from your password alone. Cloud backup of 2FA seeds, without end-to-end encryption, partially collapses that independence: the second factor now lives in the same cloud account ecosystem as the rest of your digital life.
This doesn’t mean 2FA with cloud-synced apps is useless — it’s still vastly better than no 2FA. But understanding the actual architecture of your security setup lets you make informed decisions about where the gaps are, rather than assuming the second factor is as independent as the original design intended.
The key questions to ask of any authenticator app: Does it offer cloud backup? If yes, is it end-to-end encrypted? If yes, can that claim be independently verified through open-source code or a public audit? The answers tell you the real security story of your second factor.