Privacy Policy

What we collect

• Recipient email address — stored only as a one-way cryptographic hash, never in plain text. Used to enforce a few anti-abuse rules (blocking a sender who's already been blocked by that recipient, and capping how many different senders can target the same recipient in a short window).
• Forwarding email address — the address you ask replies to be sent to. Stored as plain text, tied to your temporary identity, so a reply has somewhere to go. Deleted when the identity expires (see Retention below).
• Sender display name — the name you choose to send under. Stored as-is, tied to the identity.
• Message content — not stored. Your message passes through our mail provider at send time and is never written to our database, in any form.
• IP address — stored only as a one-way cryptographic hash, used solely to apply rate limits (how many messages or identities one connection can create per day/week), alongside a similar check tied to your browser session. Never stored in plain text, never used for anything besides that.
• A session cookie — a signed, random token that lets us apply the free-tier limits above without requiring an account. It doesn't carry your email, IP, or message content — only its hash is ever stored on our end.
• If you use a paid Access Key: a separate signed cookie holding your customer ID and a 24-hour expiry, so you're not re-entering your Access Key and PIN on every message.

What we don't do

• We don't store your message content — not temporarily, not for review, not at all.
• We don't sell data to anyone, or share it for advertising purposes.
• We don't run ad-network tracking or tracking pixels. The one sponsored placement on our landing page, when booked, is a static text/image slot — no script, no pixel, nothing that tracks you.
• We don't use analytics or advertising cookies. The two cookies described above are the only ones MIRA sets.

Third parties we rely on

We use Mailgun to send and receive email, Supabase for our database and admin login, and Cloudflare Turnstile as a bot-check on the send form (it may set its own cookie or local data under Cloudflare's own policy — we only receive its pass/fail result). We don't use any analytics, advertising, or tracking service, first-party or third-party.

How long we keep things

• Every temporary identity lives for 7 days.
• At expiry, we overwrite the identity's address details outright — this is a hard deletion of the mapping, not a status flag — and it can no longer send or receive mail from that point on.
• For 14 days after that, a minimal, already-hashed remnant of the identity stays on file, solely so a legitimate legal or safety request arriving shortly after expiry can still be acted on (see our Unmask Policy below). After 14 days, that remnant is deleted outright, permanently.
• If you're a paid customer, your account record (credit balance, Access Key) is kept separately, for as long as your account is active. It never contains message content and isn't affected by the identity-level retention above.

Our Unmask Policy

The exact, narrow conditions under which we'd ever reveal a sender's real identity — and how rarely that's even possible, given the retention above — are published in full at our Unmask Policy.

Changes to this policy

We may update this policy as MIRA changes. The version posted here is always the one in effect.