GDPR and DORA for Client Emails in 2026: A Practical Guide

GDPR and DORA for Client Emails in 2026: A Practical Guide

Client emails are personal data processing too

Every payment reminder you send contains personal data: a name, an email address, an amount owed, sometimes a tax figure, a child's name or a flat number. Data protection isn't only about advertising. GDPR applies to every statement, fee notice and account email, even if you never send a single offer.

The good news: for emails that are part of an existing client relationship, the rules are clearer and more practical than most people expect. This guide covers what GDPR means for client emails in 2026, where the line between service emails and advertising runs, and whether the EU's Digital Operational Resilience Act (DORA) is something you need to worry about. It's practical guidance, not legal advice; for your specific situation, talk to your data protection adviser.

Service emails and advertising have different legal bases

Under GDPR you need a legal basis for every processing activity (Article 6). For the emails you send to clients as part of the service, such as invoices, payment reminders, monthly statements, schedule changes or account notices, the basis is usually performance of a contract (Article 6(1)(b)). Sometimes it is a legal obligation (Article 6(1)(c)), for example when you must inform clients about something, or legitimate interests (Article 6(1)(f)). You don't need a separate opt-in to send a client their own invoice.

Advertising is a different matter. Sending unsolicited commercial messages by email is regulated by the EU ePrivacy rules and national laws implementing them, which generally require the recipient's prior consent, with a narrow exception for offering similar products to existing customers who can easily opt out. If you only send service emails, that consent question doesn't arise. It arises the moment a service email starts to sell.

Keep service emails service-only

  • The subject and the main content describe the service matter: the invoice, the due date, the change of office hours.
  • Don't attach a sales offer to a payment reminder. Once a message advertises, it may be treated as a commercial communication and need consent. It also undermines the reminder itself.
Quick test: strip the email down to the information the client needs about their own account or service. If what's left is the reason you're sending it, it's a service email. If what's left is a sales pitch, it isn't.

Data minimisation: an email is not a filing cabinet

GDPR's minimisation principle (Article 5(1)(c)) means you only process the data you need. For client emails that translates into simple habits:

  • Put in the body only what the client needs to act: the amount, the due date, the invoice number, the account for the transfer. Not full national ID numbers, not complete tax returns.
  • Treat attachments as the riskiest part. A PDF statement often holds far more data than the email itself. Make sure each client receives only their own file.
  • Keep addresses up to date. A financial statement sent to an old address someone else now uses is a data breach, not a delivery problem.

If personal data does go to the wrong person, assess it quickly. Under Article 33 a personal data breach must be reported to the supervisory authority within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to the people concerned. Most wrong-recipient emails in small offices come from manual copy-paste.

Data subject rights in everyday practice

  • Access (Article 15): a client can ask what data you hold and what you've sent them. Being able to look up each contact's email history makes this a five-minute task.
  • Rectification (Article 16): wrong address, wrong name, wrong amount. Correct it at the source so the next run doesn't repeat it.
  • Erasure (Article 17): remove former clients from your contact lists when you no longer need them. Erasure doesn't override legal retention duties, so invoices you must keep under tax or accounting law stay in your accounting system.
  • Objection and unsubscribing: respect it promptly. If a client unsubscribes from your emails but you're contractually or legally obliged to send them a notice, use another channel, such as a letter, your client portal or a phone call.

You have one month to respond to these requests (Article 12(3)), extendable by two further months for complex cases.

Retention: delete what you no longer need

The storage limitation principle (Article 5(1)(e)) applies to contact lists too. A list of current clients for reminders and statements is justified; a list that still holds people who left three years ago isn't. Once a client has received their final statement and settled up, remove them from your client email lists, and review the lists at least once a quarter.

Your email provider is a processor

Any service that sends emails to your clients on your behalf processes their personal data for you. Under Article 28 you need a data processing agreement with that provider, and the processing should appear in your records of processing activities (Article 30). Ask every provider for this agreement and its list of subprocessors.

Security belongs here too. Clients are targeted by fake invoices and fake “change of bank account” emails. Sending from your own authenticated domain, signed with DKIM and protected by a DMARC policy, makes it much harder for someone to impersonate you. Check your current setup with the free DMARC checker and read how to move DMARC from none to reject.

DORA: does it apply to you?

The Digital Operational Resilience Act (Regulation (EU) 2022/2554) has applied since 17 January 2025. It covers financial entities, such as banks, payment and e-money institutions, investment firms, insurers and crypto-asset service providers, along with the ICT third-party providers that serve them. Most accounting offices, schools, kindergartens and property managers are not financial entities, so DORA doesn't apply to them directly. If your clients are in the financial sector, though, you may be asked about the tools you use as part of their supplier checks.

If you are a financial entity, an email service used for client notices is an ICT third-party service:

DORA checklist for client notices:
  • Is the email service recorded in your register of information on ICT third-party arrangements?
  • Does the contract cover the provisions DORA requires, such as a description of the service, data locations, access and audit rights, and termination?
  • Do you have an exit plan, including a way to export your contacts and templates?
  • Would a serious outage that stops client notices be handled by your ICT incident process?

A one-page checklist for 2026

  1. List the client emails you send and the legal basis for each: contract, legal obligation or legitimate interests.
  2. Keep service emails free of advertising.
  3. Minimise the data in each email and make sure every attachment goes only to its owner.
  4. Sign a data processing agreement with every provider and update your records of processing.
  5. Write down a procedure for access, rectification and erasure requests, with a one-month deadline.
  6. Set retention rules for contact lists and remove former clients.
  7. Authenticate your domain with SPF, DKIM and DMARC to protect clients from impersonation.
  8. Check whether DORA applies to you or to your clients.

Remember what's at stake: GDPR fines can reach €20 million or 4% of worldwide annual turnover, whichever is higher. For a small business the more realistic risk is a single complaint from a client whose statement went to someone else.

How MailerBit supports these habits

  • Your own verified domain. Emails are DKIM-signed with your domain and use your Return-Path, so clients see your name, not a generic platform address.
  • Per-client attachments. A file field holds each client's own document, such as their invoice PDF, and sends it only with their email. No manual attaching, fewer wrong-recipient mistakes.
  • Unsubscribing handled for you. Every email includes one-click unsubscribe, and unsubscribed contacts are left out of later sends automatically.
  • Bounces and spam complaints are suppressed automatically, so you stop sending to addresses that no longer work.
  • Email history per contact, CSV export and deletion of contacts make access and erasure requests easier to answer.

Compliance for client emails isn't about paperwork for its own sake. It's about sending the right data to the right person, from an address they can trust. Start your 7-day free trial and set up client emails that are personal, expected and easy to defend.

Related articles

Write a Paragraph, Get a Client Email: MailerBit's AI Editor

Write a Paragraph, Get a Client Email: MailerBit's AI Editor

Turning a fee notice or payment reminder into a clean, phone-friendly email used to take an afternoon. MailerBit's AI Editor builds it from a short description in seconds.

Automating Recurring Client Emails: Best Practices for 2026

Automating Recurring Client Emails: Best Practices for 2026

Payment reminders, statements and fee notices are perfect for automation, if you get the data, timing and checks right. Practical rules for recurring client emails that run on time.

Gmail, Yahoo & Microsoft Sender Requirements: Checklist

Gmail, Yahoo & Microsoft Sender Requirements: Checklist

Gmail, Yahoo and Microsoft now enforce sender rules. A practical checklist of SPF, DKIM, DMARC, one-click unsubscribe and spam rate, so your reminders and statements keep arriving.

All articles →