Skip to main content

    Privacy everywhere you use AI.

    Locke masks sensitive data on your machine, before it reaches the AI tools it covers. Below is a click-through replica of the app. Click around.

    Download LockeWindowsLinuxmacOS planned

    Interactive demo

    Fictional sample data. Nothing you click leaves this page.

    View as
    Sample data

    Dashboard

    Whether Locke is protecting this device right now, and what it caught. · Monday, October 19

    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.

    Recent activity

    View reports
    email in OpenAI / ChatGPTmasked
    person in Anthropic / Claudemasked
    phone in OpenAI / ChatGPTmasked
    credit_card in Anthropic / Claudemasked
    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.

    Risk & compliance posture This device

    Open compliance report
    Evidenced in the available data3 of 7
    Needs your review0 of 7
    Your organization's action4 of 7
    Not assessable from this device0 of 7

    Summarised from the comprehensive requirement checklist over the 19 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.

    23
    Items masked before sending This 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.
    312
    Sensitive detections recorded (all-time, You typed only) This device
    312 of 947 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 enabled This 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 protected This 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.
    2 of 5 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.
    3Review local diagnosticsSee the diagnostics available on this device.
    4Try it in the SandboxPaste sample text and review the detector's local diagnostic output.
    See it protect something realDone — Locke recorded its first explicitly protected item from a conforming live producer event.
    Dismissing hides this in this browser.
    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.
    Review configuration Report an issue

    Monitoring status This device

    Metrics connected
    Counts are up to date across 46 recorded sessions.
    View full reports
    Counting You typed · occurrences — change what counts
    What 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.
    312 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

    20 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 counted39% · 368
    You typed
    Info you actually wrote into your message
    in your tally33% · 312
    System prompt
    The AI tool's own built-in hidden instructions
    not counted13% · 121
    Tool output
    Results from files or commands the AI read, fed back in
    not counted10% · 97
    The AI's replies
    Text the AI generated
    not counted5% · 49
    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.

    ACTIVITY BAR

    See Locke work without opening it.

    A thin light on the right edge of your screen glows when Locke acts on a request.

    • Green: masked a value or held back an attachment. Red: blocked a request. Amber: something went out unmasked
    • Steady amber when Locke knows protection needs attention, such as a stopped detection engine or capture switched off
    • Clicks pass through it and it never takes focus. An agent's burst of requests is one glow, not a strobe
    • Only a colour reaches it: not what was found, where it went or how many. On Windows it's hidden from screen shares and recordings
    • On by default. Switch it off in Settings › General or Locke's tray menu

    On Windows and Linux with X11. Wayland won't let an app hold the screen edge, so there it's a coloured dot on Locke's tray icon. On GNOME, that needs the AppIndicator extension, which Ubuntu includes.

    On Linux Wayland, the same buttons light the tray icon

    DASHBOARD

    What's protected, and what Locke caught.

    The first screen you see when Locke opens.

    • Separate status for desktop protection, browser protection and the detection engine
    • The latest detections and what Locke did about each
    • Four counts, each labelled: items masked before sending, detections recorded, AI products enabled, terminal AI tools protected
    • A risk and compliance posture summary, from the same checklist Reports exports
    Open the Dashboard in the demo

    CONTROLS

    You decide what counts as sensitive.

    Pick the AI services Locke screens, the data it masks and how strict it is.

    • Protected Surfaces: a switch per AI website or app, screened by the extension or the local proxy
    • Sensitive data: 78 types across identity, government IDs, financial, health, secrets, crypto and legal, each with a risk level
    • Strictness: Relaxed, Standard or Strict, for how sure Locke must be that a word is a name, place or organization before masking it
    • Attachments: screen or block by file format. Images and audio can't be checked yet and pass unscreened unless blocked
    Open Controls in the demo

    REPORTS

    A report you can hand to an auditor.

    Or to a client, or your own IT team.

    • Compliance reports for Comprehensive privacy, CCPA/CPRA, HIPAA, UK GDPR or EU GDPR
    • Technical reports for IT and security: activity, data types, AI destinations, recommendations
    • Export everything as one document, and your detection and masking history as CSV, JSON or PDF
    • Generated on your device and never available to team admins. They cover protection, never prompt content
    • Full reports come with Teams. Free includes one Privacy summary a month
    Open Reports as a Teams member

    ACTIVITY

    Every detection, logged without the value.

    Each detection on this device: what Locke did, and where the request was going.

    • Pulse counts for the session, the last hour or the last 15 minutes
    • One row per detection, which opens into its full metadata
    • Filter by direction, surface, data type or outcome. On Teams, export the filtered feed as CSV or JSON
    Open Activity in the demo

    SANDBOX

    See what the AI would get, before you send.

    Stage a prompt and watch detection mark each sensitive span.

    • Each detection with its type, token and confidence
    • The masked text: each value becomes a one-way token such as EML_x9k2, always the same token for the same value
    • Reversible tokenization is planned shortly after 1.0
    • The same engine and disclosure policy as your live traffic, so a test shows what your settings will do
    • Nothing tested here is ever sent anywhere
    Run the Sandbox in the demo

    Teams

    Admins set the rules. They never see content.

    Admins see who has applied the rules. Members start already configured.

    As the admin

    You set policy for every seat.

    • My Team: invite people and see who is active or invited
    • Policies: which AI apps and sites must be screened, which data types are always masked, how strict text screening is. Nothing changes on a device until you push them
    • Report requests: ask members for a date range and track pending or done. Each member generates the full report on their own device
    Open My Team as an admin

    As a member

    Protected out of the box.

    • Controls becomes a read-only Team policy page showing what the organization set
    • The same 100% local guarantee: admins set the policy, your data stays on your device
    See the member view

    On a team, members cannot pause protection. Text strictness changes and admin-approved history clears are logged in the reports each member generates. Prompt content is never collected.

    Three views of one app

    Run the demo as Free, a Teams admin or a member.

    Free

    One person, in the browser and the command line. One Privacy summary a month.

    View the demo as Free

    Teams admin

    Members, policies and report requests. The rules, never the data.

    View the demo as an Admin

    Teams member

    Protected from the first login, under the admin's policies.

    View the demo as a Member

    Free for one person. Teams from $14.99 per seat a month. See the plans.

    Why desktop

    A browser extension can't see your terminal.

    So Locke is a native app. Detection pairs checksum-validated patterns with contextual matching, so a case number is caught even when it doesn't look like one.

    Past the browser tab

    The extension screens AI websites. The desktop app covers terminals, scripts and SDK calls.

    Your content stays local

    Detection and masking run on your device. Your prompts, files and detections are never sent to us or any cloud service for analysis. Locke only signs in, checks your licence and syncs settings.

    CLI, API & local models

    A proxy on your machine screens Claude Code, gemini-cli, GitHub Copilot, curl and the official SDKs. Ollama and LM Studio join once you point their client at it.

    Injection & Unicode defense

    Blocks prompt-injection attacks and hidden Unicode tricks before they reach the model.

    File & clipboard scanning

    Opt-in: checks documents and pasted text before they go to a covered AI tool.

    Native on Windows & Linux

    x64 Windows and Linux, in Early Access now. macOS is coming soon.

    In the browser, the Locke Extension does the capture. It's a separate, free install from your browser's store.

    Questions

    Locke FAQ

    Is the demo on this page the real app?

    A click-through replica of the Locke desktop app, built from its real interface and filled with invented sample data: every name, team and number. Switch between the Free and Teams views, open every page and run the sandbox. Nothing you click is stored or sent anywhere. It shows the interface, not the product's internals.

    What is the Locke activity bar?

    A thin light on your screen's right edge that glows when Locke acts on a request. Green: it masked something or held back an attachment. Red: it blocked a request. Amber: something went out unmasked. It stays amber while protection needs attention, such as a stopped detection engine. Clicks pass through, it never takes focus, and it only receives a colour, never what was found. It's on by default on Windows and Linux with X11. Turn it off in Settings › General or the tray menu. Wayland won't let an app hold the screen edge, so there the same colours show as a dot on Locke's tray icon.

    What can a Teams admin see?

    Admins manage seats and team policy, ask members for a date-range report, and see which requests are pending or done. No report content reaches the admin: members generate their own. What members type, and what Locke detects for them, stays on their device. Reports cover what was protected, never what people typed.

    When will Locke be available?

    Now: Early Access for x64 Windows and Linux. macOS is coming soon. Download Locke, sign in and join the waitlist in the app.

    What does Locke protect?

    Locke tells AI traffic from other traffic on your device, including eligible services outside its built-in catalog. Recognizing a service does not mean every request is screened. In the browser, the Locke Extension screens AI websites by holding the request inside the page. A proxy on your machine screens command-line and API traffic: Claude Code, gemini-cli, GitHub Copilot, curl and the official SDKs. Local model servers like Ollama join once you point the client at the proxy. Locke also recognizes and screens desktop wrapper apps such as ChatGPT desktop, Claude desktop and Microsoft Copilot desktop. Coverage depends on the app, platform, request type and settings.

    Is anything sent to the cloud?

    Not your content. Detection and masking run on your device. Your prompts, files and detections never go to us or any third party. Locke needs a Sonomos account: it signs in, periodically confirms your licence (account ID and plan tier, no content) and syncs your settings across devices.

    What pricing will Locke have?

    Free for one person, with one Privacy summary report a month. Teams is $14.99 per seat a month for the first 5 seats, then $10.99 per seat a month for each seat after that. It has a 14-day free trial and a 20-seat cap, US customers only. Teams is for teams, companies and organizations needing insight into, and control over, how members use AI. It includes full compliance and technical reports. Enterprise is coming soon: everything in Teams, plus custom solutions, hands-on support and a rollout planned around your organization. Download Locke, sign in and join the waitlist in the app.

    How it compares

    How Locke compares

    Locke next to the tools you may be weighing it against.

    vs Microsoft Purviewvs CASB / SSEvs self-hosted AIAll comparisons

    Locke Early Access

    Early Access is live. Download Locke, sign in and join the waitlist in the app.

    Download Locke

    Questions first? Read the FAQ.

    Locke has its own privacy policy, separate from our website policy. Read the Locke Privacy Policy and the End-User License Agreement.