Aegis Authenticator vs Google Authenticator Comparison
Don't see the tool you use?
| Feature | ||
|---|---|---|
| Overview | ||
| Rating | 8.0 | 4.3 |
| Price | Free: free | Free: free |
| Free to use | Yes | Yes |
| Established | 2019 | 2010 |
| Platforms | ||
| Secrets & backup | ||
| Who holds the secrets | YouShow detailsHide detailsThe secrets live in a vault file on the phone. The app has no internet permission and no account, so there is no copy with the developers. Setup offers a password by default; choosing no password leaves the vault unencrypted on the phone. | Depends on settingShow detailsHide detailsSigned in to a Google Account, the app copies your secrets to that account, where Google says it encrypts them in transit and at rest. Choosing Use without an account keeps the codes only on the phone. There is no option to encrypt the synced copy with a password or key of your own, so Google can technically decrypt it. |
| Where backup is stored | FileShow detailsHide detailsAutomatic backups are off until you switch them on and pick a folder, which can belong to a cloud app on the phone. Android's own cloud backup can also include the vault after you switch it on. Both work only with a password-protected vault and use your password or a separate backup password. Android's direct phone-to-phone transfer is always allowed to include the vault. | Developer's serversShow detailsHide detailsThe only backup is the copy in your Google Account. Without an account, the app makes no backup file; codes can only be moved by scanning transfer QR codes from the old phone. |
| Backup locked with | Your password | Developer's key |
| Backup by default | Off | Prompted |
| Secrets on phone | Own password | App lock |
| Recovery | From file | By sign-in |
| Account & privacy | ||
| Account | No accountShow detailsHide detailsThere is no account and no sign-up; the app works fully offline. | OptionalShow detailsHide detailsA Google Account is needed only for syncing. The app works without one, and Google's help page describes how to use it that way from the first launch. |
| Tied to | Nothing | Existing account |
| Telemetry | No telemetry | Always on |
| Portability | ||
| Export | Yes | Partly |
| Import from | Other apps | QR or links |
| Sync between devices | No | Yes |
| Code types | TOTPHOTPSteam Guard | TOTPHOTP |
| Trust & transparency | ||
| App code | Fully open source | Closed source |
| Server code | No servers | Closed source |
| Reproducible builds | No | Not specified |
| Security audit | None on record | None on record |
| Bug bounty | No | Yes |
| Jurisdiction | NetherlandsShow detailsHide detailsThe Google Play listing gives Beem Development's contact address in Dordrecht, Netherlands. The app has no servers and holds no user data with the developers, so the jurisdiction matters little for the secrets themselves. | United StatesShow detailsHide detailsThe app is published by Google LLC, a Delaware company based in Mountain View, California. Google's terms are governed by California law unless local law requires otherwise; Google says that for most services the provider is either Google LLC, operating under US law, or Google Ireland Limited, operating under Irish law. |
| Owner | Beem DevelopmentShow detailsHide detailsBeem Development is the developer name on Google Play, F-Droid and the website. Most of the code on GitHub comes from two developers, and the project is funded by donations; no company registration is named on the project's pages. | Alphabet Inc.Show detailsHide detailsGoogle LLC is a wholly owned subsidiary of Alphabet Inc., whose shares trade on Nasdaq. Google released Authenticator in 2010 and added Google Account sync in April 2023. |
| Funded by | DonationsShow detailsHide detailsThe README and F-Droid link a donation page; there is no paid version. | CompanyShow detailsHide detailsThe app has no revenue of its own; Google pays for its development as part of its account-security products. |
| Past incident | Yes | No |
