Do I need to disclose Adjust in my privacy policy?

Yes. Adjust processes personal data including device identifiers and behavioral information, making it a required disclosure under GDPR and similar privacy laws. You must clearly inform users that Adjust is used for attribution and fraud prevention, explain what data is collected, and reference Adjust GmbH as the data processor.

What specific data does Adjust collect?

Adjust collects install attribution data, device identifiers (IDFA on iOS and Google Advertising ID on Android), click and impression tracking data, in-app revenue events, and device/network metadata. On iOS, IDFA collection requires explicit user consent via Apple's App Tracking Transparency framework before data is sent to Adjust.

Does Adjust require a cookie consent banner?

Adjust does not use cookies. However, because it processes device identifiers and personal data, you must obtain legal basis for processing—typically user consent on iOS (via ATT) and legitimate interest or consent on Android. A general privacy notice is required; a separate cookie banner is not needed for Adjust specifically.

Who is the data processor and where is data transferred?

Adjust GmbH, based in Germany (EU), is the data processor. Data is transferred to and processed within the EU under GDPR safeguards. Adjust employs probabilistic matching and fraud prevention measures. You should ensure a Data Processing Agreement is in place with Adjust before processing user data.

Deep Linking & Attribution

Privacy policy clauses for Adjust

Adjust is a mobile measurement and attribution platform that tracks app installations, user events, and in-app purchases to measure marketing campaign performance and detect fraudulent activity. Websites and app developers use Adjust to understand which marketing channels drive valuable user acquisitions and to prevent ad fraud.

Scan my site free →Copy sample clause ↓

Free scan · No signup · Results in 60 seconds

What data Adjust collects

Your privacy policy must disclose each of the following data types when you use Adjust.

Install and event attribution data

Device identifiers (IDFA/GAID)

Click and impression tracking

In-app revenue events

Device and network metadata

When does Adjust trigger privacy obligations?

Installation triggers immediate data flows

The moment you integrate Adjust's SDK into your mobile app, it begins collecting and transmitting device identifiers (IDFA on iOS, GAID on Android), click/impression data, install attribution, in-app events, and device metadata to Adjust's servers in Germany. This is not deferred—data flows start on first app launch.

Which regulations apply immediately

GDPR (if your users are in the EU/EEA):

Privacy policy clauses for Adjust

What data Adjust collects

When does Adjust trigger privacy obligations?

Installation triggers immediate data flows

Which regulations apply immediately

First concrete step

Where data goes

Common compliance pitfalls

Pitfall 1: Missing or unsigned DPA with Adjust

Pitfall 2: Conflating fraud prevention consent with tracking consent

Pitfall 3: Failing to update privacy policy with specific data categories

Legal note

Sample privacy policy clause

What regulators look for

What auditors flag first

Frequently asked questions

Do I need to disclose Adjust in my privacy policy?

What specific data does Adjust collect?

Does Adjust require a cookie consent banner?

Who is the data processor and where is data transferred?

Don't ship without Bandit.