Last updated:
NUURBY Sentinel is a Chrome extension companion to your self-hosted NUURBY security platform. This page describes what data the extension accesses, where it goes, and what is stored.
Once you configure it with your NUURBY instance's URL and access key, the extension reads: your security posture score, alert summaries and recent alerts, open vulnerability counts, open incident counts, and threat-hunting search results — all fetched directly from the instance URL you provide, using the same authenticated API your NUURBY web dashboards already use.
Nowhere except between your browser and the NUURBY instance URL you configure. The extension does not send any data to NUURBY's developers, to any analytics service, or to any third party of any kind. There is no backend server operated by the extension itself — it is a direct client to your own infrastructure.
Your instance URL, access key, and notification preferences are stored in Chrome's built-in extension storage (chrome.storage), scoped to this extension only. A small local list of already-notified alert IDs is kept to avoid duplicate notifications. None of this is transmitted anywhere beyond your own NUURBY instance.
Host permission — requested at runtime, scoped to only the specific domain you enter in Settings, needed to make authenticated API calls to your instance. Notifications — used to alert you of new critical/high-severity alerts. Storage — used to save your configuration locally. Alarms — used to periodically check for new alerts on the interval you set. Context menus — used to add the "Investigate with NUURBY" right-click option.
If this extension's data practices change in a future version, this page will be updated accordingly.