Mask text and inputs or block sensitive elements before events leave the browser.
Build your own compliance record
When a dispute lands, replay the exact session
rrweb gives you the recorder and open event format to build an audit-grade record into your own product: masked at capture, stored in your region, retained and erased on your terms. A packaged compliance suite keeps that evidence in its cloud; rrweb lets you keep it in yours.
session #8241 · capture policy
in the browser
card4242 4242 4242 4242
emaildana@acme.com
nat_id82-441-9930
masked before it leaves the browser
transmitted
card•••• •••• •••• 4242
email[masked]
nat_id[masked]
A complete record, with no tagging overhead
One recorder captures the whole session as a typed event stream. There are no analytics tags to place, maintain, or reconcile, and no gaps where an untagged interaction went unrecorded.
- Capture navigation, clicks, inputs, and DOM changes with millisecond timestamps.
- Skip the instrumentation project that tag-based tools require before they collect anything.
- Keep one continuous record per session, so an investigation never hits a blank stretch.
session capture · complete record
one recorderno tags · no gaps
manual tagginggaps between tags
clickinputnavmutation
Resolve complaints and disputes with the session itself
Store a safe subject identifier as recording metadata and mask sensitive fields before events leave the page. Your investigators search the subject, filter by time or route, and open the exact session behind a case.
- Go from a complaint reference to the recording that shows what happened in seconds.
- Mark consent, approvals, and disclosures as custom events and jump straight to that moment.
- Give a reviewer the interface evidence, not a reconstruction from memory.
case #DR-3320 · session search
subject dana@acme.com · /checkout
/checkout
Jul 12, 14:32
/billing
Jul 09, 09:18
/account
Jul 02, 17:04
evidence
Cost-effective, and yours to run
The recorder and replayer are open source. Keep recordings inside your own region for data residency, on infrastructure you already operate, with no per-seat platform fee.
- Store structured DOM events, which are lighter to keep than full-motion video.
- Run capture, storage, and replay inside your own compliance boundary.
- Own the open event format, so nothing you build on it depends on us.
data path · residency
record()
eu-central · your infrastructure
third-party vendorno egress
A record you can defend and control
Governance is built into the workflow. Set a retention window, honour erasure requests by subject, and gate replay so only the right people open a recording, for as long as they need it.
- Delete every recording tied to a subject id when an erasure request arrives.
- Expire old sessions automatically against the retention window you set.
- Issue short-lived, role-scoped playback and log who opened which recording.
governance · acct_8123
retention window · 90d erasure · subject_4f2a
replay access log
viewer casey · replay:readexp 300s
viewer robin · tenant mismatchdenied
One data path, and you own every stage of it.
The recorder captures the session, masking removes sensitive values before anything is transmitted, your infrastructure or rrweb Cloud stores and retains it, and replay stays scoped and logged. Nothing in the chain depends on a vendor you cannot audit.
01in the browser
REC
Capture
One recorder turns every interaction into an open event stream.
02before transport
card•••• 4242
email[masked]
id[masked]
Mask
Sensitive fields leave as placeholders, so secrets never travel.
03owned by you
store
index
retain
Your boundary
Store, index, and retain recordings inside your own region.
Self-host or run rrweb Platform in your cloud with a retention window you set.
04scoped and logged
replay:read · 300s
Replay
Short-lived, role-scoped playback, with every view recorded.
Get rrweb your way
Same open recorder, two backends.
Self-host the pipeline
The MIT-licensed pipeline on your own infrastructure. Recordings never leave your compliance boundary, and retention and access follow the rules you already operate.
Run it on rrweb Cloud
Managed ingest, storage, and replay with the same open recorder. Masking still happens in the browser, and you keep control of retention and access. Free tier, no credit card required.
Frequently asked questions
What makes session replay a compliance concern?
A recording is a record of what a real person saw and did, so it is personal data. That is also what makes it useful evidence. The compliance work is deciding what you ever capture, where it is stored, how long you keep it, and who can open it.
Is session replay compatible with GDPR?
It can be, and the implementation decides. Define a lawful purpose, capture only what that purpose needs, mask sensitive fields in the browser before events are transmitted, restrict access and retention, and honour deletion requests. Your legal team should review the final workflow and any consent requirements.
How do I handle a right-to-erasure request?
Store a stable internal subject identifier as recording metadata and resolve real personal details to it on your server. An erasure request then deletes every recording tied to that subject id, and a retention window removes older sessions automatically.
Where is the recording data stored?
Wherever you choose. Self-host the recorder, storage, and replay inside your own region, or run rrweb Cloud for managed ingest and replay. In both cases masking happens in the browser, so the raw sensitive values never reach the store.
Can a recording serve as an audit trail?
Yes. A recording shows what the interface displayed and what was done in it, which is what dispute and complaint reviews need. Mark consent, approvals, and disclosures as custom events so an investigator can open the exact moment on the timeline.
Can I run the whole system in my own cloud?
Yes. rrweb Platform packages the backend as containers you deploy in your own infrastructure, under a commercial license with full source access, maintenance, and support. The recorder and replayer remain MIT-licensed for teams that build and operate their own backend.
Why rrweb over a packaged compliance or session-replay SaaS?
A packaged suite holds the record in its own cloud, priced per seat, in a format only it reads. rrweb gives you the open recorder, event format, and replayer, so you build the audit record into your own product, keep it in your region, and set retention, access, and erasure yourself. Choose the suite when a separate console is acceptable; choose rrweb when the evidence has to stay inside a boundary you can audit end to end.