Plans, teams & roles

For team members

Your organization set up Locke for you. Here's exactly what they decided, what's still yours, and — the question everyone actually has — what they can and can't see.

Available toTeams Member

What your admin can see

Start here — everything else in this chapter builds on the answer.

What an admin can and cannot see about a member
	Visible to your admin
How many sensitive items were detected on your device	✓
How many were masked	✓
Whether your device meets the org policy	✓
That your protection was paused, and for how long	✓
The messages you sent to an AI tool	—
The actual values that were masked	—
Which specific prompts triggered a detection	—
Which AI tools you personally used, per message	—

What your admin decides

Your admin sets the policy every device on the team runs, and it is applied exactly as set. Three things:

What org policy controls
Policy	Means for you
Required surfaces	Certain AI sites and apps are always protected. You can add more; you can't switch a required one off.
Required data types	Certain categories are always detected. You can enable extra ones; you can't disable a required one.
Text strictness	The text strictness your admin sets is applied to your device as set.

So the rule in one line: your device always runs the policy your admin set — see the rule that explains Teams for why that's guaranteed rather than just promised.

What's still yours

Your numbers. Your Dashboard, your counters, your live feed, your history.
Your own reports. You can generate and export full compliance and technical reports for your own device whenever you like, and when your admin requests one for a date range, you generate it yourself.
The Sandbox. Yours, entirely local, and never reported on.
Your app preferences. Theme, notifications, where the corner dot sits.

What looks different in your app

Three differences you'll notice right away, and a few smaller tells.

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

1. A banner on the Dashboard naming the policy in force.

2. Controls is replaced by a message. Your admin's policy is applied to your device as set, so the Controls page shows a message naming your admin instead of switches you could change.

Reports

Keeping track of what Locke handles

Export all

One consolidated document for a single period — combines the technical report, the full detection & masking history, and the compliance report into a single file you can preview, print, or save as PDF.

Period

Generate combined reportDownload PDF

Compliance report

A regulator-ready record for legal and compliance teams — maps your detection history to a privacy regime for auditors and counsel.

Privacy regimeDate range

Generate reportDownload PDF

Technical report

One complete report for IT and information-security teams — key metrics, protection rate, sensitive data types, AI destinations, direction of exposure, daily activity, and recommendations.

Date rangeAppend detection & masking history (same date range)

Generate reportDownload PDF

Detection & masking history

Export CSVExport PDF

Time	Surface	Data type	Direction	Action
09:42:15	chatgpt.com	Email Address	outbound	masked	View
09:41:52	chatgpt.com	Social Security Number (US)	outbound	masked	View
09:40:07	claude.ai	Person Name	outbound	masked	View
09:38:44	cursor	Matter codes	outbound	masked	View
09:31:19	api.openai.com	API Key	outbound	masked	View

Compliance-friendly log — metadata only, no plaintext sensitive data is retained.

3. A note on Reports: your own reports are yours to export.

And a few smaller tells: your organization named in the sidebar, and Teams Member where a Free user sees Free plan. You won't see My Team — that page is admin-only.

When a control won't budge

On a team there are no controls to budge: policy comes from your admin's account on the server, not from a file on your computer, so it can't be edited from your device. If a policy is blocking your work, such as a masked value breaking a task you need to do, your admin is the person who can change it. Locke support can't override org policy.

Pausing, when you're on a team

You can't pause protection while you're on a team. The pause button is disabled with a note naming your admin, and capture can't be switched off from your device. Detection also keeps running if you go offline.

If you leave the team

When your seat is removed, the app explains what happened on next launch and moves you to Free. The org policy is dropped, your protection is unchanged, and your local history stays where it was. Free keeps one basic Privacy summary a month; full reports are part of Teams. Nothing about your protection gets worse — you simply go back to setting your own rules.

Who to ask

Where to take a question as a team member
Question	Ask
Why can't I turn this off?	Your admin. It's their policy, and only they can change it.
Something sensitive wasn't masked.	Check it in the Sandbox first, then Support — that's a product question, not a policy one.
Can my manager read my prompts?	No. See the top of this chapter.
I need a report for my own records.	Generate it yourself — Reports.
The app won't start.	Troubleshooting, then Support.

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: For team members
Summary: What your admin decides, what stays yours, and what they can and cannot see.
URL: https://sonomos.ai/support/locke/members/
Sections in this guide:
- What your admin can see
- What your admin decides
- What's still yours
- What looks different in your app
- When a control won't budge
- Pausing, when you're on a team
- If you leave the team
- Who to ask

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.