Health App Analytics Anonymization with anonym.plus

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

Analytics anonymization 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 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 ID, 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 IDs, 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

PHI 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

Anonymize 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 geo, and keep no re-link key, before you treat the output as anonymous.

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.

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

Yes. A stable user ID 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.