Mask sensitive data (emails, phone numbers, credit cards, SSNs) in text with configurable masking patterns.
Replace supported personal and payment identifiers in text before sharing logs, examples, tickets, or test data. The tool examines the entered text for email addresses, phone numbers, credit card numbers, and Social Security numbers, then applies the configured masking patterns to recognized values. Processing occurs in the browser, so the sensitive source text is not uploaded. The important limitation is that masking is pattern-based: a number that resembles a supported identifier may be masked even when it is harmless, while an unusual representation may remain unchanged.
The tool searches the supplied text for representations of the four supported data types. Each recognized value is replaced according to the active masking configuration, while the rest of the text remains available as context. Configuration affects the form of the replacement, so review the selected settings before treating the generated text as ready to share.
Both the original text and the masking operation stay in the browser. This matters when the input contains live credentials or personal records, but local processing does not make every use safe. The resulting text must still be inspected for identifiers outside the supported categories, missed formats, and contextual details that could identify a person.
No. It obscures recognized instances of the supported identifiers, but anonymity depends on the entire dataset and its context. Names, locations, uncommon events, timestamps, account identifiers, and combinations of ordinary attributes may still identify someone. Treat the output as a redacted working copy, not as proof that re-identification is impossible.
No. Its stated scope is email addresses, phone numbers, credit card numbers, and SSNs, and recognition depends on how those values are written. Names, postal addresses, passwords, access tokens, bank accounts, and medical identifiers are outside that stated list. Review every result manually, especially when the source uses international, abbreviated, malformed, or obfuscated formats.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.