Ext Ops Panel
Open dashboard
Permissions and history

Is Google chrome player safe to install?

Google chrome player 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.

Google chrome player

Chrome Web Store listing by Haritz Medina

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 permissions at all
Publisher
No store badges
Audience
22 users · 5.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.

Where it runs its code

We have not read this listing's manifest since we started keeping where it embeds its code, what it may ask for later and which sites can connect to it. The next pass of the store fills this in.

Who uses it and how it is kept up

22 users

Users
-2 since 01.09
18-27 · 29 readings
  1. 2026-09-0124
  2. 2026-09-0225
  3. 2026-09-0422
  4. 2026-09-0625
  5. 2026-09-0826
  6. 2026-09-0926
  7. 2026-09-1323
  8. 2026-09-1522
  9. 2026-09-2026
  10. 2026-09-2527
  11. 2026-09-2625
  12. 2026-09-2824
  13. 2026-10-0419
  14. 2026-10-0825
  15. 2026-10-0927
  16. 2026-10-1025
  17. 2026-10-1124
  18. 2026-10-1321
  19. 2026-10-1722
  20. 2026-10-1823
  21. 2026-10-1926
  22. 2026-10-2124
  23. 2026-10-2223
  24. 2026-10-2425
  25. 2026-10-2519
  26. 2026-10-2818
  27. 2026-10-2920
  28. 2026-10-3022
  29. 2026-11-0222

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

Haritz Medina. This listing has been in the store since 2017-01-09 and was last updated on 2017-01-09.

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 Google chrome player 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 Google chrome player collect?
The listing carries no declaration about the data it collects.
Has Google chrome player asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Google chrome player 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-02.

Back to Google chrome player · Alternatives to Google chrome player

Where the data comes from: how the catalog is built