Privacy and consent
You can set up Amplitude in a privacy-friendly way. The right setup depends on your policy, your region, and how much data you want to collect before consent. First choose your consent model, then configure storage and access in Amplitude to match it.
Before you choose a method, align with your legal and privacy teams on what's allowed in your case. These pages show you practical ways to implement those choices in Amplitude. They don't replace legal advice.
How this section is organized
There's no single setup that fits every company. Some organizations need strict opt-in before analytics starts. Others may use a more limited measurement-only approach in some regions. The right choice depends on your product, your data, and the rules that apply where you operate.
Privacy and consent work splits into four stages:
- Choose the consent method that fits your policy. This page covers that decision.
- Configure Amplitude to match that method. Each method has its own page.
- Add the governance, retention, and deletion controls you need, then validate before launch. Refer to Implement privacy controls.
- Review the topics that apply to your implementation in Additional privacy considerations.
These pages cover common implementation patterns and the controls most teams need first. For complex use cases, use them as a starting point and identify the decisions to make with your legal, privacy, and security teams.
Before you start
Answer these three questions before you configure anything:
- Do you need consent before analytics starts?
- Do you want to collect no data, or limited anonymous measurement, before consent?
- Which fields should reach Amplitude at all?
You're responsible for obtaining any required consent, making the right disclosures, and deciding how to classify Amplitude cookies in your policy.
A practical starting point is to write down:
- Which events you want to collect.
- Which identifiers you want to store.
- Which properties are sensitive.
- What should happen when a user declines consent.
- What should happen when a user grants consent after an initial decline.
That one-page decision document makes the implementation much easier to review and test.
Choose the setup that fits your policy
Pick one of these three methods. They're mutually exclusive starting points, though you can tighten any of them with the governance controls.
| Method | Choose it when | What you configure |
|---|---|---|
| Collect only with consent | Your policy requires consent before analytics begins. | Gate amplitude.init() behind your CMP's consent outcome. |
| Collect limited anonymous measurement | Your legal team confirms limited audience measurement is allowed without consent. | Reduce identityStorage, keep the event set small, and separate the two projects. |
| Minimize data without a consent prompt | Your legal team decides consent isn't required for your setup. | Choose a storage mode, limit identifiers, and minimize what you send. |
If you want the safest and simplest default, start with the first method: initialize Amplitude only after consent, keep your event schema tight, and add access controls and retention rules from day one.
After you choose a method
Configuring the consent method is only the first part of the setup. Whichever method you pick, you still need to filter noisy traffic, restrict who can see sensitive data, set a retention period, and prepare for deletion requests, then test the whole thing end to end.
Refer to Implement privacy controls for those controls, the recommended rollout order, and the pre-launch validation checklist.
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.