{"data":{"id":"98805","string_id":"CaajuY","status":"1","parent_id":"60654","slug":"CaajuY","order":"3","name":"Policy Compliance","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"xinru","published_time":"1716200898","add_time":"1716200885","update_time":"1768894943","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"parent_name":"Data Access","parent_type":"1","parent_slug":"SwPOLu","child":[{"id":"98802","string_id":"KwN9BT","status":"1","parent_id":"98805","slug":"GDPR","order":"1","name":"GDPR","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"xinru","published_time":"1716271040","add_time":"1716200427","update_time":"1768894943","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"98802","content":"

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.<\/p>

Please follow the procedures below to set up GDPR during SDK initialization:<\/p>

1. When users reject their sensitive information being collected, please disable related data collection function by adding isGDPRArea(true)<\/span> in SDK initialization.<\/p>

2. Ensure that users won't trigger any privacy-related events before obtaining their legally valid consent.<\/p>

3. Clarify the EU users personal data processing policy and practice in your privacy policy.<\/p>

Note:<\/strong><\/span><\/p>

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

1. Set GDPR during initialization (recommended)<\/h1>
Function<\/strong><\/p>
SolarEngineConfig config = new SolarEngineConfig.Builder()\n .isGDPRArea(true) \/\/Whether locate in GDPR region (default false)\n .adPersonalizationEnabled(true)\/\/Whether users allow Google to user their data for ad personalization (default not reported if not set by developer)\n .adUserDataEnabled(true)\/\/Whether users allow their data to be shared with Google (default not reported if not set by developer)\n .build();<\/code><\/pre>Sample Code<\/strong><\/p> import com.reyun.solar.engine.SolarEngineConfig;\n\nSolarEngineConfig config = new SolarEngineConfig.Builder()\n.isGDPRArea(true)\n.adPersonalizationEnabled(true)\n.builder.adUserDataEnabled(true)\n.build();<\/code><\/pre>2. Set GDPR through API<\/h1>Function<\/strong><\/p> public void setGDPRArea(boolean isGDPRArea);<\/code><\/pre>Sample Code<\/strong><\/p> import com.reyun.solar.engine.SolarEngineManager;\n\nSolarEngineManager.getInstance().setGDPRArea(true);<\/code><\/pre> <\/p>","pure_content":"\u00a0 \u00a0 \u00a0 \u00a0When 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. \u00a0 \u00a0 \u00a0 \u00a0Please follow the procedures below to set up GDPR during SDK initialization:1. When users reject their sensitive information being collected, please disable related data collection function by adding isGDPRArea(true) in SDK initialization.2. Ensure that users won't trigger any privacy-related events before obtaining their legally valid consent.3. Clarify the EU users personal data processing policy and practice in your privacy policy.Note: \u00a0 \u00a0 \u00a0 \u00a0According 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.1. Set GDPR during initialization (recommended)FunctionSolarEngineConfig config = new SolarEngineConfig.Builder()\n .isGDPRArea(true) \/\/Whether locate in GDPR region (default false)\n .adPersonalizationEnabled(true)\/\/Whether users allow Google to user their data for ad personalization (default not reported if not set by developer)\n .adUserDataEnabled(true)\/\/Whether users allow their data to be shared with Google (default not reported if not set by developer)\n .build();Sample Codeimport com.reyun.solar.engine.SolarEngineConfig;\n\nSolarEngineConfig config = new SolarEngineConfig.Builder()\n.isGDPRArea(true)\n.adPersonalizationEnabled(true)\n.builder.adUserDataEnabled(true)\n.build();2. Set GDPR through APIFunctionpublic void setGDPRArea(boolean isGDPRArea);Sample Codeimport com.reyun.solar.engine.SolarEngineManager;\n\nSolarEngineManager.getInstance().setGDPRArea(true);","is_draft":"0","editor_type":"1","file_path":"","add_time":"1716200427","update_time":"1768894943"},"pure_content":"\u00a0 \u00a0 \u00a0 \u00a0When 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"},{"id":"98806","string_id":"LUAd3X","status":"1","parent_id":"98805","slug":"COPPA","order":"0","name":"COPPA","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"xinru","published_time":"1716259573","add_time":"1716200916","update_time":"1768894943","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"98806","content":" If your app is required to comply with Children's Online Privacy Protection Act (\"COPPA\"), or when your app is targeting kids under 13 years old, please mark it as \"Kids App\" category following the guide in Quick Integration-Step 5<\/em><\/a>.<\/p>","pure_content":"\u00a0 \u00a0 \u00a0 \u00a0If your app is required to comply with Children's Online Privacy Protection Act (\"COPPA\"), \u00a0or when your app is targeting kids under 13 years old, please mark it as \"Kids App\" category following the guide in Quick Integration-Step 5.","is_draft":"0","editor_type":"1","file_path":"","add_time":"1716200916","update_time":"1768894943"},"pure_content":"\u00a0 \u00a0 \u00a0 \u00a0If your app is required to comply with Children's Online Privacy Protection Act (\"COPPA\"), \u00a0or when your app is targeting kids under 13 years old, please mark it as \"Kids App\" category followi"},{"id":"99073","string_id":"HdHeer","status":"1","parent_id":"98805","slug":"Compliance-Guidelines","order":"0","name":"Compliance Guidelines","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"xinru","published_time":"1716270984","add_time":"1716270908","update_time":"1768894943","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"99073","content":" On November 1, 2021, the \"Personal Information Protection Law of the People's Republic of China\" officially came into effect. Since then, various government departments and agencies have successively issued regulations and requirements related to the necessary scope of personal information for common types of mobile internet applications, the special rectification campaign against infringements of user rights in mobile apps, and the enhancement of mobile internet application service capabilities, among others. These regulatory requirements aim to protect personal information rights and have achieved significant results. In order to assist developers and operators (referred to as \"you\") using the SolarEngine SDK in better protecting personal information on mobile terminals, and to avoid violations of relevant laws, regulations, policies, and standards due to involvement in third-party business practices, this compliance guide has been compiled for your reference.<\/p> Please note that the \"compliance requirements,\" \"precautions,\" \"methods,\" and other contents in this compliance guide are drafted based on our understanding of relevant national laws, regulations, policies, and standards. They are provided as reference content and should not be construed as authoritative interpretations, legal opinions, or legal advice on any laws, regulations, policies, or standards. They also do not constitute any commitments or guarantees from the SolarEngine to external parties.<\/p> 1. Personal Information Collected<\/h1>a. Collected Data:<\/strong><\/p> \u2022 Unique device identification code (IMEI\/Android ID\/GAID\/OAID)<\/p> \u2022 Event occurrence time\/login account\/IMEI2\/UA\/device language\/device time zone\/manufacturer\/operating system version\/screen height\/screen width\/device model\/device name\/device model identification\/network status\/application version\/application build number\/package name\/application name\/channel name\/browser\/browser version\/title of the current page\/address of the current page\/title of the previous page\/address of the previous page\/unique device ID\/current time of the device\/ Device boot time\/Identification of whether ad tracking is turned on\/ADServiceToken\/Device screen density\/Installed software package referrer URL\/Referrer URL click client time\/Client time when the application is installed\/Referrer URL click server time\/ The server time when the application is installed\/the application version when it is installed for the first time\/whether the application installation-free experience was released in the past 7 days, etc.<\/p> b. Purpose of Data Collection:<\/strong><\/p> \u2022 To gather device information for generating a de-identified unique identifier for the end-user device, ensuring the provision of SDK services.<\/p> c. Timing of Data Collection:<\/strong><\/p> \u2022 Collected when you call the SolarEngine SDK initialization method.<\/p> 2. Permissions Required<\/h1>Permissions<\/th> Trigger Timing<\/th> Purpose<\/th><\/tr> INTERNET<\/td> When event triggered<\/td> To allow the application to access the internet and send statistical data for providing analytics services.<\/td><\/tr> ACCESS_NETWORK_STATE<\/td> When event triggered<\/td> To detect the current network connection status.<\/td><\/tr> ACCESS_WIFI_STATE<\/td> When event triggered<\/td> To retrieve the Wi-Fi state.<\/td><\/tr> READ_PHONE_STATE (optional)<\/td> When IMEI collected<\/td> To retrieve the IMEI of the user's device. The IMEI is used for unique identification of users.<\/td><\/tr><\/tbody><\/table> <\/p> 3. Obtain User Consent<\/h1> The following methods are for reference only. Please consult your legal advisor or regulatory authorities for specific compliance solutions:<\/p> (1) Privacy Popup<\/strong><\/p> a. When the app is first launched, it should prompt end users to read the privacy policy through a popup or other obvious means.<\/p> b. The privacy popup should include links to the user agreement and privacy policy.<\/p> c. The privacy popup should have a button for declining consent. End users should have the option to agree to or reject the privacy policy. It should not be pre-selected by default or obtained through deceptive or misleading means.<\/p> (2) Privacy Policy<\/strong><\/p> a. The app should have a separate privacy policy that is documented independently, rather than being part of the user agreement or any other document.<\/p> b. The accessibility of the privacy policy should be ensured. Once end users enter the main functional interface of the app, they should be able to access the privacy policy with no more than four clicks or swipes.<\/p> c. The privacy policy should include a list of SDKs, including the SolarEngine SDK, providing information such as the name and contact details of each SDK provider, the purpose and method of processing personal information, the types of personal information processed, and the retention period. The privacy policy should also display the privacy policy link of the SDK provider.<\/p> d. A method should be provided for users to withdraw their consent, and the SolarEngine should be promptly notified when a user withdraws their consent.<\/p> Example: disclosing SolarEngine SDK information to users<\/strong> <\/p> Category<\/th> Description<\/th><\/tr> SDK name<\/td> SolarEngine Android SDK<\/td><\/tr> Developer name<\/td> Huiliang Cloud (Beijing) Technology Co., Ltd.<\/td><\/tr> Personal information collected \uff08Please adjust the content according to your actual situation. The specific fields actually transmitted should prevail.\uff09<\/td> IMEI\/Android ID\/GAID\/Event occurrence time\/Login account\/IMEI2\/OAID\/UA\/Device language\/Device time zone\/Manufacturer\/Operating system version\/Screen height\/Screen width\/Device model\/Device name\/Device model identifier\/Network status\/App version\/App version number\/Package name\/App name\/Channel name\/Browser\/Browser version\/Current page title\/Current page URL\/Previous page title\/Previous page URL\/Device unique ID\/Device current time\/Device boot time\/ATT status identifier\/ADServiceToken\/Device screen density\/Installed package referrer URL\/Referrer URL click client time\/App install client time\/Referrer URL click server time\/App install server time\/First install app version\/Whether the app instant experience was released within the past 7 days, etc.<\/td><\/tr> Collection purpose<\/td> To understand the performance of mobile applications on different terminal devices, usage platforms or application distribution channels; To optimize advertising strategies and detect anti-fraud activities; To provide \"user tag\" services & A\/B testing services; To conduct device-level user group analysis, serving Internet advertising targeted delivery and user ROI analysis services.<\/td><\/tr> Privacy Policy Link<\/td> https:\/\/www.solar-engine.com\/privacyPolicyEN.html<\/a><\/td><\/tr><\/tbody><\/table>4. SDK Initialization Timing<\/h1> You should ensure that the user has agreed to the Privacy Policy before calling the SolarEngine SDK for initialization. The initialization steps during the first cold start after installation are as follows:<\/p> (1) The pre-initialization method does not collect device information or report data to the SolarEngine background;<\/p> (2) Ensure that the formal initialization method is called only after the user has agreed to the Privacy Policy during the app's first cold start. At this point, the SDK will start collecting device information and reporting data. Conversely, if the user does not agree to the Privacy Policy, the formal initialization method should not be called.<\/p> For detailed initialization configuration instructions, please refer to Initialize the SDK<\/a> on this page.<\/p>","pure_content":"\u00a0 \u00a0 \u00a0 \u00a0On November 1, 2021, the \"Personal Information Protection Law of the People's Republic of China\" officially came into effect. Since then, various government departments and agencies have successively issued regulations and requirements related to the necessary scope of personal information for common types of mobile internet applications, the special rectification campaign against infringements of user rights in mobile apps, and the enhancement of mobile internet application service capabilities, among others. These regulatory requirements aim to protect personal information rights and have achieved significant results. In order to assist developers and operators (referred to as \"you\") using the SolarEngine SDK in better protecting personal information on mobile terminals, and to avoid violations of relevant laws, regulations, policies, and standards due to involvement in third-party business practices, this compliance guide has been compiled for your reference. \u00a0 \u00a0 \u00a0 \u00a0Please note that the \"compliance requirements,\" \"precautions,\" \"methods,\" and other contents in this compliance guide are drafted based on our understanding of relevant national laws, regulations, policies, and standards. They are provided as reference content and should not be construed as authoritative interpretations, legal opinions, or legal advice on any laws, regulations, policies, or standards. They also do not constitute any commitments or guarantees from the SolarEngine to external parties.1. Personal Information Collecteda. Collected Data: \u2022 Unique device identification code (IMEI\/Android ID\/GAID\/OAID) \u2022 Event occurrence time\/login account\/IMEI2\/UA\/device language\/device time zone\/manufacturer\/operating system version\/screen height\/screen width\/device model\/device name\/device model identification\/network status\/application version\/application build number\/package name\/application name\/channel name\/browser\/browser version\/title of the current page\/address of the current page\/title of the previous page\/address of the previous page\/unique device ID\/current time of the device\/ Device boot time\/Identification of whether ad tracking is turned on\/ADServiceToken\/Device screen density\/Installed software package referrer URL\/Referrer URL click client time\/Client time when the application is installed\/Referrer URL click server time\/ The server time when the application is installed\/the application version when it is installed for the first time\/whether the application installation-free experience was released in the past 7 days, etc.b. Purpose of Data Collection: \u2022 To gather device information for generating a de-identified unique identifier for the end-user device, ensuring the provision of SDK services.c. Timing of Data Collection: \u2022 Collected when you call the SolarEngine SDK initialization method.2. Permissions Required Permissions Trigger Timing Purpose INTERNET When event triggered To allow the application to access the internet and send statistical data for providing analytics services. ACCESS_NETWORK_STATE When event triggered To detect the current network connection status. ACCESS_WIFI_STATE When event triggered To retrieve the Wi-Fi state. READ_PHONE_STATE (optional) When IMEI collected To retrieve the IMEI of the user's device. The IMEI is used for unique identification of users.3. Obtain User Consent \u00a0 \u00a0 \u00a0 \u00a0The following methods are for reference only. Please consult your legal advisor or regulatory authorities for specific compliance solutions:(1) Privacy Popup a. When the app is first launched, it should prompt end users to read the privacy policy through a popup or other obvious means. b. The privacy popup should include links to the user agreement and privacy policy. c. The privacy popup should have a button for declining consent. End users should have the option to agree to or reject the privacy policy. It should not be pre-selected by default or obtained through deceptive or misleading means.(2) Privacy Policy a. The app should have a separate privacy policy that is documented independently, rather than being part of the user agreement or any other document. b. The accessibility of the privacy policy should be ensured. Once end users enter the main functional interface of the app, they should be able to access the privacy policy with no more than four clicks or swipes. c. The privacy policy should include a list of SDKs, including the SolarEngine SDK, providing information such as the name and contact details of each SDK provider, the purpose and method of processing personal information, the types of personal information processed, and the retention period. The privacy policy should also display the privacy policy link of the SDK provider. d. A method should be provided for users to withdraw their consent, and the SolarEngine should be promptly notified when a user withdraws their consent.Example: disclosing SolarEngine SDK information to users Category Description SDK name SolarEngine Android SDK Developer name Huiliang Cloud (Beijing) Technology Co., Ltd. Personal information collected \uff08Please adjust the content according to your actual situation. The specific fields actually transmitted should prevail.\uff09 IMEI\/Android ID\/GAID\/Event occurrence time\/Login account\/IMEI2\/OAID\/UA\/Device language\/Device time zone\/Manufacturer\/Operating system version\/Screen height\/Screen width\/Device model\/Device name\/Device model identifier\/Network status\/App version\/App version number\/Package name\/App name\/Channel name\/Browser\/Browser version\/Current page title\/Current page URL\/Previous page title\/Previous page URL\/Device unique ID\/Device current time\/Device boot time\/ATT status identifier\/ADServiceToken\/Device screen density\/Installed package referrer URL\/Referrer URL click client time\/App install client time\/Referrer URL click server time\/App install server time\/First install app version\/Whether the app instant experience was released within the past 7 days, etc. Collection purpose To understand the performance of mobile applications on different terminal devices, usage platforms or application distribution channels; To optimize advertising strategies and detect anti-fraud activities; To provide \"user tag\" services & A\/B testing services; To conduct device-level user group analysis, serving Internet advertising targeted delivery and user ROI analysis services. Privacy Policy Link https:\/\/www.solar-engine.com\/privacyPolicyEN.html4. SDK Initialization Timing \u00a0 \u00a0 \u00a0 \u00a0You should ensure that the user has agreed to the Privacy Policy before calling the SolarEngine SDK for initialization. The initialization steps during the first cold start after installation are as follows: (1) The pre-initialization method does not collect device information or report data to the SolarEngine background; (2) Ensure that the formal initialization method is called only after the user has agreed to the Privacy Policy during the app's first cold start. At this point, the SDK will start collecting device information and reporting data. Conversely, if the user does not agree to the Privacy Policy, the formal initialization method should not be called. \u00a0 \u00a0 \u00a0 \u00a0For detailed initialization configuration instructions, please refer to Initialize the SDK on this page.","is_draft":"0","editor_type":"1","file_path":"","add_time":"1716270908","update_time":"1768894943"},"pure_content":"\u00a0 \u00a0 \u00a0 \u00a0On November 1, 2021, the \"Personal Information Protection Law of the People's Republic of China\" officially came into effect. Since then, various government departments and agencies have succe"}],"content":{"icon":"","desc":"","content_id":"98805","add_time":"1716200885","update_time":"1716281208","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}