Legal

Law Enforcement & Data Request Guidelines

v2 · 2026-09-05 · draft pending counsel review

We comply with valid legal process. Full stop. We do not volunteer data, we do not respond to informal asks, and we do not collect data "just in case" it is ever requested. Because the service is architecturally no-logs, the answer to most content requests is not a refusal — it's an empty set.

What we require, by data tier

Requested dataMinimum process
Basic account records (email, signup date, credit totals)Jurisdictionally valid subpoena
Transaction metadata (per-request model name, token counts, timestamps; authentication/access log entries within their retention window)Court order (18 U.S.C. § 2703(d) or equivalent)
Content of prompts or completionsSearch warrant on probable cause — and none exists; see below

Foreign requests must come through applicable MLAT or letters rogatory unless clearly permitted by both our law and yours.

What exists to hand over

We do not possess: prompt or completion content, conversation histories, or usage content of any kind. Our database schema has no column that holds them and the gateway's content logging is disabled. A warrant for content is answered with an affidavit describing this architecture.

What we will do

  1. Verify jurisdiction, validity, and scope of every request before any disclosure.
  2. Narrow or challenge overbroad requests through counsel where grounds exist.
  3. Notify the affected user before disclosure whenever the law permits, and publish a delayed notice after any gag period expires.
  4. Publish an annual transparency note: requests received, complied with, challenged, and the categories involved.
  5. Disclose without process only where the law compels it (e.g., NCMEC reporting obligations) or where we reasonably believe someone's life is at imminent risk.

Contact

legal@cheapweights.ai. Requests on letterhead, with case number and the specific legal instrument. We do not accept service by support ticket, DM, or phone.