Ext Ops Panel
Open dashboard
Permissions and history

Is Sonic Space 2.0 safe to install?

Sonic Space 2.0 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 2 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
Publisher
No store badges
Audience
174 users · 4.7/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

174 users

Users
+32 since 01.09
140-174 · 35 readings
  1. 2026-09-01142
  2. 2026-09-02140
  3. 2026-09-05142
  4. 2026-09-06147
  5. 2026-09-07144
  6. 2026-09-08153
  7. 2026-09-09159
  8. 2026-09-13166
  9. 2026-09-15165
  10. 2026-09-17159
  11. 2026-09-20164
  12. 2026-09-25166
  13. 2026-09-27161
  14. 2026-09-28159
  15. 2026-10-04165
  16. 2026-10-08169
  17. 2026-10-09167
  18. 2026-10-10173
  19. 2026-10-11165
  20. 2026-10-13161
  21. 2026-10-14161
  22. 2026-10-16153
  23. 2026-10-17152
  24. 2026-10-18147
  25. 2026-10-19152
  26. 2026-10-20156
  27. 2026-10-21157
  28. 2026-10-22164
  29. 2026-10-23160
  30. 2026-10-24161
  31. 2026-10-25159
  32. 2026-10-28166
  33. 2026-10-29158
  34. 2026-10-30155
  35. 2026-11-01174

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

toxic, who publishes 208 listings we track. This listing has been in the store since 2010-09-18 and was last updated on 2017-03-02.

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

Back to Sonic Space 2.0 · Alternatives to Sonic Space 2.0

Where the data comes from: how the catalog is built