Minimize data without a consent prompt
このページはまだあなたの言語に翻訳されていません。 現在取り組んでいますので、後でもう一度確認してください。
This is one of three consent methods described in the privacy and consent overview. Choose it when your legal team decides consent isn't required for your analytics setup in a given region or use case. You can still make that setup more privacy-friendly by limiting identifiers, shortening storage, and minimizing what you send.
This page shows you how to implement a decision your team has already made; it doesn't replace legal advice.
Set it up in Amplitude
Choose the storage mode that matches your policy:
identityStorage | Behavior |
|---|---|
cookie | Standard browser persistence. |
localStorage | Browser storage without cookies. Limited by subdomain, so a user on one subdomain doesn't automatically carry the same stored identity to another. |
none | No persistent identity. Amplitude generates a new device_id on every page load or app start, because there's no stored identity to reuse between loads. |
With identityStorage: "none", Amplitude generates a new device_id on each page load or app start, not on each individual event. All events fired within the same page load share the same device_id. As soon as the user closes the tab or restarts the app, the next page load generates a completely new device_id with no link to the previous one. You can't reconstruct cross-session user journeys, which is the intended behavior for strict anonymization.
Minimize data by default
Even when consent isn't required, data minimization is still a good default. Collect what you need, not what happens to be available.
To remove fields such as IP address, location, or userId before data leaves your environment, configure the Amplitude SDK at initialization time to suppress them, or route traffic through a domain proxy. Refer to Use a proxy when you want tighter control for the tradeoff between the two.
What to do outside Amplitude
Make sure your privacy notice matches what you're actually doing. If you're not asking for consent, your policy should still explain what you collect, why, and how users can opt out if that applies to your model.
これは役に立ちましたか?
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.