CVs, disciplinary notes, exit interviews — the documents HR handles are exactly the ones that must never leak. You shouldn't have to anonymise a candidate pack by hand before pasting it into ChatGPT or Claude — and then de-anonymise the answer afterwards. Our on-device detector makes a best-effort pass before supported content is sent. It can miss identifying details, so review content before sending. See Terms of Service §7b, Known limitations.
No card required. You land straight in a simple chat — drop a file and ask.
Three steps. No setup, no training, nothing to install. If you can attach a file to an email, you can use this.
Drag in the CV, interview notes, disciplinary report or survey export you're working on. On supported client paths, the client makes a best-effort pass for identifying details before sending. Coverage varies by content and format, and detection can miss. Review the content your client shows; see Terms of Service §7b, Known limitations.
On supported paths, the client attempts to replace personal data it detects with placeholders. Detection may miss details, so unmatched content may reach your selected AI provider. Review the content your client shows before sending; see Terms of Service §7b, Known limitations.
A client may use its local mapping to restore values it detected in a response. Detection and restoration can be incomplete, so review the result before relying on it.
Detection is best-effort on supported client paths. It can miss identifying details or formats; unmatched content may be sent to your selected AI provider. Review the content your client shows before sending; see Terms of Service §7b, Known limitations. File and image handling varies by client and type; not every client shows prepared content before sending. Read the data map for service data handling.
Name and identifier coverage varies by client and content type. Detection may miss details, and file handling can differ by format. Review the content your client shows before sending. If your client offers a “send unchanged” option and you select it, the original file bytes go to your selected provider. See Terms of Service §7b, Known limitations and available client options.
Employee and candidate data sits squarely under GDPR and employment-privacy law — and under something stricter still: your colleagues' trust. Here is what the architecture actually does, so you and your own advisers can evaluate AI use against both — this is not legal advice.
The workarounds people use today are slow — and fragile.
The manual rename. "Candidate A", "Employee X", find-and-replace before pasting — then reversing it all in the answer, hoping you didn't miss one instance on page 14.
The retyped summary. Typing an anonymised version of the document by hand because uploading the real one feels wrong. Half an hour gone before the AI has even started.
The quiet rule-break. Pasting the real thing and hoping it's fine. It's the fastest option — and the one that can cost someone their privacy — and the company a claim.
The blanket ban. The firm forbids AI entirely, and the productivity gain everyone else is getting goes to your competitors instead.
The duty of confidentiality isn't unique to HR. If people trust you with their private affairs, this is built for you too.
Plain answers, no fine print surprises.
On supported client paths, the client attempts to replace personal data it detects before sending. Detection is best-effort and can miss content, so unmatched details may reach the AI provider you selected. Review what your client shows before sending; see Terms of Service §7b.
A client may use a local mapping for values it detected to try to restore stand-ins in a response. Detection and restoration may be incomplete, so review the result before relying on it.
When issued, a receipt records the claims in its envelope and can be independently verified. It does not prove that every personal-data value was found or that every request produced a receipt.
File handling varies by client and type, and not every client shows prepared file content before sending. Detection may miss personal data. Review what your client displays; see Terms of Service §7b. If your client offers a “send unchanged” option and you select it, the original file bytes go to your chosen provider.
Yes — supported client paths can reduce identifiers in candidate materials. The on-device detector makes a best-effort pass and replaces matches before sending; it can miss names, details or format variations, so review content. Model providers receive the content you send. If file processing fails, choosing “Send anyway, unchanged” sends the original file bytes. CloakAPI records account, usage and receipt data; optional response buffers or maps are described in the Data Map. See the Terms of Service §7b, Known limitations.
Create an account to use the browser chat. Before sending, review the content your client displays; detection is best-effort and may miss details. File handling varies by client and type. If a client offers “send unchanged” and you select it, the original bytes go to your chosen provider. See Terms of Service §7b. The browser add-on is available from your account page; an IT team can handle setup for internal systems if needed.
Free to start, no card required. Drop a document, ask your question, and see the answer come back with the names where they belong.
Questions first? Write to hello@cloakapi.io — a human answers.