Skip to content
co:mail
How it works Features Use cases
Request access

Data Processing Agreement

Version 1 · Effective 18 November 2026

This agreement (“DPA”) sets out how we process personal data on behalf of business customers when they use comail, as Article 28 of the General Data Protection Regulation (“GDPR”) requires. It forms part of our Terms of Service.

Contents

  1. Scope and conclusion
  2. In short
  3. Definitions
  4. Roles and instructions
  5. Details of the processing
  6. Confidentiality
  7. Technical and organisational measures
  8. Sub-processors
  9. International transfers
  10. Assistance
  11. Personal data breaches
  12. Deletion at the end of the Service
  13. Information and audits
  14. Final provisions

1. Scope and conclusion

1.1 Parties. This DPA is between you, the business customer named on the Account, as controller, and Ninibe GmbH, Lübeck, Germany (“comail”, “we”, “us”), as processor. If you process the data on behalf of another controller, you are its processor and we are your Sub-processor (Section 4.7). Our registered address and commercial register details are in our Legal Notice.

1.2 When it applies. This DPA applies whenever you use the Service as a business customer (Section 1.4 of the Terms) and we process Customer Personal Data on your behalf. It does not apply to individuals who use comail for purely personal or household purposes, which the GDPR does not cover (Art. 2(2)(c) GDPR).

1.3 Conclusion. You conclude this DPA by accepting the Terms. No signature is needed: Art. 28(9) GDPR allows the contract to be in electronic form. If you need this DPA in another form for your records, write to privacy@comail.io.

1.4 What it does not cover. We process some personal data as an independent controller, not on your behalf: your Account data; the connection record of each Inbox (its address, Google account identifier and refresh token); billing data; the request data our hosting and network providers record; support tickets, feedback and support conversations; and our free-trial records (Sections 4.1, 4.2, 4.8, 4.9 and 4.10 of our Privacy Policy). Anything you or your Agents include in a support request or feedback is processed under our Privacy Policy, so include other people's personal data only where the request needs it. Paddle, our Merchant of Record, processes payment data as an independent controller. That processing is described in our Privacy Policy, not in this DPA.

2. In short

  • You are the controller; we are your processor. If you manage Inboxes for someone else, you are their processor and we are your Sub-processor. We process the personal data in your Inboxes and configuration only to provide the Service, on your instructions: these Terms, the Permissions you set, and the requests your Agents make within them.
  • We don't store your mail. Message content is fetched from Gmail for each Agent request, checked against that Agent's Permissions, passed to the Agent and not written to our database or logs. Neither our staff nor any LLM on our side can read it.
  • The Service runs in the EU. The application and its database are hosted by Google Cloud in Belgium, and Cloudflare protects the traffic to them. Our sub-processors are listed in Section 8; we email you 30 days before we change them, and you may object.
  • We tell you about breaches without undue delay and help you meet your own obligations, including towards the people in your mail.
  • When your Account ends, we delete Customer Personal Data on the schedule in our Privacy Policy. Your mail stays in your Gmail.

This summary is for convenience only and is not part of the agreement. The numbered sections below are the binding DPA.

3. Definitions

Capitalised terms defined in the Terms, such as “Account”, “Agent”, “Customer Data”, “Inbox”, “Mail Data”, “Permissions” and “Service”, have the same meaning here. “Controller”, “processor”, “personal data”, “processing”, “data subject”, “personal data breach” and “supervisory authority” have the meanings given in Art. 4 GDPR. In addition:

  • “Customer Personal Data” means personal data contained in Customer Data that we process on your behalf, including data we derive from it, such as Gmail identifiers and audit records.
  • “Sub-processor” means a processor we engage to carry out processing of Customer Personal Data.
  • “Data Protection Law” means the GDPR, the German Federal Data Protection Act (BDSG) and other data protection law of the EU or its Member States that applies to the processing.
  • “Standard Contractual Clauses” means the clauses adopted by Commission Implementing Decision (EU) 2021/914.

4. Roles and instructions

4.1 Your instructions. We process Customer Personal Data only on your documented instructions, including with regard to transfers to third countries. Your instructions are this DPA and the Terms, the Permissions, rules, labels and other settings you configure in the Service, and the requests your Agents make within those Permissions. Further instructions must be given in writing, including by email, and must be consistent with the Service as described in the Terms. If you give an instruction that goes beyond the Service, we may decline it.

4.2 Agents act on your instructions. Your Agents, and the companies that provide them, are chosen by you. They are not our Sub-processors. When we deliver Mail Data to an Agent, or carry out an action an Agent requests, we do so on your instructions.

4.3 Legal requirements. If EU or Member State law requires us to process Customer Personal Data other than on your instructions, we will tell you about that requirement before we process, unless the law prohibits it on important grounds of public interest.

4.4 Instructions that infringe the law. We will tell you without delay if, in our opinion, an instruction infringes Data Protection Law. We may suspend carrying out that instruction until you confirm or change it.

4.5 No use for our own purposes. We do not sell Customer Personal Data, use it for advertising, use it to develop, improve or train AI or machine-learning models, or otherwise process it for our own purposes. Data received from Google APIs is also subject to the Google API Services User Data Policy, including its Limited Use requirements. Aggregated statistics about use of the Service that identify no data subject (Section 11.4 of the Terms) are not Customer Personal Data.

4.6 Your responsibilities. You are responsible for the lawfulness of the processing you instruct: for having a legal basis to process the personal data in your Inboxes with comail and with your Agents, for informing data subjects where Data Protection Law requires it, and for the transfers that result from sending Mail Data to your Agents, under your agreements with their providers (Sections 5.1 and 6.1 of the Terms).

4.7 If you act as processor. If you use the Service to process personal data on behalf of another controller, for example as an agency or assistant managing Inboxes for their owners (Section 10 of the Terms), you are that controller's processor and we are your Sub-processor (Art. 28(4) GDPR). This DPA then applies with the following additions:

  • You confirm that the controller has authorised you to engage us and our Sub-processors (Section 8), and that your instructions, including the Permissions you set and the requests your Agents make, are consistent with the controller's instructions to you.
  • You remain our point of contact. We give our notices under this DPA, such as changes of Sub-processor (Section 8.3) and personal data breaches (Section 11), to you, and pass on data subject requests to you (Section 10.1). You pass them on to the controller as your agreement with it requires, and the controller's instructions, objections and audit requests (Section 13) reach us through you. Audits on the controller's behalf count towards the limit in Section 13.2.
  • Our obligations to you are those in this DPA. You are responsible for making sure that your agreement with the controller can be met with them; we are not bound by its terms.
  • If you have ceased to exist in law or become insolvent, the controller may exercise your rights under this DPA directly, in particular to have its data returned or deleted (Section 12).

5. Details of the processing

Subject matterProviding the Service: a permission layer between your Gmail and Google Workspace Inboxes and the AI agents you authorise.
DurationFor as long as you use the Service, and afterwards until the data is deleted under Section 12.
Nature of the processingRetrieving messages, threads, drafts, attachments, labels and settings from Gmail when an Agent requests them; checking them against that Agent's Permissions and transmitting only what is allowed to the Agent; creating drafts, sending messages, applying labels, archiving, marking as spam, moving to trash and unsubscribing from mailing lists where the Permissions allow; applying your rules and labels to incoming mail; creating and deleting the Gmail filters that add an Agent's labels, for an admin agent you allow to; storing your configuration, identifiers, short-lived records of changes and sends, review notes and audit records; and the logging needed to secure and troubleshoot the Service. Message content is processed in memory for the duration of a request and is not stored.
PurposeProviding, securing and supporting the Service under the Terms.
Types of personal dataNames, email addresses and other content and metadata of messages, threads, drafts and attachments (in memory only); Gmail message, thread, draft and label identifiers; email addresses and domains in rules, allow-lists and block-lists; notes left in draft reviews; audit records, which contain identifiers and the outcome of each change; and log entries with shortened identifiers and hashed email addresses.
Special categories of dataNot intended. Your Inboxes may contain data of any kind, including special categories under Art. 9 GDPR; any such data is protected by the measures in Section 7, in particular the fact that message content is never stored. Whether you may use the Service for such data is your decision (Section 5.4 of the Terms).
Data subjectsThe people whose mail is in your Inboxes, including senders, recipients and people named in messages; your employees and other users whose Inboxes you connect; and people whose addresses appear in your configuration.

6. Confidentiality

6.1 Personnel. We ensure that everyone we authorise to process Customer Personal Data has committed to confidentiality or is under an appropriate statutory obligation of confidentiality, and processes it only on your instructions.

6.2 No human access to mail. Our staff do not read Mail Data, unless you give us explicit consent for specific messages (for example, to resolve a support request), it is necessary for security purposes such as investigating abuse, or it is necessary to comply with applicable law. Our support and operator tools do not display message content, cannot decrypt mailbox tokens, and are not connected to any LLM.

7. Technical and organisational measures

We implement the following measures under Art. 32 GDPR, appropriate to the risk of the processing. We may change them as technology and threats develop, provided the overall level of protection does not decrease.

7.1 Data minimisation and pseudonymisation

  • Message content, including attachments and draft previews, is never written to our database, logs or audit records.
  • We store Gmail identifiers rather than content, and keep change and send records for 24 hours to 30 days and links between drafts and threads for 90 days.
  • Application logs never contain an email address or a full Gmail identifier in the clear: addresses are logged as a one-way hash, identifiers are shortened.

7.2 Encryption

  • All connections are encrypted in transit with TLS, including the Service's own outgoing email, which requires TLS and a verified certificate. Stored data is encrypted at rest.
  • Gmail refresh tokens are encrypted with a Google Cloud KMS key held in a hardware security module. The key material never leaves the HSM, the key is rotated every quarter, each ciphertext is bound to its database record, only the services that need the tokens may use the key, and every decryption is checked against access policies and recorded in an audit log.
  • Notes left in draft reviews are encrypted with a key specific to your Account.
  • Passwords are stored only as salted hashes, and session tokens and Agent credentials only as hashes.

7.3 Access control for Agents

  • Every Agent request is checked against that Agent's Permissions. Reads are limited in the query sent to Gmail and checked again on Gmail's response; anything outside the Permissions is dropped. A check that cannot be completed refuses the request.
  • An Agent can never widen its own access: it cannot apply the labels that grant it access, and it cannot choose its scope. Content outside its Permissions is reported as not found.
  • Sending, label changes, organising mail and reading attachments are separate grants that you control per Agent. Sending is off unless you turn it on.
  • Agents sign in with OAuth and PKCE, or with tokens you can revoke at any time.

7.4 Access control for people

  • Sign-in is protected by rate limits and lockout after repeated failures. Changing the email address, password or Google sign-in, or deleting the Account, requires confirming the password or Google sign-in within the previous ten minutes.
  • Admin access, which lets an admin agent change your setup, is off by default and turned on only by you, for a limited time or until you turn it off. Every admin call is recorded before it runs.
  • Our operator tools are not publicly reachable, do not show message content and cannot change your Permissions. The only changes operators can make are to adjust an Account's or Inbox's limits, to switch on the recording described in Section 7.5, and to ask for an Agent's mail to be checked against your rules again, which can apply or remove that Agent's labels as your rules say. Each such change is logged.
  • Each part of the Service runs under its own service identity with only the permissions it needs. Credentials are held in Google Secret Manager. The database accepts connections only through Google's IAM-authorised connector.
  • Customer data is separated by Account: each request from you or your Agents can reach only your own Account's data.

7.5 Logging and input control

  • Setup changes made in the Service or by an admin agent are recorded with what changed, on which Inbox, when and with what outcome. You can see these records in the Service.
  • Application logs record Agent operations with the Agent, Inbox, tool and outcome, using shortened identifiers and hashed addresses, never content.
  • Audit records and logs are deleted after 30 days.
  • To troubleshoot an Account, operators can turn on recording of selected Agent operations, for 7 days at a time and as metadata only.

7.6 Availability and resilience

  • The Service runs on Google Cloud (Cloud Run and Cloud SQL) in the EU, in data centres whose physical security Google provides and has certified, including under ISO/IEC 27001 and SOC 2.
  • The production database has automated backups and point-in-time recovery, and is protected against accidental deletion. Backups are overwritten within 30 days.
  • Traffic to the Service passes through Cloudflare, which filters attacks, including denial-of-service attacks, before they reach it.
  • Infrastructure is defined as code and deployed through an automated pipeline. Failed background jobs raise alerts.

7.7 Organisational measures

  • Every change to the Service is reviewed against a written list of security rules, and the rules that limit what Agents can see are covered by automated tests.
  • Retention periods in the Service are enforced automatically. Disconnecting an Inbox or deleting the Account revokes our access with Google.
  • We keep a record of the processing we carry out on behalf of customers (Art. 30(2) GDPR) and a procedure for handling personal data breaches.
  • We bind Sub-processors to data protection obligations under Section 8.

8. Sub-processors

8.1 Authorisation. You give us general authorisation to engage Sub-processors. We currently use the following:

Sub-processorProcessingLocation
Google Cloud EMEA Limited (Ireland)Application hosting, database, encryption key management, logging and monitoringEU (Belgium); some operational data, such as logs, may be processed in other regions
Cloudflare, Inc. (USA)Delivering traffic to and from the Service and protecting it against attacks (content delivery network and web application firewall). Traffic is decrypted in Cloudflare's network to be filtered; Cloudflare does not store message content.Global network; requests are generally handled in the data centre nearest the user

Google, as the provider of your Inboxes, processes your mail under your own agreement with Google and is not our Sub-processor (Section 7.4 of the Privacy Policy). Nor are the providers of your Agents (Section 4.2). The other providers in Section 7.1 of the Privacy Policy, such as our email providers, process only data we hold as controller (Section 1.4).

8.2 Obligations. We engage each Sub-processor under a written contract that imposes data protection obligations at least as protective as those in this DPA, in particular sufficient guarantees for appropriate technical and organisational measures. We remain fully liable to you for our Sub-processors' performance of those obligations.

8.3 Changes. We will inform you of any intended addition or replacement of a Sub-processor at least 30 days before it takes effect, by email to the address on your Account, and update the list on this page. If we must replace a Sub-processor urgently, for example because it stops providing its service or for security reasons, we will inform you as soon as we can, and the 30 days run from then.

8.4 Objections. You may object to a change within 30 days of its announcement, on reasonable grounds relating to data protection, by writing to privacy@comail.io. We will work with you in good faith to address the objection. If we cannot, you may terminate the affected subscriptions with effect from the change, and we will refund any prepaid fees for the period after termination.

9. International transfers

We host the Service and its database in the EU. Traffic to and from the Service passes through Cloudflare's global network, so it may be processed in transit outside the European Economic Area. We transfer Customer Personal Data to a country outside the European Economic Area only in accordance with Chapter V GDPR: where the European Commission has decided that the country ensures an adequate level of protection, including under the EU–U.S. Data Privacy Framework for certified recipients, or under the Standard Contractual Clauses we have agreed with the recipient. You can request a copy of the relevant safeguards from privacy@comail.io. Transfers to your Agents and their providers are made on your instructions (Section 4.6).

10. Assistance

10.1 Data subject requests. Taking into account the nature of the processing, we help you respond to requests from data subjects exercising their rights under Chapter III GDPR. You can carry out most requests yourself in the Service, for example by changing or deleting rules and recipient lists, disconnecting an Inbox or deleting the Account. If we receive a request about Customer Personal Data directly, we will pass it on to you without undue delay, where we can identify you, and will not respond to it ourselves except to refer the data subject to you, unless you instruct us to.

10.2 Your other obligations. Taking into account the nature of the processing and the information available to us, we help you meet your obligations under Articles 32 to 36 GDPR, including data protection impact assessments and prior consultation with a supervisory authority, in particular by providing the information in this DPA and answering reasonable requests for further information.

10.3 Authorities. If a supervisory authority or another authority contacts us about Customer Personal Data, we will tell you without undue delay, unless the law prohibits it.

11. Personal data breaches

We will notify you of a personal data breach affecting Customer Personal Data without undue delay after becoming aware of it, and where feasible within 48 hours, by email to the address on your Account. As far as the information is available to us, the notification will describe the nature of the breach, including the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address the breach and mitigate its effects; and a contact point for further information. Where we cannot provide all the information at once, we will provide it in phases without undue further delay. We will take reasonable steps to contain and investigate the breach, and support you in notifying the supervisory authority and data subjects where Articles 33 and 34 GDPR require it. Notifying you is not an acknowledgement of fault or liability.

12. Deletion at the end of the Service

12.1 Return or deletion. At your choice, we return or delete Customer Personal Data when the Service ends. Your mail is not stored by us, so it stays in your Inboxes; what we can return is your configuration. You can see it in the Service, and if you want a copy, ask us at privacy@comail.io before your Account ends.

12.2 Deletion. When your Account ends, whether you delete it or we delete it under the Terms, we delete Customer Personal Data as described in the Privacy Policy: immediately in our database, with backups overwritten within 30 days and log entries deleted after 30 days. We also revoke our access to your Inboxes with Google.

12.3 Legal requirements. We keep Customer Personal Data beyond these periods only where EU or Member State law requires us to, and then only for as long as it requires and protected under this DPA.

13. Information and audits

13.1 Information. We make available to you the information necessary to demonstrate compliance with Art. 28 GDPR, in particular this DPA, our answers to reasonable security questionnaires, and, where available, our Sub-processors' certifications and audit reports.

13.2 Audits. Where that information is not sufficient, you, or an independent auditor you mandate who is not our competitor and is bound by confidentiality, may audit our compliance with this DPA, including by inspection. Unless a personal data breach or a supervisory authority requires otherwise, audits take place no more than once in any twelve months, with at least 30 days' written notice, during normal business hours, without disproportionate disruption to our operations, and without access to other customers' data. Each party bears its own costs of an audit. Audits by a supervisory authority are not limited by this section.

14. Final provisions

14.1 Term. This DPA applies for as long as we process Customer Personal Data on your behalf. Obligations that by their nature continue after that, including Sections 6, 12 and 13, survive.

14.2 Precedence. If this DPA conflicts with the Terms, this DPA prevails on matters of data protection. Where we have agreed the Standard Contractual Clauses with you, they prevail over this DPA.

14.3 Liability. Each party's liability under this DPA is subject to Section 16 of the Terms. This does not limit either party's liability to data subjects under Art. 82 GDPR, or the powers of supervisory authorities.

14.4 Changes. We may update this DPA as described in Section 21 of the Terms, for example to reflect changes to Data Protection Law, to decisions or guidance of supervisory authorities, or to the Service. Changes that do not reduce the protection this DPA gives Customer Personal Data take effect when we publish them on this page. Changes to the list of Sub-processors follow Section 8. Earlier versions are available on request.

14.5 Law and courts. This DPA is governed by the same law, and subject to the same courts, as the Terms (Section 23).

14.6 Severability. If any provision of this DPA is invalid, the rest remains in effect, and the provisions of Data Protection Law apply in place of the invalid one.

14.7 Contact. Questions about this DPA, instructions and objections go to privacy@comail.io.

co:mail

Made in the EU

llms.txt · terms · privacy · refunds · legal notice · © 2026 Ninibe GmbH