Data processing agreement

Last updated 26 October 2026

This agreement is between you, the customer of the hosted MailRules cloud service ("you"), and Tilak Kumar G, a sole proprietor trading as TurtleByte, Bengaluru, Karnataka, India ("we", "us"). It covers the personal data we process on your behalf to provide the cloud service. For that data you are the controller and we are your processor, under Article 28 of the EU General Data Protection Regulation (GDPR) and of the UK GDPR. It forms part of our terms of service and applies automatically to every cloud account, with nothing to sign. If you need a countersigned copy, email [email protected].

It does not cover self-hosted MailRules, which runs on your server and sends us nothing.

1. Definitions and order of precedence

Words such as "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings the GDPR gives them. "Customer personal data" means the personal data described in section 3. If this agreement and the terms of service disagree about customer personal data, this agreement wins. If the Standard Contractual Clauses in section 12 apply and disagree with either, the Clauses win.

2. Subject matter, duration, nature and purpose

3. Personal data and data subjects

Data subjects: you and the people who use your MailRules account, and the senders and recipients of email in the mailboxes you connect.

Categories of personal data:

Special categories: MailRules does not ask for them, but an email can contain any kind of personal data its sender chose to include. We process it only as this agreement describes.

Not covered: billing data (payment details, invoices and tax records). Paddle.com, our reseller and Merchant of Record, collects and processes it as a controller in its own right, and we handle our own billing records as a controller, as our privacy policy describes.

4. Your instructions

We process customer personal data only on your documented instructions, including for transfers outside the EU and UK, unless the law requires otherwise; in that case we tell you first, unless the law prevents it. Your instructions are this agreement, the terms of service, and the rules, mailboxes, settings and integrations you set up in MailRules. If we believe an instruction breaks the GDPR or other data protection law, we tell you.

You are responsible for having a lawful basis for the processing, and you confirm you have the right to grant access to every mailbox you connect.

5. Confidentiality

Everyone we authorise to process customer personal data is bound by confidentiality. No person at MailRules reads your email, unless you ask us in writing to look at a specific email, it is needed to investigate a security problem or abuse, or the law requires it. If the law requires us to disclose customer personal data, we tell you unless we are legally prevented from doing so.

6. Security

We protect customer personal data with these measures:

7. Sub-processors

You give us general authorisation to use sub-processors. We impose on each one, by contract, data protection obligations that give at least the protection this agreement requires, and we remain responsible to you for their work. Our email, analytics and monitoring run on servers we operate ourselves. The current sub-processors are:

Sub-processorPurposeData
Hetzner Online GmbH (Finland, EU)Servers we manage ourselves for the app, database, email, analytics and monitoringAll cloud data, encrypted
Cloudflare (Clef, Workers AI)Deciding which rule fits an email. Cloudflare does not keep or train on the inputsHeaders, excerpt, rule text
Anthropic (Claude Haiku)Emails the first model is unsure about, writing rules, Suggest from my mail, and draft replies (Pro). API inputs are deleted within 30 daysHeaders, excerpt, rule text; for a draft reply, also the thread's previous message when the rule allows it
Google Cloud (Key Management Service)Protecting the keys that encrypt your dataEncrypted keys only, no email or account data
WorkOSSign-up, sign-in and password resetName, email address and sign-in details

None of these AI providers trains models on your data. If you enter your own model key, or connect Slack or a webhook, MailRules sends data to that provider or destination on your instruction, under your own agreement with it; it is not our sub-processor. Paddle.com is not a sub-processor either: as Merchant of Record it processes billing data as a controller in its own right (section 3).

Changes: we tell you by email at least 30 days before adding or replacing a sub-processor, and update this list. You may object on reasonable data protection grounds by email within that notice period. If we cannot resolve your objection, you may close your account before the change takes effect and get a pro-rated refund of any amount you prepaid.

8. Helping you meet your obligations

Taking into account the nature of the processing, we help you:

This help is free, except that we may charge reasonable costs for an assessment or consultation that needs more than the documents we already publish.

9. Personal data breaches

If we become aware of a personal data breach affecting customer personal data, we notify you without undue delay and within 48 hours of becoming aware of it, at the email address on your account. We tell you, as far as we know it then and as soon as we learn more: what happened, the categories and approximate number of data subjects and records concerned, the likely consequences, and what we have done or propose to do. We take reasonable steps to contain the breach and limit its effects, and we help you notify the supervisory authority and data subjects where you must.

10. Deletion and return

On request, we confirm the deletion in writing by email, free of charge.

11. Information and audits

We make available to you the information you need to show that we meet our obligations under Article 28, and we allow for and contribute to audits, including inspections, by you or an auditor you appoint. You first send us your questions in writing, and we answer within 30 days. If the answers are not enough, you may audit at most once in any 12 months, unless a personal data breach or a supervisory authority requires another. An audit needs 30 days' notice, takes place during business hours, is at your cost, and is carried out by an auditor bound by confidentiality.

12. International transfers

Our servers are in Finland, in the European Union. TurtleByte is based in India, and the AI model providers may process data in other countries, including the United States. Where customer personal data leaves the EU or UK to a country without an adequacy decision:

We use the same kind of safeguards with our sub-processors where required.

13. Liability

Each party's liability under this agreement is subject to the limits in section 10 of the terms of service: our total liability is capped at the amount you paid us in the 12 months before the claim. Nothing in this agreement limits liability that cannot be limited by law, or a data subject's rights under the Standard Contractual Clauses.

14. Term and governing law

This agreement lasts as long as we process customer personal data for you. It is governed by the law and courts set out in section 12 of the terms of service, except where the Standard Contractual Clauses require otherwise. We may change it as section 13 of the terms describes, with at least 14 days' notice by email for a material change.

15. Contact

TurtleByte (proprietor: Tilak Kumar G), Bengaluru, Karnataka, India.
Data protection and this agreement: [email protected]
Everything else: [email protected]