Privacy information

This technical description replaces the legacy page's inaccurate claims about cookies and anonymous-only collection. A complete operator privacy policy has not yet been published here.

What tracking records

Pipetrace records pages, referral sources, browser and device context, approximate country, interactions and supported performance measurements. Websites can also send named actions, revenue events and their own identifiers through the tracking API.

Browser identifiers and storage

The script persists a random visitor identifier using browser storage, including a first-party cookie, localStorage and IndexedDB. A per-tab session identifier groups activity into visits. The server can use an IP/user-agent/site hash for short-lived identifier recovery. A generated visitor name labels a browser identity; it does not make the underlying records anonymous.

URLs and custom data

Page and referrer URLs can contain query parameters. Custom events and identify calls contain the values supplied by the website. Avoid sending sensitive values in URLs, event properties or identifiers.

Visitor controls

The browser script supports opt-out and stops further browser collection when opt-out is enabled. Opting out does not erase events already received by the server. See the data collection reference for implementation details.

Backend retention and deletion

Default trace, log and correlation retention is 14 days; metric retention is 90 days. Canonical queries hide expired records immediately. Physical deletion uses a separate tracked maintenance operation that pauses admission, accounts for outstanding writes, writes neutral identity/version markers and verifies the purge. Failed or uncertain cleanup stays pending with admission closed. Retention shortening requires the same verified operation; increasing retention cannot restore purged data.

Project deletion denies access and intake immediately and reports completion only after verified backend physical cleanup and bounded control-data deletion. Neutral markers and referenced proof can remain for safe replay handling; minimal owner completion receipts last 30 days. Backups are separate operator-held copies with their own protection and lifetime. Website-only deletion removes its browser records and queues backend correlation cleanup while preserving unrelated backend telemetry.

The browser opt-out setting does not control backend exporters and does not erase previously received data. These are technical implementation facts, not an operator legal policy.

Legacy browser history

Backend retention does not add a scheduled purge for legacy raw browser analytics events. The browser runtime does not schedule automatic deletion after 90 days. Site deletion removes its associated analytics records. Retention, account-data handling and operator contact details need to be set out in the operator's published policy.