Privacy everywhere
you use AI.
Locke finds sensitive data in what you send to the AI tools it covers, and masks it on your device.
Early Access for 64-bit Windows and Linux. macOS is coming soon.
Partnered with
Partners, not customers or endorsements. About our partners
You've already shared more than you think
Sensitive data goes into AI tools every day. Almost nobody checks.
- 47%
Unapproved AI usage
of genAI users at work use personal AI apps their employer does not manage
The employer has no say over what goes into those apps, or how long it stays there.
- 39.7%
What gets shared
of employee interactions with AI tools involve sensitive data, counting prompts, pastes and file uploads
The average employee enters proprietary information into an AI tool about once every three days.
- $670K
The cost of exposure
higher average breach cost at organizations with high levels of shadow AI than at those with little or none
Masked before the request leaves
On supported routes, Locke picks the AI requests out of your traffic and masks the sensitive values in them.
The values go. The meaning stays.
Each value becomes a one-way placeholder that keeps its meaning. The AI never sees the real one.
Detecting sensitive data…
Raw data never crosses this line
Detection and masking run on your device. Only the masked version reaches the AI provider, and its reply comes back masked too.
Diagram: Your AI apps send data to Locke, running on your device. Locke detects sensitive data and one-way masks it before it crosses the device boundary to the AI provider. The AI provider's reply crosses back into the device while still masked; Locke 1.0 does not restore raw values; restoration is planned after 1.0. Raw sensitive data never leaves the device boundary.
Detection (multi-engine) · Masking (one-way) · Return (still masked; restoring the originals is planned after 1.0)
Try it here. Nothing leaves this page.
The demo runs in your browser. Open devtools and watch the network tab.
7 detections7 typesNetwork requests: 0
The AI's replyIn 1.0 it comes back masked.
Sure — here's a draft referencing Ms. Zquce Bysktikw. Let me know if you'd like any changes.
A simulation of Locke's on-device engine. In Locke 1.0, masking is one-way.
Click through the full Locke app demoThe routes Locke screens today
On supported routes, Locke recognizes AI traffic, including eligible services outside its built-in list. Recognition and screening are separate: detection and masking are supported on the routes below.
AI websites
via the browser extension
Command-line agents
via the local proxy
IDE assistants, APIs & SDKs
via the local proxy
Local model servers
when you point them at Locke
Desktop wrapper apps
recognized and screened by the desktop app
For anyone whose prompts carry sensitive information
Lawyers
Research and draft with AI while Locke masks client details before they're sent.
Healthcare
Keep PHI out of the prompt.
Financial services
Use AI for analysis and reporting, minus the client account data.
Technology
Protect API keys, credentials and proprietary code when you code with AI.
Individuals
Ask AI about your money or your health while Locke masks the details it finds.
See how Locke compares to cloud DLP and enterprise AI plans, or look up a term in the glossary.
Early Access starts with a download.
Locke runs on 64-bit Windows and Linux, with macOS coming soon. Download it, sign in and join the waitlist from inside the app.
Download LockeOr try the interactive demo first.



