[Enforcement library](/enforcement)

# Mindemo Oy: therapy-booking trackers sent health context to Google, Meta and Microsoft

Finland's Data Protection Ombudsman fined health provider Mindemo Oy, formerly Heltti Oy, EUR 33,000 and reprimanded it. Cookies and trackers on its online therapy booking sent details such as the therapy type and therapist chosen to Google, Meta and Microsoft for visitors who accepted cookies, without adequate risk assessment or safeguards.

## Key facts

- **Regulator or court:** Finnish Data Protection Ombudsman
- **Jurisdiction:** Finland
- **Framework:** GDPR Articles 5(1)(f), 25(1) and (2), and 32(1) and (2)
- **Record date:** 2026-10-02
- **Procedural status:** Administrative fine and reprimand; not yet final and open to appeal to the administrative court

Accepting cookies did not make it safe to send therapy bookings to ad platforms. The Finnish authority treated the therapy type and therapist a visitor picked as health data and found the security and privacy-by-design duties broken.

[Start a free scan](/run-free-codebase-scan)

- **Authority**: Finnish Data Protection Ombudsman (Tietosuojavaltuutettu): Deputy Ombudsman Heljä-Tuulia Pihamaa and the sanctions board
- **Reference**: TSV/303/2022, decisions of 2 October 2026, announced 8 October 2026
- **Controller**: Mindemo Oy (formerly Heltti Oy)
- **Law**: GDPR Articles 5(1)(f), 25(1) and (2), and 32(1) and (2)
- **Outcome**: Reprimand and EUR 33,000 administrative fine
- **Stage**: Not yet final; can be appealed to the administrative court
- **Source review**: 24 October 2026

## The problem

Mindemo Oy provides health services, including therapy, and was previously called Heltti Oy. Its online booking service used cookies and other tracking tools. For users who accepted cookies, data about starting and confirming a booking, the chosen therapy type and the chosen therapist went to Google, Meta and Microsoft. Users who did not accept cookies were not affected. The data was not anonymised or pseudonymised and could be linked to users, for example through IP addresses and other technical data ([press release](https://www.epressi.com/tiedotteet/laki/mindemo-oylle-seuraamusmaksu-verkkosivuevasteiden-tietosuojapuutteista.html)).

## What the authority found

- **Health data.** Information about a therapy booking relates to a person's mental health and treatment, so it is special-category data under GDPR Article 9(1), even without a diagnosis ([The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e)).
- **Identifiable to the recipients.** The authority rejected the argument that Mindemo itself could not identify anyone. What mattered was that Google, Meta and Microsoft could link IP addresses and device data to their own users' accounts ([The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e)).
- **No real safeguards.** Mindemo did not assess the high risk before processing and had no technical measures that actually limited identifiability or what was sent. Its referrer policy did not help, because LinkedIn received the full URL, including the specialty searched, in a separate variable ([The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e)).
- **Duration.** Data went to the tracking providers unlawfully for at least a year ([press release](https://www.epressi.com/tiedotteet/laki/mindemo-oylle-seuraamusmaksu-verkkosivuevasteiden-tietosuojapuutteista.html)).

## Technical issue

- **Test bookings.** In 2025 the authority made unconfirmed test bookings with a gender-identity therapist, an ADHD and autism therapist, and for Kela-funded therapy for bipolar disorder ([The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e)).
- **What was sent.** The specialty searched, the named therapist chosen, that a booking had started, and that Kela therapy was chosen went to Google and Microsoft (Bing, LinkedIn), with IP address, headers, device data and cookies. Microsoft also received the location. Mindemo said Meta Pixel received conversion data and Facebook identifiers, and that Google Signals was on.
- **Cause.** Mindemo put the error down to an employee when the booking system launched in April 2024. The trackers were removed in May 2025, during the investigation.

**Inth's technical interpretation:** consent was collected here, and the authority still found a breach, because it judged security and privacy by design rather than the legal basis for cookies. A consent banner decides whether tags load; it does not make it acceptable for them to carry health context. Keep advertising and analytics tags off booking flows, or strip URLs and event payloads, and check the actual payloads, not just headers.

Fixed:

```ts
// Booking page sends specialty and therapist to ad and analytics vendors after consent
gtag('event', 'begin_booking', { specialty, therapist_name });

// Even with consent, keep health context out of third-party payloads
if (consent.has('analytics') && !location.pathname.startsWith('/booking')) {
  gtag('event', 'page_view', { page_location: location.origin + '/' });
}
```

## Timeline

| Date | Event |
| --- | --- |
| 4 November 2022 | A member of the public reports that the willfeel.fi site passes data to tracking services |
| April 2024 | Booking system launched with the trackers in place |
| 2025 | The authority tests with.heltti.fi and heltti.fi |
| 12 May 2025 | Request for clarification sent to the company |
| May 2025 | Trackers removed; recipients asked to delete the data |
| 2 October 2026 | Decisions: reprimand and EUR 33,000 fine |
| 8 October 2026 | Decision announced |

Dates other than 2 and 8 October 2026 come from [The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e).

## Outcome

The sanctions board imposed a EUR 33,000 administrative fine and the Deputy Ombudsman issued a reprimand for shortcomings in the secure processing of personal data. No compliance order was made, because the company had already removed the trackers and asked the providers to delete the data. The decision is not yet final and can be appealed to the administrative court ([press release](https://www.epressi.com/tiedotteet/laki/mindemo-oylle-seuraamusmaksu-verkkosivuevasteiden-tietosuojapuutteista.html)).

## What it cost

| Item | Amount | Source |
| --- | --- | --- |
| Administrative fine | EUR 33,000 (not yet final) | [Press release](https://www.epressi.com/tiedotteet/laki/mindemo-oylle-seuraamusmaksu-verkkosivuevasteiden-tietosuojapuutteista.html) |
| 2025 turnover cited in the decision | EUR 11,524,059.53 (maximum fine EUR 20 million) | [The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e) |

Mitigating factors were removing the trackers, asking recipients to delete data and cooperation beyond what the law requires. ISO 27001 certification did not prevent the sanction ([The DPO summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e)).

## Why it matters

- **Consent is not a safe harbour for health context.** Data only flowed for visitors who accepted cookies, and it was still a breach.
- **Booking steps are health data.** Which therapist or specialty someone picks is enough; no diagnosis needs to be sent.
- **Identifiability is judged from the recipient's side.** If Google, Meta or Microsoft can tie it to an account, it is personal data.
- **Second Finnish tracker fine in health.** Compare [Yliopiston Apteekki](/enforcement/yliopiston-apteekki), fined EUR 1.1 million over online-pharmacy events.

Related pages: [GDPR and ePrivacy cookies](/enforcement/laws/gdpr-and-eprivacy-cookies), [Sensitive context in event data](/enforcement/issues/sensitive-context-in-event-data), [Undisclosed data exchanges](/enforcement/issues/undisclosed-data-exchanges), [IP addresses and device identifiers](/enforcement/issues/ip-addresses-and-device-identifiers).

## How Inth catches this

- **Consent banner**: Holds analytics and advertising tags until their category is granted, and can keep chosen tags off specific paths such as booking flows.
- **Website audit**: Records which vendors receive requests on each booking step and which URLs and event parameters they carry, after acceptance as well as before.

### Out of reach

- Inth can show what was sent; it cannot decide whether a given field is health data or whether safeguards are adequate under GDPR.

Consent records with choice, country and policy, and per-page runtime observations that show what was sent and when.

[Start a free scan](/run-free-codebase-scan)

## Checks for your own systems

Your ticks stay on this page. Inth does not save or send them.

### In the repository

- [ ] List every tag on booking and appointment flows and the parameters each event sends.
- [ ] Check that a referrer policy is not your only control; look for full URLs in event payloads.

### In the browser and network

- [ ] Accept all cookies, make a test booking and inspect every third-party payload for specialty, provider or condition.
- [ ] Repeat after refusing and confirm nothing is sent.

### With the people responsible

- [ ] Do a documented risk assessment before adding any tag to a health flow.
- [ ] Decide who approves tags on sensitive pages and keep a record of changes.

## Sources and limits

- [Finnish Data Protection Ombudsman press release (ePressi)](https://www.epressi.com/tiedotteet/laki/mindemo-oylle-seuraamusmaksu-verkkosivuevasteiden-tietosuojapuutteista.html), 8 October 2026
- [Same release on tietosuoja.fi](https://tietosuoja.fi/-/mindemo-oy-lle-seuraamusmaksu-verkkosivuevasteiden-tietosuojapuutteista)
- [Decision TSV/303/2022 in Finlex](https://www.finlex.fi/fi/viranomaiset/tietosuojavaltuutettu/2026/32)
- [The DPO decision summary](https://thedpo.eu/de/decisions/e0b940af-2bbf-44db-94bb-138914b1ef1e)

The press release was read in Finnish from the official ePressi copy; the tietosuoja.fi page blocked automated access. The Finlex decision page loads its text with scripts and was not read directly, so the test bookings, the referrer-policy finding, turnover and mitigating factors come from The DPO's summary of the decision. Whether Mindemo has appealed was not checked.

Source review: 24 October 2026. This page describes the cited records. It does not audit Mindemo's current systems. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.