Draft — pending legal review. This document has not yet been reviewed by counsel and may change before Irisend is generally available.
Subprocessors
Effective date: 2026-11-10 Last updated: 2026-11-10
This page lists the subprocessors Irisend ("Irisend") engages to provide the Service, as required under Article 28(2)-(4) GDPR and our Data Processing Agreement. By using the Service, and subject to the DPA, Customer grants Irisend general written authorization to engage the subprocessors listed below.
Notice of Changes
We will give Customers at least 14 days' advance notice (via email to the account's billing/technical contact and/or a changelog entry at [to be completed: SUBPROCESSOR_UPDATES_URL]) before adding a new subprocessor or replacing an existing one, so Customer may object per the terms of the DPA. If Customer objects on reasonable data-protection grounds and the parties cannot resolve the objection, Customer's exclusive remedy is to terminate the affected part of the Service.
Change Log
| Date | Change |
|---|---|
| 2026-11-10 | Primary production hosting moved from OVH to Contabo GmbH. OVH remains listed for the status page and internal operations tooling (support-ticket handling), and also holds a backup archive (a database dump file, not a running database) of the production database taken when the old production stack was removed from OVH on 2026-11-10, retained temporarily as a migration safeguard and deleted once no longer needed. The API, the dashboard and the email-sending pipeline no longer run on OVH. |
Current Subprocessors
| Subprocessor | Purpose | Data processed | Location / region | Transfer mechanism |
|---|---|---|---|---|
| Amazon Web Services (AWS), Inc. — Amazon SES, and supporting AWS infrastructure (compute, storage, queues) | Email sending (transactional + marketing), receiving inbound email for domains where Customer enables receiving (SES receiving, with the raw inbound message stored in S3), infrastructure hosting for the API and worker services, S3 storage of raw DMARC aggregate reports for deliverability monitoring | Recipient and sender email addresses, outbound and inbound message content, headers and attachments, delivery/bounce/complaint events, DMARC authentication-report data (reporting mail servers' source IPs), account data | eu-west-1 (inbound mail is received in the sending region chosen for the domain) | AWS Data Processing Addendum incorporating EU SCCs; AWS EU-U.S. Data Privacy Framework certification where applicable — acceptance status on the production AWS account not yet confirmed, see open items |
| Contabo GmbH (Munich, Germany) | Primary production hosting: virtual private server running our self-hosted Coolify platform, with the API, worker, SMTP relay, PostgreSQL database, Redis, and the irisend.com website and dashboard | Account data, Customer Content in transit and at rest on the production server (including the production database), logs | [to be completed: CONTABO_DATACENTER_LOCATION] | EU-based provider; Contabo Data Processing Agreement (Art. 28 GDPR) — acceptance on the production Contabo account not yet confirmed, see open items |
| OVH SAS / OVHcloud | Status page (status.irisend.com), internal operations tooling (handling of customer support tickets via the internal agent platform used by our support team), and a backup archive (a database dump file, not a running database) of the production database taken at the migration to Contabo, retained temporarily and deleted once no longer needed. The live API, dashboard and email-sending pipeline do not run on OVH | Support ticket content you send us (name, email address, message), operational monitoring data, and the contents of the pre-migration production database archive (account data and Customer Content as they were at the time of the migration, until deleted). Test systems on OVH are intended to hold synthetic data only (to be confirmed by the Platform Engineer before publishing) | [to be completed: OVH_DATACENTER_LOCATION] (OVH EU data center) | EU-based processing; OVH Data Processing Agreement |
| Cloudflare, Inc. | DNS resolution, CDN/proxy, and DDoS/WAF protection for irisend.com and customer-facing endpoints (as our own infrastructure vendor) | IP addresses, DNS query metadata, limited request metadata | Global edge network (EU-based routing preferred where configured) | Cloudflare Data Processing Addendum incorporating EU SCCs; Cloudflare EU-U.S. DPF certification |
| Stripe, Inc. / Stripe Payments Europe, Ltd. | Billing, subscription management, usage-based metered billing, and tax calculation for paid plans | Billing contact details, payment metadata (Irisend does not store full card numbers), VAT/tax status used for reverse-charge determination | EU/US (Stripe infrastructure) | Stripe Data Processing Agreement incorporating EU SCCs; Stripe EU-U.S. DPF certification — acceptance status for the production Stripe account not yet confirmed, see open items |
| [to be completed: EMAIL_SUPPORT_TOOL] (e.g., a helpdesk/email tool for customer support) | Customer support ticketing and communication | Name, email address, support ticket content | [to be completed: SUPPORT_TOOL_REGION] | Vendor DPA incorporating EU SCCs where applicable |
| [to be completed: ANALYTICS_TOOL] (if used; e.g., product analytics for the dashboard) | Product usage analytics for the dashboard | Account/usage data, IP address (may be truncated/anonymized) | [to be completed: ANALYTICS_REGION] | Vendor DPA incorporating EU SCCs where applicable |
Rows marked with a placeholder vendor name apply only once that vendor is actually integrated; remove unused rows before publishing. Stripe billing (checkout, subscriptions, usage-based meter billing) is implemented in the codebase (apps/api/src/routes/stripe.ts, apps/worker/src/report-usage.ts) and is live whenever STRIPE_SECRET_KEY/STRIPE_WEBHOOK_SECRET are configured for an environment — it is no longer merely planned, but confirm those keys are actually set for production and that Stripe's DPA has been accepted for that account before relying on this row as accurate for live customers. Confirm the Contabo and OVH datacenter locations, that the Contabo and OVH data processing agreements are in place, and any additional vendors (error tracking, log aggregation, customer-support tooling, the AI model provider used by the internal support agents, and any off-site backup storage provider) before go-live and add them here — omitting an in-use subprocessor from this list is a DPA/GDPR compliance gap.
A note on Cloudflare's two roles. Cloudflare appears above as our subprocessor for the marketing site/dashboard/API. Separately, if Customer chooses to connect its own Cloudflare account via OAuth to let Irisend auto-configure DNS records for a sending domain (/domains/:id → "Connect Cloudflare"), Cloudflare is acting as Customer's own vendor under Customer's own Cloudflare account and contract — Irisend only holds a scoped, Customer-revocable OAuth token used strictly on Customer's instruction to read/write that domain's DNS records (see DPA §5.4), and this is not a sub-processor relationship under Art. 28(4) GDPR.
Security and Reputation Lookup Services
To stop phishing, malware, and spam before they are sent, Irisend checks domain names and URLs found in Messages, and the domains Customers use to send, against the services below. These services receive only a domain name or URL: never the message text, recipient addresses, or Customer account details. Where a service accepts a hostname or a URL without its query string, we send only that. 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. A lookup against a public blocklist or registry may not involve Customer personal data in practice. They are described in the Privacy Policy (Section 4a) and the Acceptable Use Policy.
| Service | Purpose | Data sent | Location / region | Status |
|---|---|---|---|---|
| The Spamhaus Project (Domain Block List) | Check whether a sending domain or a domain in a link is listed as spam- or phishing-related | Domain name (DNS query) | [to be completed: SPAMHAUS_LOCATION] | Terms/DPA position to be confirmed before go-live |
| SURBL | Same purpose, second blocklist | Domain name (DNS query) | [to be completed: SURBL_LOCATION] | Terms/DPA position to be confirmed before go-live |
| abuse.ch (URLhaus) | Check whether a link points to a URL known to distribute malware | URL or hostname | [to be completed: ABUSE_CH_LOCATION] | Terms/DPA position to be confirmed before go-live |
| Google Web Risk (Google Cloud), only if enabled | Check whether a link is on Google's list of unsafe web resources | URL (or hashed URL prefix, depending on the API mode in use) | Global (Google Cloud) | Google Cloud Data Processing Addendum incorporating EU SCCs; remove this row if Web Risk is not enabled in production |
| Domain registries (via the public RDAP service) | Look up when a sending domain was registered | Domain name | Global (public registry data) | Public registry lookup; no Customer account data sent |
Draft note: the reputation lookups are being built under IRI-275 and IRI-276. Do not publish this section before those features are live in production, and remove any row for a service that is not used. For each service, confirm the vendor's location and whether it will sign a DPA before it appears on the live list; the Notice of Changes above (14 days' notice) applies when a service is added after launch.
Infrastructure Subprocessors of Our Subprocessors
Our subprocessors may themselves rely on further subprocessors (e.g., AWS's own regional data-center entities, or Cloudflare's network partners). Their current subprocessor lists are published at:
- AWS: https://aws.amazon.com/compliance/sub-processors/
- Stripe: https://stripe.com/legal/service-provider-list (or current Stripe DPA subprocessor annex)
- Cloudflare: https://www.cloudflare.com/subprocessors/
Questions
This document is a draft template and does not constitute legal advice. See research/legal.md for review recommendations before publishing.