Trust is earned in the open.
A privacy product shouldn't ask for faith. This is what we do and don't do, in terms you can check.
What leaves your device
None of your content. Only what it takes to run your account.
Your prompts & files
Processed on your device. Sensitive values become one-way placeholders before anything goes to the AI provider you configured. Reversible tokenization is planned shortly after Locke 1.0.
Detection results & counters
Stay in local files on your machine, with owner-only permissions.
Telemetry / analytics
No behavioural analytics, and no background channel for it. Crash reports and support messages travel only if you send them.
Your Sonomos account
Sent to Sonomos. Locke requires a signed-in account. Sign-in runs through Clerk, our authentication provider, which holds your name, email address and session activity.
Licence check
Sent to Sonomos periodically while the desktop app runs. It carries your account identifier and plan (Free or Teams), and no content, detection data or usage data. Like any request, it discloses your IP address. We keep your current subscription status, not a usage history.
Your settings
Which AI services Locke monitors and which categories it flags. Synced to your account so they follow you across devices and, on the Teams plan, so an administrator can apply a policy. Configuration only: no content, and no record of the sites you visit.
Your content to Sonomos servers
Never. No Sonomos server receives the content Locke inspects. It is processed on your device, and the masked request goes straight to the AI provider you chose.
This website
Static pages. No cookies and no tracking, only anonymous analytics. See our no-tracking policy and our website privacy policy, which covers every site on sonomos.ai. Locke has a separate privacy policy.
We make money from Teams plans, not data
A free plan for individuals, paid Teams plans and no ads. We don't sell data, and the processing that matters happens on your machine, not ours.
Check our work
Read how Locke is built and where it falls short.
The Sonomos Trust Center
Locke's security documentation for enterprise review: architecture, threat model, compliance readiness and known gaps. Access-restricted during the beta. The link asks you to sign in, and we grant access for security reviews on request.
trust.sonomos.aiWhat Locke does not cover yet
Microsoft Copilot browser chat, browsers without the extension, files Locke cannot read, and what we plan to add.
Known limitationsNot yet audited or certified
Our engineering repos keep an HONEST.md file of what isn't true yet. This is the public version.
Locke is pre-1.0. It hasn't yet undergone a formal third-party security audit or a SOC 2 Type II audit. Both are planned.
For now, our claims rest on reproducible benchmarks, not certifications. You can run the same benchmarks we do, straight from the repos.
Report a vulnerability
We welcome responsible disclosure and commit to responding. The formal policy is in our security.txt.
See it on your own machine.
