Auto‑Captured Data

UI Zap attaches useful context to every report so engineers can reproduce issues quickly. Below is a breakdown of the data we collect by default when available in the browser.

Console logs

• Levels: log, info, warn, error (and related console output).
• Fields: message text (stringified), timestamp, and origin info when the browser provides it (file/line/column).
• Errors: stack traces and error name/message when available.
• Notes: collapsed groups and non‑string payloads are captured by value where the browser exposes them.

Network requests

• Scope: XHR/fetch calls initiated from the page (subject to browser/CORS/CSP limitations).
• Fields: method, URL, status code, duration, response type, and headers metadata.
• Size & timing: content length (if provided), start/end timestamps, and calculated duration.
• Limitations: resources within third‑party iframes or blocked by CSP may not be visible to the extension.

Environment

• Page: URL, title, and referrer (when available).
• Device: viewport width/height and device pixel ratio.
• Runtime: browser name/version, OS, locale, and time zone.

Reproduction cues

• Events: clicks/taps, input/change/submit events, scrolls, and navigation.
• Structure: ordered steps with timestamps to show sequence and timing.
• Targeting: references to elements (e.g., simplified CSS selectors) to help identify where interactions occurred.
• Input privacy: we record field names and event types, not the plaintext contents of sensitive inputs.