Judged on merit.
Identity curtained.
A CV is the densest identity document you own — name, address, birth date, every employer, every city. cloak-cv reviews, rewrites and tailors it with AI. On your device, values the detector finds are swapped for realistic stand-ins. The casting sheet shows those detected swaps for review before sending; a value the detector misses may remain as written.
- Detected values replaced before sending
- 5 ways to be judged
- On-device receipt
Detection can miss details. The casting sheet shows detected swaps; review your CV for values the detector may not catch.
A recruiter-grade critique: what lands, what's weak, what's missing.
- On-device
- 0
- CV server /api/cv
- 0POSTs
- Gateway direct
- 0requests
- Third-party
- 0
The panel's verdict will appear here after you add a CV and choose an action.
The panel shows stand-ins for detected values; detector misses may remain as written. The verdict is un-cloaked for you alone.
The audition, in three moves
The curtain drops, on-device
A WebAssembly engine and multilingual name model look for names, addresses, birth dates, phones, emails and account numbers across Latin, Cyrillic, Arabic, Devanagari and CJK. Values the engine detects are replaced with locale-matched stand-ins. Detected payment cards and secrets use opaque markers derived from the value with no secret key; the marker cannot be turned back into the value, though someone with a candidate value can check whether it matches. Structured identifiers match by rule; free-form names rely on the on-device model, so an unusual one can slip past. Review the substitutions before sending. This review does not send the CV to the relay; model or resource downloads may still use the network.
The panel reviews the text
The reviewed CV request is sent to the reviewing model through the CloakAPI gateway after you approve the exact text. Values the engine detects are replaced before sending; values it misses may remain as written. Our server checks the page's privacy engine and sends the exact request to the CloakAPI gateway for a check before forwarding it to the AI service. That check does not prove that a caller tokenised the text. Known limit in Release 1: a caller on this same origin can bypass this page and submit text without client-side tokenisation. The gateway is content-blind, and the map back stays in the tab.
The curtain lifts, for you alone
The verdict returns carrying the same stand-ins; cloak-cv maps them back to your real details on-device, issues an on-device receipt for the request and hands you the result — copy it, or download it as md, txt, docx or pdf, built entirely in your browser. When issued, a receipt records that the cloaking ran for that send.