Law Enforcement Guidelines

Legal process requirements, technical limits on what Elektrine holds, and emergency threat reporting.

01 Legal process required

Elektrine discloses non-public user records only in response to valid, binding legal process issued with jurisdiction over Elektrine. Informal emails, phone calls, or unverified requests are not fulfilled.

Requests from agencies outside Elektrine's operating jurisdiction must come through an applicable Mutual Legal Assistance Treaty (MLAT), letters rogatory, or equivalent domestic court process.

  • Identify the issuing court or authority, official contact details, and case or docket reference.
  • Name a specific Elektrine identifier (exact email address, handle, or account number) and a narrow date range.
  • State the legal basis and the exact category of records compelled. Overbroad or fishing requests will be narrowed or challenged.

02 Data that does not exist

Elektrine is built so sensitive data is never collected or never readable by the server. Legal process cannot compel records that do not exist.

  • IP addresses: we do not store IP addresses in web logs, Postgres, sessions, API tokens, passkeys, outgoing mail headers, or Maid VPN. Abuse and rate-limit counters use keyed hashes in volatile RAM.
  • Identity documents: registration does not collect legal names, phone numbers, street addresses, or government IDs.
  • Client-side encrypted content: when zero-knowledge browser encryption or E2EE chat is enabled, mail, files, notes, calendar, contacts, passwords, and messages are encrypted with user-held keys Elektrine does not hold and cannot decrypt.
  • Maid VPN: no traffic logs, DNS history, or connection logs. Anonymous blind tokens are cryptographically unlinkable to accounts.

03 Account types and burner aliases

Standard accounts

For non-Monarch accounts, the database holds basic account metadata (username or generated account number, handle, creation timestamp, optional recovery email if added) and mailbox/content records that are readable only when the user has not turned on client-side encryption.

Monarch accounts

Monarch accounts do not store real usernames, canonical email addresses, account numbers, recovery emails, invite/payment linkage, or fine-grained login telemetry in Postgres. Timestamps are coarsened to UTC midnight, and mail, files, notes, calendar, and contacts are encrypted client-side with user keys.

Stateless burner aliases

Monarch burner addresses (<55-char>@<domain>) are stateless RFC 5297 AES-256-SIV tokens rather than rows in an alias table. Elektrine keeps no log of burner creation times or recipient lists.

While the split-key routing oracle is online, a burner address can be resolved to an opaque internal account row (placeholder username a<14-hex>) so Elektrine can stop active abuse or ban the account and revoke all 256 burner slots. That account row still contains no real name, IP logs, payment linkage, or plaintext content.

04 Preservation requests

Upon receiving a formal written preservation request from a government agency identifying a specific account or address, Elektrine can preserve existing, non-deleted account records as they exist at that moment for up to 90 days pending formal legal process (renewable once upon written request).

Preservation applies only to records that already exist on disk. It does not enable logging, recover deleted data, or decrypt client-side ciphertext.

05 Emergency and imminent threats

If an Elektrine address is being used for a credible, imminent threat of death, serious bodily harm, or violence (such as a bomb threat), contact us immediately from an official agency email address. We will immediately suspend outbound sending and revoke all associated burner aliases once we verify the message originated from Elektrine.

  • Include the full raw email headers (DKIM-Signature, Received, Authentication-Results). External senders routinely spoof From: headers; raw headers let us confirm the message actually left Elektrine before banning an account.
  • Include the requesting officer's full name, agency, badge or ID number, direct callback number, and a concise description of the imminent threat.

06 User notice and transparency

Our default policy is to notify affected users before disclosing account information, unless a binding non-disclosure order prohibits notice or there is an imminent threat to life or physical safety.

Aggregate counts of legal demands we are allowed to mention are published in our Transparency Report, and our signed Warrant Canary is updated regularly.

07 Contact

Legal process
legal@elektrine.com
Abuse / urgent stop
abuse@elektrine.com