Tinder’s €11 million GDPR fine: check what your data export promises

Scott Dooley
6 min read · Nov 18, 2026

Ireland’s Data Protection Commission (DPC) has fined MTCH Technology Services Limited €11 million over Tinder users’ access to their personal data. Its 13 November announcement identifies a practical problem for any organisation offering a data download: the export’s contents must match what users are told it provides.

For HR, compliance and product managers, the immediate task is to compare the promise on screen with the data delivered and the process behind it. A working download button does not establish that the organisation has answered an access request properly.

What the DPC found

The inquiry, launched in January 2020, examined Tinder’s Download My Data tool. The DPC found that categories of personal data were omitted without notice to users, or supplied only in summary form. The personal data provided through the tool did not meet the GDPR’s right-of-access requirements, the DPC announcement says.

The EDPB report, published on 17 November 2026, identifies an Article 15(3) infringement: MTCH described the automated tool as a means to request a copy of personal data without making clear that some personal data was outside its coverage. That report records 13 November as the final decision date.

The DPC imposed a reprimand and a fine of €11 million, together with an order requiring MTCH to bring its processing into compliance within three months. The announcement says tens of thousands of users used the tool during the period examined.

Why the tool’s description matters

The DPC expressly recognises that automated access tools can help people exercise their rights. Such tools do not have to provide a complete copy of personal data, but must be fair and transparent about the extent of the data supplied. That distinction in the regulator’s explanation matters: this case does not establish that every self-service export must contain every record.

It also does not establish that explaining an export’s limits, by itself, satisfies an organisation’s access obligations. The finding concerns a failure to provide a copy of personal data in the circumstances described. Treat the interface, its explanations and the wider response process as connected parts of the audit.

A product team can accurately describe a limited download while maintaining a separate process to handle requests for other personal data. The practical test is whether a person can understand the download’s coverage and obtain help with an access request beyond it.

Audit your access-request process

The checks below are our recommendations for managers, rather than a list of measures prescribed by the DPC’s unpublished decision. Use them to produce a short record of gaps, owners and corrective actions.

Map export coverage

Ask the product or system owner to list the personal-data categories in the export, their source systems and any date limits. Compare that list with the organisation’s data inventory. For each category, record whether the download includes the underlying data, a summary or nothing.

Illustrative audit scenario: an employee portal exports profile and payroll details, while appraisal notes sit in a separate HR system. Record the gap and identify who handles a request covering those notes. This is an example for testing your process, not a finding about Tinder. Our guide to employment data requests offers related UK workplace context.

Explain omissions

Read the button label, help text, confirmation email and downloaded file together. Compare each statement with the coverage map. Replace broad promises that the tool cannot support, and explain material limits where people will see them before relying on the export.

Distinguish a technical gap from a decision to withhold information. An export that cannot retrieve a category needs an operational response; its technical limits are not, by themselves, a legal justification for withholding personal data. Ask the privacy lead to review any proposed withholding explanation.

Provide a route for further requests

Place a clear contact route beside the explanation of the download’s scope. Name the team that receives further requests and ensure it can obtain information from systems outside the tool. Give support staff instructions for routing a request that says the download is incomplete.

Test the handover. A support agent should be able to send the request to an accountable owner, with the original request and the export already supplied. Avoid making the person repeat the same explanation to several teams.

Test and document responses

Use authorised test accounts to compare known data with the export. Include a case with information held outside the main application and one where the export contains a summary. Check that the wording remains accurate in both.

Keep the test date, tool version, expected coverage, actual result and action owner. Repeat the check when a new system or data category is introduced. Ask one colleague unfamiliar with the tool to read its explanation and describe what they expect to receive; investigate any mismatch.

What remains unconfirmed

At the time of checking, the DPC announcement says the full decision will be published in due course. It does not identify the omitted categories or set out the complete technical changes required. Do not infer those details from the fine or turn the three-month order into a universal implementation deadline.

FAQs

Does a download tool satisfy a GDPR access request?

The existence of a tool does not establish compliance. In this case, the DPC found an Article 15(3) failure involving the data supplied and the way the tool was described. Assess the response and supporting process, rather than treating a completed download as automatic closure.

Must every export include all personal data?

No. The DPC says an automated tool need not provide a complete copy, but must be fair and transparent about its scope. That statement does not remove the wider access obligations addressed in the case summary.

What did the DPC order MTCH to do?

Bring its processing into compliance within three months. The published announcement also records a reprimand and a fine of €11 million. It does not provide the full remedial specification.

Assign an owner to compare your tool’s wording with its coverage map, test the follow-up route, and record what needs to change.