Miljödata’s GDPR Fine Works Out to 82 Öre per Person Exposed
Sweden's IMY fined the HR software supplier SEK 1.8 million after a breach of 2.2 million people's records. The decision shows that was more than 3% of the firm's revenue, and still almost nothing per victim.
Updated Oct. 19, 2026: We rewrote this story from IMY’s full written decision rather than press coverage. The decision shows the fine came to about 3.1% of Miljödata’s 2025 turnover, above the 2% line, and that the company denied any GDPR breach and asked for a reprimand instead. As of Oct. 19 we found no public record of an appeal.
Sweden’s data protection authority has fined Miljödata, the HR software supplier whose August 2025 breach exposed staff sick-leave and rehabilitation records from a majority of Sweden’s municipalities, SEK 1.8 million. The Integritetsskyddsmyndigheten, or IMY, announced the decision on Sept. 22, finding that Miljödata i Karlskrona AB broke Article 32(1) of the GDPR by failing to secure the personal data of about 2.2 million people. Miljödata has three weeks from receiving the decision to appeal, and IMY is still examining two municipalities and a region that used the system.
Divide the fine by the people affected and it comes to about SEK 0.82 each, or 82 öre. The decision itself explains why the number is so small, and it is not because IMY went easy.
What IMY decided on Sept. 22
The decision, case IMY-2025-21177, was signed by Director-General Eric Leijonram. It orders Miljödata to pay “en administrativ sanktionsavgift på 1 800 000 kronor,” an administrative fine of SEK 1.8 million, for failing to take appropriate technical and organisational measures before and during an incident discovered on Aug. 23, 2025, according to IMY’s case page.
IMY’s release lists three failings. Security was not strong enough for the kinds of data Miljödata held. Checks when installing new software were inadequate. And there was no automatic real-time monitoring to spot intrusions. IMY judged the company negligent.
“GDPR ställer krav på lämpliga säkerhetsåtgärder för de personuppgifter man hanterar,” Leijonram said in the release: the GDPR requires appropriate security measures for the personal data you handle.
The data was not trivial. The decision describes personal identity numbers, contact and employment details, absence records, and sensitive health data including sick leave, rehabilitation documentation and staff notes, with about 20 data points per person. In limited cases it covered children and people with protected identities. IMY says the customers included a majority of Sweden’s municipalities, several regions, state agencies and many private companies.
How one outdated component let the attackers in
The decision’s timeline is short and unflattering. Miljödata installed a security component about seven days before the attack and had not checked its version, even though its vulnerability had been publicly documented more than a year earlier. The attacker was inside for about three days before alarms went off.
- About a week before the incident: the vulnerable component is installed.
- Aug. 20, 2025: the attack begins.
- Aug. 23, 2025: technical alarms trigger and the breach is detected. Servers are isolated within about an hour.
- Aug. 26, 2025: Miljödata reports the breach to IMY.
- Sept. 14, 2025: part of the data is published on the dark web.
- Sept. 22, 2026: IMY issues its decision and fine.
Afterwards, the decision records, Miljödata rebuilt its domain controllers, replaced the affected security products and brought in EDR tooling and round-the-clock SOC monitoring. IMY did not count those investments in the company’s favour, finding they had not materially reduced the harm to the people whose data had already leaked.
The per-victim arithmetic

Here is the fine set against the numbers in IMY’s own decision. The per-person and per-data-point figures are our calculations.
| Measure | Figure | Source |
|---|---|---|
| Fine | SEK 1,800,000 | IMY decision |
| People affected | About 2,200,000 | IMY decision |
| Fine per person | About SEK 0.82 (82 öre) | Our calculation |
| Data points per person | About 20 | IMY decision |
| Fine per data point | About SEK 0.04 | Our calculation |
| Miljödata turnover, 2025 | SEK 58,476,045 | IMY decision |
| 2% of turnover | SEK 1,169,521 | IMY decision |
| Fine as share of turnover | About 3.1% | Our calculation |
| Legal maximum in this case | EUR 10 million | IMY decision, GDPR Art. 83(4) |
Read the bottom half of that table first. Miljödata is small: SEK 58.5 million in 2025 turnover, with a parent company that reported none. IMY treated the two as one undertaking and fined them more than 3% of a year’s revenue. For a firm that size, that is a real hit.
Now read the top half. A company holding health records for 2.2 million people paid less than a krona for each of them.
Why the GDPR cap was never the constraint
The GDPR’s Article 83(4) sets the ceiling for a security failure like this at EUR 10 million or 2% of worldwide annual turnover, whichever is higher. IMY spelled out that “Två procent av den totala årsomsättningen för företaget för budgetår 2025 är således 1 169 521 kronor” (two per cent of the company’s total turnover for 2025 is therefore SEK 1,169,521). Because that is below the fixed figure, the decision says the highest possible fine in the case is EUR 10 million.
So IMY had room to go much higher, and chose a number well under the ceiling that it described as effective, proportionate and dissuasive given the gravity of the breach and the size of the company. It rated the breach as high-gravity because of the number of people, the sensitivity of the data, how central the processing was to Miljödata’s business and how negligent the company had been.
Our read: that is the structural problem. GDPR fines are calibrated to the offender’s size, and proportionality is a legal requirement. Nothing in the formula scales with how many people a small supplier holds data on. When hundreds of public bodies hand the same records to one niche vendor, the fine that vendor can bear says little about the damage it can do.
Britain has seen the same pattern. In March 2025 the ICO fined a software provider about £3 million after a 2022 ransomware attack; the supplier was Advanced, which TechRadar described as an NHS IT supplier. We have not included a per-person comparison here because we could not confirm the affected-people count from the regulator’s own text this cycle.
Miljödata’s defence, and what IMY rejected
Miljödata denied breaching the GDPR at all, according to the decision. It argued the attack was a crime, not the result of negligence; that it had layered protection including two-factor authentication and separate role accounts; that it had no reason to suspect an expensive product from a well-known vendor was out of date; and that no concrete harm or claims had followed. If IMY did find a violation, the company said, a reprimand would be the only proportionate response.
IMY credited one thing: Miljödata’s quick information work after the breach, including individual meetings with several hundred controllers and coordination with Sveriges Kommuner och Regioner, the association of municipalities and regions. It treated encryption of attachments and free-text fields as the expected baseline, and self-reporting and cooperation as neutral.
What happens next for Miljödata and its customers
Under the decision’s appeal instructions, Miljödata had three weeks from receiving it to file an appeal with IMY, which forwards valid appeals to the administrative court in Stockholm (Förvaltningsrätten i Stockholm). As of Oct. 19, our searches of IMY and Swedish coverage found no public report of whether Miljödata appealed.
The customers are next. IMY says it has opened reviews of two municipalities and one region connected to the attack, and those are ongoing. If you are trying to work out what a leaked identity number means for you, the steps in our guide to what to do after an ID number leak carry over. More in privacy and security.
What it means
The decision is careful, well reasoned and, by the GDPR’s own logic, fair to Miljödata. It also shows that the deterrent for a breach like this has to come from somewhere other than the supplier’s fine. The open reviews of Miljödata’s customers are where that question now sits: whether a municipality that sends staff health records to an outside vendor must check the vendor’s security, not just its price.
The stolen records went online on Sept. 14, 2025. A year and eight days later, the price came to 82 öre a person.
Researched and drafted with AI tools, fact-checked against primary sources and approved by a human editor before publishing. Prices and dates are as of publication. Our standards →
Sources- imy.se — announced the decision on Sept. 22
- imy.se — decision itself
- imy.se — case page
- eur-lex.europa.eu — GDPR's
- ico.org.uk — fined a software provider about £3 million
- techradar.com — TechRadar described
Latest from prompt/power
- Broadcom’s AI chip sales now outstrip its entire business from a year ago. What to watch on Dec. 9Nov 19
- NeurIPS 2026 is in three cities. Here’s how the split worksNov 19
- Pay yearly or monthly? What you save on AI subscriptions in CanadaNov 19
- IBM, NVIDIA and Fermilab plan a quantum test bed. Here’s what each brings, and what’s still missingNov 19
- GPT-6.2 Astra is OpenAI’s first released model rated ‘High’ for AI self-improvement. What that means, and what it costsNov 18