Ext Ops Panel
Open dashboard
Permissions and history

Is CookieCut — Auto-Reject Banners safe to install?

CookieCut — Auto-Reject Banners asks for 3 browser permissions and 1 site pattern. 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.

CookieCut — Auto-Reject Banners

Chrome extension by Uncommon Weather LLC · Make Chrome Yours · Privacy

Open in the Chrome Web Store
What the developer says, and 4 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
Runs its code on every site
Data collection
5 kinds of data declared
Upkeep
Updated 94 days ago
Publisher
No store badges
Audience
149 users · 4.0/5

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: 1 match pattern.

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

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.

Sites that can connect to it

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

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 Make Chrome Yours · Privacy, 42% of extensions ask for access to every site. This one: Runs its code on every site.

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

149 users

Users
-21 since 01.09
149-196 · 35 readings
  1. 2026-09-01170
  2. 2026-09-03167
  3. 2026-09-04172
  4. 2026-09-05174
  5. 2026-09-06172
  6. 2026-09-07168
  7. 2026-09-08167
  8. 2026-09-09170
  9. 2026-09-13178
  10. 2026-09-15180
  11. 2026-09-16175
  12. 2026-09-20165
  13. 2026-09-21168
  14. 2026-09-25163
  15. 2026-09-26164
  16. 2026-09-28167
  17. 2026-10-05196
  18. 2026-10-08194
  19. 2026-10-09192
  20. 2026-10-10192
  21. 2026-10-13177
  22. 2026-10-16182
  23. 2026-10-17180
  24. 2026-10-18177
  25. 2026-10-19176
  26. 2026-10-20178
  27. 2026-10-21180
  28. 2026-10-23176
  29. 2026-10-24172
  30. 2026-10-25177
  31. 2026-10-26175
  32. 2026-10-28161
  33. 2026-10-29159
  34. 2026-10-30158
  35. 2026-11-01149

What the store shows

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

The listing says it offers in-app purchases.

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

Uncommon Weather LLC, who publishes 9 listings we track. This listing has been in the store since 2025-07-09 and was last updated on 2026-07-30.

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. Cookie Decliner — Auto Reject Banners Runs its code on every site · 1 permission 70 users
  2. Cookie Cutter — Auto-Decline Cookie Banners Runs its code on every site · 2 permissions, 1 site pattern 6 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 CookieCut — Auto-Reject Banners access?
Specific sites only: 1 match pattern. It declares 3 browser permissions.
What data does CookieCut — Auto-Reject Banners collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information, Web history, User activity, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has CookieCut — Auto-Reject Banners asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does CookieCut — Auto-Reject Banners 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-01.

Back to CookieCut — Auto-Reject Banners · Alternatives to CookieCut — Auto-Reject Banners

Where the data comes from: how the catalog is built