Our new white paper examines how ordinary personal data becomes health data through inference, and what organisations need to do about it.
Health data is no longer produced only in hospitals and clinics. Wearables, wellness apps, connected devices and AI-driven analytics routinely generate insights about people’s physical and mental health from data that looks entirely ordinary: sleep patterns, step counts, purchases, browsing behaviour or typing cadence.
The legal consequences are significant. Under the GDPR and comparable regimes, data is health data because of what it reveals, not where it was collected. The Court of Justice of the EU has confirmed that this applies even where the conclusion drawn is only probable, or turns out to be wrong. Once that threshold is crossed, stricter rules apply: a separate legal condition for processing, mandatory impact assessments, and, in several jurisdictions, health-sector rules on where the data may be stored.
Yet many organisations do not recognise when this happens. Inferences are often generated in analytics layers, vendor models or third-party SDKs, never flagged as health data, and therefore never brought within the controls designed to govern it.
What the white paper covers
- How and why inference turns ordinary data into regulated health data, drawing on recent CJEU case law and regulatory guidance
- The overlapping layers of regulation that can apply at once: general data protection law, cross-border transfer rules, health-sector localisation and IoT-specific regimes
- A comparative overview across the EU, UK, UAE (including the DIFC and ADGM), Saudi Arabia, the United States, Canada and China
- A practical, seven-step governance framework for managing what your systems infer, not just what they collect
The paper is written for privacy, legal, compliance, product and data teams in organisations that build or operate digital services, including those that do not consider themselves to be in the health sector.