Transparency
Transparency report
How many legal requests we have received, what we could produce if compelled, and what simply does not exist to produce.
Since launch on 6 August 2026, through 16 August 2026: zero requests of any kind. This page starts at zero and will be updated when that changes - a report that only appears once there is something to report is not a report.
0
Government or law enforcement requests
0
Court orders received
0
Subpoenas received
0
National security requests
0
Requests where data was produced
0
Accounts affected
What exists to be handed over
The useful question is not how many requests arrived but what could be produced if one did. PrivaMesh runs one machine - a worker that pays the Solana network fee for each transaction. It sees an account identifier and a timestamp. It never sees plaintext, and it never learns who a message is for.
So a compelled disclosure would show that some account paid for some send at some time. It would not show the message, the recipient, your contacts or your history, because there is no account database and no message store. The architecture page lists every component and what each can observe.
What we cannot do
We cannot decrypt a message, identify who you talk to, produce a contact list, restore your history, or delete your account - there is no account to delete. Those are not policy positions that a court order could change; they are consequences of not holding the data in the first place.
The honest caveats are on the limitations page: the RPC provider sees your IP, the chain records transaction timing permanently, and neither of those is ours to withhold.
Frequently asked questions
What could PrivaMesh actually hand over?
That an account paid for a send, and when. The fee worker sees an account identifier and a timestamp. There is no message content, no recipient, no contact list, no account record and no connection history, because none of those are stored anywhere we control.
Would you tell me if you received a request?
This page is updated when the numbers change. We cannot promise per-user notice, because some orders forbid it - which is exactly why the design aims to hold nothing worth requesting.
Is there a warrant canary?
No. A canary is a signal that becomes meaningful only once it disappears, and a project this small could remove one by accident. Publishing the counts and keeping them current is the more honest version of the same promise.