Ext Ops Panel
Open dashboard
Permissions and history

Is PDF Eye Saver safe to install?

PDF Eye Saver asks for 3 browser permissions and 3 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.

PDF Eye Saver

Chrome extension by thin · 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
Access to every site
Data collection
Declares it collects none
Upkeep
Updated 216 days ago
Publisher
No store badges
Audience
100 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

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

Reaches your browsing data or every site

Worth knowing

How usual this is for its category

In Productivity · Tools, 20% 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 3 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

100 users

Users
+30 since 01.09
69-134 · 42 readings
  1. 2026-09-0170
  2. 2026-09-0369
  3. 2026-09-0470
  4. 2026-09-0672
  5. 2026-09-0771
  6. 2026-09-0874
  7. 2026-09-1075
  8. 2026-09-1378
  9. 2026-09-1576
  10. 2026-09-1774
  11. 2026-09-2179
  12. 2026-09-2584
  13. 2026-09-2682
  14. 2026-09-2879
  15. 2026-10-0486
  16. 2026-10-0890
  17. 2026-10-0993
  18. 2026-10-1094
  19. 2026-10-1198
  20. 2026-10-13101
  21. 2026-10-1699
  22. 2026-10-17100
  23. 2026-10-18103
  24. 2026-10-19109
  25. 2026-10-20110
  26. 2026-10-21112
  27. 2026-10-22116
  28. 2026-10-23125
  29. 2026-10-24126
  30. 2026-10-25134
  31. 2026-10-26127
  32. 2026-10-28122
  33. 2026-10-29119
  34. 2026-10-30113
  35. 2026-11-0199
  36. 2026-11-0296
  37. 2026-11-06100
  38. 2026-11-08104
  39. 2026-11-09101
  40. 2026-11-10103
  41. 2026-11-11100
  42. 2026-11-12100

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

thin, who publishes 2 listings we track. This listing has been in the store since 2025-12-02 and was last updated on 2026-04-10.

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. dark.pdf No site access · 2 permissions 156 users ★ 3.7
  2. Dark Mode No site access · 3 permissions 45 users ★ 4.5
  3. PDF Dark Mode Access to specific sites only · 2 permissions, 4 site patterns 36 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 PDF Eye Saver access?
Every site you visit. This extension can read and change the content of any page you open. It declares 3 browser permissions.
What data does PDF Eye Saver 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 PDF Eye Saver asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does PDF Eye Saver 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-12.

Back to PDF Eye Saver · Alternatives to PDF Eye Saver

Where the data comes from: how the catalog is built