When most people picture a GDPR fine, they picture a breach, like a misconfigured database or a stolen customer list. Ireland's latest penalty against the company behind Tinder involves nothing of the kind. Nobody broke in. The regulator's finding is that when users asked for their data, the company's own self-service tool gave them an incomplete copy and didn't say so.

On Nov. 13, Ireland's Data Protection Commission (DPC) announced that it had fined MTCH Technology Services EUR 11 million, about $10 million according to The Record. It also issued a formal reprimand and ordered the company to bring its processing into compliance within three months. The decision got wider coverage on Nov. 16.

The case is about one feature: Tinder's "Download My Data" tool. It's a useful reminder that a privacy-request portal is a compliance control, and regulators will test it like one.

What the DPC found

According to the DPC's release, the regulator opened the inquiry on its own initiative (an "own-volition" inquiry, meaning no single complaint triggered it) in January 2020. It looked at how Tinder handled users' requests for access to their personal data.

The legal hook is Article 15(3) of the GDPR. Article 15 is the "right of access." Paragraph 3 gives people the right to get a copy of the personal data an organization is processing about them. Tinder offered that copy through Download My Data, and the DPC said tens of thousands of users used it during the period the inquiry assessed.

The DPC found the tool did not give users all of the personal data they were entitled to. Some categories of data were left out with no notice to the user. Other categories were given only in summary form. The Next Web, citing Politico, described the same problem: some categories were dropped entirely and others were condensed.

Three DPC Commissioners made the decision: Des Hogan, Dale Sunderland and Niamh Sweeney. The penalty has three parts: a reprimand, the EUR 11 million fine, and an order to fix the processing within three months. The DPC said it will publish the full decision later. Until it does, the public record doesn't say which data categories were missing or summarized.

A complete copy isn't strictly required, but honesty is

The most useful detail for anyone who builds or runs these tools came from DPC deputy commissioner Graham Doyle. In comments reported by The Record, Doyle said self-service tools don't have to provide a complete copy of a user's data, but they must be fair and transparent about how much of the data they actually provide.

That distinction is the key to the case. By Doyle's account, the regulator isn't saying every export button has to dump every byte a company holds. It is saying a tool that presents itself as "your data" can't quietly give you less. If a portal covers some categories and not others, or condenses records into summaries, users need to know. That way they can understand the gap and ask for the rest through another channel.

The failure the DPC describes is about transparency as much as completeness. Categories were "omitted without notice." A user who downloaded the archive had no reason to think anything was missing.

Six years from inquiry to fine

The timeline is long even by EU enforcement standards. The inquiry opened in January 2020, and the decision was announced in November 2026. Both The Next Web and The Record noted that's nearly six years from start to finish.

That matters for two reasons. First, the DPC's findings describe how the tool worked during the period it examined. The public sources don't say how today's version of Download My Data compares. Second, the three-month compliance order means the company now has a short, fixed deadline after a very slow investigation.

What the company says

A Tinder spokesperson told Politico, as quoted by The Next Web, that the company engaged with the DPC throughout the investigation and stands behind its privacy protections. The Record reported that the company did not immediately respond to its request for comment. Neither outlet reported whether the company plans to appeal.

Why a security site cares about an access-rights fine

Data subject access requests (DSARs) usually sit with the privacy or legal team, not the security team. But the plumbing behind a "download my data" feature is a data-inventory problem, and that's security territory. To produce an accurate export, an organization has to know where a user's personal data lives: production databases, analytics pipelines, moderation systems, logs, third-party processors. If an export leaves out a category, it's often because nobody mapped that system to the user record in the first place.

The same blind spot that produces an incomplete export also produces incomplete breach scoping, incomplete retention enforcement and incomplete deletion. If you can't list it, you can't protect it, delete it or hand it back.

What It Means for Defenders

Who is directly affected: MTCH Technology Services, the company the DPC fined over Tinder, which must bring its processing into compliance within three months. Tinder users don't need to rotate credentials or patch anything. This is not a breach. The finding is that the access copies users received through Download My Data were incomplete and didn't disclose that.

Who should take notes: any organization that runs a self-service data export, privacy portal or automated DSAR workflow for people covered by the GDPR. The sources don't give a technical fix, but the DPC's findings and Doyle's comments point to practical checks:

  • Reconcile your export against your data inventory. List every category of personal data you process about a user and confirm whether the self-service tool includes each one. Any category the tool doesn't cover is the kind of silent omission the DPC objected to.
  • Disclose what the tool leaves out. Per Doyle, a tool need not be a complete copy, but it must be fair and transparent about its scope. If some categories aren't included, say so clearly in the tool and in the export, and tell users how to request the rest.
  • Don't pass off summaries as the data itself. The DPC faulted Tinder for giving some categories only in summary form. If you summarize, label it as a summary and offer the underlying records on request.
  • Keep the export in step with the product. Each new feature, data store or processor is a new category the export may miss. Add a DSAR-coverage check to change management, the same way you'd add logging or access-control review.
  • Keep a manual path open. A self-service tool should supplement a working access-request process, not replace it, especially for categories the tool can't produce.
  • Document your reasoning. When regulators look at a tool years after the fact, as in this nearly six-year inquiry, records of what the tool covered and why will matter.

For teams working toward CMMC or other U.S. frameworks, the GDPR obligation itself may not apply. The underlying discipline does: an accurate, maintained map of where sensitive data lives is a prerequisite for protecting it, reporting on it and proving to an assessor that you control it.

The full DPC decision, once published, should show which data categories were affected and how the regulator weighed the penalty. We'll update this coverage when it's released.

Sources