Pigeon legal-process log
Requests
One entry for every request we may publish: what was asked, what we could hand over, and what we did.
No requests have been published. As of 24 October 2026, Pigeon had received 0 (report 1).
A request under an order that forbids disclosure isn't listed while the order is in force (why).
What an entry shows
Every entry has the same fields, in the same order, filled from structured data. Nothing on an entry is typed straight into a page.
| Shown as | Field | What it says |
|---|---|---|
| Entry | public_id | DRP, the year, and a number given when the entry is published, never when the request arrives. |
| Received | date | When the request arrived, to the day, the month or the quarter: in a small service an exact date can identify someone. |
| Kind | type | One of the kinds in the report: subpoena, court order, search warrant, and so on. |
| Jurisdiction | jurisdiction | The country, then federal or the state or region; the court or agency where we may say so. |
| Asked for | asked | What the request asked for, from a closed list of categories. |
| What we could hand over | could_produce | Filled in by the build, not by a person: for each category asked, the answer from the version of our table in force on the date received. |
| What we handed over | produced | For each category: none held, produced, produced after narrowing, or refused. |
| Challenged | challenged | Whether we pushed back, and how: narrowed by agreement, challenged in court, or a gag order challenged. |
| User notified | user_notice | Whether the person was told, and if not, why. |
| Status | status | Open, complied, partly complied, refused, withdrawn or closed. |
| Documents | documents | The request and our reply, redacted, where the law lets us publish them, each with its SHA-256. |
| Approved by | approved_by | Pigeon's owner, who signed it off, and the date. The build refuses an entry without that sign-off. |
| Corrections | history | Every change after publication, with its date. Nothing is edited over. |
The format is published as a schema: entry.schema.json.
An entry never shows anything that identifies a user or a requester's staff: no handles, keys, addresses, names, phone numbers or emails. The format has no field for them, and the build rejects an entry with any field the format doesn't list.