Sensitive data masking automatically detects and hides sensitive information displayed in web pages. It blurs input fields containing passwords, emails, and credit card numbers, and masks sensitive text visible on the page. This is useful for browser automation workflows that handle real user data, recordings, or live views where sensitive information should not be exposed.Documentation Index
Fetch the complete documentation index at: https://docs.anchorbrowser.io/llms.txt
Use this file to discover all available pages before exploring further.
Sensitive data masking is disabled by default. Enable it when your sessions handle real credentials, financial data, or other PII that should not appear in recordings or live views.
Quick Start
What Gets Masked
When enabled, the extension automatically detects and masks the following without any additional configuration.Input Fields (blurred)
The following input fields are visually blurred withfilter: blur(8px):
- Password fields (
type="password") - Email fields (
type="email") - Phone fields (
type="tel") - Credit card fields (detected by
nameorautocompleteattributes containingcard,cc,cvv,cvc,expir) - SSN fields (detected by
namecontainingssn,social_security) - Token and API key fields (detected by
namecontainingtoken,secret,api_key,access_key,private_key) - One-time code fields (
autocomplete="one-time-code")
Text Content
Sensitive patterns found in visible text on the page are handled in two ways:- Dedicated elements: When an element’s text is primarily a sensitive value (e.g.,
<span>alice@example.com</span>), the entire element is blurred. - Inline text: When a sensitive value is embedded in a larger sentence (e.g., “Contact us at alice@example.com for help”), only the matched portion is replaced with
****.
Custom CSS Selectors
You can specify additional CSS selectors to blur elements that the automatic detection might not cover. Custom selectors can be applied globally or scoped to specific sites.Selector Options
| Option | Type | Description |
|---|---|---|
custom_selectors | string[] | CSS selectors applied globally across all sites. Matched elements are blurred. |
site_selectors | object | Per-site CSS selectors. Keys are hostnames (supports *. wildcard prefix), values are arrays of CSS selectors. |
"example.com"matches onlyexample.com"*.example.com"matchesapp.example.com,dashboard.example.com, etc.
Custom Regex Patterns
For data formats not covered by the built-in patterns, you can define custom regular expressions. Custom patterns follow the same blur-vs-replace logic as built-in patterns.Pattern Options
| Option | Type | Required | Description |
|---|---|---|---|
regex | string | Yes | A regular expression pattern to match sensitive data. |
mask | string | No | Replacement string for matched text. Defaults to ****. |
Configuration Reference
| Option | Type | Default | Description |
|---|---|---|---|
active | boolean | false | Enable or disable sensitive data masking. |
custom_selectors | string[] | [] | Additional CSS selectors to blur globally. |
site_selectors | object | {} | Per-site CSS selectors keyed by hostname. |
custom_patterns | object[] | [] | Custom regex patterns with optional replacement strings. |
Related Features
- Recording - Session recordings where sensitive data masking prevents PII exposure
- Browser Live View - Live view where masked data stays hidden from observers
- Stealth - Bot detection avoidance (separate concern from data masking)

