cloak-convert is built so your files' contents can't leak — not by policy, by construction. Here is exactly what happens to a file, and what a browser-enforced content-security policy guarantees.
PDF, Word, Markdown, HTML, CSV, TSV, JSON and Excel round-trips are computed entirely in your browser. Zero bytes are uploaded. The egress monitor stays SEALED — cross-check it against your own Network panel.
When you ask AI to restructure or summarise a document, its text is cloaked on your device first: names, emails, dates and IDs become realistic surrogates. Only the surrogate text is relayed through the CloakAPI gateway; the reply is mapped back locally. The raw values — and the map that restores them — never leave the tab.
The relay is the published SDK's fail-closed wrapper: it tokenises the whole request before sending, obtains a pretokenisation MAC, and blind-relays the surrogate body. If the engine can't load, or a secrets-class value (card / IBAN / national ID) is present, it refuses to send — it never falls back to plaintext.
Each conversion produces an egress receipt: what format changed, how many sensitive values were in the chamber, and exactly how many bytes — if any — were relayed. On-device jobs read 0 bytes, always.
Every page ships a strict Content-Security-Policy. The only off-origin destinations the browser will even permit a connection to are the CloakAPI gateway and your account — nothing else can be reached, so a bug or a bad dependency can't quietly phone home:
connect-src 'self' https://api.cloakapi.io https://app.cloakapi.io
This is delivered as a real policy, not a promise. Deterministic conversions make no connections at all; the two allowed hosts are used only for AI-assisted relays (surrogates only) and billing.
On-device OCR isn't available yet, so an image-only (scanned) PDF is detected and reported honestly rather than uploaded to a cloud OCR service — nothing is read or sent. Text-based PDFs, Word docs and the data formats all convert on-device today.
cloak-convert uses the same published @cloakapi/sdk any developer can install — the cold-downloadable build, no privileged internal access. The privacy engine you run is the one shipped to everyone.
Platform Privacy Policy ↗