GDPR

When it comes to EU user personal information processing, the SolarEngine SDK will automatically collect certain fields such as GAID, IMEI, IMEI2, and Android ID. However, according to the EU privacy policy, if EU users disagree with their personal data collection, developers need to disable the sensitive data collection in their SDK.

     Please follow the procedures below to set up GDPR during SDK initialization:

1. In the code for SDK initialization, special settings are not required by default.

2. When users reject their sensitive information being collected, please disable related data collection function by adding isGDPRArea(true) in SDK initialization.

3. Ensure that users won't trigger any privacy-related events before obtaining their legally valid consent.

4. Clarify the EU users personal data processing policy and practice in your privacy policy.

     According to the GDPR, only when end users clearly reject their personal information being collected, you will need to set isGDPRArea(true) to stop SDK from collecting privacy-related fields.

    If your product is operated within the EU region and advertised on Google, please make sure to send this parameter, so that you will comply with Google's EU user consent policy.

Set GDPR During Initialization (Recommended)

   To comply with the upcoming Digital Markets Act (DMA), Google has updated their consent mode for traffic in European Economic Area (EEA). SolarEngine also took action to adapt to the new updates.

Here is a comparison:

Call example:

SEConfig seConfig = new SEConfig();
seConfig.isGDPRArea = false;
seConfig.adPersonalizationEnabled = false;
seConfig.adUserDataEnabled = true;
SolarEngine.Analytics.initSeSdk("appkey", seConfig);

Set GDPR Through API

public static void setGDPRArea(bool isGDPRArea)

Call example:

SolarEngine.Analytics.setGDPRArea(true);