Ext Ops Panel
Open dashboard
Permissions and history

Is Zendesk Ticket Notifier safe to install?

Zendesk Ticket Notifier asks for 5 browser permissions and 2 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.

Zendesk Ticket Notifier

Chrome extension by cyber192 · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 5 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
2 kinds of data declared
Publisher
No store badges
Audience
230 users · 5.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

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

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 2 site patterns.

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.

How usual this is for its category

In Productivity · Workflow, 19% 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 5 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

230 users

Users
+49 since 01.09
181-230 · 33 readings
2026-09-14: released 7.7.02026-09-23: released 7.16.12026-09-25: released 7.26.02026-09-26: released 7.29.12026-10-03: released 10.8.92026-10-11: released 11.0.0
  1. 2026-09-01181
  2. 2026-09-02186
  3. 2026-09-04190
  4. 2026-09-05193
  5. 2026-09-06189
  6. 2026-09-08188
  7. 2026-09-09200
  8. 2026-09-13195
  9. 2026-09-15201
  10. 2026-09-17214
  11. 2026-09-20217
  12. 2026-09-21216
  13. 2026-09-25217released 7.26.0
  14. 2026-09-26218released 7.29.1
  15. 2026-09-28217
  16. 2026-10-04214
  17. 2026-10-08217
  18. 2026-10-11211released 11.0.0
  19. 2026-10-13213
  20. 2026-10-16217
  21. 2026-10-17216
  22. 2026-10-18212
  23. 2026-10-19210
  24. 2026-10-21208
  25. 2026-10-22211
  26. 2026-10-23210
  27. 2026-10-24213
  28. 2026-10-25211
  29. 2026-10-26215
  30. 2026-10-28217
  31. 2026-10-30225
  32. 2026-11-01229
  33. 2026-11-02230

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.

  1. Asked for more permissions (7, was 6)
  2. Swapped which permissions it asks for
  3. Asked for more permissions (6, was 5)

Versions we have seen

  1. Version 11.0.0
  2. Version 10.8.9 · Asked for more permissions (7, was 6)
  3. Version 7.29.1
  4. Version 7.26.0
  5. Version 7.16.1 · Swapped which permissions it asks for
  6. Version 7.7.0 · Asked for more permissions (6, was 5)

Who publishes it

cyber192, who publishes 3 listings we track. This listing has been in the store since 2026-03-18 and was last updated on 2026-10-16.

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. Zendesk Ticket Color Coder Access to specific sites only · 2 permissions, 2 site patterns 26 users ★ 4.0
  2. Zendesk Ticket Tracker Access to specific sites only · 3 permissions, 6 site patterns 8 users ★ 5.0
  3. ZenNotification Access to specific sites only · 4 permissions, 1 site pattern 53 users

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 Zendesk Ticket Notifier access?
Specific sites only: 2 match patterns. It declares 5 browser permissions.
What data does Zendesk Ticket Notifier collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Zendesk Ticket Notifier asked for more permissions over time?
Its permissions changed 3 times while we watched, most recently on 2026-10-03.
Does Zendesk Ticket Notifier 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 Zendesk Ticket Notifier · Alternatives to Zendesk Ticket Notifier

Where the data comes from: how the catalog is built