Ext Ops Panel
Open dashboard
Permissions and history

Is NaReader-「小説家になろう」読み上げ safe to install?

NaReader-「小説家になろう」読み上げ 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.

NaReader-「小説家になろう」読み上げ

Chrome extension by さこ13 · Make Chrome Yours · Accessibility

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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
Publisher
No store badges
Audience
161 users

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.

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

161 users

Users
+16 since 01.09
145-164 · 37 readings
  1. 2026-09-01145
  2. 2026-09-02148
  3. 2026-09-04151
  4. 2026-09-06161
  5. 2026-09-07158
  6. 2026-09-08156
  7. 2026-09-10153
  8. 2026-09-13151
  9. 2026-09-15152
  10. 2026-09-17148
  11. 2026-09-20153
  12. 2026-09-22152
  13. 2026-09-25150
  14. 2026-09-27151
  15. 2026-09-28154
  16. 2026-10-05157
  17. 2026-10-08164
  18. 2026-10-09159
  19. 2026-10-10156
  20. 2026-10-13149
  21. 2026-10-16150
  22. 2026-10-18152
  23. 2026-10-21155
  24. 2026-10-22152
  25. 2026-10-23158
  26. 2026-10-24157
  27. 2026-10-25158
  28. 2026-10-28157
  29. 2026-10-29156
  30. 2026-11-01154
  31. 2026-11-03155
  32. 2026-11-06149
  33. 2026-11-07151
  34. 2026-11-08150
  35. 2026-11-09145
  36. 2026-11-10148
  37. 2026-11-14161

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

さこ13. This listing has been in the store since 2023-04-16 and was last updated on 2023-06-16.

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 NaReader-「小説家になろう」読み上げ 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 NaReader-「小説家になろう」読み上げ collect?
The developer declares that it collects these kinds of data: Web history, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has NaReader-「小説家になろう」読み上げ asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does NaReader-「小説家になろう」読み上げ 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-14.

Back to NaReader-「小説家になろう」読み上げ · Alternatives to NaReader-「小説家になろう」読み上げ

Where the data comes from: how the catalog is built