Requests by type
| Type | Received |
|---|---|
| Demands for user dataSubpoenas, court orders and warrants seeking information about a person who uses Glossia. | 18 |
| Emergency requestsRequests made without legal process where someone’s life or safety was said to be at risk. | 1 |
| Requests about relaysDemands for logs, traffic or access to a relay that Frothly runs. | 3 |
| Requests to remove or block contentGlossia carries only encrypted messages, so there is nothing for us to remove. | 0 |
| Demands to weaken GlossiaDemands to add a way to read messages, or to change the software to help someone do so. | 0 |
| Total | 22 |
Where requests came from
| Region | Requests |
|---|---|
| North America | 8 |
| Europe | 5 |
| Latin America and the Caribbean | 1 |
| Africa | 1 |
| Middle East and Central Asia | 2 |
| South and Southeast Asia | 4 |
| Oceania | 1 |
We report regions rather than countries where a single request could identify the person it concerned.
What we disclosed
No user data. We do not have messages, contact lists, account details, phone numbers or logs of who connected to which relay, so there was nothing to disclose.
In 2 cases we confirmed information that is already public: that a relay is listed in the directory, and which organization runs it.
Notes
In March, a county sheriff’s office in Southern California asked us to identify the person behind a set of messages that, it later emerged, had been sent by one of its own undercover officers. We had no records to provide, and the request was withdrawn.
Police in Oceania made an emergency request concerning a missing person. We hold no information that could help locate anyone. We told them so within the hour, and suggested where else they might look. The person was found safe.