Ext Ops Panel
Open dashboard
Permissions and history

Is Audister: Text to Speech & PDF Read Aloud safe to install?

Audister: Text to Speech & PDF Read Aloud asks for 6 browser permissions 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.

Audister: Text to Speech & PDF Read Aloud

Chrome extension by Karl · Make Chrome Yours · Accessibility

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
No site access
Data collection
2 kinds of data declared
Audience
49 users · 5.0/5

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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Worth knowing

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.

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 Make Chrome Yours · Accessibility, 23% of extensions ask for access to every site. This one: No site access.

The typical extension there declares 2 browser permissions; this one declares 6 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

49 users

Users
+35 since 01.09
13-49 · 30 readings
2026-09-03: released 1.2.12026-09-08: released 1.3.02026-09-10: released 1.3.12026-09-16: released 1.3.22026-09-17: released 1.3.32026-10-03: released 1.3.42026-10-04: gained the good publisher record badge2026-10-15: released 1.3.62026-10-31: released 1.3.7
  1. 2026-09-0114
  2. 2026-09-0213
  3. 2026-09-0314released 1.2.1
  4. 2026-09-0416
  5. 2026-09-0619
  6. 2026-09-0718
  7. 2026-09-0919
  8. 2026-09-1322
  9. 2026-09-2026
  10. 2026-09-2124
  11. 2026-09-2526
  12. 2026-09-2625
  13. 2026-09-2826
  14. 2026-10-0533
  15. 2026-10-0830
  16. 2026-10-0934
  17. 2026-10-1031
  18. 2026-10-1333
  19. 2026-10-1635
  20. 2026-10-1734
  21. 2026-10-1835
  22. 2026-10-2036
  23. 2026-10-2138
  24. 2026-10-2237
  25. 2026-10-2340
  26. 2026-10-2538
  27. 2026-10-2637
  28. 2026-10-2939
  29. 2026-10-3043
  30. 2026-11-0149

What the store shows

The listing says it offers in-app purchases.

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.

Versions we have seen

  1. Version 1.3.7
  2. Version 1.3.6
  3. Version 1.3.4
  4. Version 1.3.3
  5. Version 1.3.2
  6. Version 1.3.1
  7. Version 1.3.0
  8. Version 1.2.1

Who publishes it

Karl. This listing has been in the store since 2026-07-21 and was last updated on 2026-10-31.

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. Read PDF Aloud: PDF Text to Speech & Voice Reader No site access · 1 permission 391 users ★ 5.0
  2. Read Aloud Runs its code on every site · 3 permissions 194 users ★ 3.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 Audister: Text to Speech & PDF Read Aloud access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 6 browser permissions.
What data does Audister: Text to Speech & PDF Read Aloud collect?
The developer declares that it collects these kinds of data: Authentication information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Audister: Text to Speech & PDF Read Aloud asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Audister: Text to Speech & PDF Read Aloud 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-01.

Back to Audister: Text to Speech & PDF Read Aloud · Alternatives to Audister: Text to Speech & PDF Read Aloud

Where the data comes from: how the catalog is built