Is Cookie-Editor safe to install?

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:

• Read your browsing history

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

• Read and change cookies on the sites it can access cookies
• See the address and title of every tab you have open tabs

Routine for an extension

• Open a panel beside the page sidePanel
• Store data in your browser storage

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.

• <all_urls> every site

How usual this is for its category

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

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

• Read and change cookies on the sites it can access (cookies): 7% of extensions in this category ask for it.
• See the address and title of every tab you have open (tabs): 26% of extensions in this category ask for it.

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

168 users

• Last updated in the store 170 days ago, on 2026-05-16.
• No new version in the last 90 days.

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

Maehdakvan. This listing has been in the store since 2026-05-11 and was last updated on 2026-05-16.

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 Cookie-Editor access?

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

What data does Cookie-Editor 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 Cookie-Editor asked for more permissions over time?

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

Does Cookie-Editor publish a privacy policy?

No, the store listing does not link to a privacy policy.