PureStats documentation

Session replay and heatmaps

Configure privacy-protected session recordings, click heatmaps and scroll reports using S3-compatible storage or HTTPS WebDAV on a Hetzner Storage Box.

Session replay is an optional site feature for investigating interaction problems that aggregate analytics cannot explain. Recordings are disabled until a site owner selects and verifies storage under Site settings → Session replay.

PureStats loads the separate /pf-replay.min.js module only for enabled sites. The core tracker remains unchanged in size, and recordings follow the site's consent mode, Do Not Track preference, path exclusions and traffic filtering rules.

Privacy defaults

Replay deliberately captures less than the page itself exposes:

  • All text nodes, form inputs and content-editable values are masked before upload.
  • Password fields and elements marked with data-purestats-block, data-sensitive or .purestats-block are excluded completely.
  • URL query strings and fragments are removed from captured element attributes.
  • Canvas recording, inline images and font collection are disabled.
  • Server-side sanitization repeats the masking before a chunk is stored.

Review your own pages before enabling replay. Block any component that may expose private visual context even after text masking.

Storage and retention

Production recordings are written directly to the private storage configured for the site. Access credentials are encrypted at rest. Local replay storage is accepted only in development and automated tests.

When available, PureStats-managed storage provides a separate private folder for every site without requiring storage credentials. PureStats assigns the folder from the immutable site ID; site owners cannot change its path or access another site's recordings. Saving this option does not enable recording.

Alternatively, choose S3-compatible for your own object-storage bucket, or Hetzner Storage Box for your own HTTPS WebDAV connection. For a Storage Box, enable WebDAV in the Hetzner Console and use a writable subaccount restricted to a dedicated replay folder. Enter its account-specific https://u123456-sub1.your-storagebox.de endpoint, relative base folder, username and password. The endpoint must not contain credentials, a custom port or a path. A Storage Box is not an S3 endpoint.

Save the configuration and run Test connection before enabling collection. This verifies upload, download and deletion of a temporary object. Changing the provider or storage location requires removing existing recordings first; rotating credentials for the same location does not.

Recordings expire after exactly 30 days. The daily retention job deletes expired objects and database metadata. A configurable storage watermark warns at 80% and pauses new uploads at 100% instead of exceeding the limit. Privacy deletion requests remove matching replay objects as well as analytics records.

Watermarks are technical storage safeguards, not commercial account quotas. They count objects managed by PureStats, not unrelated files or the box's total free capacity. The operator must also monitor available capacity in Hetzner and leave headroom for other files. Deleting a file manually does not replace PureStats retention or privacy deletion.

Reviewing recordings

Open More → Session replays to filter sessions by date and page, inspect click and scroll heatmaps, and launch the sandboxed replay player. Only the site owner and PureStats administrators may list, view or delete recordings. Every list, playback and deletion action is written to the replay access audit log.

Replay is a diagnostic tool, not a replacement for aggregate analytics. Keep it disabled when the additional detail is not necessary for a defined investigation.