Reference

What Locke detects

All 78 built-in detection types, by category, with the risk level Locke assigns each one. Anything not on this list is what custom rules are for.

You switch these on and off individually under Controls › Detection data types — see Controls. Almost all of them are on out of the box.

What the risk levels mean

Risk levels
Level	Means
High	Directly harmful if exposed — identity theft, financial loss, or immediate system access.
Mid	Identifying or sensitive, but not immediately exploitable on its own. Dangerous in combination.
Low	Public or low-sensitivity identifiers. Masked mainly to avoid linking activity back to a person or organization.

The five that start switched off

Everything else is enabled by default. These five are region-specific, and switching every country's formats on at once produces false alarms for people who never encounter them. If you work with these identifiers, switch them on:

NHS Number (UK)
National Insurance Number (UK)
Social Insurance Number (Canada)
Sort Code (UK)
IFSC Code (India)

The full catalog

Personal & identity

Who someone is — the details that identify a specific human being.

Personal & identity data types
Type	Risk	Default
Person Name	High	On
Email Address	Mid	On
Phone Number	Mid	On
Address / Location	Mid	On
Date of Birth	Mid	On
GPS Coordinate	High	On
Minor / Child Term	High	On
Passport Number	High	On
Driver License	High	On

Government & tax IDs

State-issued identifiers. Among the most damaging things to leak, and the hardest to change afterwards.

Government & tax IDs data types
Type	Risk	Default
Social Security Number (US)	High	On
Individual Taxpayer ID Number (ITIN)	High	On
Employer Identification Number (EIN)	High	On
NHS Number (UK)	High	Off
National Insurance Number (UK)	High	Off
Social Insurance Number (Canada)	High	Off

Financial

Payment and banking details. Directly exploitable if they get out.

Financial data types
Type	Risk	Default
Credit Card	High	On
Card Verification Value (CVV)	High	On
Bank Account Number	High	On
ABA Routing Number	Low	On
IBAN	Mid	On
SWIFT / BIC Code	High	On
Sort Code (UK)	Mid	Off
IFSC Code (India)	Mid	Off

Health & medical

Clinical information and the codes that encode it. Regulated almost everywhere.

Health & medical data types
Type	Risk	Default
Health Term	High	On
Medical Record Number	High	On
Health Plan ID	High	On
DEA Number	High	On
NPI Number	Low	On
ICD-10 Diagnosis Code	High	On
CPT Procedure Code	High	On
HCPCS Code	High	On
NDC Drug Code	High	On

Secrets & credentials

Keys, tokens and connection strings. A leaked credential is a live door into a system.

Secrets & credentials data types
Type	Risk	Default
API Key	High	On
Generic Secret	High	On
Private Key (PEM)	High	On
JWT Token	High	On
Bearer Token	High	On
Database URL	High	On
GCP API Key	High	On
Azure API Key	High	On
AWS Key	High	On
OAuth Token	High	On
Exchange API Key	High	On
Discord Token	High	On

Crypto & web3

Wallet keys, seed phrases and addresses. Irreversible if exposed — there is no chargeback.

Crypto & web3 data types
Type	Risk	Default
BIP-39 Seed Phrase	High	On
Wallet Private Key (WIF)	High	On
Extended Public Key (xpub)	Mid	On
Lightning Invoice (BOLT-11)	Low	On
Bitcoin Address	Mid	On
Ethereum Address	Mid	On
Ripple Address	Mid	On
Solana Address	Mid	On
Monero Address	Low	On
Transaction ID	Low	On

Legal & business

Case, contract and filing identifiers. Often confidential by court order or agreement.

Legal & business data types
Type	Risk	Default
Legal Case Number	High	On
Court Order Number	High	On
Litigation ID	High	On
Subpoena Number	High	On
Deposition ID	High	On
Evidence ID	High	On
Witness ID	High	On
Filing Number	High	On
Settlement Reference	High	On
Contract Number	Mid	On
Organization Name	Mid	On
State Bar Number	Low	On
Patent Number	Low	On
Trademark Number	Low	On
Entity Number	Low	On

Device & network

Identifiers that pin activity to a specific machine or connection.

Device & network data types
Type	Risk	Default
IMEI	Mid	On
ICCID (SIM Card)	Mid	On
IP Address	Mid	On
IPv6 Address	Mid	On
MAC Address	Mid	On
Android ID	Mid	On
iPhone UDID	Mid	On
UUID	Low	On
Serial Number	Low	On

When the catalog isn't enough

No built-in list can know your matter codes, your project codenames, or the client shorthand your team uses in every message. Those are custom rules: give Locke a pattern or a list of terms, decide whether to mask or just flag matches, and test it in the Sandbox before you rely on it. Teams admins can push custom rules to everyone at once — see My Team.

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: What Locke detects
Summary: The full catalog of sensitive data types, by category, with risk levels.
URL: https://sonomos.ai/support/locke/data-types/
Sections in this guide:
- What the risk levels mean
- The five that start switched off
- The full catalog
- When the catalog isn't enough

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.