Privacy Policy

1. Who is responsible

2. What we process, why, and on what legal basis

• Account and sign-in: your email address, workspace name and role, the sign-in methods you set up (passkeys, the identifier and email of a linked Google, GitHub or GitLab account), and your active sessions with the browser and IP address they came from — to provide the service (performance of the contract).
• API keys and workspace configuration: key names, permissions and last use, sending domains, delivery and monitoring endpoints, inbound forwarding addresses and endpoints — to provide the service (performance of the contract).
• Billing: plan, subscription status and billing country; card and invoice details are collected by our payment provider — to take payment (performance of the contract) and to keep accounting and tax records (legal obligation).
• Security and abuse prevention: a log of account changes (who, what, when, from which IP address), delivery counters, one-way hashes of recipient addresses, and server logs, which can contain IP addresses and, when a service email cannot be queued, the account email address — our legitimate interest in keeping accounts secure, running the service reliably and protecting deliverability for all customers.
• Service emails: sign-in links and codes and notices about your account — performance of the contract.
• DMARC reports: when your domain's DMARC record names our report address, mailbox providers send us aggregate reports about mail using that domain. We keep the reporting organisation, report id, date range, sending IP addresses, message counts, the result and alignment of DKIM and SPF, and the domain in the From header, and we send you a summary — to provide the service (performance of the contract). These reports are processed in the EU only. We do not accept forensic (per-message) reports.
• New workspaces: if you answer "How did you hear about us?" when you sign up on our website, your answer from a fixed list (the question is optional). When a workspace is created, we send its name, the owner's email address, the plan and that answer to our own inbox so we can welcome new customers personally — our legitimate interest in learning which channels bring customers and in getting in touch with them.
• Offer claims: if you claim the migration discount or the founding-partner offer, the email address you give, which offer (and for the migration discount, which provider you are leaving), whether we approved it and when it was used — to decide on the claim and apply the discount at checkout (steps at your request before a contract and performance of the contract).
• Product feedback you choose to send (from the dashboard, the API, the command-line tool, or an AI agent using our plugin, which sends it only after you approve the draft): its rating, the product area, what you write about what worked or did not and what you were trying to do, whether a person or an agent wrote it, and which workspace and API key or user sent it. We refuse feedback that contains an email address. We may also receive it by email in our own inbox — our legitimate interest in improving the service.
• Messages you send to our contact address: your email address and what you write — our legitimate interest in answering you.

3. Email you send through Blindrelay

4. Who receives data

5. Transfers outside the EU

6. How long we keep data

• Account, workspace configuration, API keys and suppression entries: until you delete them or the workspace.
• Sessions, with their browser and IP address: until the session ends or expires.
• Log of account changes: 90 days. Records of actions our staff take on a workspace: 12 months.
• DMARC aggregate report data, including sending IP addresses: 90 days, or until you delete the domain or the workspace.
• Server logs: 30 days.
• Messages waiting to be retried: up to 24 hours, then deleted (none if the workspace turned retries off).
• Delivery records: deleted when delivery finishes; bounce matching data and delivery counters up to 72 hours; recipient hashes used to detect list abuse up to 48 hours.
• Offer claims: until we decide on them; a rejected claim, or an approved one not used in time, for 12 months after the rejection or the end of the period to use it; a claim whose discount was used, for 10 years after it was used, as evidence for our accounts.
• New-workspace notices in our contact inbox (workspace name, owner email, plan, sign-up source): 12 months after they arrive.
• Product feedback you choose to send: 12 months after you send it.
• Invoices and payment records: 10 years, as Czech tax law requires; they are kept by our payment provider.

7. Your rights

8. Right to object

9. Complaints

10. Whether you must provide data

11. Automated decisions

12. Storage in your browser

13. Changes to this policy