Ext Ops Panel
Open dashboard
Permissions and history

Is Deep IP Trace – WebRTC Protection safe to install?

Deep IP Trace – WebRTC Protection asks for 2 browser permissions and 1 site pattern. 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.

Deep IP Trace – WebRTC Protection

Chrome extension by deepiptrace · Make Chrome Yours · Privacy

Open in the Chrome Web Store
What the developer says, and 4 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
Access to specific sites only
Data collection
2 kinds of data declared
Audience
19 users

What data it declares

The developer declares that it collects these kinds of 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

Specific sites only: 1 match pattern.

Worth knowing

Routine for an extension

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.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 1 site pattern.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Make Chrome Yours · Privacy, 44% of extensions ask for access to every site. This one: Access to specific sites only.

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

19 users

Users
+10 since 31.08
6-19 · 34 readings
  1. 2026-08-319
  2. 2026-09-029
  3. 2026-09-058
  4. 2026-09-067
  5. 2026-09-076
  6. 2026-09-098
  7. 2026-09-1311
  8. 2026-09-1712
  9. 2026-09-2113
  10. 2026-09-2512
  11. 2026-10-0416
  12. 2026-10-0815
  13. 2026-10-0914
  14. 2026-10-1015
  15. 2026-10-1113
  16. 2026-10-1614
  17. 2026-10-1713
  18. 2026-10-1812
  19. 2026-10-1915
  20. 2026-10-2014
  21. 2026-10-2313
  22. 2026-10-2414
  23. 2026-10-2517
  24. 2026-10-2615
  25. 2026-10-2816
  26. 2026-10-2914
  27. 2026-10-3015
  28. 2026-11-0114
  29. 2026-11-0215
  30. 2026-11-0417
  31. 2026-11-0619
  32. 2026-11-0718
  33. 2026-11-0819
  34. 2026-11-1419

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

deepiptrace. This listing has been in the store since 2026-08-15 and was last updated on 2026-08-16.

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. WebRTC Leak Blocker No site access · 2 permissions 25 users
  2. WebRTC Privacy Shield No site access · 2 permissions 159 users
  3. WebRTC Leak Protection No site access · 2 permissions 642 users ★ 5.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 Deep IP Trace – WebRTC Protection access?
Specific sites only: 1 match pattern. It declares 2 browser permissions.
What data does Deep IP Trace – WebRTC Protection collect?
The developer declares that it collects these kinds of data: Location, Web history. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Deep IP Trace – WebRTC Protection asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Deep IP Trace – WebRTC Protection 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-14.

Back to Deep IP Trace – WebRTC Protection · Alternatives to Deep IP Trace – WebRTC Protection

Where the data comes from: how the catalog is built