Session replay for privacy-conscious teams
Some teams will not adopt session replay unless the defaults are conservative and the data can live on infrastructure they control. That is the case Replayly is built for.
Which features matter
Privacy controls
Masking, Do Not Track, consent mode, text masking, and CSS block selectors.
Self-hosting
Run the app, database, and object storage in a place you choose.
Session replay
Still get a usable player and filters once the privacy bar is met.
The job to be done
Privacy-conscious teams are usually answering a reviewer, a customer, or their own policy: what is captured, where it is stored, and how a visitor can opt out. Replayly's product answers are documented on the privacy controls page, the fact sheet, and the public privacy policy.
This is not legal advice. You still need your own policy, notices, and — where required — agreements. The software is designed so you are not forced to disable masking just to see whether the tracker works.
A practical rollout
Self-host if residency is a requirement. Leave input masking on. Enable consent mode if your site already has a banner. Sample a small percentage of traffic, review a few sessions, and only then raise the volume.
If a hosted tool is enough and you are comfortable with that vendor's regions, you may not need Replayly. The compare pages exist so you can make that call without marketing fog.