Ext Ops Panel
Open dashboard
Permissions and history

Is Volume Control: Persistent Per-Site Sound safe to install?

Volume Control: Persistent Per-Site Sound asks for 1 browser permission and 1 site pattern. 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.

Volume Control: Persistent Per-Site Sound

Chrome extension by dieter.kaeppel · 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
Runs its code on every site
Data collection
1 kind of data declared
Upkeep
Updated 163 days ago
Publisher
No store badges
Audience
223 users · 3.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

Specific sites only: 1 match pattern.

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

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: Runs its code on every site.

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

223 users

Users
+34 since 01.09
189-328 · 33 readings
  1. 2026-09-01189
  2. 2026-09-03194
  3. 2026-09-05197
  4. 2026-09-07209
  5. 2026-09-08211
  6. 2026-09-09240
  7. 2026-09-13296
  8. 2026-09-15320
  9. 2026-09-17328
  10. 2026-09-20284
  11. 2026-09-21282
  12. 2026-09-25271
  13. 2026-09-26269
  14. 2026-09-28280
  15. 2026-10-04248
  16. 2026-10-08231
  17. 2026-10-09228
  18. 2026-10-10228
  19. 2026-10-13233
  20. 2026-10-16236
  21. 2026-10-18238
  22. 2026-10-19237
  23. 2026-10-20236
  24. 2026-10-21232
  25. 2026-10-22231
  26. 2026-10-23233
  27. 2026-10-24232
  28. 2026-10-25227
  29. 2026-10-28233
  30. 2026-10-29228
  31. 2026-10-30221
  32. 2026-11-01224
  33. 2026-11-02223

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

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.

Who publishes it

dieter.kaeppel, who publishes 6 listings we track. This listing has been in the store since 2026-01-20 and was last updated on 2026-05-23.

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. Volume Control for Google Chrome™ No site access · 4 permissions 90k users ★ 4.4
  2. Volume Pro Runs its code on every site · 4 permissions 7 users
  3. Tab Volume Controller No site access · 5 permissions 69 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 Volume Control: Persistent Per-Site Sound access?
Specific sites only: 1 match pattern. It declares 1 browser permission.
What data does Volume Control: Persistent Per-Site Sound collect?
The developer declares that it collects these kinds of data: Personally identifiable information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Volume Control: Persistent Per-Site Sound asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Volume Control: Persistent Per-Site Sound 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 Volume Control: Persistent Per-Site Sound · Alternatives to Volume Control: Persistent Per-Site Sound

Where the data comes from: how the catalog is built