Skip to main content
green gradient background, "The Future of Application Security Is Already Here." and a read the report button.
Maileva's 22 Million: What Processor Breaches Teach DPOsSecurity & Breach Notification
5 min readFor Data Protection Officers (DPOs)

Maileva's 22 Million: What Processor Breaches Teach DPOs

The Maileva incident has been a hot topic for Data Protection Officers (DPOs) since the company confirmed that attackers stole the names and postal addresses of 22 million people. Maileva, a mailing services provider within the Docaposte group, handles the printing and posting of invoices, payment reminders, and administrative documents for thousands of customer organizations. Some customers have warned that the content of letters may also have been viewed.

Below are the questions we keep hearing from practitioners, answered with the GDPR provisions that actually apply.

Q1. Maileva reported to the CNIL. Does that mean our organization is off the hook?

No. A processor's notification and a controller's notification are separate duties. Under Article 33(2), the processor must notify the controller "without undue delay" after becoming aware of a personal data breach. Under Article 33(1), the controller must then notify the supervisory authority within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals.

Maileva's report to the CNIL does not discharge your obligation as a controller. In this case, Maileva informed the affected organizations and left them responsible for contacting their own customers and other recipients. That is the normal allocation: the processor tells you, and you decide what goes to the supervisory authority and to data subjects.

Q2. When does our 72-hour clock start if the processor tells us late?

The EDPB's breach notification guidelines treat the controller as "aware" once it has a reasonable degree of certainty that a security incident has compromised personal data. Receiving the processor's notice is the usual trigger. A slow processor doesn't excuse you from the clock, but it does make your contract terms matter. If your agreement only says "promptly," you have little to enforce. Set a defined window, such as 24 hours from detection, and require the processor to share what it knows even when the picture is incomplete.

Q3. Our processor's processor was the one breached. Are we still responsible?

Yes. Look at the chain in this incident. A hospital told patients that payment reminders sent over a two-week period may have been viewed. The hospital uses a medical billing provider, which in turn uses Maileva to print and mail those reminders. The billing provider also said correspondence it handled for other healthcare clients was affected.

The hospital is the controller. Under Article 28(2) and 28(4), a processor needs the controller's authorization to engage another processor, and the primary processor stays fully liable to the controller for its sub-processor's performance. In practice, you need to know who is in your chain. If you can't name your sub-processors, you can't assess your exposure, and you can't write an accurate Article 33 notification when the call comes.

Q4. Is a name and postal address really worth worrying about?

Don't dismiss it. Names and addresses are personal data under Article 4(1), and the risk assessment under Articles 33 and 34 depends on context, not on the data fields alone. Two points from this incident matter here.

First, the people counted in the breach are recipients of letters, and many may have had no direct dealings with Maileva. Their exposure is in the relationship between them and the sender. A name and address tied to an unpaid-invoice letter says something different from a name and address on a marketing mailer.

Second, some customer notices described more than names and addresses: dates of care and amounts owed in one case, tenant account numbers and housing details in another. Health-related billing data may trigger Article 9 considerations. Run your risk assessment against the actual documents your organization sent through the processor, not against the headline field list.

Q5. Do we have to tell individuals, and what do we say?

Article 34 requires communication to data subjects without undue delay when the breach is likely to result in a high risk to their rights and freedoms. The content must be in clear and plain language and include the elements in Article 34(2): the nature of the breach, the DPO's or another contact point's details, the likely consequences, and the measures taken or proposed.

Make the consequences concrete. One practical risk here is fraud: a recipient who receives an unexpected payment reminder should verify the amount and payment instructions with the sender, using a phone number from its official website or customer portal, not the one printed on the letter. Putting that advice in your notice is more useful than generic reassurance. Document your decision either way, as Article 33(5) requires you to record every breach and the reasoning behind your response.

Q6. What should we have in place before our own Maileva moment?

Start with the contract. Article 28(3) sets the minimum terms, including processing only on documented instructions, confidentiality, appropriate technical and organizational measures, sub-processor controls, assistance with breach obligations, and audit rights. Then test whether those clauses work in practice.

A short checklist you can run this quarter:

  • Map your processors and their sub-processors, including who handles document content, not just who stores databases.
  • Set a contractual breach notification window tighter than "without undue delay," and name a 24/7 contact on both sides.
  • Review data minimization in what you send. If a mailing partner only needs a name and address to post a letter, consider whether the document body needs to contain more than the recipient requires.
  • Check retention. One affected organization warned that letters sent over the past decade could be exposed. Ask each processor how long it keeps print files and why.
  • Rehearse the scenario. Run a tabletop where a processor tells you on a Friday that your correspondence may have been viewed. Who decides on the Article 33 notification? Who drafts the Article 34 communication?
  • Request evidence, not assurances. Article 28(1) requires processors that provide "sufficient guarantees." Ask for audit reports, penetration test summaries, and incident history.

Where to go for more

Read the EDPB Guidelines 9/2022 on personal data breach notification for the "awareness" test and worked examples. The EDPB's guidelines on the concepts of controller and processor help when roles in a chain are unclear. For this incident specifically, watch the CNIL's website for any statement on the investigation, and the notices published by Maileva and the customer organizations that have written to their recipients. If you use Maileva or a similar mailing provider, check your own correspondence history now, before the processor's notice arrives.

Promotional banner graphic asking if you are ready for PCI DSS 4.0 with a call-to-action to get the guide

You Might Also Like