PII masking

What never leaves the visitor's browser, and how to mask more.

Privacy & compliance

Masking happens in the browser, before anything is transmitted. Passwords, payment fields, and text inputs are masked by default — the characters are replaced at capture time, so the real values never reach our servers and cannot be recovered from a recording.

Masking your own elements

Add a masking class to any element whose contents should be redacted in replay — an account balance, a customer name, a medical detail.

html
<!-- contents replaced with blocks in replay -->
<div class="ds-mask">Account balance: ₹48,200</div>

<!-- element is not recorded at all -->
<div class="ds-block">
  <iframe src="/sensitive-embed"></iframe>
</div>
Audit this properly once, on the pages that handle real customer data, rather than trusting defaults. Defaults cover the obvious input types; they can't know that your third <div> is a national ID number.

Related

Still have a question?

Support is included on every plan, including Free. Tell us what you're trying to do and we'll point you at the right page — or fix the docs.

Contact support