Session replay without the creep factor.

Session replay is the most useful debugging tool of the last decade. It's also the easiest to misuse. The same recording that shows you a broken checkout can capture an email address, a credit card field, or a private message.

The rule is simple: record interaction, not identity.

What to mask by default

• All input fields — text, email, password, search. Always.
• Anything inside a form labelled with personal data.
• Profile photos, avatars, message threads, account balances.
• Anything served from a logged-in subdomain you haven't explicitly cleared.

What's actually useful to see

Mouse paths, scroll depth, clicks, rage clicks, dead clicks, network errors, console errors, time spent per section. That's where the bugs live. None of it requires knowing who the person is.

Consent that doesn't lie

Under GDPR and ePrivacy, replay is not anonymous analytics — it requires explicit opt-in before recording starts. Not a pre-checked box. Not a banner that auto-accepts after 5 seconds. A real click on a real button.

Catch before they bounce ships with consent-aware mode off by default — you flip it on the day you're ready, and the tracker simply does nothing until the visitor agrees. No retroactive recording, no buffered events.

Retention is part of privacy

We keep replays for 30 days on most plans, 90 on Pro, then they're gone. Long retention is not a feature, it's a liability. If you can't justify keeping a recording for six months, you shouldn't keep it for six months.

Done well, replay feels like watching usability tests you didn't have to run. Done badly, it's surveillance with a dashboard. The difference is whether you'd be comfortable showing the recording to the person you recorded.