Ext Ops Panel
Open dashboard
Permissions and history

Is JWT.io Viewer safe to install?

JWT.io Viewer asks for 1 browser permission and 1 site pattern. 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.

JWT.io Viewer

Chrome extension by elcimar · Productivity · Developer

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
Access to specific sites only
Data collection
Declares it collects none
Publisher
Featured
Audience
385 users · 3.0/5

What data it declares

The developer declares that it does not collect or use your 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 does not link 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

When you add it, Chrome asks you to allow it to:

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

Specific sites only: 1 match pattern.

Routine for an extension

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 1 browser permission.

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

385 users

Users
-26 since 01.09
383-411 · 32 readings
  1. 2026-09-01411
  2. 2026-09-02401
  3. 2026-09-04402
  4. 2026-09-06401
  5. 2026-09-07399
  6. 2026-09-08403
  7. 2026-09-09402
  8. 2026-09-13391
  9. 2026-09-15390
  10. 2026-09-17402
  11. 2026-09-20408
  12. 2026-09-21409
  13. 2026-09-25407
  14. 2026-09-27402
  15. 2026-09-28399
  16. 2026-10-04393
  17. 2026-10-08392
  18. 2026-10-09387
  19. 2026-10-10390
  20. 2026-10-13393
  21. 2026-10-16402
  22. 2026-10-17403
  23. 2026-10-18401
  24. 2026-10-22402
  25. 2026-10-23398
  26. 2026-10-24400
  27. 2026-10-25397
  28. 2026-10-26394
  29. 2026-10-28397
  30. 2026-10-30393
  31. 2026-11-01383
  32. 2026-11-02385

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

elcimar. This listing has been in the store since 2023-06-30 and was last updated on 2023-06-30.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. JWT Parser No permissions at all · No permissions declared 6 users
  2. JWT Decoder No site access · 1 permission 1k users ★ 4.5
  3. JWT Decoder No site access · 1 permission 2 users (last published figure)

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 JWT.io Viewer access?
Specific sites only: 1 match pattern. It declares 1 browser permission.
What data does JWT.io Viewer collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has JWT.io Viewer asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does JWT.io Viewer 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 JWT.io Viewer · Alternatives to JWT.io Viewer

Where the data comes from: how the catalog is built