Our approach
Secbird is built to protect private communication. We also recognise that authorities sometimes need information to investigate serious crimes. This page explains how we respond to requests for user data, what we can and cannot provide, and how requests must be submitted.
Requests must be valid and binding under Swiss law
We only respond to requests that are legally valid and binding under Swiss law and that are issued by a competent authority. Requests from authorities outside Switzerland must be made through the appropriate international legal assistance channels so that they can be reviewed and, if valid, enforced by the competent Swiss authorities.
Every request is reviewed carefully. We check that:
- the request comes from an authority with jurisdiction;
- it has a valid legal basis and follows the required procedure;
- it is specific, identifying the account concerned and the information sought;
- it is proportionate to the investigation.
We push back on requests that are unclear, overly broad or not properly authorised, and we may challenge them where appropriate.
What we cannot provide
Because of how Secbird is designed, we cannot provide the content of users' email:
- Messages are end-to-end encrypted or stored with zero-access encryption using keys that only the user holds.
- This includes message bodies, attachments, subject lines, contacts and calendar data.
- We do not hold users' passwords or unlocked private keys, so we cannot decrypt stored data, now or in the future.
We do not log the IP addresses users connect from, and we do not require a phone number or another email address to create an account, so we cannot provide this information either.
What we may be able to provide
In response to a valid and binding order, the information we may be able to provide is limited to:
| Information | Availability |
|---|---|
| Account username and creation date | Available |
| Plan type and account status | Available |
| Payment records for paid plans, such as amount and date | Available if a paid plan was purchased |
| Message content, subjects, attachments, contacts, calendars | Not available: encrypted with the user's keys |
| IP addresses used to access the account | Not available: not logged |
| Phone number or recovery email | Not available: not collected |
User notification
We believe users have a right to know when their data is requested. Our policy is to notify the affected user of a request before disclosing any information, so that they have the opportunity to seek legal advice or challenge the request. We will only delay or withhold notification where a court order or applicable law expressly prohibits it, and we will notify the user once the prohibition ends.
Emergency requests
In exceptional situations involving an imminent threat to life or of serious physical harm, we may consider an emergency request from a competent authority. Such requests must explain the nature of the emergency, and they are still limited to the information described above.
How to submit a request
Requests must be sent by the competent authority to legal@secbird.me. Please include:
- The name of the requesting authority and the officer responsible, with official contact details.
- The legal basis for the request and a copy of the order or decision.
- The Secbird address concerned.
- A specific description of the information requested.
We do not accept requests through other channels, and we do not respond to informal requests.
Transparency
We are committed to being open about how we handle requests for user data and to explaining our practices publicly.