The numbers below are the entire universe of government, court, and law-enforcement contact SafeLane has had during this reporting period. We commit to publishing this report every quarter for as long as the company exists, and to retaining all prior reports here.
Requests received
| Request type | Received | Fulfilled | Contested |
|---|---|---|---|
| Subpoenas (UK) | 0 | 0 | 0 |
| Court orders (UK) | 0 | 0 | 0 |
| Technical Capability Notices (UK) | 0 | 0 | 0 |
| National Security Letters (any jurisdiction) | 0 | 0 | 0 |
| MLAT requests from foreign governments | 0 | 0 | 0 |
| Civil discovery requests | 0 | 0 | 0 |
| Removal demands | 0 | 0 | 0 |
Accounts affected
Zero accounts have been the subject of any government or law-enforcement request during this reporting period.
What we would disclose, if asked
Because SafeLane is designed with end-to-end encryption, even a fully-compelled response would yield:
- Your email address
- The encrypted ciphertext of your vault items (mathematically opaque)
- KDF parameters and salt (useless without your master passphrase)
- Subscription state (trial / active / cancelled)
- Audit log entries: timestamps and IP addresses of sign-ins
We could not produce the contents of your vault under any conceivable legal compulsion because we do not hold the keys.
What we would refuse
We would refuse — and litigate — any request to:
- Insert a back door into the SafeLane client
- Degrade encryption strength for a subset of users
- Push a targeted client update that exfiltrates a specific user's vault
- Hand over keys we do not hold
- Identify users by aggregate metadata patterns
Warrant canary
As of 17 May 2026, SafeLane has not received any of the requests enumerated above, has not been served with a gag order, and has not been compelled to modify the software in any way.
This canary is republished on the Security page at every release. If it stops appearing, or its wording materially changes without explanation, treat that as a signal.
Past reports
None yet — this is the first quarter of reporting.
Methodology notes
- We count each unique demand once, on the date it was received, not on the date we responded.
- "Fulfilled" means we provided any data in response. "Contested" means we challenged the demand, in whole or in part, before fulfilling or refusing.
- UK-specific request categories are listed because we are a UK company. We will add jurisdictions as they become relevant.
Contact
Press, researchers, or anyone wanting to verify a specific number: email info@usesafelane.com.