Government requests
How we respond when law enforcement or a government agency demands user data — and the numbers, published every six months.
Four rules, no exceptions
Valid legal process
We do not volunteer user data to governments. Every request must arrive through valid legal process appropriate to the data sought.
Narrowest scope
We review every demand for overbreadth and produce the narrowest data set that satisfies it — or push back in court.
User notice
We notify affected users before producing their data unless a court order or clear statute prohibits it, and after any gag expires.
Semiannual reporting
We publish request counts and disclosure rates twice a year, in the most granular bands the law allows.
What we can and cannot produce
SpaltX holds far less data than most assume. Aircraft do not stream flight video to us by default, and we require escalating legal process as data gets more sensitive. The full rules are in the Government Data Request Policy.
| Request type | Minimum legal process | Data reachable |
|---|---|---|
| Subpoena | Valid administrative, grand jury, or trial subpoena | Basic subscriber records: name, email, billing address, account creation date, order history metadata. |
| Court order (18 U.S.C. § 2703(d)) | Court order on specific and articulable facts | Non-content records and logs: sign-in timestamps and IP addresses, firmware download and entitlement logs, fleet device registration records. |
| Search warrant | Warrant issued on probable cause by a court of competent jurisdiction | Stored content: support and contact message bodies, Forge documents and CAD files, uploaded attachments. |
| Emergency disclosure | Good-faith belief that disclosure is needed to prevent death or serious physical injury | The narrowest data set that addresses the emergency, evaluated case by case by our legal team. |
| National security process | National Security Letter or FISA process | As compelled by the specific process; reported only in bands, as US law requires. |
The numbers
Requests received and requests where any data was produced, per reporting period. A produced request often covers a fraction of the records demanded.
Our Government Data Request Policy took effect July 16, 2026, and the first reporting period (July – December 2026) is still open. The first transparency report is due January 2027 and will appear here.
We publish counts only once a period closes and the tally has been verified. We will not post estimated or illustrative figures on this page: an empty table is honest, an invented one is not.
Submitting a request
Serve legal process on our registered agent, or submit it from an official government email address to lawenforcement@spaltx.com. Requests from personal email addresses are not processed. General questions can go through the contact form.
- The issuing agency, requesting officer, and a badge or ID number
- The specific account identifier (email address or order number)
- The precise records sought and the relevant date range
- The legal authority for the request, attached as served process
- A response deadline consistent with the process served
Emergency disclosure
Where there is a good-faith belief that disclosure is needed to prevent death or serious physical injury, mark the subject line EMERGENCY and send the request to lawenforcement@spaltx.com. Include the nature of the emergency, why the records are needed to address it, and a callback number. Emergency requests jump every other item in our queue and are answered before anything else.
Definitions, required process per data type, user notice, preservation, non-US requests, and cost reimbursement — the complete rules we apply.