Ext Ops Panel
Open dashboard
Permissions and history

Is AWS Favicons safe to install?

AWS Favicons declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

AWS Favicons

Chrome extension by Maddison Hellstrom · 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
No permissions at all
Data collection
Declares it collects none
Publisher
No store badges
Audience
480 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 does not link 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.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: No permissions at all.

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

480 users

Users
-19 since 01.09
465-512 · 35 readings
  1. 2026-09-01499
  2. 2026-09-04505
  3. 2026-09-06501
  4. 2026-09-07496
  5. 2026-09-09491
  6. 2026-09-10497
  7. 2026-09-13490
  8. 2026-09-15494
  9. 2026-09-17495
  10. 2026-09-21502
  11. 2026-09-22503
  12. 2026-09-25512
  13. 2026-09-26510
  14. 2026-09-28505
  15. 2026-10-05491
  16. 2026-10-08493
  17. 2026-10-09491
  18. 2026-10-10488
  19. 2026-10-11491
  20. 2026-10-13498
  21. 2026-10-16497
  22. 2026-10-17495
  23. 2026-10-18493
  24. 2026-10-19491
  25. 2026-10-20494
  26. 2026-10-21499
  27. 2026-10-23498
  28. 2026-10-24502
  29. 2026-10-25504
  30. 2026-10-28503
  31. 2026-10-29494
  32. 2026-10-30488
  33. 2026-11-01465
  34. 2026-11-04476
  35. 2026-11-06480

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

Maddison Hellstrom. This listing has been in the store since 2022-09-17 and was last updated on 2022-09-17.

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 AWS Favicons access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
What data does AWS Favicons 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 AWS Favicons asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does AWS Favicons publish a privacy policy?
No, the store listing does not link 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-06.

Back to AWS Favicons · Alternatives to AWS Favicons

Where the data comes from: how the catalog is built