Ext Ops Panel
Open dashboard
Permissions and history

Is PDF to Audio safe to install?

PDF to Audio asks for 1 browser permission 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.

PDF to Audio

Chrome extension by Live Polls · Productivity · Workflow

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 343 days ago
Audience
150 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.

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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 · Workflow, 19% of extensions ask for access to every site. This one: No site access.

The typical extension there declares 3 browser permissions; this one declares 1 browser permission.

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

150 users

Users
+18 since 01.09
129-155 · 43 readings
  1. 2026-09-01132
  2. 2026-09-02131
  3. 2026-09-03129
  4. 2026-09-04136
  5. 2026-09-06137
  6. 2026-09-08139
  7. 2026-09-13136
  8. 2026-09-15135
  9. 2026-09-17132
  10. 2026-09-21133
  11. 2026-09-22132
  12. 2026-09-25138
  13. 2026-09-27140
  14. 2026-09-28141
  15. 2026-10-04147
  16. 2026-10-08150
  17. 2026-10-09149
  18. 2026-10-10153
  19. 2026-10-11151
  20. 2026-10-16154
  21. 2026-10-17152
  22. 2026-10-18150
  23. 2026-10-19147
  24. 2026-10-20149
  25. 2026-10-21151
  26. 2026-10-22149
  27. 2026-10-23147
  28. 2026-10-24151
  29. 2026-10-25148
  30. 2026-10-28142
  31. 2026-10-29140
  32. 2026-10-30146
  33. 2026-11-01144
  34. 2026-11-04146
  35. 2026-11-06141
  36. 2026-11-07146
  37. 2026-11-08145
  38. 2026-11-09152
  39. 2026-11-10154
  40. 2026-11-11155
  41. 2026-11-14147
  42. 2026-11-15150
  43. 2026-11-16150

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

Live Polls, who publishes 20 listings we track. This listing has been in the store since 2025-12-08 and was last updated on 2025-12-08.

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. Reader PDF Voice No permissions at all · No permissions declared 13 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 to Audio access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 1 browser permission.
What data does PDF to Audio 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 to Audio asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does PDF to Audio 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-16.

Back to PDF to Audio · Alternatives to PDF to Audio

Where the data comes from: how the catalog is built