Features / Cookieless & privacy-first
Cookieless session replay and input masking
Privacy that's a property of how it's built, not a policy you have to trust.
What it does
- No cookies means no consent-banner trigger Sessions are identified without setting a cookie, so recording doesn’t add a new item to your cookie banner or change your consent posture — one less thing to explain to a privacy team or a user.
- Inputs masked at the source Text typed into fields is masked in the browser, before it’s ever sent — not redacted on a server after the fact. What could have been captured never leaves the visitor’s machine in the first place.
- Under 15 KB on the wire, per session The tracker records structured DOM events, not video or screenshots, so a typical session adds well under 15 KB to the page — a real constraint that also happens to mean less data collected, not more.
- Retention windows you set, per site Choose how long tapes are kept, per site, and they expire on schedule automatically. Storage stays proportional to what you actually need retained, not to everything ever recorded.
Most session replay tools ask you to trust a privacy policy. This one is built so there’s less to trust in the first place — the constraints are in the recorder, not in a document describing what the recorder promises not to do.
Cookieless is a design decision, not a checkbox
Sessions are identified and stitched together without setting a tracking cookie. That’s not a “cookieless mode” toggled on top of a cookie-based system — there’s no cookie to disable. Practically, it means adding session replay to a site doesn’t add a line to your cookie banner or change what you’re asking visitors to consent to, because nothing about how visitors are identified changed.
Masking happens before the data exists to leak
Text typed into form fields is masked in the browser, at the point of capture. This is a meaningfully different guarantee than “we redact sensitive fields on our servers” — a value that’s masked at the source was never transmitted as plain text in the first place, so there’s no window where an unmasked value exists anywhere except the visitor’s own browser. If a transcript shows “typed in a field,” that’s the whole record of the event — not a redacted version of something more detailed sitting in a log somewhere.
The trade-off is real and deliberate: if a bug depends on the exact string someone typed, replay will tell you the field was filled and stop there. That’s covered in more depth in reproducing bugs you can’t trigger — for most debugging, knowing that a field was interacted with matters more than knowing what was typed into it.
Small on the wire because it’s structured, not recorded
The tracker sends structured DOM events — what changed, not a video frame or a screenshot — which keeps a typical session under 15 KB. That’s a performance property (a heavy tracking script is its own kind of user harm) and a privacy property at the same time: there’s less raw data leaving the browser to begin with, by construction, not by later filtering.
Retention that expires on schedule, not by request
Set a retention window per site, and tapes age out automatically once they pass it — no manual purge, no ticket to file when someone asks how long recordings are kept. Storage stays proportional to the window you chose rather than growing forever, and the answer to “how long do you keep this” is a setting you can point to rather than a policy someone has to go verify.
The regulatory side of this — what GDPR actually requires versus what’s commonly assumed — is covered separately in session replay and GDPR.