Content-blind translation

Translate the papers
you could never send.

Contracts, medical notes, HR letters — the text you need in another language but would never paste into a public translator. cloak-translate swaps the names, IDs and addresses it detects for realistic stand-ins on your device, relays only the stand-ins for translation, then maps the real values back into the result. The gateway only ever receives the cloaked text — review the preview before you send, because an identifier the detector misses travels with it.

  • Cloaked before anything leaves
  • 18 languages, every script
  • Signed on-device receipt
Try
Your textdusk · source
Waiting for text…
Egress monitor 0 raw-PII bytes
On-device
0
Gateway relay
0surrogates
Third-party
0
Translationdawn · Spanish

Your translation will appear here.

Cloak first — press Translate to relay the surrogate text.

The crossing, in three moves

01

Detect & cloak, on-device

A WebAssembly engine plus a multilingual name model find names, emails, phones, cards, IBANs and IDs — across Latin, Cyrillic, Arabic, Devanagari and CJK — and replace 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 — the preview shows exactly what leaves. Zero network.

02

Relay a cloaked copy

Only the surrogate-bearing text is sent to the translation model, through the CloakAPI gateway with a cryptographic pre-tokenisation proof. The real values — and the map back — stay in the tab.

03

Un-cloak the result

The translation returns carrying the same surrogates; cloak-translate maps them back to your real values on-device, and signs a receipt carrying the raw-PII byte count measured on the bytes that actually left — a count above zero stops the send instead of reporting it.