Four parts. One engine.
The extension enforces. The policy decides. The log proves. The dashboard reports.
Read at the source. Keep it local. Govern the edges by policy.
Each one, and what it does not do.
Two layers. Twenty-one data types.
Sixteen by checksum. Four by a model on the device. One honest flag.
- A checksum match always beats the model
- Prompts and files, the same engine
- No text layer: flagged, your policy decides
Working from the first hour.
Five actions. Four EU templates: GDPR baseline, Financial, Government, Education.
- Built from department, data type, destination, channel
- New rules simulate against live traffic first
- Every version signed. Rollback is one click
The view a board can see.
Interactions, detections, blocks, shadow AI, a fourteen-day trend. By department, never by person.
- No individual metric exists in the product
- Unmasking needs a second approver and is logged
- In works-council mode, it does not exist
The edges the browser can't reach.
Developer APIs, agents and sanctioned tools, on keys you issue.
- Mistral and Azure OpenAI EU stay in the EU
- OpenAI, Anthropic and DeepSeek can be blocked per department
- Desktop apps are governed by a device blocklist, never by interception
See it stop realistic data in a real browser.
Book a 30-minute callWhat we see. What we don't.
We say it in the product and in the contract.
| Surface | Sees content | Redacts | Blocks | How |
|---|---|---|---|---|
| Browser AI toolsChatGPT, Claude, Gemini, Copilot, Perplexity, DeepSeek | Full | Yes | Yes | The extension reads the page before encryption |
| Developer APIs, agentsSanctioned tools and automation | Full | Yes | Yes | Opt-in gateway, keys you issueNo interception |
| Native desktop appsClaude Desktop, Slack and similar | Metadata only | No | Destination | A device blocklist steers use into the browserDiscovery only |
| Scanned documentsPDF or image without a text layer | Flag | No | Yes | Flagged. Your policy decides.No text recognition yet |
No proxy. No root certificate. No kernel driver. No app hooking.
Each exclusion removes a risk.
Proxy or root certificate
Breaks on certificate pinning. Weakens the security it promises.
Kernel driver
One bad update can take a fleet down. Not ours.
Desktop app hooking
Desktop apps are governed by policy, not hooks.
Text recognition on scans
Scans are flagged, not read. The seam exists for later.
Productivity score
Never built. Nothing to switch off.
Content on our servers
Labels and hashes only. Nothing worth stealing.
Let's talk.
Thirty minutes. You watch the product stop realistic data in a real browser.
- Six leaks: three prompts, three files, live
- The dashboard a security lead sees on Monday
- An evidence pack exported and verified while you watch
- Whether a proof of value in your estate makes sense