Privacy

The browser tracker sends the configured domain, current page path and query string, browser-provided referrer, project-scoped visitor and session identifiers, UTM attribution, and page-view, engagement, or custom-event information as appropriate. Enabled replay and heatmap features send their respective interaction data.

Image tracking pixels and graphs with track=1 receive only metadata exposed by an image request. This can include the embedding URL, campaign parameters, user agent, network-derived identifier, device and operating-system inference, and supported edge location. They cannot read browser storage, viewport dimensions, engagement, or page interactions.

Anonymous visitor, session, and customer-provided tracking identifiers are hashed with project context before storage. Pageview location is derived from supported hosting-edge country and city data. Raw IP addresses are not stored with pageviews.

• Do not put email addresses, names, passwords, payment details, or other sensitive personal information in an event name or properties.
• Avoid placing sensitive values in page paths or query strings on pages that use the tracking script.
• Remove referrerpolicy="unsafe-url" from image embeds when a full page URL could contain sensitive query data.
• Review your own privacy notice, consent requirements, and applicable law before deploying analytics.