Implement privacy controls
After you pick a consent method in the privacy and consent overview and configure it, these controls apply whichever method you chose. Work through them in the rollout order at the end of this page, then validate the whole setup before you launch.
Use a proxy when you want tighter control
A domain proxy is useful when you want more control over what reaches Amplitude. It lets you send tracking requests through your own domain and can help with filtering, blocking, debugging, audit logging, and anonymization before forwarding data to Amplitude.
This is especially helpful if you want to remove fields such as IP address, location, or userId before data leaves your environment. A proxy isn't the only way to do this. You can also exclude or suppress specific fields directly in the SDK at initialization time by passing options in amplitude.init(...), which is easier when you only need to strip a small number of fields client-side.
A proxy is the better choice when you need centralized control, server-side enforcement, audit logging, or want the filtering to happen outside the client entirely, so that sensitive fields never leave your infrastructure at all. If you build a proxy, involve your developer operations and information security teams early.
Add governance controls
Whichever consent method you choose, these four controls apply. Each has its own reference page.
Keep noisy traffic out of your data
Privacy settings work better when your data is also clean.
- Bot traffic: if you track public web traffic, bots can distort your metrics. Create a block filter so Amplitude never ingests the data. Refer to Block bot web traffic for the procedure and the User-Agent list Amplitude matches against.
- Internal traffic: if your team tests in production, block internal IP addresses so employee traffic doesn't inflate your metrics. Keep a separate development project for testing and use production only for final validation.
Restrict who can see sensitive data
Collecting data responsibly is only half the job. Control who can see it.
Data Access Control (DAC) lets you classify properties as PII, revenue, or sensitive, then grant or deny access to those classifications by group. With DAC enabled, restricted users can't view charts, cohorts, dashboards, notebooks, or user sessions that contain restricted data; Amplitude hides classified properties from Event Stream and User or Account Lookup; and restricted values appear as [DAC Restricted].
To set it up, ask Amplitude Support to enable DAC for your organization, classify the properties you want to protect in Amplitude Data, then open Settings > Organization settings > Groups and configure access on the Data Access tab.
For broader role control beyond sensitive properties, use RBAC.
Set a retention period
If you don't need to keep event data forever, set a retention period. Time to Live (TTL) lets you define event retention at the organization level and override it per project.
Be careful here. TTL causes irreversible data loss, and existing charts zero out for periods outside the retention window. Set a shorter TTL for higher-risk datasets and a longer one only where there's a clear business need.
Prepare for deletion requests
If a user asks you to delete their data, your process needs to cover both Amplitude and any upstream systems. The User Privacy API lets you programmatically submit deletion requests for known Amplitude IDs or User IDs. Deletions are project-based by default; set delete_from_org to true to delete the user across your organization.
Two things matter in practice: deleting a user doesn't block future tracking for that user, and if the same user data still exists in your warehouse or another ingestion source, Amplitude may ingest it again on the next sync.
So your deletion workflow should be:
- Receive the request.
- Identify the correct user IDs.
- Delete the user in Amplitude.
- Delete the same user from the warehouse or any synced source.
- Log completion for audit purposes.
Validate your setup before launch
After your setup is live, test it with real scenarios. At minimum, test a visitor who hasn't consented, a visitor who grants consent, a signed-in user, a user who logs out, and a user whose data is deleted.
In Amplitude, use User Lookup to inspect the event stream for a specific user and confirm what data Amplitude actually ingested. For each test case, check:
- Whether the SDK initialized.
- Whether Amplitude cookies or storage were created.
- Whether Amplitude received the expected events.
- Whether the expected identifiers were present.
- Whether restricted data is visible only to the right users.
This step is worth the time. Most privacy issues come from small implementation gaps, not from the policy itself.
Recommended rollout order
- Choose the consent method.
- Decide what data is allowed.
- Configure SDK initialization and storage.
- Connect your CMP if needed.
- Add filters for bots and internal traffic.
- Classify and restrict sensitive properties.
- Set data retention.
- Document your deletion workflow.
- Validate everything with end-to-end tests.
That sequence keeps the work manageable and makes it much easier to explain your setup to internal stakeholders and external auditors.
Before you consider the setup complete, review Additional privacy considerations for Session Replay, access requests, data residency, post-launch caveats, and Amplitude's position on modeled data.
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.