Ext Ops Panel
Open dashboard
Permissions and history

Is Jellyfish safe to install?

Jellyfish 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.

Jellyfish

Chrome theme by JimF777

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
57 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

57 users

Users
+6 since 31.08
50-63 · 29 readings
  1. 2026-08-3151
  2. 2026-09-0253
  3. 2026-09-0355
  4. 2026-09-0456
  5. 2026-09-0554
  6. 2026-09-0750
  7. 2026-09-0851
  8. 2026-09-1355
  9. 2026-09-1553
  10. 2026-09-1754
  11. 2026-09-2058
  12. 2026-09-2156
  13. 2026-10-0455
  14. 2026-10-0856
  15. 2026-10-0955
  16. 2026-10-1059
  17. 2026-10-1363
  18. 2026-10-1660
  19. 2026-10-1758
  20. 2026-10-1860
  21. 2026-10-1957
  22. 2026-10-2055
  23. 2026-10-2154
  24. 2026-10-2251
  25. 2026-10-2454
  26. 2026-10-2558
  27. 2026-10-2861
  28. 2026-10-2959
  29. 2026-11-0157

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

JimF777, who publishes 9 listings we track. This listing has been in the store since 2018-05-11 and was last updated on 2018-07-21.

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

Where the data comes from: how the catalog is built