Health App Analytics Anonymisation with anonym.plus

Turn in-app event records into anonymous data outside UK GDPR scope.

Analytics anonymisation is the removal of personal data from the usage stream a health app records. Once it is truly anonymous, it is no longer personal data under UK GDPR Recital 26. anonym.plus does this on your device and keeps the behaviour patterns for product work.

When this applies

These streams track who tapped what, tied to a user identifier, email, and IP. For funnel analysis you want the behaviour, not the people behind it.

How anonym.plus handles it

  1. Open the usage dump in anonym.plus on a local device.
  2. It finds user identifiers, emails, IPs, and device handles.
  3. Screen names and action types stay in place.
  4. Swap the personal fields with the map switched off.
  5. Save the anonymous file on your machine.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
IdentifiersIDuser_id → [USER]
ContactEMAIL_ADDRESSprofile email → [EMAIL]
NetworkIP_ADDRESS198.51.100.9 → [IP]
IdentifiersIDdevice handle → [DEVICE]
DatesDATE_TIMEaction time → [TIME]
LocationLOCATIONgeo region → [PLACE]

Compliance achieved

Anonymise health app analytics offline — see plans & start free →

Limitations & cautions

A usage trail can be unique even with no name, since a rare path through the app fingerprints one person. Coarsen timestamps and location, and keep no re-link key, before you treat the output as anonymous under the ICO motivated-intruder test.

Frequently asked questions

When is this stream truly anonymous?

When no one can reasonably re-identify it. That means no kept key and low residual risk from a unique behaviour trail, per UK GDPR Recital 26.

Is a user identifier personal data if it is just a number?

Yes. A stable user identifier singles out one person, so it counts as personal data even without a name attached.

Can I keep the funnel steps?

Yes. Action types and screen flow stay. Only the personal handles are removed.