Ext Ops Panel
Open dashboard
Permissions and history

Is Web Reader Assistant safe to install?

Web Reader Assistant asks for 2 browser permissions and 13 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.

Web Reader Assistant

Chrome extension by The Prompting Fox · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 5 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
Runs its code on every site
Data collection
Declares it collects none
Upkeep
Updated 212 days ago
Publisher
No store badges
Audience
85 users · 5.0/5

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: 13 match patterns.

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.

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.

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 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

85 users

Users
+9 since 31.08
68-86 · 31 readings
  1. 2026-08-3176
  2. 2026-09-0278
  3. 2026-09-0577
  4. 2026-09-0679
  5. 2026-09-0875
  6. 2026-09-1074
  7. 2026-09-1372
  8. 2026-09-1568
  9. 2026-09-1774
  10. 2026-09-2177
  11. 2026-09-2574
  12. 2026-09-2679
  13. 2026-09-2877
  14. 2026-10-0480
  15. 2026-10-0884
  16. 2026-10-1082
  17. 2026-10-1184
  18. 2026-10-1386
  19. 2026-10-1682
  20. 2026-10-1781
  21. 2026-10-2079
  22. 2026-10-2182
  23. 2026-10-2277
  24. 2026-10-2378
  25. 2026-10-2483
  26. 2026-10-2581
  27. 2026-10-2680
  28. 2026-10-2883
  29. 2026-10-2984
  30. 2026-10-3085
  31. 2026-10-3185

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

The Prompting Fox, who publishes 2 listings we track. This listing has been in the store since 2024-10-28 and was last updated on 2026-04-02.

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. Reading Review No site access · 3 permissions 3 users
  2. NoteVis No site access · 4 permissions 13 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 Web Reader Assistant access?
Specific sites only: 13 match patterns. It declares 2 browser permissions.
What data does Web Reader Assistant 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 Web Reader Assistant asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Web Reader Assistant 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-10-31.

Back to Web Reader Assistant · Alternatives to Web Reader Assistant

Where the data comes from: how the catalog is built