blckit intercepts API keys, passwords, PHI, and credentials before they reach any AI — in your browser, your terminal, or your IDE. You keep working normally.
Free. No account. Takes 30 seconds to install.
✓ You're on the list. Install it now:
Download the zip, unzip it, then load it in your browser below.
Live demo — try it
Try pasting something sensitive, or pick an example:
Wherever you use AI
ChatGPT, Claude, Gemini, Copilot, Perplexity, Grok, Slack, Gmail, Teams, WhatsApp, Doximity, Zoom, TigerConnect, Notion — every supported tab, automatically.
Using AI from the command line? blckit wraps any CLI tool. Same detection, same sealed tokens, same audit log — no browser required.
Cursor, VS Code, Windsurf. blckit intercepts before your code context reaches the model — at the source, not after the fact.
One token format across every surface. 〈API_KEY_1〉 means the same thing whether it came from your browser, your terminal, or your editor.
How it works
Add blckit to Chrome, Firefox, or Edge. It runs silently in every tab — no setup, no accounts, no configuration required.
In the browser: ChatGPT, Claude, Gemini, Copilot, Perplexity, Slack, Gmail, Teams, Doximity, Zoom, and more. In the terminal: any AI CLI tool. In your IDE: Cursor, VS Code, Windsurf. blckit covers the surface — you don't change how you work.
When you hit send, blckit intercepts in under 50ms. Detected secrets are replaced with sealed tokens like 〈API_KEY_1〉. The real value never reaches the server.
A tamper-evident Ed25519-signed ledger on your device records every seal. No data leaves your machine. You own the audit trail.
What blckit catches
How we built it
Detection runs locally in the extension. Nothing is sent to our servers — because we don't have any in your data path.
The entire extension is readable on GitHub. Inspect what it does before you install it. Security tools that hide their code are the threat.
Tokens are encrypted with a key that never leaves your device. Your browser is the only place that can unseal them.
Every seal is recorded in an Ed25519-signed, hash-chained local ledger. Tamper-evident proof that protection happened.
Detection runs before your send completes. Under 50ms round-trip. You won't notice it.
After auto-seal, a 10-second toast lets you undo if blckit caught something that wasn't actually sensitive.
Every tier, every surface