Write the email.
Keep the names.
Paste an email you received, or just say what you want to say. cloak-post drafts, replies, rewrites and summarizes it. On your device, the detector replaces the recipient, address, phone and account values it finds with realistic stand-ins before sending. A value it misses can remain as written, so review the request text before sending. cloak-post reseals detected values in the returned draft. The gateway relays the request from your device without inspecting its content.
- Detected values replaced before sending
- 4 ways to write
- On-device receipt
cloak-post does not send your mail. It hands you the finished draft to send yourself.
Answer an email you received.
- Same-site requests
- 0
- Gateway relay
- 0attempts
- Third-party
- 0
Your finished email will appear here.
Seal first — cloak-post drafts from surrogates, then reseals with your real names.
The delivery, in three moves
Seal, on-device
A WebAssembly engine plus a multilingual name model find names, emails, phones, addresses and cards — across Latin, Cyrillic, Arabic, Devanagari and CJK — and frank each with a realistic surrogate. Structured identifiers (cards, IBANs, national IDs, phones, emails, dates) match by rule; free-form names rely on the on-device model, so an unusual one can slip past — review the draft before sending. This step sends nothing.
Relay a cloaked copy
The cloaked copy — detected values replaced by surrogates, anything undetected as written — is sent to the drafting model through the CloakAPI gateway. The gateway verifies the request before processing it. This does not verify that the on-device privacy checks ran. The real values — and the map back — stay in the tab.
Reseal & copy
The draft returns carrying the same surrogates; cloak-post maps them back to your real values on-device, issues an on-device receipt recording that the cloaking pipeline ran (it does not measure what the detector missed), and hands you the email to copy and send. This path does not send the mail for you.