Cloak it first

CloakAPI swaps the names, emails and ID numbers it detects for stand-ins on your device, then sends the request to the model you choose: Claude, GPT, Gemini, Grok, DeepSeek or one on your own hardware. Calls can carry a signed receipt that anyone can check offline.

Detection can miss details. Review before you send. Known limitations

Your code, on this device

prompt = ("Email Ingrid Halvorsen at "
    "ingrid@example.com about rent")

client = OpenAI(
    base_url="http://localhost:8799/v1",
    api_key="cloak_…")
reply = client.chat.completions.create(
    model="claude-sonnet-5",
    messages=[{"role": "user",
               "content": prompt}])

Sent to Claude through the gateway

"Email stand-in for a name: <<CLOAK:PERSON:7c3e91>> at stand-in for an email: <<CLOAK:CONTACT_EM:22fff1>> about rent"

Marked text was swapped on this device. Unmarked text is sent as written.

Cloaked 1 name, 1 email View receipt

Receipt

Receipt fields for this sample request
Receipt ID01JC7Q2FX4…R8D3E
Signed2026-11-09T09:41:07Z
Input hashsha256:a4d8…f3e1
Gateway keygw-prod-2026-q2

Signature valid How to verify a receipt

A sample request and receipt, with synthetic data

How a request travels

  1. On your device

    The SDK, local proxy, extension, desktop app or chat finds names, emails, card and ID numbers and swaps each one for a stand-in. The map back to the originals stays with you.

    What detection covers
  2. At the gateway

    The gateway checks your key, balance and request format, then forwards the cloaked request to the AI provider you picked. It doesn’t scan your text, and it keeps no copy of prompts or answers by default.

    Data map
  3. On the way back

    The answer comes back the same way. Clients that hold the map put the originals back in locally, and the call can come with a receipt signed by the gateway.

    Reading a receipt

Pick your way in

Start with the one that fits how you work. You can add others later.

Where do you use AI?

  • On ChatGPT, Claude, Gemini or Grok

    Chrome extension

    Cloaks the names, emails and numbers it detects before your message reaches the site.

    Get the extension

    Before your first send it downloads a name model, 178 MB (178,495,423 bytes).

  • In a private chat window

    Private chat

    Ask Claude, GPT, Gemini, Grok or DeepSeek in a browser tab. Detected details become stand-ins before the message leaves.

    Open the chat

    The tab loads 178 MB (178,495,423 bytes) for name detection and runs it in this browser. Pattern checks work while it loads.

  • For one task

    Apps

    A CV, an email, a translation, a spreadsheet: ten apps, each built for one job.

  • On files and longer documents

    Desktop app

    Cloak documents and prompts in a native app, and run models on your own hardware if you want.

    Get the desktop app

    Reading the release register…

    At launch it fetches a name model of 178 MB (178,495,423 bytes). The desktop app can send with the layers that are ready if the name model is unavailable, and shows a warning.

Writing code? What are you building?

  • Privacy for the AI tools I use

    Your own setup

    Point your tools at the local proxy, or add an SDK to your code. Cloaking runs on your machine.

    Read the quickstart

    Eight SDKs: TypeScript from npm and Python from PyPI. .NET, Go, Java, PHP, Ruby, and Rust are available as downloads.

    Running one shared proxy for a team? Read this first
  • A product with AI, for my own users

    Build on CloakAPI

    Give your users on-device cloaking and signed receipts through the REST API and SDKs. Cloakup is built this way.

Eleven apps run on CloakAPI

Each one does one job, cloaks what it detects before anything goes to an AI, and has its own plan.

The first name check may download about 357 MB to this browser.

Proof you can check

Three flat rates, no tiers

You pay what the provider charges for the call, plus one markup, from a prepaid balance you top up from $25. The API has no seats and no monthly minimum. The apps have their own plans.

CloakAPI markup by how the call is made
How the call is madeMarkup
With CloakAPI’s provider keys15%
With your own provider keys5%
With local models5%

Eligible accounts may receive $2 of trial credit after email verification. The credit works on any priced model until it is used up. Trial details

Worked example: one call on CloakAPI’s keys

Provider cost, markup and total for one example call
Provider cost$0.0420
CloakAPI markup, 15%$0.0063
Total$0.0483