Draft — pending legal review. This document has not yet been reviewed by counsel and may change before Irisend is generally available.
Privacy Policy
Effective date: 2026-11-10
This Privacy Policy explains how Irisend ("Irisend", "we", "us"), registered at [to be completed: COMPANY_ADDRESS] (KVK [to be completed: KVK_NUMBER]), collects, uses, and shares personal data.
Two roles. Irisend processes two categories of personal data:
- Account data — information about you as our Customer (or your team members) when you sign up for and use the Irisend dashboard and API. For this data, Irisend is the data controller and this Privacy Policy applies directly.
- Recipient/message data — information contained in or generated by the emails our Customers send or receive through the Service (e.g., recipient and sender email addresses, message content and attachments, open/click events) ("Customer Content"). This includes inbound emails sent to a domain on which a Customer has enabled receiving. For this data, Irisend is a data processor (or "service provider" under CCPA/CPRA) acting only on the instructions of our Customer, who is the controller. If you received an email sent via Irisend, or sent an email to an address that receives through Irisend, and have questions about that email, please contact that organisation directly — we are not able to act on data-subject requests about Customer Content ourselves except as instructed by, or under the direct arrangement with, our Customer. Our processing of Customer Content is governed by our Data Processing Agreement, not this Privacy Policy.
The rest of this policy addresses our role as controller of account data.
1. What We Collect
- Account and identity data: name, email address, password hash, sign-in security credentials you choose to set up (the public key and identifier of each passkey, and — for authenticator-app two-factor authentication — an encrypted secret and encrypted backup codes), company name, billing address, tax ID, phone number (optional).
- Payment data: processed by our payment processor (Stripe); we store limited metadata (e.g., last 4 card digits, subscription status) but not full card numbers.
- Usage and log data: API requests, dashboard interactions, IP address, browser/device information, timestamps, sending volumes, and diagnostic logs, collected for security, billing, and service-improvement purposes.
- Third-party integration data: if you choose to connect a third-party DNS provider account (currently: Cloudflare, via OAuth) to automate sending-domain setup, an access/refresh token for that account, which we use only to read and write the DNS records needed for your domain, until you disconnect the integration.
- Abuse-prevention and risk data: signals we use to keep spammers and bots off the Service: the IP address, email domain, and bot-challenge result (Cloudflare Turnstile) at sign-up, risk flags and scores for your Team, your trust tier and its history, results of the checks we run on your sending domains (registration date, blocklist listings), the outcome of scanning your Messages (see Section 4a), enforcement actions taken and the reasons, and abuse reports and appeals concerning your account.
- Support communications: content of support tickets, emails, and chat messages you send us.
- Cookies and similar technologies: see our Cookie Policy.
2. How We Use Account Data
We use account data to: provide and operate the Service; authenticate and secure accounts; process payments and prevent fraud; detect, prevent, and respond to spam, phishing, malware, and other abuse, and enforce our Acceptable Use Policy (Section 4a); provide customer support; send service, security, and billing communications; monitor and improve the Service (including aggregated, de-identified analytics); comply with legal obligations (e.g., tax, accounting, know-your-customer checks); and, where you have opted in, send product updates and marketing communications.
3. Legal Bases (GDPR / UK GDPR)
Where GDPR or UK GDPR applies, we rely on:
- Contract (Art. 6(1)(b)) — to create and operate your account and provide the Service.
- Legitimate interests (Art. 6(1)(f)) — for fraud and abuse prevention (including scanning Messages and sending domains, risk scoring, and enforcement under the AUP, which protects recipients, other customers, and the reputation on which the Service depends), service security, product analytics, and direct marketing to existing customers about similar products (with an opt-out in every message).
- Consent (Art. 6(1)(a)) — for non-essential cookies and marketing emails to non-customers, revocable at any time.
- Legal obligation (Art. 6(1)(c)) — for tax, accounting, law-enforcement requests, and handling notices and statements of reasons under the EU Digital Services Act.
4. Sharing and Subprocessors
We do not sell your personal data. We share account data with:
- Service providers who process data on our behalf under contract (hosting, email delivery, payment processing, analytics, customer support tooling) — see our Subprocessors list, updated as providers change.
- Reputation and security lookup services (Spamhaus, SURBL, abuse.ch, and Google Web Risk if enabled) that receive only the domain names or URLs we check, as described in Section 4a. We list these services as subprocessors for transparency; whether each acts as our processor or as an independent recipient is to be confirmed with legal counsel.
- Professional advisors (lawyers, auditors, accountants) as needed.
- Successors in the event of a merger, acquisition, or asset sale, subject to equivalent privacy protections.
- Authorities, where required to comply with law, court order, or to protect the rights, property, or safety of Irisend, our users, or the public.
4a. Abuse Prevention and Content Scanning
To keep spammers and bots off the Service and to keep Irisend's sending reputation (and therefore every customer's deliverability) intact, we run automated checks before and while Messages are sent. This section explains them.
- What is checked. The sender and recipient domains, headers, the URLs and domains found in message bodies and tracked links, attachment types, file contents and hashes, similarity of a message to messages from other Teams, and, for sending domains, their registration data and blocklist status. We also measure bounce and complaint rates and sending volumes per Team and per domain.
- Who looks at the result. Checks are automatic. Our staff see the content of a Message only when it has been held or flagged, when someone has reported it, when you contact support about it, or when the law requires it (see Terms of Service, Section 3.4).
- Roles. The scanning of Messages that contain Customer Content is part of operating the Service for our Customer and is covered by the Data Processing Agreement. Decisions to restrict, suspend, or terminate an account under the AUP, and the records we keep about them, are made by us as a controller for the purposes described in Section 3.
- Third-party reputation lookups. To judge whether a link or a domain is dangerous, we send the domain name or URL (not the message text, not recipient addresses, and not your account details) to reputation services: The Spamhaus Project (Domain Block List) and SURBL (domain blocklists), abuse.ch (URLhaus, a database of malware URLs), and, if enabled, Google Web Risk (Google's database of unsafe web resources). We query public domain registries over RDAP to find out when a sending domain was registered. Where a service accepts a hostname or a URL without its query string, we send only that, because query strings can contain personal data. We list these services as subprocessors for transparency; whether each acts as our processor or as an independent recipient is to be confirmed with legal counsel. They are listed on our Subprocessors page, where changes are announced. We keep short-lived cached results to avoid repeating the same lookup.
- Automated decisions and human review. Our systems can automatically block a Message, hold it, limit what a Team can send, or pause sending. Terminating an account, and lifting a suspension, always involve a person. If an automated action affects you, you can ask for it to be reviewed by a person, say what you think went wrong, and contest it, using the appeal route in the AUP.
- Reports. If you send us an abuse report (by email or the report form), we process your name, email address, and what you tell us in order to assess the report, tell you what we decided (as the DSA requires), and, where necessary, pass it to the account holder or an authority. We remove your contact details when forwarding a notice to the account holder where the law allows.
- Retention. Scan results and verdict caches are short-lived. Risk flags, enforcement records, and the evidence behind them are kept while your account is active, and for accounts closed for abuse for as long as needed to prevent the same actor from returning, and no longer than [to be completed: ABUSE_RECORD_RETENTION].
5. International Data Transfers
Irisend is based in the Netherlands. Some of our subprocessors and reputation-lookup providers (e.g., AWS, Stripe, Google) process data outside the EEA/UK, including in the United States. Where we transfer personal data outside the EEA/UK, we rely on the European Commission's Standard Contractual Clauses (2021/914, as applicable modules), the UK International Data Transfer Addendum, and/or the recipient's certification under the EU-U.S. Data Privacy Framework (and UK extension), together with supplementary technical and organizational measures, as the applicable safeguard.
6. Data Retention
We retain account data for as long as your account is active and for a reasonable period afterward to comply with legal obligations (e.g., tax records, typically 7 years), resolve disputes, and enforce agreements. Server and access logs are generally retained for up to 12 months. You may request earlier deletion subject to Section 8.
7. Security
We apply technical and organizational measures described in our Security page, including encryption in transit, access controls, and monitoring. No system is 100% secure; we will notify affected individuals and authorities of a qualifying personal data breach as required by applicable law (e.g., within 72 hours of becoming aware, under GDPR Art. 33).
8. Your Rights
Depending on your location, you may have the right to: access the personal data we hold about you; correct inaccurate data; request deletion; restrict or object to processing; receive a portable copy of your data; and withdraw consent at any time (without affecting prior lawful processing).
- EEA/UK residents (GDPR/UK GDPR): exercise these rights via [email protected]. You also have the right to lodge a complaint with your local supervisory authority (in the Netherlands: the Autoriteit Persoonsgegevens).
- California residents (CCPA/CPRA): you have the right to know, delete, correct, and opt out of "sale" or "sharing" of personal information (we do not sell or share personal information for cross-context behavioral advertising) and the right to non-discrimination for exercising these rights. Submit requests via [email protected].
- Other jurisdictions: we will honor equivalent rights available under applicable local law (e.g., Canada's PIPEDA, Australia's Privacy Act, Brazil's LGPD (Lei Geral de Proteção de Dados, Law No. 13,709/2018)) on request.
We will respond to verified requests within the time required by applicable law (e.g., one month under GDPR, extendable by two months for complex requests; 45 days under CCPA).
9. Children
The Service is not directed to individuals under 16, and we do not knowingly collect personal data from children. If you believe a child has provided us personal data, contact [email protected] for deletion.
10. Marketing Emails From Us
If you subscribe to product updates or marketing from Irisend, every message includes a one-click unsubscribe link and, where applicable, RFC 8058 List-Unsubscribe / List-Unsubscribe-Post headers. You can also manage preferences from your account settings.
11. Waitlist
While Irisend is pre-launch, self-serve signup is gated behind a referral waitlist at /waitlist. If you join it, we collect: your email address; an optional answer to "what will you send"; attribution data (a referral code if you followed someone's invite link, UTM parameters, and the referring website's hostname); and consent evidence (the version of this policy you agreed to and when). Legal basis: consent (Art. 6(1)(a) GDPR) — you give it explicitly when you submit the form, with no pre-ticked boxes, and can withdraw it at any time via the link below. Purpose: operating a double-opt-in waitlist (confirming your email, showing your queue position and referral link, and inviting you to create an account when it's your turn), and measuring interest in the Service before general availability. Retention: an automated daily job deletes entries that were never confirmed 30 days after signup, entries that left the waitlist 30 days after leaving, and every other entry at the latest 12 months after you gave (or, by re-joining, renewed) your consent. Your rights: every waitlist email carries a link to a status page where you can view your position, leave the waitlist (no further emails; you drop out of the queue and can re-join any time), or permanently delete your entry and all associated referral data yourself, with no account or support request needed — the same rights described in Section 8 above, self-serve rather than by email request. Referral data about other people (e.g., that you referred them) is limited to a confirmed/unconfirmed count; we do not share one waitlist entry's email address with another.
12. Changes to This Policy
We will post updates here and, for material changes, notify you via email or in-dashboard notice at least 30 days before they take effect.
13. Contact
Data controller: Irisend, [to be completed: COMPANY_ADDRESS], [email protected].
If we appoint an EU representative under GDPR Art. 27 or a UK representative under UK GDPR Art. 27 (required if Irisend has no EU/UK establishment but targets EU/UK individuals), their contact details will be listed here: [to be completed: EU_REPRESENTATIVE_CONTACT].
This document is a draft template and does not constitute legal advice. See research/legal.md for review recommendations before publishing.