Plans, teams & roles

Free vs Teams

Two plans, and three roles across them. The difference is never how well you're protected — it's what you can report on, and who gets to decide.

The two plans

Free and Teams compared
	Free	Teams
Price	$0	$14.99 per seat a month for the first 5 seats, then $10.99 per seat a month for each seat after that. 14-day free trial, up to 20 seats, US customers only
Who it's for	One person — consumers, freelancers, developers	Teams, companies and organizations: anywhere someone needs insight into, and control over, how team members use AI
Protection	The complete feature set	The same complete feature set
Reports	One basic Privacy summary per calendar month, not an audit record	Unlimited full compliance and technical reports for every member and admin
Who sets the rules	You	Your admin sets the policy; it applies to your device as set
Team features	None	Team policies, report requests, admin-approved history clears

The three roles

Teams has two roles inside it, so there are three states the app can be in. The bottom-left corner of the window always tells you which one you're in.

The three roles
Role	Sidebar reads	In one sentence
Free	Free plan	You own every setting on your machine, and nobody else sees your numbers.
Teams Member	Teams Member	Your admin sets a protection floor; everything above it, and all of your own data, stays yours.
Teams Admin	Teams Admin	Everything a member has, plus seats, org-wide policy, team reporting, and billing.

Settings

App & account configuration — no protection rules here

Account

Dana Whitfield

[email protected]verified

First name

Last name

Your email, password, two-factor authentication, passkeys, connected accounts and active devices are managed in your account settings.

Save changesManage account & securitySign out

Plan & billing

FreeFree

Everything Locke protects for one person, plus one basic Privacy summary report a month. Full reports are part of Teams.

Upgrade to Teams

Notifications

Masking alerts

Weekly report email

New surface detected

App behavior & display

ThemeStart on loginOverlay position

What counts as a detection

Locke protects everything it finds. This only changes which of those finds are added up in your numbers.

You typed

Info you actually wrote into your message

Injected context

Things your AI tool quietly attaches to every message — saved notes, memory, project files

System prompt

The AI tool's own built-in hidden instructions

Tool output

Results from files or commands the AI read, fed back in

The AI's replies

Text the AI generated

Other

Everything else

Count

Occurrences counts every masked spot — 20 copies of the same email is 20. Distinct values counts unique values — the same 20 copies is 1.

Diagnostics & updates

Log verbosity

Check for updatesSupport & feedback

Sonomos Locke v1.0.0 · up to date

Save preferences

Settings › Plan & billing always names your current plan. This is what Free looks like.

One thing to know before you go looking: the Plan & Billing card in Settings writes your role in sentence case — Teams member or Teams admin — while the sidebar pill and the rest of this guide capitalize it as Teams Member and Teams Admin. Same role, two labels, nothing to read into it.

What each role can do

Capabilities by role
Capability	Free	Teams Member	Teams Admin
Core protection — engine, masking, sensitivity	✓	✓	✓
Apps and sites protected	unlimited	unlimited	unlimited
Detection history retention	you choose	you choose	you choose
Custom detection rules	✓	—	✓
Per-surface and per-type control	✓	—	✓
Sandbox	✓	✓	✓
Privacy summary (basic, one a month)	✓	✓	✓
Full compliance and technical reports	—	unlimited, your own	unlimited, your own
Request a report from members	—	—	✓
Clear your own detection history	✓	by admin approval	✓
Team policies	—	receives	✓
Pause protection	✓	—	✓
Organization context in the app	—	✓	✓
Set policy for other people	—	—	✓
Invite and manage seats	—	—	✓
Billing	n/a	—	✓

The one rule that explains Teams

A Teams Admin sets a floor, not a fixed configuration. Every policy they push is a minimum:

Required surfaces must be protected on every member's device. Members can add more; they can't switch a required one off.
Required data types must be detected. Members can enable extra categories; they can't disable a required one.
Scanning floor is a minimum sensitivity. A member on a Strict policy stays Strict: members can't loosen or change it.

Which is to say: a member can always protect more, never less — an admin can add requirements but can never take away something a member already had. That single rule is what makes it safe to push a policy to a hundred devices at once without breaking anyone's setup, and it's exactly what the phrasing on the admin's Policies tab is telling you.

What Free shows, and what it locks

Team-only management surfaces — My Team, org policy, report requests — simply aren't in a Free app. Reports are different: every report type beyond the monthly Privacy summary is visible but locked, with an Upgrade to Teams prompt that opens your plan page in the browser.

When a Teams member can't change a control because their admin set it, the control stays visible and shows who locked it and why. Hiding that would just make the app look broken. Members also can't clear their own detection history: they ask their admin for a date range, and approval clears it on their device. Each clear is logged in their reports.

The gating patterns
Situation	What you see
Free user, Teams-only report	The report is shown locked with an Upgrade to Teams prompt.
Free user, Teams-only management	My Team and policy aren't in your app.
Teams Member, admin-locked control	The control is visible and disabled, with your admin named as the reason.

Moving between plans

Plan transitions
Change	What happens
Free → Teams Member	You accept an invitation from your admin. Your org's policy arrives and takes effect as a floor; your own settings above that floor are kept.
Teams Member → Free	Your admin removes your seat. On next launch the app explains the change, drops the org policy, and keeps your full protection. You lose the org rules and full reports; the monthly Privacy summary applies from then on.
Free → Teams Admin	Choose Upgrade to Teams in the app or at my.sonomos.ai/plan, create your team and start the free trial. My Team appears in your sidebar.

Where to go next

Running a team: My Team (admins).
On a team someone else runs: For team members.
On your own: protection is unchanged for you — carry on with Controls.

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: Free vs Teams
Summary: The two plans side by side, plus exactly what an admin can do that a member can't.
URL: https://sonomos.ai/support/locke/plans/
Sections in this guide:
- The two plans
- The three roles
- What each role can do
- The rule that explains Teams
- Teams features are hidden, not locked
- Moving between plans
- Where to go next

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.