Ext Ops Panel
Open dashboard
Permissions and history

Is Jira Compass - AI Ticket Analysis safe to install?

Jira Compass - AI Ticket Analysis asks for 4 browser permissions and 6 site patterns. 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.

Jira Compass - AI Ticket Analysis

Chrome extension by Sharaj · Productivity · Developer

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
Access to specific sites only
Data collection
Declares it collects none
Audience
9 users

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: 6 match patterns.

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

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

9 users

Users
-1 since 01.09
9-11 · 27 readings
2026-10-28: released 1.3.02026-11-03: released 1.4.0
  1. 2026-09-0110
  2. 2026-09-0211
  3. 2026-09-0410
  4. 2026-09-0511
  5. 2026-09-0710
  6. 2026-09-099
  7. 2026-09-1310
  8. 2026-09-1511
  9. 2026-09-1710
  10. 2026-09-219
  11. 2026-09-2510
  12. 2026-09-2611
  13. 2026-09-2810
  14. 2026-10-089
  15. 2026-10-0910
  16. 2026-10-109
  17. 2026-10-1310
  18. 2026-10-1811
  19. 2026-10-1910
  20. 2026-10-2111
  21. 2026-10-2210
  22. 2026-10-2411
  23. 2026-10-2510
  24. 2026-10-3011
  25. 2026-11-0110
  26. 2026-11-0211
  27. 2026-11-049

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.

  1. Changed where it works (changed: optional site access)
  2. Asked for more permissions (10, was 8) (changed: site access)

Versions we have seen

  1. Version 1.4.0 · Changed where it works (changed: optional site access)
  2. Version 1.3.0 · Asked for more permissions (10, was 8) (changed: site access)

Who publishes it

Sharaj, who publishes 35 listings we track. This listing has been in the store since 2025-06-29 and was last updated on 2026-11-02.

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. Toolbox 4 Jira No site access · 5 permissions 3k users ★ 4.4
  2. Task Clarity Runs its code on every site · 2 permissions, 4 site patterns 11 users ★ 5.0
  3. Jira AI Ticket Triager Pro Access to specific sites only · 3 permissions, 2 site patterns 8 users ★ 5.0

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 Jira Compass - AI Ticket Analysis access?
Specific sites only: 6 match patterns. It declares 4 browser permissions.
What data does Jira Compass - AI Ticket Analysis 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 Jira Compass - AI Ticket Analysis asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-11-03.
Does Jira Compass - AI Ticket Analysis 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-04.

Back to Jira Compass - AI Ticket Analysis · Alternatives to Jira Compass - AI Ticket Analysis

Where the data comes from: how the catalog is built