MOD-ANL · Analytics & monitoring module See what customers do, and what breaks, before they tell you.

As the module is set up, yes. EU law requires consent to store or read information on a customer's phone unless it is strictly necessary for a service they asked for, and the EDPB confirms that covers app SDKs and identifiers. Each analytics, attribution and engagement tool starts only after the customer agrees to its purpose. Crash and performance tools can wait for consent too: no EU-level guidance exempts them, and the final call is your data protection officer's. Customers change their choice in the app's settings, as easily as they gave it.

They are kept out by design. Every event follows a tracking plan your team approves, customers appear under a random platform ID, and card numbers, account numbers, document images and passwords never go into an event, a session recording or an error report. Where a tool offers session replay, text and inputs are masked and screens with card or identity details are masked or left out. Engagement tools receive only the contact details they need to reach customers who opted in. Keeping card data out matters for PCI DSS too, which forbids keeping sensitive authentication data after authorisation; your assessor decides what is in scope.

In the EU wherever the tool allows, which is most of them. Mixpanel, Amplitude, PostHog, Segment, Customer.io, Braze, CleverTap, Adjust, Sentry, Datadog and New Relic offer an EU region, chosen when the account is created and in most cases fixed after that, and AppsFlyer keeps every account's data in the EU. Google Analytics collects data from EU devices on servers in the EU. Branch, Singular and BugSnag's hosted service keep data in the United States, so with them we settle the options before launch, such as an EU hosting arrangement or BugSnag On-premise in your own infrastructure. Data that does leave the EU travels under the EU-US Data Privacy Framework, for providers certified under it, or under standard contractual clauses.

The GDPR asks you to pass an erasure on to everyone who received the data (Article 19). The platform stops sending the customer's data, then asks each tool to delete it. Most offer an API for it, such as Mixpanel's GDPR API, Amplitude's User Privacy API, Braze's /users/delete, a suppression in Customer.io and the OpenDSR APIs of AppsFlyer and Singular; with a few, such as New Relic, the request goes to the provider. Crash and error reports carry no personal details by design, and they are removed when their retention period ends.

Only where a tool tracks in Apple's sense: linking data from your app with other companies' apps or websites for advertising or ad measurement, which mobile attribution can do. The app then shows Apple's App Tracking Transparency prompt before the attribution SDK starts. Customers who decline still count in Apple's AdAttributionKit and SKAdNetwork results, which need no permission. Mixpanel and Amplitude do not track in Apple's sense by default. Apple's prompt does not replace consent under EU law, so the app asks for both.

If you are an EU financial entity, yes. Each hosted tool provides ICT services, so it goes into your register of information on ICT third-party arrangements, which DORA has required since 17 January 2025 (Article 28(3)), in the templates of Implementing Regulation (EU) 2024/2956. We help you fill in each tool's entry: who provides it, what it does for you and where your data is processed.