Ext Ops Panel
Open dashboard
Permissions and history

Is AFAD タグチェックツール safe to install?

AFAD タグチェックツール asks for 1 browser permission and 6 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.

AFAD タグチェックツール

Chrome extension by GENIEE · Productivity · Tools

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
Runs its code on every site
Data collection
Declares it collects none
Publisher
No store badges
Audience
203 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

Specific sites only: 6 match patterns.

Reaches your browsing data or every site

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.

How usual this is for its category

In Productivity · Tools, 20% 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 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

203 users

Users
+4 since 31.08
177-218 · 36 readings
  1. 2026-08-31199
  2. 2026-09-02201
  3. 2026-09-03200
  4. 2026-09-05206
  5. 2026-09-06208
  6. 2026-09-07207
  7. 2026-09-08203
  8. 2026-09-09204
  9. 2026-09-10207
  10. 2026-09-13205
  11. 2026-09-15201
  12. 2026-09-17203
  13. 2026-09-20199
  14. 2026-09-21197
  15. 2026-09-25184
  16. 2026-09-27177
  17. 2026-10-04211
  18. 2026-10-08218
  19. 2026-10-09214
  20. 2026-10-10213
  21. 2026-10-13203
  22. 2026-10-16207
  23. 2026-10-17206
  24. 2026-10-18205
  25. 2026-10-20208
  26. 2026-10-21207
  27. 2026-10-22203
  28. 2026-10-23201
  29. 2026-10-24202
  30. 2026-10-25209
  31. 2026-10-28208
  32. 2026-10-29213
  33. 2026-11-01214
  34. 2026-11-03213
  35. 2026-11-06206
  36. 2026-11-07203

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

GENIEE, who publishes 2 listings we track. This listing has been in the store since 2023-12-16 and was last updated on 2025-08-12.

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. Tag Checker Tool Runs its code on every site · 2 permissions 166 users
  2. TagProof — Analytics & Pixel QA Inspector No site access · 3 permissions 5 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 AFAD タグチェックツール access?
Specific sites only: 6 match patterns. It declares 1 browser permission.
What data does AFAD タグチェックツール 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 AFAD タグチェックツール asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does AFAD タグチェックツール 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-07.

Back to AFAD タグチェックツール · Alternatives to AFAD タグチェックツール

Where the data comes from: how the catalog is built