Ext Ops Panel
Open dashboard
Permissions and history

Is Soap Reader — CORS Proxy safe to install?

Soap Reader — CORS Proxy 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.

Soap Reader — CORS Proxy

Chrome extension by Nihagy · Productivity · Developer

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
Access to every site
Data collection
Declares it collects none
Upkeep
Updated 154 days ago
Publisher
No store badges
Audience
18 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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 4 site patterns.

Show the remaining 1
  • *://127.0.0.1/* only 127.0.0.1

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: Access to 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

18 users

Users
+1 since 01.09
16-21 · 25 readings
  1. 2026-09-0117
  2. 2026-09-0218
  3. 2026-09-0417
  4. 2026-09-0718
  5. 2026-09-0820
  6. 2026-09-1018
  7. 2026-09-1521
  8. 2026-09-1620
  9. 2026-09-2016
  10. 2026-09-2617
  11. 2026-09-2816
  12. 2026-10-0420
  13. 2026-10-0819
  14. 2026-10-0920
  15. 2026-10-1018
  16. 2026-10-1717
  17. 2026-10-1818
  18. 2026-10-1918
  19. 2026-10-2119
  20. 2026-10-2421
  21. 2026-10-2520
  22. 2026-10-2819
  23. 2026-10-2920
  24. 2026-11-0118
  25. 2026-11-0218

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

Nihagy, who publishes 5 listings we track. This listing has been in the store since 2026-05-21 and was last updated on 2026-06-01.

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. WSDLY - SOAP Client No permissions at all · No permissions declared 1k users ★ 3.0
  2. Soap Filter No permissions at all · No permissions declared 48 users
  3. WSDL documenter Runs its code on every site · 2 permissions 508 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 Soap Reader — CORS Proxy access?
Every site you visit. This extension can read and change the content of any page you open. It declares 2 browser permissions.
What data does Soap Reader — CORS Proxy 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 Soap Reader — CORS Proxy asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Soap Reader — CORS Proxy 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-02.

Back to Soap Reader — CORS Proxy · Alternatives to Soap Reader — CORS Proxy

Where the data comes from: how the catalog is built