Law Enforcement Guidelines
For police, prosecutors, courts and other authorities requesting data about Inpriv users. Users can read this page too: we publish it so everyone knows how requests are handled.
Requests go to legal@inpriv.xyz, sent from an official government email domain. Emergencies: see below. Requests in English are handled fastest.
What exists, and what doesn't
Inpriv is built so that some data never reaches us. We can only provide records we actually hold. The Privacy Policy describes all of them.
| Record | Available? | Kept for |
|---|---|---|
| Account: username, @inpriv.xyz address, display name, created and last sign-in times, whether 2FA is on | Yes | Life of the account |
| Recovery email address, if the user added one | Yes | Until removed or the account is deleted |
| Access log: the network an IP address belongs to (IPv4 /24, IPv6 /48, not the full address), country, network operator (ASN), browser family and time, for sign-ins (including failed ones), account changes, mailbox creation and key changes, and sent messages (without the recipient) | Yes | 30 days |
| Access-log entries written before 22 October 2026: full IP address, full user agent, and the recipient of sent messages; Temp inbox creation | Yes, until they expire | 90 days after they were written (all gone by 20 January 2027) |
| Sessions and account security events (with the first part of the IP address and the browser name) | Yes | Up to 90 days |
| Which network created a Temp inbox | No. Not recorded. | — |
| That an address was issued: the address, the kind of service (account, Temp, team) and the day | Yes | As long as Inpriv runs |
| Mail metadata: the other party's address, subject line, time and size of each stored message | Yes, while the user hasn't deleted the message | Until the user deletes it |
| Content of stored Mail messages (between Inpriv users, and mail from outside after it's stored) | No. Encrypted to the user's keys, which are locked with a passphrase we never receive. Mail to and from other providers is readable to our server only while it passes through, and isn't kept in readable form. | — |
| Temp inbox: address, created and expiry times, and received messages, including content | Only while the inbox exists | 24 hours |
| Passwords, mailbox passphrases, private keys | No. Passwords reach our server at sign-in to be checked and are stored only as salted hashes. Passphrases and private keys never reach it. | — |
| Real name, postal address, phone number, payment details, ID documents | No. We don't collect them. | — |
Mail sent to or received from other providers passes through our email provider Resend and the other provider. They may hold their own records, under their own policies.
What a request must include
- the name of the authority, and the name, rank, phone number and official email of the requesting officer;
- the legal basis: a subpoena, court order, warrant or equivalent valid legal process, with a copy attached;
- the exact identifiers:
@inpriv.xyzaddresses, or IP addresses with exact timestamps and timezone; - the specific records you're asking for, and the time range;
- any non-disclosure order, and the legal basis for it.
We review every request for validity and scope. We push back on requests that are overly broad, unclear or not legally valid, and we disclose only the minimum the process requires. Requests from authorities outside the jurisdiction we're bound by may need to go through a mutual legal assistance treaty (MLAT) or a similar channel.
Emergencies
If there's an imminent risk of death or serious physical injury, write to legal@inpriv.xyz with the subject "EMERGENCY DISCLOSURE REQUEST". Describe the emergency, explain how the data will help, and include the identifiers. We may voluntarily disclose information that's needed to prevent the harm, where the law allows.
Preservation
We'll preserve specific existing records (for example access-log entries that would otherwise be deleted after 30 days) for 90 days on receiving an official preservation request, while you obtain formal legal process. We'll extend that once by another 90 days if asked. A preservation request doesn't disclose anything; it only keeps data from being deleted.
Notifying users
We tell users about requests for their data before disclosing it, so they can seek legal advice, unless:
- the law or a court order forbids it;
- it's an emergency;
- notice would endanger someone or seriously harm an investigation.
When a restriction ends, we'll notify the user.
Requests we don't accept
- Requests that don't come from an authority, or don't come through valid legal process. This includes requests from private parties, lawyers or companies for other people's data, unless the law requires us to comply.
- Requests to decrypt content, to weaken encryption, or to add surveillance to the service. We can't decrypt stored mail, and we won't build a way to.
Abuse reports
If you only want to report abuse, such as spam or phishing from an @inpriv.xyz address, and aren't requesting data, write to abuse@inpriv.xyz. We act on abuse without a legal request; see the Acceptable Use Policy.