Pigeon transparency report
Here is everything we've been made to drop, and everything we could. It's mostly nothing, because we don't keep it.
Report 1, published 22 October 2026. Reports are moving to their own site, droppings.io; this first one stays here.
Requests received
As of 22 October 2026, Pigeon has received:
| Kind of request | Received |
|---|---|
| Subpoenas | 0 |
| Court orders for records | 0 |
| Search warrants | 0 |
| Orders to collect data from now on (pen register, wiretap) | 0 |
| Preservation requests | 0 |
| Emergency requests | 0 |
| Requests from outside the US | 0 |
| Civil subpoenas from private parties | 0 |
| Copyright (DMCA) notices | 0 |
| Take It Down Act requests | 0 |
| Other removal requests and court-ordered removals | 0 |
| Reports to NCMEC | 0 |
Accounts affected: 0. Data produced: none.
National security requests (national security letters and orders under the Foreign Intelligence Surveillance Act) aren't in this table. US law lets a provider report them only in ranges, for set periods, after a delay, and longer for a new service (50 U.S.C. 1874). We'll report them in the form the law allows once we're allowed to.
What we could give
This is what Pigeon's servers currently hold, and so the most any request could get. It's the same table as in our law enforcement guidelines; if it changes, both change, and this report records the date.
- Message content: only encrypted data we can't decrypt, while it waits to be delivered. No keys.
- Who talks to whom, contact lists, groups: nothing.
- Name, phone number, email, payment details: nothing; we don't ask for them.
- IP addresses: none from the past; our servers don't record them. A court can order a provider to start recording, and if one did, we'd report it here when the law allowed.
- A handle's public key Planned: public anyway.
- An abuse report someone chose to send us: that report.
How we count
- Every request we receive is counted under the kind in the table, as of the report's date, with the number of accounts it named and what we produced.
- Some orders legally prevent disclosure. A court can order a provider not to tell anyone about a subpoena, order or warrant for a time (18 U.S.C. 2705(b)), and national security letters carry a gag by law. We don't publish anything an order forbids us to publish. When a gag ends, we'll add the request, with the period in which we received it.
- The counts are true on the date shown, and only then. They make no promise about any later date.
- No warrant canary. Some services publish a statement such as “we have never received a secret order” and remove it if one arrives. We don't. Whether a canary works in law is untested in the courts, and a false sense of safety is worse than none. Nothing on this page is a canary, and if this page stops being updated, read nothing into that alone.
- Where it's lawful and safe, we'll publish the request and our reply, with personal details removed. Anything about a child's safety or an emergency is never published in a way that could identify anyone.
- Removals. Every file we remove after a report or request is counted. Our servers delete only the exact upload named.
- Corrections are added with their date. We don't quietly edit a published number.
We publish a new report at least every six months.