Ext Ops Panel
Open dashboard
Permissions and history

Is Allow third-party cookies API safe to install?

Allow third-party cookies API asks for 1 browser permission 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.

Allow third-party cookies API

Chrome extension by chwaleedmehar9 · Productivity · Workflow

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 site access
Data collection
Declares it collects none
Publisher
No store badges
Audience
84 users

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.

Reaches your browsing data or every site

How usual this is for its category

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

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

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

84 users

Users
-9 since 31.08
77-94 · 33 readings
  1. 2026-08-3193
  2. 2026-09-0292
  3. 2026-09-0487
  4. 2026-09-0785
  5. 2026-09-0884
  6. 2026-09-0980
  7. 2026-09-1079
  8. 2026-09-1380
  9. 2026-09-1578
  10. 2026-09-2077
  11. 2026-09-2178
  12. 2026-09-2580
  13. 2026-09-2683
  14. 2026-09-2881
  15. 2026-10-0485
  16. 2026-10-0884
  17. 2026-10-0985
  18. 2026-10-1088
  19. 2026-10-1192
  20. 2026-10-1394
  21. 2026-10-1692
  22. 2026-10-1791
  23. 2026-10-1893
  24. 2026-10-1989
  25. 2026-10-2088
  26. 2026-10-2191
  27. 2026-10-2289
  28. 2026-10-2386
  29. 2026-10-2487
  30. 2026-10-2591
  31. 2026-10-2889
  32. 2026-10-3087
  33. 2026-11-0184

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

chwaleedmehar9, who publishes 4 listings we track. This listing has been in the store since 2022-06-09 and was last updated on 2022-06-09.

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 Accepter Runs its code on every site · No permissions declared 22 users ★ 1.0

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 Allow third-party cookies API access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 1 browser permission.
What data does Allow third-party cookies API 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 Allow third-party cookies API asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Allow third-party cookies API 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-01.

Back to Allow third-party cookies API · Alternatives to Allow third-party cookies API

Where the data comes from: how the catalog is built