Ext Ops Panel
Open dashboard
Permissions and history

Is Grok TTS Reader: Free AI Text to Speech safe to install?

Grok TTS Reader: Free AI Text to Speech asks for 6 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.

Grok TTS Reader: Free AI Text to Speech

Chrome extension by democraticdeveloper · 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
Access to specific sites only
Data collection
Declares it collects none
Audience
418 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

Specific sites only: 3 match patterns.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

Pages it runs its code on

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

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

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

418 users

Users
+190 since 31.08
228-418 · 35 readings
2026-09-02: released 1.1.22026-09-06: released 1.1.32026-09-09: released 1.1.42026-09-26: released 1.1.52026-10-12: released 1.1.62026-10-18: released 1.1.72026-10-24: released 1.1.82026-10-26: released 1.1.92026-10-29: released 1.2.0
  1. 2026-08-31228
  2. 2026-09-03233
  3. 2026-09-04249
  4. 2026-09-07256
  5. 2026-09-08266
  6. 2026-09-10263
  7. 2026-09-13265
  8. 2026-09-15271
  9. 2026-09-17280
  10. 2026-09-20295
  11. 2026-09-21298
  12. 2026-09-25307
  13. 2026-09-27312
  14. 2026-09-28314
  15. 2026-10-04333
  16. 2026-10-08339
  17. 2026-10-09344
  18. 2026-10-10347
  19. 2026-10-11343
  20. 2026-10-13355
  21. 2026-10-16360
  22. 2026-10-17369
  23. 2026-10-18375released 1.1.7
  24. 2026-10-19374
  25. 2026-10-20376
  26. 2026-10-21383
  27. 2026-10-22380
  28. 2026-10-23382
  29. 2026-10-24390released 1.1.8
  30. 2026-10-25393
  31. 2026-10-28395
  32. 2026-10-29401released 1.2.0
  33. 2026-10-30396
  34. 2026-11-01418
  35. 2026-11-02418

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.2.0
  2. Version 1.1.9
  3. Version 1.1.8
  4. Version 1.1.7
  5. Version 1.1.6
  6. Version 1.1.5
  7. Version 1.1.4
  8. Version 1.1.3

Who publishes it

democraticdeveloper, who publishes 10 listings we track. This listing has been in the store since 2026-07-21 and was last updated on 2026-10-29.

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. Gemini Reader: AI Text to Speech with Google Voices No site access · 5 permissions 4k users ★ 4.3
  2. SKDOSS Text to Voice (TTS API) No site access · 5 permissions 136 users
  3. Whisper To Me Runs its code on every site · 3 permissions, 1 site pattern 12 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 Grok TTS Reader: Free AI Text to Speech access?
Specific sites only: 3 match patterns. It declares 6 browser permissions.
What data does Grok TTS Reader: Free AI Text to Speech 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 Grok TTS Reader: Free AI Text to Speech asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Grok TTS Reader: Free AI Text to Speech 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 Grok TTS Reader: Free AI Text to Speech · Alternatives to Grok TTS Reader: Free AI Text to Speech

Where the data comes from: how the catalog is built