Security & Privacy

Data Privacy

Crosscheck's Chrome extension collects developer context alongside your captures to make bug reports actionable. This page explains exactly what data is collected, what is not collected, and how that data is handled.

What the Extension Collects

Data TypeDescriptionWhen Collected
Console LogsMessages logged to the browser console (log, warn, error, info)Continuously while extension is active on the page
Network RequestsURLs, HTTP methods, status codes, timing, and response sizes of network requestsContinuously while extension is active on the page
DOM SnapshotsSerialized DOM mutations recorded by session recording technology for instant replayOn enabled websites only, for the replay buffer (last 1 to 5 minutes, configurable)
ScreenshotsPixel capture of the visible viewport or the full pageOn user action (click capture button)
Screen RecordingsVideo of the browser tab or desktop using the browser's built-in recording capabilitiesOn user action (start/stop recording)
User Action TimelineClicks, keypresses, and navigation events with timestampsContinuously while extension is active on the page
Page MetadataPage URL, title, viewport dimensions, browser infoAt the time of capture

What the Extension Does Not Collect

Crosscheck is designed to avoid capturing sensitive user data:

  • Passwords: The extension does not intercept or capture password field values.
  • Form data content: The content of form inputs (text fields, dropdowns, etc.) is not captured or transmitted.
  • Cookies: Browser cookies are never read, logged, or included in captures.
  • Local storage or session storage: The extension does not access or export the page's storage APIs.
  • Authentication tokens from the page: Tokens used by the application under test are not extracted from headers or storage.
Privacy by Design
The extension only collects data that helps developers reproduce and debug issues. It avoids capturing credentials, personal form data, or authentication material from the page under test.

Data Stays Local Until Shared

All collected data remains in your browser's local memory until you explicitly create a capture and upload it. Browsing with the extension active does not automatically send any data to Crosscheck's servers.

The data flow is:

  • Extension collects DevTools data in local browser memory.
  • You click the capture button to create a screenshot, recording, or replay.
  • Only then is the data saved to your Crosscheck workspace.
  • If you close the tab or navigate away without capturing, the data is discarded.

Instant Replay Buffer

The instant replay feature uses session recording technology to continuously record DOM mutations in memory. This buffer stores approximately the last 120 seconds of page activity. The buffer is automatically recycled. If you do not capture a replay, the buffered data is discarded automatically.

Buffer Size is Configurable
The replay buffer duration can be adjusted in the extension settings. Shorter buffers use less memory. The buffer is always stored locally and never saved unless you explicitly capture a replay.
Last updated: March 2026