Data masking

Keep private data out of every screenshot and replay

Add a CSS class to hide or mask sensitive parts of your site, so customer details never end up in a bug report. Password fields are always hidden.

Data masking

You decide what a report can show

Mark what is private once in your page, and every capture follows the rule.

Hide an elementEnterprise

Add the class sf-exclude and the element is left out of screenshots and replays.

Mask a valueEnterprise

Add sf-mask to scramble what an element shows, so the layout stays but the data does not.

Keep something visibleEnterprise

Add sf-unmask to show an element that would otherwise be masked, such as a name you need to see.

Passwords are always hidden

Password fields are never captured, and what people type into inputs is masked in session replay.

Blur anything by hand

Reporters can blur sensitive parts of a screenshot with the Blur tool before they send it.

FAQ

Frequently asked questions

Everything you need to know before you start collecting feedback.

Still have questions?

Our team replies fast and is happy to walk you through PinMarks.

Talk to us →

Add a CSS class to the element: sf-exclude hides it, sf-mask masks it and sf-unmask shows it.

In screenshots and in session replays, so private data does not end up in a report.

Yes. Password fields are always hidden on every plan, and what people type into inputs is masked in session replay.

Private data masking is on the Enterprise plan.

Yes. They can blur any part of a screenshot with the Blur tool before they send it.

No credit card required

Stop chasing bugs.
Start pinning them.

Start collecting visual feedback today — fix bugs faster and keep your whole team in the loop.

15-day free trial · No credit card · Cancel anytime