Masking policies
Keeping customer data out of your recordings, enforced rather than remembered.
A screen recording of your product is a recording of your customers. Masking policies remove sensitive values before frames are encoded, so they never reach storage.
Rule types
- Detector — built-in patterns for emails, phone numbers, card numbers, API keys, JWTs and IBANs.
- Selector — any DOM element matching a CSS selector. Best for known regions like a customer list.
- Region — a fixed rectangle of the frame, in percentage coordinates. Use when the layout is stable.
- Pattern — your own regular expression, applied to on-screen text via OCR and to the transcript.
Workspace enforcement
On Team and above, an admin can mark a policy as enforced. Enforced policies apply to every recording in the workspace and cannot be disabled by the person recording.
Masking applies to derived assets too
A value masked in the video is also removed from the transcript, the generated guide, the screenshots and the search index. If you only blur the frames yourself, the transcript will still contain it.
Example policy
json
{
"name": "Production safeguards",
"enforced": true,
"rules": [
{ "type": "detector", "detectors": ["email", "card", "api_key", "jwt"] },
{ "type": "selector", "selector": "[data-customer-name]", "style": "blur" },
{ "type": "region", "rect": [0, 0.12, 0.18, 0.88], "style": "pixelate" },
{ "type": "pattern", "regex": "ACC-[0-9]{8}", "style": "redact" }
]
}