The app, screen by screen
Reports
Turns the detection history saved on this device into a document someone else will accept — an auditor, your security team, or your own records.
Available toAll plans
Everything here is about this device, under your account. The page says so in its header, and every report says it again: there is no organization-wide report, and nothing on this page is sent anywhere until you save or print it yourself.
| Card | Written for | Contains |
|---|---|---|
| Export everything | Anyone who asked for 'everything' | Your technical report, detection history and Comprehensive privacy compliance report for the period, in one document. |
| Compliance report | Auditors, legal, insurers | Your detection history summarized for the privacy regime you pick. |
| Technical report | IT and information security | Detailed activity, sensitive data types, AI destinations, and recommendations. |
| Detection history deletions | Anyone checking that the record is complete | Every clear of detection history made on this device, under this account. |
| Detection & masking history | You, and anyone who wants the raw record | The event-by-event list, exportable as CSV, JSON or PDF. |
| AI service policy outcomes | IT and security | Decisions Locke's proxy made under your AI-service policy on this device. |
| Engine access audit trail | Security reviewers | Which processes the detection engine admitted or refused. Identities and outcomes only, never content. |
The Report period at the top governs every report and export below it.
- Report period — one choice for the whole page. Dates are UTC calendar days.
- Export everything — one document with everything, for when you don't know which report they want.
- Compliance report — pick the privacy regime.
- Technical report — optionally append the full event history.
The Report period
The Report period card at the top of the page sets the period for every report and export on it. There is no separate date range per report: each card simply repeats the period you chose, with a reminder to change it above. Dates are UTC calendar days, so the same detection lands in the same month on every machine.
| Period | Covers |
|---|---|
| Current app session | Since the Locke app last started. The default. It reads the live session buffer of up to 2,000 events; choose another period to read the stored history. |
| This month | From the first of the current UTC month. |
| Last month | The whole previous UTC month. The usual choice for a monthly report. |
| Last 30 days | The rolling 30 days up to today. |
| Custom range | Your own start and end dates, both included, up to 366 days. |
The header's Refresh re-reads the figures, and Detection counts read at … tells you when they were last read. Every full report also lists the text strictness in force (relaxed, standard or strict) and every change to it — when, from what, to what, and by whom or what source — along with pauses and detection-history clears in the period.
Export everything
One document with your technical report, your detection history and a Comprehensive privacy report compliance section, all for the selected period. Use it when someone asks for "the report" and you don't know which one they mean.
Export everything, Compliance report and Technical report each end in the same four buttons. (Detection & masking history has its own: Export CSV, Export JSON, Save as PDF and Print….)
| Button | What you get |
|---|---|
| Save as PDF | A PDF file, ready to send. |
| Download HTML | The same report as a web page, with the evidence payload embedded for verification. |
| Download JSON | The machine-readable data, for your own tooling. |
| Print… | Your system's print dialog. |
There is no preview step: the report is built from the period and options on the page at the moment you press the button.
Compliance report
The report an auditor wants: your detection record, summarized for a specific privacy regime. Review it before sharing.
| Regime | Use when |
|---|---|
| Comprehensive privacy report | You want the evidence without tying it to one framework. The default. |
| CCPA / CPRA | California consumer privacy. |
| HIPAA | US healthcare — protected health information. |
| UK GDPR | You process personal data of people in the UK. |
| EU GDPR | You process personal data of people in the EU. |
- Your compliance lead asks for evidence that patient data isn't reaching AI tools in September. Open Reports.
- In Report period, choose Last month — or Custom range with the dates they asked about.
- On the Compliance report card, set Privacy regime to HIPAA.
- Press Save as PDF (or Download HTML if they want to verify it). Note the report ID printed in the file — it lets you check a copy later.
Technical report
For IT and security readers who want the shape of the risk rather than a regulatory framing: detailed activity, which sensitive data types appeared and how often, which AI destinations received traffic, and recommendations based on what it found.
Tick Append detection & masking history (same date range) to add the full event list to the end — useful when you're handing over a single file and expect follow-up questions.
Detection & masking history
The raw record for the period, newest first and metadata only — no value is ever on an event. The table shows 25 events at a time and reveals more on request; Details on a row opens every field recorded for it. Exports always include every event in the period.
| Column | What it holds |
|---|---|
| When | When the detection happened. |
| Outcome | What happened to it: masked, unmasked, blocked, withheld, mask failed, bypassed, or outcome unknown. |
| Data type | What was found. |
| Direction | Outbound (you to the AI) or inbound (the AI back to you). |
| Destination | The AI service the request was headed to. |
| Surface | Which capture path recorded it — Locke's proxy or the browser extension. |
| Values masked | How many values were replaced. |
Export CSV and Export JSON give you the whole period as data; Save as PDF and Print… produce it as a document. For a live view of the same events, with filters and search, Open Activity takes you to the Activity page.
Deletions and audit trails
Three cards record what happened to the record itself, so a reader can judge how complete it is.
| Card | What it shows |
|---|---|
| Detection history deletions | Every clear of detection history made on this device under this account: the dates cleared and who approved it. "No approval required" is its own state — your own clear on Free, or an admin's own clear, has no approver. The card's own record is kept for the signed-in account and erased when you sign out, and an empty list is not proof that nothing was ever deleted — the card says so. Clears are made in Settings › Data & privacy. |
| AI service policy outcomes | Decisions recorded when Locke's proxy applied your AI-service policy on this device. Empty until it has applied one. |
| Engine access audit trail | The detection engine's own append-only record of every process it admitted or refused, filterable by outcome and by service. Identities and outcomes only, never content — it records access, not what an admitted process did afterwards. |
Report IDs and digests
Every saved report carries an integrity digest — a SHA-256 fingerprint of the evidence embedded in it — and a report ID made from the generation date and the first eight characters of that digest. The report itself explains how to recompute the digest, so anyone with a copy can check it. Be clear about what that proves: a match shows the embedded evidence is unchanged. It is not a signature, it is not countersigned by anyone, and it does not prove the device or its logs were accurate. Keep the ID with the file.
When your admin asks for a report
Available toTeams MemberTeams Admin
Admins can ask members for a report under My Team › Team reports — see My Team. The member sees a banner on their Reports page: Your team admin asked you for a report, naming the regime and dates. Use requested settings sets the period and regime to match; saving Export everything or the Compliance report as a PDF, HTML or JSON file completes the request. Printing, and the other reports, don't.
The report is generated on the member's device and stays there. The admin sees only that it was generated — never what is in it, and no detection figure. Reports and exports stay local to each device and account; to share one, the member sends the file themselves. There is no combined report across the team yet — see Known limitations.
One caveat worth stating plainly: these reports show what Locke detected and what it did about it. They are evidence about the tool’s activity, not an audit, a certification, or legal advice, and producing one does not by itself make an organisation compliant with HIPAA, the GDPR, the CCPA or anything else. Detection is best-effort and can miss things. Whether your programme satisfies a given regime is a judgement for your compliance team and your counsel.
On the Free plan
Available toFree
Free shows one card you can use — the Monthly privacy summary — and the Teams reports as locked cards with Upgrade to Teams.
One summary a month on Free. The other reports are part of Teams.
The summary is a one-page overview of the month for your own records: total detections this month, your top categories, whether protection is on, and your text strictness. It is not an audit record and is watermarked as one. Press Save this month's summary as PDF; you get one per UTC calendar month, and downloading the same month's summary again is free. The allowance is counted on your Sonomos account, not on this computer, so Locke needs to reach your account to save one — and signing out, reinstalling or clearing local data doesn't reset it.
