We commit to publishing a transparency report at least annually. Even if the answer is zero, publishing zero is meaningful — it establishes the pattern, and it's contractually harder to walk back than a first-time public number.
Reporting period
This report covers the period from launch (2026-03-01) through 2026-08-06. Next scheduled report: 2027-02-01, covering the second half of 2026 and the first month of 2027 (then annually).
Requests received
Requests complied with
Zero requests received means zero complied with. If we ever receive a valid legal request, we'll disclose only the specific data legally required, notify affected users when legally permitted, and update this page.
How we handle a request when we get one
- 1. Verify authenticity — is this actually issued by the claimed authority, and are the certifications intact?
- 2. Verify legal scope — does this request cover data we hold, and is the scope proportionate?
- 3. Push back on overreach — if a request is vaguer or broader than the law permits, we ask for narrower scope in writing.
- 4. Notify the affected user — unless a gag order specifically prohibits it, we notify the user before disclosing their data. Where a gag prohibits notification, we still note the number in this report even if we can't identify the case.
- 5. Disclose only what's required — we do not volunteer additional data beyond the specific scope.
- 6. Log the request permanently in our internal audit trail.
Canary statement
As of the last update to this page ( 2026-08-06), LADLE has not received any national-security letters, gag orders, or classified legal-process requests that would prohibit us from stating so. If this canary text is ever removed or fails to update, that removal is itself the signal.
Related
/legal/privacy-choices — your rights · /legal/dpa — data-processing terms · /legal/subprocessors — every vendor we use.
REPORT A LEGAL PROCESS · LEGAL@LADLE.CHAT