Ext Ops Panel
Open dashboard
Permissions and history

Is Overwatch - AI Incident Resolution safe to install?

Overwatch - AI Incident Resolution asks for 9 browser permissions and 4 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.

Overwatch - AI Incident Resolution

Chrome extension by admin · Productivity · Developer

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
Declares it collects none
Audience
8 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 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: 4 match patterns.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

Pages it runs its code on

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

Show the remaining 6
  • *://*.datadoghq.eu/* datadoghq.eu and all its subdomains
  • *://*.newrelic.com/* newrelic.com and all its subdomains
  • *://*.pagerduty.com/* pagerduty.com and all its subdomains
  • *://*.signoz.io/* signoz.io and all its subdomains
  • *://*.elastic.co/* elastic.co and all its subdomains
  • *://*.prometheus.io/* prometheus.io and all its subdomains

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.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 1 site pattern.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

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

8 users

Users
+4 since 01.09
4-9 · 27 readings
2026-09-08: released 3.6.82026-09-10: released 3.7.0
  1. 2026-09-014
  2. 2026-09-036
  3. 2026-09-045
  4. 2026-09-064
  5. 2026-09-085released 3.6.8
  6. 2026-09-098
  7. 2026-09-107released 3.7.0
  8. 2026-09-138
  9. 2026-09-159
  10. 2026-09-168
  11. 2026-09-257
  12. 2026-09-268
  13. 2026-09-287
  14. 2026-10-048
  15. 2026-10-087
  16. 2026-10-098
  17. 2026-10-107
  18. 2026-10-118
  19. 2026-10-167
  20. 2026-10-187
  21. 2026-10-218
  22. 2026-10-227
  23. 2026-10-248
  24. 2026-10-299
  25. 2026-11-019
  26. 2026-11-038
  27. 2026-11-048

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.

Versions we have seen

  1. Version 3.7.0
  2. Version 3.6.8

Who publishes it

admin. This listing has been in the store since 2026-02-28 and was last updated on 2026-09-10.

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. Zabbix Supervision Hub No site access · 4 permissions 11 users
  2. Sentinel Owner Alert Access to specific sites only · 2 permissions, 1 site pattern 5 users
  3. Monitoring Plus シナリオ監視作成 Runs its code on every site · 2 permissions, 1 site pattern 36 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 Overwatch - AI Incident Resolution access?
Specific sites only: 4 match patterns. It declares 9 browser permissions.
What data does Overwatch - AI Incident Resolution 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 Overwatch - AI Incident Resolution asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Overwatch - AI Incident Resolution 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-04.

Back to Overwatch - AI Incident Resolution · Alternatives to Overwatch - AI Incident Resolution

Where the data comes from: how the catalog is built