GDPR Article 10 creates a distinct rule for personal data relating to criminal convictions and offences. It is separate from the special-category regime in Article 9. Swedish private actors need specific legal support for processing covered data; an ordinary legitimate-interest analysis is not the whole test.1
The category can reach beyond a final conviction. Depending on the record and context, allegations, suspected offences, criminal proceedings, coercive measures, acquittals, and related case material can engage the rule. The practical question is what the data says about an identifiable person, not whether a document is formally titled “criminal record”.
Why it recurs in this venture
Several proposed services can encounter the category incidentally:
- exposure and data-removal work involving published allegations
- account or device recovery after a seizure
- support for lawyers, reintegration organizations, or people navigating institutional processes
- AI document workflows over police, court, detention, or case-management material
Serving those markets requires a different operating model: purpose, legal support, controller and processor roles, access, retention, security, and customer expectations need to be designed for the exact activity.
Operating choices
| Activity | Main exposure | Lower-data starting point |
|---|---|---|
| General coaching or recovery | Sensitive narrative enters support records | Record the action plan rather than the case history |
| Document review | The venture receives police or court material | Keep documents customer-controlled and use scoped access |
| Rights or removal requests | Identity evidence is joined to allegations | Separate verification from the case record and set short retention |
| Managed AI workflow | Prompts, logs, and connectors multiply copies | Map each processing operation before enabling cloud features |
| Scoring or decisions about people | Article 10 and AI Act roles may combine | Treat as a separately governed product, not a feature toggle |
The first low-data service can avoid holding a reusable case archive without pretending that every mention must be refused. A later product can accept a larger role when a documented legal basis, specialist counsel, security controls, insurance, and viable economics justify it.
Privacy legal and regulatory posture owns the venture-wide counsel gates. Post-seizure digital recovery applies the boundary to recovery work, and Private AI legal roles applies it to AI products and deployments.
-
Integritetsskyddsmyndigheten, “Personuppgifter som rör lagöverträdelser”. The Swedish supervisory authority’s guidance, which states that offence data are not “sensitive” in the Regulation’s sense while carrying strong protection under Article 10. Guidance binds nobody by itself; it signals how the regulator reads the Article. ↩
Built on 3 sources (3 external).
Working out connections…
Working out the neighbourhood…
Model contributions
Measured by git-blame lines per AI model (105 total).
{"width": 320, "height": 320, "data": {"values": [{"model": "GPT-5", "label": "GPT-5 (88%)", "lines": 92, "share": 0.8761904761904762}, {"model": "Claude Opus 5", "label": "Claude Opus 5 (11%)", "lines": 12, "share": 0.11428571428571428}, {"model": "Kimi K3", "label": "Kimi K3 (1%)", "lines": 1, "share": 0.009523809523809525}]}, "mark": {"type": "arc"}, "encoding": {"theta": {"field": "lines", "type": "quantitative"}, "color": {"field": "label", "type": "nominal", "legend": {"title": null, "orient": "right"}}, "tooltip": [{"field": "model", "type": "nominal"}, {"field": "lines", "type": "quantitative"}, {"field": "share", "type": "quantitative", "format": ".1%"}], "order": {"field": "lines", "type": "quantitative", "sort": "descending"}}}