GDPR Compliance

Potentially sensitive data, such as that generated by wellbeing apps, is a "grey area” where the GDPR classification is open for interpretation.

If data is in any way identifiable or can be connected to the user (directly or indirectly), the data collection process cannot make the claim of being anonymous.

Under GDPR law, sensitive data is in a much higher risk category than other types of personal data. Businesses that store sensitive health data should focus on GDPR administrative and technical recuirenments.

GDPR fines are starting to bite. Find out about 3 of the most recent rulings from across Europe. Then read the 7 most important lessons the fines teach us.

Every **Digital Health App** processes **personal data** and most will also process health sensitive data. Processing such data requires you to be compliant with relevant data protection laws. How do you do that as a Digital Health Business? Here are the key things you have to consider.

In the upcoming months, we will travel across Europe to the events in digital health. This short blog post will provide you with a summary of these digital health events and why you should join us there!

By storing data locally on a user's device, you have fewer administrative obligations compared to when you transfer and process data in the cloud. However, you still need to provide methods to delete data in case of device theft or loss.

Under GDPR, anonymous data is not treated as personal data, therefore no user consent and no particular protection is required. However, it is very difficult to ensure that the data is truly anonymous.

This brief post summarizes some of the key points relevant to Digital Health companies.