
Beem Development · Netherlands
Beem Development · Netherlands
Apps that generate the one-time codes for two-factor login. Each app stores a secret for every account you add, and whoever holds those secrets can generate your codes. For each of the 5 we reviewed, we look at who can read the secrets, where the backup goes and whose key protects it, what account or phone number the app asks for, whether you can export your codes, and who pays for the development.
Don't see the authenticator app you use?
Every authenticator app is scored out of 10 against five weighted categories. Who can read the secrets behind your codes carries the most weight, and a synced backup is not counted as a plus on its own.
Who can read the secrets behind your codes, whether a backup exists, where it goes, whether it is on by default and whose key protects it, how the secrets are protected on the phone, and what happens when the phone is lost. An app where the vendor can read the secrets cannot score high here.
Whether the app works without an account, what it asks for (an email address, a phone number), and what it reports about you through telemetry.
Whether the code is open, whether builds can be reproduced, whether an independent audit exists and who paid for it, a bug bounty, and past incidents.
Whether you can take your codes with you (export formats, import from other apps), whether one set of codes works on several devices, which platforms and code types are covered, and how well the app works day to day.
Who pays for development, whether the app is likely to be maintained, and whether the price, where there is one, is clear. Most authenticators are free, so price alone does not separate them.
An authenticator is only as private as the place its secrets live. Secret Custody & Recovery therefore comes first: it asks who can read the secrets, whether a backup exists, where it goes and whose key protects it, and what happens when the phone is lost. Account & Metadata Privacy asks what the app wants in exchange: an account, an email address or a phone number, and what it reports about you. Transparency & Verifiability asks whether the code is open and whether an audit exists and who paid for it. Usability, Portability & Platforms asks whether you can take your codes with you if you leave.
Not by itself. A backup protects you from losing access to your accounts, but a copy on the vendor's servers widens the circle of those who could read the secrets. The reviews show both sides: whether a backup exists, where it goes, whether it is on by default and whose key protects it.
Some apps, especially community projects, have none. A missing audit is not scored anywhere else: it only limits how much Transparency & Verifiability can earn, and the review says plainly that none exists.