Is Classical Music History safe to install?
Classical Music History declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.
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 permissions at all
- Data collection
- No declaration in the listing
- Publisher
- Established publisher
- Audience
- 197 users · 4.0/5
What data it declares
The listing carries no declaration about the data it collects.
The listing does not link to a privacy policy.
What Chrome asks you to allow
From the permissions it declares, Chrome shows no permission warning when you add it.
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.
We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.
Who uses it and how it is kept up
197 users
- 2026-08-31213
- 2026-09-02216
- 2026-09-05219
- 2026-09-07220
- 2026-09-08217
- 2026-09-09216
- 2026-09-10218
- 2026-09-13219
- 2026-09-15220
- 2026-09-17217
- 2026-09-20207
- 2026-09-22213
- 2026-09-25207
- 2026-09-27204
- 2026-09-28207
- 2026-10-05208
- 2026-10-08199
- 2026-10-09194
- 2026-10-10197
- 2026-10-11194
- 2026-10-13193
- 2026-10-16204
- 2026-10-17199
- 2026-10-18205
- 2026-10-19206
- 2026-10-20209
- 2026-10-21210
- 2026-10-22209
- 2026-10-23206
- 2026-10-24205
- 2026-10-25200
- 2026-10-28202
- 2026-10-29200
- 2026-10-30206
- 2026-11-01201
- 2026-11-04197
- Not updated in the store for over a year: the last update was on 2015-10-22.
- No new version in the last 90 days.
What the store shows
- Established publisher The store's badge for publishers with a good record and no history of violations.
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
Silvawood, who publishes 7 listings we track. This listing has been in the store since 2015-03-07 and was last updated on 2015-10-22.
How to check or remove it in Chrome
- Type chrome://extensions in the address bar and find the extension in the list.
- 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.
- To uninstall it, choose Remove on the same page.
Questions people ask
- What can Classical Music History access?
- No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
- What data does Classical Music History collect?
- The listing carries no declaration about the data it collects.
- Has Classical Music History asked for more permissions over time?
- The permissions this extension requests have not changed since we started watching it.
- Does Classical Music History publish a privacy policy?
- No, the store listing does not link 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-04.
Back to Classical Music History · Alternatives to Classical Music History
Where the data comes from: how the catalog is built