Locke sits between you and the AI tools you use, and quietly takes the private bits out of whatever you send them. It runs on your computer, it doesn't slow you down, and once it's on there's nothing you have to remember to do.
You paste a spreadsheet into ChatGPT to get help cleaning it up. It has customer emails in it. You ask Claude to summarize a patient note. It has a name and a date of birth in it. You hand Cursor a config file with a live API key in it. None of this is careless — it's just work. But once that text leaves your machine, it's on someone else's servers, and you can't take it back.
Locke is the step in between. When you send a message to an AI tool, Locke reads it first, spots anything sensitive, and swaps each sensitive value for a realistic stand-in before the message leaves your computer. The AI still understands the shape of what you're asking. It just never sees the real thing.
LOCKEby Sonomos
Pause protection
Dashboard
At-a-glance protection status
Protected
Local-only detection active · 3 surfaces seen this session · nothing leaves this device
Manage surfaces Report an issue
Compliance check
Low risk
No unmasked sensitive sends in the last 24 hours
View full reports
1,798
Sensitive items caught
Every appearance of sensitive information Locke has found in what you count.
1,798
Sensitive items hidden
Of the items found, how many were masked before they could reach an AI.
30
Apps & sites protected
AI apps and websites Locke watches for sensitive data before it's sent.
Live monitoring feed
09:42:15Email Address in chatgpt.commasked
09:41:52Social Security Number (US) in chatgpt.commasked
09:40:07Person Name in claude.aimasked
09:38:44Matter codes in cursormasked
live tail · processed locally, never leaves your device
The Locke desktop app. This is the Dashboard — the first thing you see when you open it.
1The status card. Green and Protected means Locke is running and watching.
2Counters for what Locke has caught and hidden, and how many apps and sites it's watching.
3The live feed — every masked item, as it happens, newest first.
Who this guide is for
Both kinds of reader, on purpose. If you just want your stuff protected and would rather not think about it, the first three chapters are all you need. If you're the person rolling Locke out to a team, writing detection rules, or producing a report an auditor will read, the rest of the guide is written for you and doesn't skip the details.
Nothing here assumes you know what PII stands for. Where a technical term is unavoidable, it's explained the first time it appears.
The two plans, in one line each
The two Locke plans
Plan
Who it's for
What you get
Free
One person, for free
The whole protection engine for one person: every detection category, custom rules, plus one basic Privacy summary report a month.
Teams
Teams, companies and organizations that need insight into, and control over, how their members use AI
Everything in Free, plus unlimited full reports for every member, and an admin who sets policy for everyone and requests reports from the team.
Teams has two roles inside it — admin and member — and the difference matters, so it has its own chapter: Free vs Teams.
How to read this guide
It's built to be read in order, and it's also fine to jump. Every chapter stands alone, screens are shown as they actually look, and the five flows that are easier to watch than to read are walkthroughs you can step through.
Two conventions worth knowing: text like Controls › Scanning floor is a path through the app's own navigation, and a box labelled Available to at the top of a section tells you which plans and roles see it.