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. Your admin never sees your figures. What they do see is the state of your membership and a handful of yes-or-no facts about your device.
What an admin can and cannot see about a member
Visible to your admin
That you're on the team, or that your invitation is still pending
✓
Which team policy revision your device last applied, and when
✓
Whether you generated a report they asked for — never what is in it
✓
The date range of a history clear you ask for, and the reason if you give one
✓
Which days your detection history went missing without an approved clear
✓
How many sensitive items were detected or masked on your device
—
Your reports and exports
—
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 writes team policies and pushes them to your device, which applies them exactly as set. A policy covers:
What a team policy controls
Policy
Means for you
Required AI apps and sites
The AI apps and websites Locke screens. Your device is locked by the team, so Locke keeps screening every app and site it screens by default, even one a policy leaves out.
Always-masked detection types
Values of these types are always masked before anything is sent.
Text strictness
Relaxed, Standard or Strict: how sure Locke must be that a word is a name, a place or an organization before it masks it.
File types
Which files are blocked. Images and audio, which Locke can't check yet, are sent unscreened unless your admin blocks them; files Locke can't read, such as archives and Apple iWork files, are always blocked.
AI services Locke doesn't recognize
Your admin can have them screened or blocked for everyone. Otherwise your device keeps Locke's standard handling: it screens likely AI services and asks about suspected ones. Your own exceptions don't apply on a locked device.
If more than one policy applies to you, your device combines them: every listed app and site, every listed type, every blocked file type, and the strictest text setting. And none of it can be loosened from your device — see When a setting won't budge.
What's still yours
Your detections. Your Dashboard, Activity and detection history, all kept on your device.
Your own reports. You can generate and export full compliance and technical reports for your own device whenever you like, and when your admin asks for one, you generate it yourself.
The Sandbox. Try text against your device's protection; the input never leaves your device.
Your app preferences. Appearance, language and notifications, in Settings.
Clearing detection history is the one thing that needs your admin: in Settings › Data & privacy › Delete detection history, pick the days, choose Request approval to clear this date range…, then Send this request to a Teams Admin. Your admin sees the dates and the reason you pick, never what was detected. If they approve, Locke clears exactly that range on your device and lists the clear in your reports.
What looks different in your app
1. Team policy instead of Controls. Where a Free user has Controls, your sidebar has Team policy: a read-only page of what your organization enforces on this device.
Team policy
Protection settings from your organization
Your protection settings are configured by your organization's admin. They apply to this device automatically and can't be changed here. Ask your admin if something needs to change.
What your organization enforces
Policies
HIPAA-focused
Text strictness
Strict — Masks borderline matches too. More masking, fewer misses.
Image and file strictness
Coming later
File types blocked
Audio and voice (not screened yet), GIF image, JPEG image, PNG image, WebP image Audio and voice uploads are blocked. Image uploads are blocked. Formats Locke can't screen yet (archives, Apple iWork files, video and similar) are always blocked.
AI apps and sites screened
Every AI app and site Locke screens by default. This device is locked by your team, so Locke keeps screening any a policy leaves out.
Always masked
Personal & identity: Person Name, Email Address, Phone Number, Address / Location, Date of Birth, GPS Coordinate, Passport Number, Driver License
Government & tax IDs: Social Security Number (US)
Financial: Credit Card, Card Verification Value (CVV), Bank Account Number, IBAN
Health & medical: Health Term, Medical Record Number, Health Plan ID, DEA Number, NPI Number, ICD-10 Diagnosis Code, CPT Procedure Code, HCPCS Code, NDC Drug Code
Secrets & credentials: API Key, Generic Secret, Private Key (PEM), JWT Token, Bearer Token, Database URL, GCP API Key, Azure API Key, AWS Key, OAuth Token
Device & network: IP Address
Applied on this device
Oct 19, 2026, 8:47 AM (team revision 12)
Team policy: the policy in force on your device, and when it arrived.
1The banner: your protection settings are configured by your organization's admin, apply to this device automatically, and can't be changed here.
2Policies, Text strictness, File types blocked, AI apps and sites screened and Always masked — what your device enforces. Image and file strictness reads Coming later.
3Applied on this device — when your device applied the policy, and its team revision. Your admin sees the same revision.
3. A note on Reports. Your Reports page says: You can view and export your own reports. Reports and exports stay local to this device and account and are never available to team admins.
Reports This device
Review and export activity saved on this device · Learn more
Detection counts read at 2:32:14 PM
Your team admin asked you for a report. HIPAA report for 2026-10-01 to 2026-10-19. You generate it here, on this device; the report itself is never sent to your admin, only that you made it.
Report period
Every report and export on this page covers this period. Dates are UTC calendar days.
Export everything
Save one document with your technical report, detection history, and Comprehensive privacy compliance report for the selected period.
Period
Current app session — choose another period under Report period above.
You can view and export your own reports. Reports and exports stay local to this device and account and are never available to team admins.
Current app session only. The live history is a bounded buffer of up to 2,000 events; choose another period above to read the persistent history for those dates. Every figure and export here is individual — this device, under your account; organization-wide reporting is not available yet.
Compliance report
Summarizes the available detection history for the privacy rules you select. Review it before sharing.
Privacy regimeDate range
Current app session — choose another period under Report period above.
Technical report
Detailed activity, sensitive data types, AI destinations, and recommendations for IT and security teams.
Date range
Current app session — choose another period under Report period above.
Detection history deletions
When
Scope
Detections deleted
Sessions deleted
Authorization
2026-10-14T09:02:18.000Z
Oct 14, 2026, 9:02:18 AM local
all detection history, from 2026-10-13T14:00:00.000Z until 2026-10-13T15:00:00.000Z
6
0
Approved by user_3Fz8Lq2WcN6d
Kept by this app on this device for the signed-in account, and erased when you sign out. “No approval required” is a distinct state — an individual’s, or an administrator’s own, clear has no approver and needs none — and is never shown as an approval. This is not the detection engine’s own audit log.
Detection & masking history
Current app session
When
Outcome
Data type
Direction
Destination
Surface
Values masked
masked
email
outbound
OpenAI / ChatGPT
extension
2
masked
person
outbound
Anthropic / Claude
proxy
1
masked
phone
outbound
OpenAI / ChatGPT
proxy
1
masked
credit_card
outbound
Anthropic / Claude
extension
1
masked
location
outbound
Google Gemini / Vertex / AI Studio
proxy
1
masked
ipv4_address
outbound
GitHub Copilot
proxy
1
masked
medical_record
outbound
OpenAI / ChatGPT
extension
1
masked
ssn
outbound
OpenAI / ChatGPT
extension
1
masked
email
outbound
Mistral / Le Chat
proxy
3
masked
person
outbound
OpenAI / ChatGPT
proxy
2
masked
medical_record
outbound
Anthropic / Claude
extension
1
blocked
api_key
outbound
GitHub Copilot
proxy
masked
date_of_birth
outbound
OpenAI / ChatGPT
extension
1
masked
email
outbound
Cohere
proxy
1
masked
date_of_birth
outbound
Anthropic / Claude
extension
1
unmasked
person
inbound
Anthropic / Claude
proxy
masked
phone
outbound
Anthropic / Claude
extension
1
masked
location
outbound
OpenAI / ChatGPT
proxy
1
masked
email
outbound
Google Gemini / Vertex / AI Studio
proxy
2
masked
credit_card
outbound
OpenAI / ChatGPT
extension
1
masked
person
outbound
Mistral / Le Chat
proxy
1
masked
ipv4_address
outbound
OpenAI / ChatGPT
proxy
1
Showing 22 of 22 events.
Session buffer, metadata only — exports include every event in the period. Open Activity
AI service policy outcomes
Screened automatically
Sent through Locke's screening before it left this device.
41
Blocked
Stopped by policy, or cancelled when Locke asked.
0
Allowed by policy
Sent without screening because a policy allows it.
0
You chose Send Anyway
Sent once without screening because you chose to when Locke asked.
0
0 of 41 were to AI services Locke's list does not include. From the proxy log on this device since Locke started reading it; no host names are recorded.
The detection engine's own append-only record of every process admitted to — or refused by — its services, including this app and administrator control connections. Identities and outcomes only, never content; read-only here, and it records access, not what an admitted process did afterwards. Each capture path connects through its own service: proxy-bridge for network captures, extension-bridge for the browser extension. Records from a short stretch when one service, bridge, served both name that instead — the actor says which path it was.
Reports, with your admin's request at the top. The note about your own reports sits further down the page.
And a few smaller tells: Teams Member under your name where a Free user sees Free plan, with your organization beneath it; no My Team (that page is admin-only); and in Settings, an Organization card that reads Your team admin manages membership, policies and billing. This is read-only here.
When your admin asks for a report
Your admin can ask you to generate a report for a privacy regime and a date range. You'll see a banner at the top of your Dashboard and Reports page: Your team admin asked you for a report. It names the regime and the dates, and says what happens next: you generate it here, on this device; the report itself is never sent to your admin, only that you made it.
Dashboard
Whether Locke is protecting this device right now, and what it caught. · Monday, October 19
Your team admin asked you for a report. HIPAA report for 2026-10-01 to 2026-10-19. You generate it here, on this device; the report itself is never sent to your admin, only that you made it.
Your organization configuration is read-only here — a saved policy preview, not enforced by this device.
Protection status
Running
Desktop ProtectionUp
Browser ProtectionConnected
Detection engineReady
Configured to monitor 13 AI products.
The engine is responding. This health check does not confirm that your traffic is being screened.
location in Google Gemini / Vertex / AI Studiomasked
Detections and first sightings of a surface come from this session's capture feed; policy rows are the proxy's and the extension's own acks of the surface policy; deletions are this device's record. Rule edits are not in this feed — nothing on this device records when a Never flag or a data-type choice changed.
Summarised from the comprehensive requirement checklist over the 21 outbound detection events this session — the same template Reports exports. A tool-generated record, not legal advice. The same summary is shown for every role: Locke has no organization-wide compliance posture.
25
Items masked before sendingThis device
PII Locke replaced in what you sent since this app opened — across every AI app you used, not one chat. Like the recorded tally, it counts each request's new turn only: the AI tool's own system prompt, the context it injects (saved notes, project files), the tool output it feeds back and re-sent conversation history are masked but not counted. It counts per request rather than per recorded value, so the two figures can differ.
204
Sensitive detections recorded (all-time, You typed only)This device
204 of 618 recorded, per your tally settings — the rest sit in origins you are not counting, or are replayed conversation history.
Recorded detection occurrences in the selected all-time tally — masking outcomes not included.
A deliberate subset: everything recorded here was masked, but not everything masked is recorded here.
13
AI products enabledThis device
Distinct AI products Locke screens, with at least one hostname enabled in its local surface catalog (27 hostnames in all). Every catalog entry ships enabled, so this is Locke's default list until you change it in Controls — runtime interception is reported separately when available.
Not counted: Microsoft Copilot in the browser and Web search (7 hostnames), which Locke lists but does not screen — see Controls.
7 verified · 0 degraded · 20 unverified this session, from captured traffic only.
4
Terminal AI tools protectedThis device
4 of the 4 terminal tools Locke knows about send prompts to an API host Locke's proxy is still told to screen (Claude Code, OpenAI Codex CLI, Gemini CLI, GitHub Copilot CLI). Locke's surface catalog groups hostnames, not command-line tools, so this mapping is Locke's own — it counts endpoint coverage, not tools installed or running on this machine, and runtime interception is reported separately when available.
These four figures are not slices of one another: the first is your live capture feed since this app opened, the second is the all-time metrics store narrowed by your tally settings, the third is your local surface list, and the fourth is how many known terminal tools that list still covers. Only the second is stored history. All four are individual figures — this device, under your account. Locke does not show organization-wide totals anywhere yet.
Detailed status and diagnostics
Welcome to Locke
Local diagnostics are ready. A couple of quick steps and you're set.
1 of 3 done
Check the detection engineThe detection engine answered a health check. That doesn't confirm your traffic is routed through it.Answering
2Review configurationSee which AI apps and sites Locke covers.
3See it protect something realLocke's capture log is being watched and nothing has come through yet. Send something sensitive through a configured AI surface and this ticks off.
You can reopen this anytime from Support.
Your surface and data-type choices on Controls do reach Locke — switching a data type off means Locke still finds that value and sends it through in the clear on purpose. The numbers on this page show what Locke has handled. See the card below for current protection status.
Detection engine is answering
The engine is responding. This health check does not confirm that your traffic is being screened.
What this check confirms
Locke's detection engine answered a health check. This check reaches the detection engine directly. It does not pass through the screening path your traffic takes — the system redirect, the proxy, or Locke's guard — so it cannot tell you that any of those are working. If requests are failing or arriving unredacted while this reads green, that gap is where to look. To report this, open Support › Diagnostics and press Copy diagnostics, then send us what it copies.
Counting You typed · occurrences — change what countsWhat the recorded count leaves out
Locke masks more than it records. Four kinds of masked value are deliberately left out of the total above:
Replayed conversation history. A chat client re-sends the whole transcript every turn. A value is recorded once, on the turn it arrives — every later replay is masked again and not counted again.
Text the machine wrote. Values written by the AI itself are never recorded. Names, places, organisations and keyword-dictionary hits found in tool output are masked but not recorded.
Repeats of a value already counted. The same value in the same position counts once per session. After a large number of distinct occurrences that memory is cleared, so a value seen earlier can be counted once more.
Types the metrics store has no column for. A detected type outside its vocabulary is masked but not recorded.
None of this changes what Locke masks — only what it counts. Your own tally settings then filter that recorded subset further.
204 sensitive occurrences in the selected all-time tally. Masking success is shown only when the capture pipeline supplies explicit outcomes.
Live monitoring feed This device
22 validated detections in the current app-session buffer.
14:32:08email in OpenAI / ChatGPTmasked
14:29:51person in Anthropic / Claudemasked
14:28:34phone in OpenAI / ChatGPTmasked
14:26:58credit_card in Anthropic / Claudemasked
last event just now · live tail · processed locally, never leaves your device
Sensitive data origins (all-time)
Injected context
Things your AI tool quietly attaches to every message — saved notes, memory, project files
not counted37% · 231
You typed
Info you actually wrote into your message
in your tally33% · 204
System prompt
The AI tool's own built-in hidden instructions
not counted13% · 82
Tool output
Results from files or commands the AI read, fed back in
not counted11% · 66
The AI's replies
Text the AI generated
not counted6% · 35
Much of this content isn't typed by you — the app, its tools, or the AI itself can add it. These are detection/count-only aggregates; they do not establish a masking outcome. Choose what's included under Settings → What counts as a detection. Percentages are the share of all recorded origins, including rows excluded from your tally.
The request banner on your Dashboard.
Choose Generate report on the Dashboard, and Reports opens with the requested period and regime already set. On the Reports page itself, Use requested settings does the same.
Save Export everything or the Compliance report as a PDF, HTML or JSON file. That completes the request; the other reports and printing don't.
The file stays with you. Your admin's Requests list changes to Done — that is all they learn.
A request you don't answer expires after 14 days, and your admin can cancel it before then.
When a setting won't budge
Your device is locked to your team's policy, and nothing that would weaken protection can be changed from it. Settings your team holds stay visible and say why: Your organization's policy keeps protection on for this device, so this setting is managed by your admin.
The lock comes from your team's account on Sonomos's servers, not from a file on your computer, so it can't be edited away, and neither signing out nor going offline lifts it. 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 your team's policy.
Pausing, when you're on a team
You can't pause protection while you're on a team. There is no Pause protection button on your device, and in Settings › Protection both the pause and When Locke can't check a request show as managed by your admin, so unchecked requests are always blocked rather than sent. Detection also keeps running if you go offline.
If you leave the team
Your admin removes you from My Team, and the app tells them what that means: They will lose access to this team. You can invite them again later. The team's lock on your device is lifted once Locke next checks your account with Sonomos, and without a Teams seat you're on Free: the same protection, with one Monthly privacy summary a month instead of full reports. Your local detection history stays where it was. Nothing about your protection gets worse — you go back to choosing your own settings in Controls.
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.
I pasted something by accident and want it out of my history.
Request a clear in Settings › Data & privacy; your admin approves it.
Something sensitive wasn't masked.
Check it in the Sandbox first, then Support — that's a product question, not a policy one.