The Adjust SDK contains features that you can use to handle user privacy in your app.
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)(1). 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:
- Adjust will permanently delete all of the user’s historical personal data from its internal systems and database.
- Adjust will no longer receive data from this user/device via the Adjust SDK.(2)
Third-party sharing for specific users
You can use the Adjust SDK to record when a user changes their third-party sharing settings. Third party sharing settings are configured using the AdjustThirdPartySharing
class.
Instantiate an AdjustThirdPartySharing object
To enable or disable third party sharing with the Adjust SDK, you need to instantiate an AdjustThirdPartySharing
object. This object contains variables that control how third party sharing is handled by Adjust.
To instantiate a third party sharing object, create a new AdjustThirdPartySharing
instance and pass the following parameters:
isEnabled
(Boolean
): Whether third party sharing is enabled. Passtrue
to enable third party sharing orfalse
to disable third party sharing
Once you’ve instantiated your AdjustThirdPartySharing
object, you can send the information to Adjust by calling the Adjust.trackThirdPartySharing
method with your AdjustThirdPartySharing
instance as an argument.
Send granular information
You can attach granular information when a user updates their third-party sharing preferences. Use this information to communicate more detail about a user’s decision. To do this, call the addGranularOption
method with the following parameters:
partnerName
(String
): The name of the partner for whom the granular option applies.key
(String
): The option key.value
(String
): The option value.
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 the following arguments to the addGranularOption
method:
Parameter | Description |
---|---|
partner_name | Use facebook to toggle LDU. |
data_processing_options_country | The country in which the user is located.
|
data_processing_options_state | Notifies Facebook in which state the user is located.
|
Provide consent data to Google (Digital Markets Act compliance)
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 third party sharing instance for the partner google_dma
.
Key | Value | Description |
---|---|---|
eea | 1 (positive) | 0 (negative) | Informs Adjust whether users installing the app are within the European Economic Area. This includes EU member states, Switzerland, Norway, Iceland and Slovenia. |
ad_personalization | 1 (positive) | 0 (negative) | Informs Adjust whether users consented with being served personalized ads via Google Ads and/or Google Marketing Platform. This parameter also informs the npa parameter reserved for Google Marketing Platform. |
ad_user_data | 1 (positive) | 0 (negative) | Informs Adjust whether users consented with their advertiser ID being leveraged for attribution purposes. |
Update partner sharing settings
By default, Adjust shares all metrics with any partners you’ve configured in your app settings. You can use the Adjust SDK to update your third party sharing settings on a per-partner basis. To do this, call the addPartnerSharingSetting
method with the following arguments:
Argument | Data type | Description |
---|---|---|
partnerName | String | The name of the partner. Download the full list of available partners |
key | String | The metric to share with the partner |
value | Boolean | The user’s decision |
You can use the key
to specify which metrics you want to disable or re-enable. If you want to enable/disable sharing all metrics, you can use the all
key. The full list of available metrics is available below:
ad_revenue
all
attribution
update
att_update
cost_update
event
install
reattribution
reattribution_reinstall
reinstall
rejected_install
rejected_reattribution
sdk_click
sdk_info
session
subscription
uninstall
When you set a false
value against a metric for a partner, Adjust stops sharing the metric with the partner.
Examples
If you want to stop sharing all metrics with a specific partner, pass the all
key with a false
value.
To re-enable sharing, pass the all
key with a true
value.
You can stop or start sharing specific metrics by calling the addPartnerSharingSetting
method multiple times with different keys. For example, if you only want to share event information with a partner, you can pass:
all
with afalse
value to disable sharing all information.event
with atrue
value to enable event sharing
Set URL strategy
The URL strategy feature allows you to set either:
- The country in which Adjust stores your data (data residency).
- The endpoint to which the Adjust SDK sends traffic (URL strategy).
This is useful if you’re operating in a country with strict privacy requirements. When you set your URL strategy, Adjust stores data in the selected data residency region or sends traffic to the chosen domain.
To set your country of data residency, call the AdjustConfig.setUrlStrategy
method following parameters:
domains
(List<String>
): The country or countries of data residence, or the endpoints to which you want to send SDK traffic.useSubdomains
(boolean
): Whether the source should prefix a subdomain.isDataResidency
(boolean
): Whether the domain should be used for data residency.
See the table below for a list of mappings.
URL strategy | Main and fallback domain | Use sub domains | Is Data Residency |
---|---|---|---|
EU data residency | "eu.adjust.com" | true | true |
Turkish data residency | "tr.adjust.com" | true | true |
US data residency | "us.adjust.com" | true | true |
China global URL strategy | "adjust.world" , "adjust.com" | true | false |
China URL strategy | "adjust.cn" , "adjust.com" | true | false |
China only URL strategy | "adjust.cn" | true | false |
India URL strategy | "adjust.net.in" , "adjust.com" | true | false |
Examples
Consent measurement for specific users
If you’re 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 trackMeasurementConsent
method with the following argument:
consentMeasurement
(Boolean
): Whether consent measurement is enabled (true
) or not (false
).
When enabled, the SDK communicates the data privacy settings to Adjust’s servers. Adjust’s servers then applies your data privacy rules to the user. The Adjust SDK continues to work as expected.
COPPA compliance
If you need your app to be compliant with the Children’s Online Privacy Protection Act (COPPA), call the AdjustConfig.enableCoppaCompliance
method before SDK intialization. This method performs the following actions:
- Disables third-party sharing.
- Prevents the SDK from reading device and advertising IDs (for example:
gps_adid
andandroid_id
).
Play Store Kids Apps
If your app targets users under the age of 13, and the install region isn’t the USA, you need to mark it as a Kids App. This prevents the SDK from reading device and advertising IDs (for example: gps_adid
and android_id
).
To mark your app as a Play Store Kids App, call the enablePlayStoreKidsCompliance
method on your AdjustConfig
instance before SDK initialization.