Ext Ops Panel
Open dashboard
Permissions and history

Is Authra 2FA - QR Auto Scanner safe to install?

Authra 2FA - QR Auto Scanner asks for 4 browser permissions and 3 site patterns. 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.

Authra 2FA - QR Auto Scanner

Chrome extension by rezky.pradana.budihartono · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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
Access to specific sites only
Data collection
2 kinds of data declared
Upkeep
Updated 136 days ago
Audience
11 users

What data it declares

The developer declares that it collects these kinds of 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

Specific sites only: 3 match patterns.

Worth knowing

Routine for an extension

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 5 site patterns.

Show the remaining 2
  • http://localhost:5173/* only localhost
  • http://127.0.0.1:5173/* only 127.0.0.1

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 4 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

11 users

Users
-1 since 01.09
9-13 · 29 readings
  1. 2026-09-0112
  2. 2026-09-0213
  3. 2026-09-0511
  4. 2026-09-0613
  5. 2026-09-0712
  6. 2026-09-0913
  7. 2026-09-1312
  8. 2026-09-1513
  9. 2026-09-1711
  10. 2026-09-2112
  11. 2026-09-2213
  12. 2026-09-2511
  13. 2026-09-2713
  14. 2026-09-2812
  15. 2026-10-0413
  16. 2026-10-0810
  17. 2026-10-109
  18. 2026-10-1310
  19. 2026-10-1810
  20. 2026-10-2111
  21. 2026-10-229
  22. 2026-10-2311
  23. 2026-10-2410
  24. 2026-11-0110
  25. 2026-11-0311
  26. 2026-11-0712
  27. 2026-11-0810
  28. 2026-11-0911
  29. 2026-11-1011

What the store shows

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

rezky.pradana.budihartono, who publishes 2 listings we track. This listing has been in the store since 2026-06-15 and was last updated on 2026-06-27.

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. Local Authenticator: Private TOTP Vault No site access · 1 permission 11 users ★ 5.0
  2. 2FA verification code No site access · 3 permissions 35 users
  3. 2FA Authenticator Assistant No site access · 3 permissions 27 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 Authra 2FA - QR Auto Scanner access?
Specific sites only: 3 match patterns. It declares 4 browser permissions.
What data does Authra 2FA - QR Auto Scanner collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Authra 2FA - QR Auto Scanner asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Authra 2FA - QR Auto Scanner 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-10.

Back to Authra 2FA - QR Auto Scanner · Alternatives to Authra 2FA - QR Auto Scanner

Where the data comes from: how the catalog is built