Privacy policy for the Hitinspect extension. Last updated: October 7, 2026.
Capture control
HitInspect reads matching Adobe Analytics AppMeasurement (/b/ss/) and Adobe Experience Platform Web SDK (/v{n}/interact and /v{n}/collect) requests only while its DevTools panel is visible. Closing or switching away from the panel stops new capture. Child tabs opened by the inspected page can continue into the original panel while it remains visible.
Data processed locally
Matching request URLs, query parameters and validated Web SDK event bodies are parsed and displayed locally. They can include page names, URLs, custom variables, visitor or device identifiers, product and purchase information, geographic values and Activity Map values. The inspected website determines the contents of its analytics payloads.
HitInspect does not send captured data, variable dictionaries, comparisons or exports to its developer or external services. It has no telemetry, does not set cookies and does not require an Adobe account connection. It reads the network requests already made by the inspected page.
Storage and retention
The newest 200 real analytics calls per inspected root tab are retained temporarily in chrome.storage.session. Navigation markers do not use this allowance. Chrome storage quota pressure can force a lower limit; HitInspect shows a warning if that occurs.
Existing history survives panel close and is removed by Clear, closing its root tab, or restarting Chrome. Display preferences, variable dictionaries and project profiles are stored in chrome.storage.local and persist across browser restarts. Chrome Sync is not used. Uninstalling the extension removes its stored data.
Identity masking and exports
Optional masking hides known Adobe identity fields (mid, aid, vid, fid, mcorgid and sdid) and Web SDK identityMap IDs across details, raw data, comparisons, copy actions and JSON or CSV exports. It changes the displayed or exported representation; the temporarily stored original is not rewritten.
Masking is not a general anonymizer. Personal information in custom variables, page URLs or other fields may remain visible and may be included in exports. Exported files are created only when you request them and remain under your control; you decide independently whether to share them.
Permissions
- webRequest reads matching analytics request URLs and bodies for local inspection. It does not block or modify requests.
- webNavigation associates child tabs with the inspected root tab and adds navigation markers to the request timeline.
- storage keeps temporary request history and persistent preferences, dictionaries and project profiles in Chrome's local storage APIs.
- Access to all sites supports arbitrary inspected sites, first-party Adobe collection domains and custom proxy hosts. Capture is limited to matching analytics requests associated with a visible panel and its adopted child tabs. Unrelated requests are not retained.
Limited Use
HitInspect uses data obtained through Chrome APIs only to provide its user-facing analytics inspection features. This use complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Captured data is not sold, used for advertising, transferred to the developer or third parties, or made available to the developer for human review.
Your control
Close or switch away from the panel to stop new capture. Use Clear to delete retained history. Close the inspected root tab or restart Chrome to remove its session history. Remove the extension through chrome://extensions to delete its stored data.
Changes and contact
Policy changes are reflected on this page with a revised update date. For privacy questions, open an issue in the project repository. Avoid including sensitive request payloads in public issues.
HitInspect is an independent developer tool, not affiliated with or endorsed by Adobe Inc.