Ext Ops Panel
Open dashboard
Permissions and history

Is Google Tag Manager Internal Traffic Filter safe to install?

Google Tag Manager Internal Traffic Filter asks for 2 browser permissions 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.

Google Tag Manager Internal Traffic Filter

Chrome extension by Semetrical Ltd · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 3 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.

Data collection
Declares it collects none
Upkeep
Updated 181 days ago
Publisher
Trader
Audience
57 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

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.

How usual this is for its category

In Productivity · Developer, 30% 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 2 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

57 users

Users
+13 since 01.09
41-57 · 27 readings
  1. 2026-09-0144
  2. 2026-09-0246
  3. 2026-09-0445
  4. 2026-09-0648
  5. 2026-09-0747
  6. 2026-09-0948
  7. 2026-09-1047
  8. 2026-09-1351
  9. 2026-09-1553
  10. 2026-09-1754
  11. 2026-09-2052
  12. 2026-09-2657
  13. 2026-09-2854
  14. 2026-10-0543
  15. 2026-10-0841
  16. 2026-10-0945
  17. 2026-10-1044
  18. 2026-10-1147
  19. 2026-10-1651
  20. 2026-10-1854
  21. 2026-10-2156
  22. 2026-10-2255
  23. 2026-10-2451
  24. 2026-10-2552
  25. 2026-10-2748
  26. 2026-10-2956
  27. 2026-11-0157

What the store shows

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

Semetrical Ltd, who publishes 2 listings we track. This listing has been in the store since 2025-12-29 and was last updated on 2026-05-04.

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 Google Tag Manager Internal Traffic Filter access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 2 browser permissions.
What data does Google Tag Manager Internal Traffic Filter 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 Google Tag Manager Internal Traffic Filter asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Google Tag Manager Internal Traffic Filter 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 Google Tag Manager Internal Traffic Filter · Alternatives to Google Tag Manager Internal Traffic Filter

Where the data comes from: how the catalog is built