Amplitude
How to configure Amplitude at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Amplitude and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Amplitude Browser SDK 2 (@amplitude/analytics-browser), including autocapture and optional Session Replay. Amplitude, Inc. is a US company.
What the service does in this scope. The SDK creates a first-party cookie AMP_ plus the first characters of the API key, storing device ID, session ID and last event time. All persistent storage can be disabled with identityStorage: "none", in which case a new device ID is created on every visit. IP address tracking can be switched off in trackingOptions.ipAddress. Projects created in the EU data centre are used with serverZone: "EU". The SDK can be initialised only after consent.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | EU data centre; IP tracking off; autocapture limited; no Session Replay; after consent. |
| Configuration B — Higher risk | US data centre (default); IP tracking on; full autocapture and Session Replay; user IDs; after consent. |
No configuration without prior consent. With default storage, a persistent device ID is stored. With identityStorage: "none", no identifier is stored, but events with interaction data are still transmitted; Amplitude does not document this as a consent-free configuration.
Step 1 — Configure Amplitude
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Support marketing analytics |
| 2 | Data centre | Project created in Amplitude EU; serverZone: "EU" | EU | US (default) |
| 3 | Initialisation | amplitude.init only after consent | After consent | After consent |
| 4 | IP address | trackingOptions: { ipAddress: false } | Off | On (default) |
| 5 | Autocapture | autocapture options | Page views and sessions only | Full autocapture |
| 6 | Session Replay | Session Replay plugin | Not used | Used |
| 7 | User ID | init(API_KEY, userId) / setUserId | Not used | Used |
| 8 | Withdrawal | setOptOut(true) | Configure | Configure |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Amplitude, Inc. is a US company and can be required to disclose data in its possession, custody or control regardless of storage location.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address, Authentication-derived identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address, Non-precise location data, Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per contract | Per contract |
| Processing location | EU data centre; United States as potential access location | United States |
Privacy-policy follow-up
- Amplitude as processor; cookies; autocapture and replay (B); data centre; potential access by US authorities.
Verification checklist
- No requests to
api.amplitude.com/api.eu.amplitude.comand noAMP_cookie before consent. - A: no IP-derived location in events.
-
setOptOut(true)on withdrawal.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on