Privacy features
Send erasure request
The EU’s General Data Protection Regulation (GDPR) and similar privacy laws worldwide (CCPA, LGPD, etc.) grant data subjects comprehensive rights when it comes to the processing of their personal data. These rights include, among others, the right to erasure (see Art. 17 GDPR). As a data processor, Adjust is obliged to support you (the data controller) in the processing of such requests from your (app) users.
You can send the user's erasure request to Adjust by calling the gdprForgetMe
method. Once Adjust has been notified:
- We will permanently delete all of the user’s historical personal data from our internal system and database.
- We will no longer receive data from this user/device via the Adjust SDK.
Third-party sharing for specific users
You can use the Adjust SDK to record when a user changes their third-party sharing settings.
Disable third-party sharing for specific users
Some users may want to opt-out of sharing their data with third-parties. To communicate this to Adjust, call the Adjust.trackThirdPartySharing
method with a false
value.
When the Adjust backend receives this information it will stop sharing the user's data with third-parties. The Adjust SDK will continue to work as expected.
Enable or re-enable third-party sharing for specific users
If a user enables or re-enables sharing with third-parties, you need to relay this to the backend. Call the Adjust.trackThirdPartySharing
method with a true
value to do this.
When the backend gets this information it will update the user's settings. The Adjust SDK will continue to work as expected.
Send granular information to the Adjust backend
You can attach granular information when a user updates their third-party sharing preferences. You can use this information to communicate more detail about a user's decision.
Set third-party sharing for specific partners
You can give users the option to customize their third-party sharing settings on a per-partner basis. There are three levels of user consent: Yes, Analytics, and No. See Partner-specific settings for more information.
To communicate the user’s consent level to Adjust, call the addPartnerSharingSetting
method. Pass the following arguments:
Argument | Data type | Description |
---|---|---|
partner name or partner ID | String | The name or ID of the partner. See the list of available partners and their information below. |
key | String | The metric to share with the partner. |
value | Boolean | The user's consent decision. |
Available partners
Adjust works with hundreds of different partners that you can define your third-party sharing preferences for. Download the file below to view the complete list of partners and their corresponding Partner name and ID.
For SAN partners: you can use either the Partner display name or the Partner ID in your requests.
For non-SAN partners you should only use the Partner ID in your requests.
Examples
Manage Facebook Limited Data Use
Facebook provides a feature called Limited Data Use (LDU) to comply with the California Consumer Privacy Act (CCPA). This feature enables you to notify Facebook when a California-based user is opted out of the sale of data. You can also use it if you want to opt all users out by default.
You can update the Facebook LDU status by passing arguments to the AdjustThirdPartySharing.addGranularOption
method.
0
value in either the data_processing_options_country
or data_processing_options_state
field, the Adjust SDK will pass both fields back as 0
.
Provide consent data to Google (Digital Markets Act compliance)
Added in v4.26.0.
To comply with the EU's Digital Markets Act (DMA), Google Ads and the Google Marketing Platform require explicit consent to receive Adjust’s attribution requests to their APIs. To communicate this consent, you need to add the following granular options to your Adjust third party sharing object for the partner google_dma
.
Passing these options is required if you use Google Ads or Google Marketing Platform and have users located in the European Economic Area (EEA).
Key | Value | Description |
---|---|---|
eea | 1 = users are in the EEA and the DMA applies 0 = users are not in the EEA and the DMA does not apply | The eea parameter informs Google whether users are located in the EEA and thus whether the European regulations, including the DMA, apply to this user and conversion. The parameter type is boolean. |
ad_personalization | 1 = user consented 0 = user did not consent |
|
ad_user_data | 1 = user consented 0 = user did not consent | The ad_user_data parameter informs Google whether users granted consent to personal data being shared for measurement purposes or not. The consent applies to all the Core Platform Services (CPS) advertisers have specified in their Google Ads and Google Marketing Platform UI. |
npa | 1 = user did not consent 0 = user consented |
|
Data residency
The data residency feature allows you to choose the country in which Adjust will store your data. This is useful if you are operating in a country with strict privacy requirements. When you set up data residency, Adjust will store your data in a data center located in the region your have chosen.
To set your country of data residency, call the AdjustConfig.setUrlStrategy
method on your config object. For example, you can call the following to set your data residency region to the EU:
Consent measurement for specific users
If you are using Data Privacy settings in your Adjust dashboard, you need to set up the Adjust SDK to work with them. This includes settings such as consent expiry period and user data retention period. To toggle this feature, call the Adjust.trackMeasurementConsent
method. When enabled, the SDK will communicate the data privacy settings to the backend.
Only for those users where Adjust.trackMeasurementConsent
method was called, the Adjust backend will then apply your data privacy rules to the user. The Adjust SDK will continue to work as expected.