DeepScope extension privacy
Last updated:
What DeepScope does
DeepScope detects technologies on active HTTP and HTTPS web pages and shows the observations behind each supported detection. Automatic scanning is enabled by default. You can turn it off in Settings and inspect pages manually through the side panel.
Website information used for inspection
Inspection can read the page URL and hostname, DOM markers, metadata, script and resource URLs, selected response headers, cookie names, storage key names, JavaScript globals, and bounded excerpts from supported page resources. These observations help identify technologies and explain detections.
DeepScope does not intentionally collect passwords, cookie values, storage values, payment details, health information, precise location, or personal communications. Page-derived evidence can contain incidental sensitive text. Stored evidence is bounded and processed by pattern-based redaction; those controls do not guarantee that every sensitive value is removed.
Local storage and diagnostics
Detection results, bounded evidence, snapshots, replay summaries, and matcher state remain in the browser profile’s extension storage. Recent snapshots let you revisit inspections in History.
DeepScope also keeps a separate bounded local diagnostic journal of build, context, lifecycle, timing, and error information. Settings can clear technology data. Diagnostics can clear diagnostic records independently. Removing the extension removes its extension storage.
The Copy report action in Diagnostics copies a support report to your clipboard. It does not upload a report automatically. Review the report before sharing it with support or anyone else.
Network requests and sharing
The current extension source does not upload visited URLs, page HTML, observations, detection results, replay traces, or diagnostic records to a Kaiju backend. Detector definitions and application assets are packaged with the extension.
Inspection can make bounded requests to the inspected website, including a request for response headers and requests for selected same-origin scripts or stylesheets. Those requests go to the inspected site’s origin, whose own privacy practices apply. Detection happens locally in the browser.
DeepScope does not sell inspection data or use it for advertising. Data use is limited to the extension’s disclosed technology-inspection features, in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Browser permissions
- HTTP and HTTPS site access: permits automatic inspection of active web pages. It is persistent host access, rather than access granted only by a toolbar click. Turning automatic scanning off controls scanning behavior; it does not remove the granted host permission.
- activeTab: supports access to the selected tab following a user action.
- scripting: runs packaged observation scripts in supported pages.
- storage: saves settings, results, caches, and diagnostics locally.
- offscreen: supports local matcher work under Chrome’s extension lifecycle.
- sidePanel: displays the extension beside the website in Chrome.
- clipboardWrite: supports user-requested copying, including diagnostic reports.
This website
This notice covers the browser extension. The product page is part of Kaiju’s website and uses its hosting, privacy preferences, and configured visitor integrations. See the website privacy notice and cookie notice for those activities. The interactive demo uses fictional observations and does not inspect your tabs or run the extension.
Contact and changes
Contact hello@kaiju.industries about DeepScope privacy. We will update this notice when supported releases change their data handling or permissions.