Ext Ops Panel
Open dashboard
Permissions and history

Is adiobox: Audio Player for Chrome(OS) safe to install?

adiobox: Audio Player for Chrome(OS) 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.

adiobox: Audio Player for Chrome(OS)

Chrome extension by Yates Media Group · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 3 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
No permissions at all
Data collection
2 kinds of data declared
Upkeep
Updated 341 days ago
Audience
925 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

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.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 2 site patterns.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Workflow, 19% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 3 browser permissions; this one declares no 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

925 users

Users
+222 since 01.09
703-936 · 36 readings
  1. 2026-09-01703
  2. 2026-09-02711
  3. 2026-09-04719
  4. 2026-09-06728
  5. 2026-09-07731
  6. 2026-09-09733
  7. 2026-09-10742
  8. 2026-09-13747
  9. 2026-09-15751
  10. 2026-09-20781
  11. 2026-09-22771
  12. 2026-09-25765
  13. 2026-09-26784
  14. 2026-09-28789
  15. 2026-10-04824
  16. 2026-10-08823
  17. 2026-10-09817
  18. 2026-10-10818
  19. 2026-10-11812
  20. 2026-10-13821
  21. 2026-10-16850
  22. 2026-10-17854
  23. 2026-10-18868
  24. 2026-10-19874
  25. 2026-10-20867
  26. 2026-10-21868
  27. 2026-10-22882
  28. 2026-10-23896
  29. 2026-10-24897
  30. 2026-10-25893
  31. 2026-10-26908
  32. 2026-10-28928
  33. 2026-10-29929
  34. 2026-10-30936
  35. 2026-11-01925
  36. 2026-11-02925

What the store shows

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

Yates Media Group. This listing has been in the store since 2024-07-30 and was last updated on 2025-11-26.

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 adiobox: Audio Player for Chrome(OS) 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 adiobox: Audio Player for Chrome(OS) collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Location. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has adiobox: Audio Player for Chrome(OS) asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does adiobox: Audio Player for Chrome(OS) 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 adiobox: Audio Player for Chrome(OS) · Alternatives to adiobox: Audio Player for Chrome(OS)

Where the data comes from: how the catalog is built