Ext Ops Panel
Open dashboard
Permissions and history

Is myip.foo - WebRTC Blocker safe to install?

myip.foo - WebRTC Blocker 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.

myip.foo - WebRTC Blocker

Chrome extension by VirtualOx B.V. · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 2 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
No site access
Data collection
Declares it collects none
Upkeep
Updated 348 days ago
Publisher
No store badges
Audience
122 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 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

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

How usual this is for its category

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

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

122 users

Users
-43 since 31.08
122-208 · 32 readings
  1. 2026-08-31165
  2. 2026-09-02166
  3. 2026-09-04155
  4. 2026-09-06159
  5. 2026-09-07166
  6. 2026-09-09170
  7. 2026-09-13166
  8. 2026-09-15149
  9. 2026-09-17177
  10. 2026-09-21207
  11. 2026-09-25167
  12. 2026-09-27149
  13. 2026-09-28157
  14. 2026-10-04208
  15. 2026-10-08197
  16. 2026-10-09195
  17. 2026-10-10196
  18. 2026-10-13201
  19. 2026-10-16190
  20. 2026-10-17184
  21. 2026-10-18181
  22. 2026-10-19179
  23. 2026-10-20184
  24. 2026-10-21171
  25. 2026-10-22188
  26. 2026-10-23175
  27. 2026-10-25172
  28. 2026-10-26165
  29. 2026-10-28146
  30. 2026-10-29124
  31. 2026-10-30141
  32. 2026-11-01122

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

VirtualOx B.V., who publishes 2 listings we track. This listing has been in the store since 2025-11-18 and was last updated on 2025-11-18.

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 myip.foo - WebRTC Blocker 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 myip.foo - WebRTC Blocker 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 myip.foo - WebRTC Blocker asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does myip.foo - WebRTC Blocker 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 myip.foo - WebRTC Blocker · Alternatives to myip.foo - WebRTC Blocker

Where the data comes from: how the catalog is built