Additional privacy considerations
Depending on your implementation, you may need to configure more than cookies, storage, and access controls. Review these topics before you consider the setup in the privacy and consent overview complete.
Session Replay
If you use Session Replay, review it separately from your core analytics setup. Replay can capture a richer set of user interactions, so it often requires its own privacy review, masking rules, and consent treatment.
In practice, that means you should:
- Decide whether Replay is covered by the same consent choice as analytics or needs separate treatment.
- Review masking and exclusion settings before rollout.
- Make sure your privacy notice accurately describes the use of replay technology.
Refer to the Session Replay documentation for details.
Access requests, not only deletion requests
Many privacy programs focus first on deletion, but customers may also need to respond to requests for access to personal data. If you support privacy requests, plan for both.
For deletion workflows, use the User Privacy API. If you also need to support data access requests, refer to the DSAR API documentation.
Document one operational workflow that covers:
- Request intake.
- Identity verification.
- Access or deletion in Amplitude.
- Cleanup in upstream systems.
- Audit logging.
Privacy notices and disclosures
Your implementation and your privacy notice should stay aligned. If you collect analytics data, use Session Replay, or rely on a limited anonymous measurement flow, review your disclosures to make sure they still describe what you collect, why you collect it, and how users can exercise their choices.
This matters most when teams change implementation details over time. A privacy issue often comes not from the tool itself, but from a gap between what the product does and what the notice says.
Hosting region and data residency
For some organizations, especially in Europe, hosting region is part of the privacy decision. Amplitude offers both US and EU data center options, and that choice may affect your internal review process.
If data residency matters to your business, confirm your hosting setup early and make sure it matches your internal requirements. Refer to data residency options.
Operational caveats after launch
Some privacy controls work exactly as expected, but still have practical consequences to plan for:
- Deleting a user doesn't prevent Amplitude from tracking that user again.
- If deleted data still exists in a warehouse or synced source, Amplitude may reingest it.
- Retention settings can permanently remove historical data and affect old charts.
- Privacy settings need retesting after every major instrumentation or tag-management change.
A good rollout doesn't end at launch. Re-test your setup periodically, especially after SDK updates, consent banner changes, new event launches, or changes to upstream pipelines.
Server-side tracking as an alternative for known users
For logged-in or identified users, server-side tracking offers an alternative that avoids some client-side consent constraints. If a user is authenticated, you can pass their user ID directly to Amplitude's HTTP API from your backend, bypassing the browser SDK entirely.
In many jurisdictions, server-side tracking of authenticated users doesn't trigger ePrivacy Directive requirements. ePrivacy applies to accessing or storing information on the user's device, such as cookies and localStorage, and server-side calls don't touch the device. For logged-in users, server-side Amplitude tracking may therefore not require consent under ePrivacy rules in some regions.
Important caveats:
- This only applies to known, logged-in users. For anonymous visitors, you still need a client-side identifier to track behavior across pages, even if your server generates that identifier, as with cookieless tracking approaches. As soon as you store or access any persistent identifier on the user's device, ePrivacy rules apply.
- Your legal team should confirm whether server-side tracking of identified users is sufficient for your jurisdiction and use case.
- Confirm with your privacy team that processing authenticated user data server-side aligns with your data processing agreements and your GDPR lawful basis.
Why Amplitude doesn't generate modeled data for non-consenting users
Some analytics platforms fill the gap left by non-consenting users by modeling estimated behavior, statistically inferring what those users might have done based on users who did consent. Amplitude doesn't take this approach, for two reasons.
- Modeled data is inconsistent and hard to interpret. Platforms that offer modeling typically generate estimates only when they have enough activity volume to do so. Below certain thresholds, the platform produces no model at all, and coverage is uneven across segments, time periods, and properties. You can't easily tell when you're looking at real data and when you're looking at an estimate, and applying consistent analysis rules across your dataset becomes nearly impossible.
- Modeled data behaves differently depending on where you query it. If you export modeled event data to a warehouse and run the same analysis there, you often get different results than you do inside the analytics UI. Platforms typically apply this logic at query time in the UI, not at ingestion. This creates a split source of truth that's very difficult to reconcile, particularly for teams who rely on warehouse exports for reporting or compliance.
Amplitude's approach focuses on clear consent boundaries and accurate first-party data. It's better to know precisely what you measured and for whom than to fill gaps with estimates that are hard to validate or explain to auditors. If your organization uses Google services alongside Amplitude, you can configure Google Consent Mode for those tools independently. It doesn't affect how Amplitude processes data.
Privacy and Amplitude AI features
If your Amplitude account includes AI-powered features, such as Ask Amplitude, AI-generated insights, or other AI-assisted workflows, you may have questions about how your user data interacts with those features. For example, you may want to know whether third-party large language models (LLMs) process event data, and what data handling agreements apply.
Amplitude's Trust Page includes a dedicated AI FAQ that covers these topics, including questions about data sharing with AI providers. For more detailed technical information, the Amplitude AI privacy and security documentation covers third-party LLM usage and related data handling practices.
Review these resources and align with your privacy team before enabling AI-powered features, particularly if you operate under GDPR or handle sensitive personal data.
When to ask for help
If your setup includes regional legal complexity, multiple consent categories, sensitive personal data, or multiple downstream activation tools, involve your legal, privacy, and security teams early. It's much easier to design a privacy-conscious setup from the start than to retrofit one later.
In general, the safest approach is to keep the implementation simple, collect only what you need, and add complexity only when there's a clear business and legal case for doing so.
Was this helpful?
For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.