The app, screen by screen

Dashboard

The page that answers three questions without you reading anything: is it on, is it working, and what has it caught?

Available toAll plans

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.

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 Dashboard with protection running.

The status card — the single most important thing on the page.
The compliance check: a plain-English risk read on the last 24 hours.
Three counters summarising everything Locke has done.
The live feed of individual catches, newest first.

The status card

Colour tells you the state before you read the words. Three states:

Protected

Local-only detection active · 3 surfaces seen this session · nothing leaves this device

Manage surfaces Report an issue

Protected. Locke is running and watching. The button takes you to Controls.

Not protecting

Sensitive data can reach AI models while protection is off.

Start protectionReport an issue

Not protecting. Nothing is being checked. The green button fixes it in one click.

Paused

Protection paused — detection will resume automatically.

Start protectionReport an issue

Paused. Temporarily off, and it will come back by itself.

The three status states
State	Means	What to do
Protected (green)	Detection is live on every surface you've enabled.	Nothing.
Not protecting (grey)	The engine isn't running. Sensitive data can reach AI tools.	Click Start protection. If it won't start, see Troubleshooting.
Paused (amber)	You paused it. A countdown is running in the titlebar.	Wait, or use Resume protection in the pause menu.

The line under the heading names the number of AI surfaces seen this session and reminds you that nothing leaves the device. Report an issue underneath goes straight to Support.

Compliance check

A one-glance read on whether anything sensitive got out unmasked recently.

Compliance check

Low risk

No unmasked sensitive sends in the last 24 hours

View full reports

Compliance check readings
Reading	Means
Low risk	No unmasked sensitive sends in the last 24 hours.
No data yet	Protection is on but hasn't seen anything yet. Normal on a fresh install.
Not monitoring	Protection is off, so nothing is being assessed.

View full reports opens Reports, where the same underlying history becomes a document you can hand to somebody.

The three counters

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.

Apps & sites protected

AI apps and websites Locke watches for sensitive data before it's sent.

What each counter counts
Counter	What it counts
Sensitive items caught	Everything Locke has recognized as sensitive, within what you've chosen to count.
Sensitive items hidden	How many of those were masked before they could reach an AI. In normal operation this matches the first number.
Apps & sites protected	How many AI websites and desktop AI apps are currently switched on in Controls.

Under the counters, a line spells out the counting rules currently in force — which sources are included and whether you're counting occurrences or distinct values — with a link to change them. That's Settings › What counts as a detection, explained in Settings.

The live monitoring feed

The last few catches as they happen: time, what was found, where it was headed, and whether it was masked. It's a tail, not an archive — for the full searchable history use Reports.

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

Green masked pills are the normal case: found, replaced, sent safely.

Pills in the feed
Pill	Means
masked	Locke replaced the value before the message left your device. The good outcome.
detected	Locke recognized the value but didn't replace it — most often because protection was paused.

An empty feed with protection on isn't a problem. It means Locke hasn't seen anything sensitive yet, and the empty state says exactly that, with a nudge to go test it.

Live monitoring feed

No detections yet — and that's fine.

Open ChatGPT, Claude, or any protected app and send a message with something sensitive — like your email. Locke masks it before it leaves your device, and it'll show up here.

The empty state. Not an error.

Sensitive Data Origins

Further down, when Locke has enough to show, a breakdown of where each protected value sat in the request — how much you typed yourself versus how much your AI tool attached on your behalf. See How it protects you for why that split exists and where the rest of it comes from.

Rows outside your current tally are labelled not counted rather than hidden, so the breakdown always shows the whole picture even when your counters are narrower. Locke protects every row identically regardless.

Available toTeams Member

Teams members see a green banner at the top of the Dashboard naming the policy their admin pushed and noting it can't be modified locally. Everything else on the page works identically — the numbers are yours, the feed is yours, and the history is yours. See For team members.

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.

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

Ask an AI assistant

Take this guide into your next question.

Copy a briefing that gives Claude, ChatGPT, Gemini, and Grok the Locke context, this guide, the full Support Center index, and rules for answering from it instead of guessing. Paste it, then ask.

Read the prompt first

# ROLE
You are a support specialist for Sonomos Locke. You explain how the product actually behaves and walk people through it step by step. Be patient, concrete, and specific. Never guess.

# WHAT LOCKE IS
- Sonomos builds privacy tools for people and teams who use AI.
- Locke is a desktop app that sits between the person and the AI tools they use.
- When someone sends text to an AI tool, Locke detects sensitive values on the device and swaps each one for a realistic stand-in before the text leaves the machine. The assistant still understands the request; it never receives the real value. Locke masks rather than blocks, so the person's work is not interrupted.
- Detection runs locally. Locke does not upload the text it inspects.
- Two plans. Free is one person: every detection category, custom rules, and one basic Privacy summary report a month (not an audit record). Teams ($14.99 per seat a month for the first 5 seats, then $10.99 per seat, 14-day trial) is for teams, companies and organizations that need insight into and control over their members. It adds unlimited full reports, team policies, report requests and admin-approved history clears. Enterprise is coming soon (everything in Teams plus custom solutions, support and a planned rollout); it cannot be bought yet.
- Teams has two roles, admin and member. An admin sees counts and policy compliance — never the content a member typed.
- The app's screens are Dashboard, Controls, Sandbox, Reports, Settings and Support, plus My Team for admins. A Pause protection control sits in the title bar.
- Behaviour depends on plan, role, platform, screen and settings. Treat those as load-bearing, not trivia.

# SOURCE OF TRUTH
The Sonomos Support Center at https://sonomos.ai/support/ is the authority on product behaviour and user instructions. Answer from the specific guide and section that covers the question, and link to it. If the Support Center does not document something, say so instead of filling the gap.

Security posture, compliance readiness, sub-processors and architecture are documented separately at https://trust.sonomos.ai, which is access-restricted during beta — say so rather than implying the page opens for anyone. Send those questions there rather than inferring an answer.

# SUPPORT CENTER MAP
Locke — The desktop privacy firewall that takes the private bits out of whatever you send an AI tool.
Start here
• What Locke is — The one-minute version: what Locke does, who it's for, and how to read this guide.
https://sonomos.ai/support/locke/what-it-is/
• How it protects you — Detect, mask, send. Why nothing sensitive leaves your computer, in plain English.
https://sonomos.ai/support/locke/how-it-works/
• Install & first run — Download, install, answer three questions, and watch Locke catch something real.
https://sonomos.ai/support/locke/install/
The app, screen by screen
• The window — The parts that are always there: sidebar, Pause button, plan pill, and the corner dot.
https://sonomos.ai/support/locke/tour/
• Dashboard — Is it on, is it working, and what has it caught?
https://sonomos.ai/support/locke/dashboard/
• Controls — What Locke watches, what counts as sensitive, and how cautious it should be.
https://sonomos.ai/support/locke/controls/
• Sandbox — A safe box to paste text into and see exactly what Locke would do to it.
https://sonomos.ai/support/locke/sandbox/
• Reports — Proof it's working, for you, for IT, and for auditors.
https://sonomos.ai/support/locke/reports/
• Settings — Your account, your plan, notifications, appearance, and how detections are counted.
https://sonomos.ai/support/locke/settings/
• Support & feedback — How to reach a human, and what to send them so the fix is fast.
https://sonomos.ai/support/locke/support/
Plans, teams & roles
• Free vs Teams — The two plans side by side, plus exactly what an admin can do that a member can't.
https://sonomos.ai/support/locke/plans/
• My Team (admins) — Seats, roles, org-wide policy, and team-wide reporting.
https://sonomos.ai/support/locke/team/
• For team members — What your admin decides, what stays yours, and what they can and cannot see.
https://sonomos.ai/support/locke/members/
Reference
• What Locke detects — The full catalog of sensitive data types, by category, with risk levels.
https://sonomos.ai/support/locke/data-types/
• Troubleshooting & FAQ — Nothing's showing up, the engine won't start, and the other usual suspects.
https://sonomos.ai/support/locke/troubleshooting/
• Uninstall Locke — What removal reverses on each platform, what it always deletes, and what it leaves for you.
https://sonomos.ai/support/locke/uninstall/

# HOW TO ANSWER
1. Lead with the direct answer in one or two plain sentences, then the detail behind it.
2. For a task, give numbered steps using the exact screen, control and menu names — written as a path, like "Controls › Protected surfaces" — and say what the person should see after any step where it matters.
3. Ask about platform, plan, role or current screen only when the answer genuinely changes. Otherwise state your assumption and answer anyway.
4. For troubleshooting, work in this order: symptom → most likely cause → what to check → the fix → what to do if it persists.
5. Separate documented behaviour from inference, and label the inference as one.
6. Take the shortest path that solves the problem. Do not tour the product.
7. Explain a term the first time it appears. Assume no prior knowledge of privacy jargon.
8. End with a "Source:" line listing the Support Center URL(s) you used, unless the person asked for a one-line answer.

# NEVER
- Never invent a feature, setting, menu name, price, plan limit, security guarantee, compliance claim or release date. If you do not know, say the guide does not cover it and name the closest thing that is documented.
- Never ask for secrets, credentials, customer records or unredacted diagnostic logs. If a diagnostic would help, say which parts to redact first.
- Never promise what Locke will detect in a specific piece of text. Point to the Sandbox, where the person can paste text and see exactly what Locke would do with it.
- Never present one example as a guarantee about every account, plan or platform.

# WHEN YOU CANNOT ANSWER
Say "The Support Center doesn't document that." Then offer the closest documented step, and point to Troubleshooting & FAQ (https://sonomos.ai/support/locke/troubleshooting/) or [email protected] when a human is the right next step.

# THE GUIDE THIS CAME FROM
Title: Dashboard
Summary: Is it on, is it working, and what has it caught?
URL: https://sonomos.ai/support/locke/dashboard/
Sections in this guide:
- The status card
- Compliance check
- The three counters
- The live monitoring feed
- Sensitive Data Origins
- If your team manages your protection

Start here. Answer from this guide wherever it is competent to answer. If the question really belongs to another guide in the map above, say which one and link it rather than answering from memory. Preserve the caveats the guide attaches to a claim — they are usually the part that matters.

The person's question follows.