Ext Ops Panel
Open dashboard
Permissions and history

Is 2FA Authenticator safe to install?

2FA Authenticator asks for 2 browser permissions and declares no blanket site access. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

2FA Authenticator

Chrome extension by yyzrever · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 3 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
No site access
Data collection
Declares it collects none
Upkeep
Updated 107 days ago
Publisher
No store badges
Audience
33 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Routine for an extension

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: No site access.

The typical extension there declares 3 browser permissions; this one declares 2 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

33 users

Users
unchanged since 01.09
29-37 · 34 readings
  1. 2026-09-0133
  2. 2026-09-0237
  3. 2026-09-0634
  4. 2026-09-0831
  5. 2026-09-0929
  6. 2026-09-1330
  7. 2026-09-1532
  8. 2026-09-1631
  9. 2026-09-2030
  10. 2026-09-2532
  11. 2026-09-2631
  12. 2026-09-2832
  13. 2026-10-0433
  14. 2026-10-0830
  15. 2026-10-0933
  16. 2026-10-1031
  17. 2026-10-1132
  18. 2026-10-1331
  19. 2026-10-1632
  20. 2026-10-1731
  21. 2026-10-1832
  22. 2026-10-1931
  23. 2026-10-2432
  24. 2026-10-2531
  25. 2026-10-2632
  26. 2026-10-2831
  27. 2026-10-3033
  28. 2026-11-0631
  29. 2026-11-0732
  30. 2026-11-0833
  31. 2026-11-0931
  32. 2026-11-1032
  33. 2026-11-1133
  34. 2026-11-1333

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

yyzrever. This listing has been in the store since 2026-06-15 and was last updated on 2026-07-29.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. 2FA Live No permissions at all · No permissions declared 40 users ★ 5.0
  2. AnyOTP No permissions at all · No permissions declared 10 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can 2FA Authenticator access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 2 browser permissions.
What data does 2FA Authenticator collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has 2FA Authenticator asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does 2FA Authenticator publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-13.

Back to 2FA Authenticator · Alternatives to 2FA Authenticator

Where the data comes from: how the catalog is built