Privacy policy

Last updated: 4 September 2026

Summary

Debug Inspector for Coveo does not collect, store, transmit, or sell any user data.

What it does

The web app parses a search response that you paste or drop into the page. The Chrome extension adds a Inspect Coveo panel to DevTools; while DevTools is open on a tab, it reads that tab's Coveo Search API requests and responses through the chrome.devtools.network API and renders an analysis locally in the panel.

Data handling

No collection. Neither the web app nor the extension sends data to the author or any third party. There are no analytics, telemetry or reporting calls of any kind, and there is no server component. See Website hosting for the one thing this does not cover.
No persistence. Captures are held in memory for the lifetime of the DevTools session and discarded when DevTools or the tab closes. Nothing is written to disk, localStorage, chrome.storage, or any remote service.
No account or identity. There is no sign-in and no user identifier.
Credential redaction. Before a captured request is displayed, Authorization, Cookie, Proxy-Authorization, Set-Cookie and x-api-key header values are replaced with ***redacted***. Credentials carried in the URL query string (access_token, api_key, token and similar) are redacted the same way.

Replay

The panel offers an optional Replay with debug action. When you click it, the extension re-issues the selected search request from the inspected page with debug: true added, so the response includes ranking detail. It runs only on your explicit action, goes only to the endpoint the page already called, and its result is displayed locally and never stored or transmitted elsewhere.

Permissions

The extension declares no permissions and no host_permissions. It works solely through the DevTools extension API, scoped to the tab whose DevTools window you have open.

Website hosting

This website and the web app are served as static files by a third-party hosting provider. Like any web server, it writes standard request logs that include visitor IP addresses, for security and abuse prevention. Those logs are held by the hosting provider under its own privacy policy; this project neither receives nor uses them. Nothing you paste into the web app is included — parsing happens entirely in your browser and is never uploaded.

The Chrome extension loads nothing from this site, so it is unaffected.

Contact

Questions about this policy can be raised as an issue on the project's source repository.