Dutch apps. Your choices.¶
Community patches for Morphe, with clear explanations of the data your apps share.
Understand what your apps share¶
You open a weather app to check the rain. Alongside that forecast, the app may record which screens you visit, the places you look up, or which video you play. Some requests provide the service you asked for; others measure your behaviour or support advertising.
Morphe patches change selected parts of supported Android apps. This guide explains what those changes do and what data exchange remains. You do not need to know what a tracker or an SDK is to start.
What would you like to do?¶
| Your question | Start here |
|---|---|
| How do I use these patches? | Installation guide |
| What changes in my app? | Apps by category |
| What happens when an app tracks me? | Tracking, step by step |
| What are Snowplow, Kantar or OneTrust? | Tracker and service explanations |
| Can activity be linked to me without my name? | Identifiers |
| How do you know what an app sends? | Our evidence and its limits |
A useful first example¶
Buienradar's inspected code connects its audience-measurement request to a Snowplow identifier. That means the request has a label associated with an app installation, rather than being just an unconnected count. Our finding comes from the code path; we have not captured every request from a phone. Follow this example.
Choose your route¶
The guides help you install and choose patches. Learn about tracking explains mechanisms with examples. Apps describes specific versions. Trackers explains services shared by several apps. Evidence shows the basis and remaining questions.
There are thirteen supported apps in this documentation snapshot, reviewed on 28 October 2026. Research-only apps are listed separately. A working patched app can still send location, account or device information for retained services; each app page explains the relevant exceptions.