Data Processing Agreement

How Solidini processes personal data in your Receiver.email inboxes on your behalf, as required by Article 28 of the GDPR.

Last updated: 20 November 2026

1. Parties and scope

This Data Processing Agreement ("DPA") is between the customer that accepted the Terms of Service ("Customer") and Solidini, a sole proprietorship (eenmanszaak) under Dutch law, registered with the Dutch Chamber of Commerce (KvK) under number 97133981, at Vestingsmuur 10, 3991 RX Houten, the Netherlands ("Solidini"). It is part of the Terms and applies automatically, without a signature. If you need a signed copy, email [email protected].

This DPA covers personal data in Customer Data (as defined in the Terms) that Solidini processes on Customer's behalf ("Customer Personal Data"), mainly the email received at Customer's addresses. Customer is the controller, or a processor acting for its own customers; Solidini is the processor, or sub-processor. Personal data that Solidini processes for its own purposes, such as account details, is covered by the Privacy Policy.

If Customer is an individual using the Service only for personal or household purposes, the GDPR may not apply to Customer's own use. Solidini then still processes Customer Data only as this DPA describes.

Terms such as "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meaning given in the GDPR (Regulation (EU) 2016/679). "Data Protection Law" means the GDPR, the Dutch GDPR Implementation Act (UAVG) and other data protection law that applies to the processing.

2. Instructions

  1. Solidini processes Customer Personal Data only on Customer's documented instructions, including with regard to transfers to third countries, unless EU or member state law requires otherwise; in that case Solidini tells Customer before processing, unless that law forbids it.
  2. Customer's instructions are this DPA, the Terms, and the way Customer configures and uses the Service, such as creating projects, choosing a plan and its retention period, calling the API, connecting webhooks and agents, and deleting emails or projects. Further instructions must be in writing and consistent with the Service.
  3. Solidini tells Customer without delay if, in its opinion, an instruction infringes Data Protection Law.
  4. Customer is responsible for the lawfulness of the processing: for having a legal basis, for informing data subjects where needed, and for not sending data to the Service that the Acceptable Use Policy excludes, such as special categories of personal data.

3. Confidentiality

Solidini ensures that everyone authorised to process Customer Personal Data has committed to confidentiality or is under a statutory obligation of confidentiality, and has access only as far as needed for their tasks.

4. Security

Solidini implements the technical and organizational measures in Annex 2 to ensure a level of security appropriate to the risk, as required by Article 32 GDPR. Solidini may change these measures as technology develops, but will not lower the overall level of security.

5. Sub-processors

  1. Customer gives general authorisation for Solidini to engage sub-processors. The current sub-processors are listed in Annex 3 and on the Sub-processors page.
  2. Solidini informs Customer by email to its organization admins at least 30 days before adding or replacing a sub-processor. Customer may object within that period on reasonable grounds relating to data protection. The parties will then discuss a solution in good faith; if there is none, Customer may end the affected Service before the change takes effect and receive a refund of prepaid fees for the period after that.
  3. Solidini imposes on each sub-processor, by contract, data protection obligations that offer at least the same protection as this DPA, and remains liable to Customer for the performance of the sub-processor's obligations.

6. Transfers outside the EEA

  1. Customer Personal Data is stored in the United States (Google Cloud, region us-central1) and passes through Cloudflare's global network on its way to the Service. Customer authorises these transfers.
  2. Solidini ensures that every transfer of Customer Personal Data outside the European Economic Area complies with Chapter V GDPR: the recipient is certified under the EU-US Data Privacy Framework, or Solidini has agreed with it the Standard Contractual Clauses adopted by the European Commission (Decision (EU) 2021/914), or another valid transfer mechanism applies.
  3. Where Customer is located outside the EEA and returning Customer Personal Data to it is a transfer, Module 4 (processor to controller) of those Standard Contractual Clauses applies and is incorporated by reference, with Dutch law and the courts of the Netherlands chosen under its Clauses 17 and 18, section 1 of this DPA serving as its Annex I.A and Annex 1 as its Annex I.B. Where UK or Swiss data protection law applies, the UK International Data Transfer Addendum or the Swiss adjustments to those clauses apply accordingly.

7. Assistance

  1. Data subject requests: Customer can find, retrieve (including the raw message) and delete emails itself through the dashboard and API. If Solidini receives a request from a data subject about Customer Personal Data, it forwards it to Customer without undue delay and does not answer it itself, unless Customer asks it to. Solidini assists Customer with appropriate technical and organizational measures to answer such requests.
  2. Other obligations: taking into account the nature of the processing and the information available to it, Solidini assists Customer with its obligations under Articles 32 to 36 GDPR: security, breach notifications, data protection impact assessments and prior consultation of supervisory authorities. Solidini may charge reasonable costs for assistance that goes beyond what the Service offers, unless the need for it is caused by a breach of this DPA by Solidini.

8. Personal data breaches

Solidini notifies Customer without undue delay, and where possible within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notification describes, as far as known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Solidini provides further information as it becomes available, takes reasonable steps to contain the breach and limit its consequences, and does not notify authorities or data subjects on Customer's behalf unless Customer asks it to or the law requires it.

9. Deletion and return

  1. During the agreement, emails and their attachments are deleted automatically at the end of the retention period of Customer's plan, and Customer can delete emails and projects at any time.
  2. Before the agreement ends, Customer can retrieve Customer Personal Data through the API. Within 30 days after it ends, Solidini deletes all remaining Customer Personal Data, unless EU or member state law requires it to be kept. Copies in logs, in our storage provider's recovery period for deleted files, and in backups if any exist, are erased when those expire, at the latest 44 days after the agreement ends.
  3. On request, Solidini confirms the deletion in writing.

10. Information and audits

  1. Solidini makes available to Customer all information necessary to demonstrate compliance with Article 28 GDPR and this DPA, including by answering a reasonable security questionnaire once a year.
  2. If that information is not sufficient, or a supervisory authority requires it, Customer may audit Solidini's compliance, itself or through an independent auditor bound by confidentiality, at most once every 12 months (more often after a personal data breach), with at least 30 days' written notice, during business hours, and without access to data of other customers. Customer bears the costs of the audit.
  3. For the infrastructure of sub-processors, Solidini may meet audit requests by providing their independent certifications and audit reports (such as ISO 27001 or SOC 2).

11. Liability, duration and precedence

Solidini's liability under this DPA is subject to the limitation of liability in section 13 of the Terms, as far as Data Protection Law allows; this does not limit liability towards data subjects under Article 82 GDPR. This DPA applies for as long as Solidini processes Customer Personal Data. If this DPA and the Terms conflict, this DPA prevails for the processing of personal data. This DPA is governed by the same law and courts as the Terms.

Annex 1: Description of the processing

  • Subject matter and purpose: receiving email at Customer's receiver.email addresses, storing and parsing it, and making it available to Customer through the dashboard, API, SDKs, MCP server (run by Customer, or hosted by Solidini at mcp.receiver.email), CLI, event stream and webhooks, so that Customer can test and automate email flows.
  • Nature of the processing: receipt, storage, parsing, extraction of links and one-time codes, retrieval, transmission to destinations Customer configures, and deletion.
  • Categories of data subjects: senders of email to Customer's addresses; recipients and other people named in those emails; people whose data appears in email content or attachments, such as Customer's test users or end users.
  • Categories of personal data: email addresses and display names; message headers, including IP addresses and host names of sending servers; subject, body and attachments; links, including tokens in them; one-time codes; and any other personal data Customer causes to be sent to its addresses.
  • Special categories: none intended. Customer must not send them (see the Acceptable Use Policy).
  • Frequency: continuous, for every email received at Customer's addresses.
  • Retention: per plan, from receipt: 7 days (Free), 30 days (Starter), 90 days (Pro), as agreed in writing (Enterprise), or until Customer deletes the email or the project. The raw copy of a message that could not be processed is deleted within 90 days. Messages waiting in the dead-letter queue (which carry the recipient address, not the content): 7 days. Webhook delivery logs: 30 days. Copies in database backups: at most 14 days. Our storage provider can recover deleted files for up to 7 days before they are erased.
  • Location: United States (Google Cloud us-central1); in transit through Cloudflare's global network. Technical logs may be stored in other regions of these providers.

Annex 2: Technical and organizational measures

Access control

  • Every request is checked against the caller: API keys reach only their own project, users only the organizations they belong to, with admin, member and viewer roles. Role changes and removals take effect immediately. Isolation between customers is covered by automated tests.
  • Sign-in by one-time email codes, stored only as a keyed hash, valid for 10 minutes and limited to 3 attempts, with rate limits per email address and IP address.
  • Short-lived access tokens (15 minutes); refresh tokens stored hashed, rotated on every use, and revoked when reuse is detected. Users can see their sessions, sign out, and sign out all other sessions; an access token already issued stays valid for at most 15 minutes.
  • API keys are stored only as hashes and shown once, when created; they can be given an expiry date and revoked at any time.
  • The hosted MCP server keeps no API keys or email content between requests: each request brings its own key, and the server remembers only a hash of the key and its project, in memory, for a short time.
  • Access to production systems is limited to Solidini and the automation it controls, through its own accounts at the infrastructure providers.

Encryption and transmission

  • The dashboard and API are served over HTTPS only.
  • Mail is accepted over TLS when the sending server supports it. Between our mail edge and our pipeline, mail travels over HTTPS and is authenticated with a shared secret.
  • All stored data is encrypted at rest by the infrastructure provider.
  • Webhook deliveries are signed, so receivers can verify they came from us.

Separation and minimisation

  • Staging and production run in separate cloud projects with separate data.
  • One-time codes are extracted when an email is read and are not stored separately. Attachments over the plan's size limit are not stored as separate files; they remain in the raw message until it is deleted.
  • An hourly job deletes emails and their files when their retention period ends. Deleting a project deletes its emails, files, API keys and webhooks.

Integrity, availability and accountability

  • Service credentials (token signing key, the secret between mail edge and pipeline, and provider API keys) are kept in Google Secret Manager, not in source code. The secret between mail edge and pipeline is also stored as an encrypted secret in Cloudflare.
  • Raw email is stored before it is processed. Processing is attempted up to 5 times, after which the message is kept in a dead-letter queue for investigation.
  • Changes to organizations, projects, API keys, webhooks and members are recorded in an activity log visible to admins.
  • Rate limits on the API and sign-in protect against abuse and overload.
  • Code changes are type-checked, linted and tested with the automated test suite; staging deploys from CI run only after the tests pass.

Incidents

  • Security reports can be sent to [email protected]. Incidents are assessed, contained and, where they affect Customer Personal Data, notified as described in section 8.

Annex 3: Sub-processors

Authorised sub-processors of Customer Personal Data, also listed on the Sub-processors page:

ProviderPurposeDataLocationTransfer safeguard

Google Cloud

Google Cloud EMEA Limited (Ireland), with infrastructure operated by Google LLC (USA)

Hosting of the API, the remote MCP server (mcp.receiver.email) and the email processing pipeline: database (Firestore), file storage (Cloud Storage), queues (Pub/Sub), scheduled jobs and logsAll Customer Data: received emails, attachments, extracted links, and project and account data; technical logsUnited States (us-central1, Iowa); logs may be stored in other Google regionsEU-US Data Privacy Framework certification and Standard Contractual Clauses

Cloudflare

Cloudflare, Inc. (USA)

Receives mail for receiver.email (Email Routing), checks the address and passes it to our pipeline (Workers); DNSReceived emails while in transit, recipient and sender addresses in logsGlobal network; company in the United StatesEU-US Data Privacy Framework certification and Standard Contractual Clauses