Produce the masked string for the method you choose
Pick a value and a method and the masked string appears immediately. Keeping leading or trailing characters, replacing everything, a SHA-256 hash and format preserving tokenisation are supported, and every result states whether the method is reversible. Input stays inside the browser and is never transmitted, but checking with a sample value of the same shape is still safer than using real personal data.
Reversibility is the distinction that matters most. A hash is one way, so the original cannot be recovered and it only serves to tell whether two values match. Tokenisation is reversible if you keep a token-to-value mapping, which makes that mapping store a new thing to protect. Keeping characters does not allow recovery of the original, yet whatever you keep stays visible. Lengths are counted in code points, so combined emoji may split into several characters. Current as of October 2026.
Which fields must be masked, and how far, depends on law, regulator guidance and the purpose of processing, and it requires interpretation. This tool makes no such judgement. Deciding what is in scope, detecting fields automatically and converting whole files are not supported. Legal requirements differ by case and jurisdiction, so have the relevant team or a professional confirm before applying anything.
Frequently Asked Questions
No. Scope and extent depend on law, regulator guidance and the purpose of processing, which requires interpretation, so this tool makes no judgement and only produces the masked result for the method you choose.
A hash is one way, so the original cannot be recovered and it only tells whether two values match. Tokenisation is reversible if you keep the mapping, which makes that mapping store a new thing to protect.
An unsalted hash can be brute forced for low-entropy values, so it can be reversed. Those values need a keyed HMAC or a salt.