{"data":{"id":"68423","string_id":"oaoCKl","status":"1","parent_id":"68373","slug":"mqm8R6","order":"8","name":"Privacy Policy","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"1707211447","add_time":"1707205615","update_time":"1783493558","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"parent_name":"SDK Integration Guides","parent_type":"1","parent_slug":"cUkkAX","child":[{"id":"159209","string_id":"yKbXzp","status":"1","parent_id":"68423","slug":"Overseas-privacy-configuration","order":"0","name":"Privacy Configurations","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"GDPR","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1727680621","add_time":"1725613424","update_time":"1783072534","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"159209","content":"## \u25cf GDPR\n> Since May 25, 2018, the European Union's General Data Protection Regulation has officially taken effect. To protect the interests and privacy of developers and users, we have updated the \"[TopOn Privacy Policy](https:\/\/help.toponad.net\/docs\/Privacy-Policy)\". At the same time, we have also added privacy permission settings in the SDK. Please check the SDK configuration according to the following content.\n\n### 1. Configure GDPR in the TopOn SDK\n#### 1.1 Set the TopOn GDPR Level via the TopOn SDK API\n\n(After setting, the SDK internally uses this level to configure the GDPR reporting level for third-party ad networks):\n\n

\n\n```java\nATSDK.setGDPRUploadDataLevel(context, level);\n\n\/\/ The following options are available for level\nATSDK.PERSONALIZED, \/\/ Device data is allowed to be reported\nATSDK.NONPERSONALIZED, \/\/ Device data is not allowed to be reported\nATSDK.UNKNOWN \/\/ Unknown level, can only be obtained via the getGDPRDataLevel method, cannot be set via the setGDPRUploadDataLevel method\n```\n\n<\/div>\n\n

\n\n```java\nTUSDK.setGDPRUploadDataLevel(context, level);\n\n\/\/ The following options are available for level\nTUSDK.PERSONALIZED, \/\/ Device data is allowed to be reported\nTUSDK.NONPERSONALIZED, \/\/ Device data is not allowed to be reported\nTUSDK.UNKNOWN \/\/ Unknown level, can only be obtained via the getGDPRDataLevel method, cannot be set via the setGDPRUploadDataLevel method\n```\n\n<\/div>\n\n\n#### 1.2 Set the TopOn GDPR Level via the Authorization Page Provided by TopOn\n\n(The authorization page sets the reporting level based on the user's selection):\n\n

\n\n```java\nATSDK.showGDPRConsentDialog(context, new ATGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n ATSDK.init(context, \"your app id\", \"your app key\");\n }\n});\n```\n\n<\/div>\n\n

\n\n```java\nTUSDK.showGDPRConsentDialog(context, new TUGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n TUSDK.init(context, \"your app id\", \"your app key\");\n }\n});\n```\n\n<\/div>\n\n### 2. Recommended GDPR Configuration Process for the EU Region\n> It is recommended to add the following GDPR setup process. If you have not configured GDPR, the TopOn SDK will use the ad network's default GDPR settings when the user is in the EU region.\n\n

\n\n```java\nATSDK.showGDPRConsentDialog(context, new ATGDPRConsentDismissListener() {\n\t@Override\n\tpublic void onDismiss(ConsentDismissInfo consentDismissInfo) {\n\t\tATSDK.init(context, \"your app id\", \"your app key\");\n\t}\n});\n```\n\n<\/div>\n\n

\n\n```java\nTUSDK.showGDPRConsentDialog(context, new TUGDPRConsentDismissListener() {\n\t@Override\n\tpublic void onDismiss(ConsentDismissInfo consentDismissInfo) {\n\t\tTUSDK.init(context, \"your app id\", \"your app key\");\n\t}\n});\n```\n\n<\/div>\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/3nANbV\/67c0088515092.png)\n\n---\n\n## \u25cf CCPA\n> The [California Consumer Privacy Act (CCPA)](https:\/\/oag.ca.gov\/privacy\/ccpa) provides various privacy rights to California consumers. Businesses subject to CCPA will fulfill multiple obligations to these consumers, including information disclosure, consumer rights similar to the EU General Data Protection Regulation (GDPR), the right to \"opt out\" of specific data transfers, and the \"opt-in\" requirement for minors.\n\nPlease go to the [TopOn Dashboard - App](https:\/\/app.toponad.com\/m\/app) page, then click the \"**Edit**\" button to configure CCPA, as shown below:\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/3nANbV\/67c00884cdea0.png)\n\n---\n\n## \u25cf COPPA\n> The [Children's Online Privacy Protection Act (COPPA)](https:\/\/www.ftc.gov\/business-guidance\/privacy-security\/childrens-privacy) primarily targets the online collection of personal information from children under 13. According to the [COPPA FAQ](https:\/\/www.ftc.gov\/business-guidance\/resources\/complying-coppa-frequently-asked-questions), developers are responsible for determining whether their app is targeted at children under 13, considering, but not limited to, the following factors: \"the subject matter of the application, visual content, use of animated characters or child-oriented activities and incentives, music or other audio content, age of models, presence of child celebrities or celebrities appealing to children, language or other characteristics of the website or online service, and whether the advertising promoted or appearing on the website or online service is targeted at children.\"\n\n1. Please go to the [TopOn Dashboard - App](https:\/\/app.toponad.com\/m\/app) page, then click the \"**Edit**\" button to configure COPPA, as shown below:\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/3nANbV\/67c00884c8968.png)\n\n2. Pass the `user's age` in the following way **before initializing the TopOn SDK**:\n\n> \u26a0\ufe0f When the user's age passed is ***under 13***, it will comply with the relevant COPPA regulations.\n\n

\n\n```java\nMap customMap = new HashMap<>();\ncustomMap.put(\"age\", \"User's age\"); \nATSDK.initCustomMap(customMap); \n```\n\n<\/div>\n\n

\n\n```java\nMap customMap = new HashMap<>();\ncustomMap.put(\"age\", \"User's age\"); \nTUSDK.initCustomMap(customMap); \n```\n\n<\/div>\n\n---\n\n## \u25cf About Pangle's PAConsent\n\n> \u26a0\ufe0f **Note**\n> - **Pangle removed COPPA and CCPA settings starting from v7.1.x.x, unifying them under PAConsent**\n> - TopOn SDK supports the use of PAConsent in v6.4.88 and above\n> - If not set as follows, the Pangle SDK default value `Consent` will be used\n> - It is recommended to set this before TopOn SDK initialization\n\n

\n\n```java\n\/\/ Consent\nPangleATInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_PA_CONSENT_TYPE_CONSENT);\n\n\/\/ Do not consent\nPangleATInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_GDPR_CONSENT_TYPE_NO_CONSENT);\n```\n\n<\/div>\n\n

\n\n```java\n\/\/ Consent\nPangleTUInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_PA_CONSENT_TYPE_CONSENT);\n\n\/\/ Do not consent\nPangleTUInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_GDPR_CONSENT_TYPE_NO_CONSENT);\n```\n\n<\/div>\n\n---\n\n## \u25cf Privacy Information Switches\n\n> * To ensure that your app successfully passes detection, in line with the current regulatory focus, you can place the TopOn SDK initialization after the user agrees to the privacy policy.\n> * If you have higher requirements, you can use the following methods for control. Restricting user device data reporting may affect ad fill. Please use with caution.\n> **For details on data collected by the TopOn SDK**, please see: [Privacy Compliance Guide](https:\/\/help.toponad.net\/cn\/docs\/ByIf1V)\n>\n> * The TopOn SDK provides APIs for you to restrict the reporting of these privacy data. When restricting the reporting of device data, it may affect the normal use of TopOn features, such as: traffic grouping, cross-promotion, TopOn Adx, etc. **Please set with caution.**\n> * When GDPR is set to not consent, only the following will be collected: phone OS version name, screen orientation, and the TopOn SDK version number integrated in the app.\n\n

\n\n```java\n\/\/ Call this code before SDK initialization to restrict the reporting of device privacy data. The passed information will be restricted from reporting.\nATSDK.deniedUploadDeviceInfo(\n DeviceDataInfo.DEVICE_SCREEN_SIZE, \/\/ Screen resolution\n DeviceDataInfo.ANDROID_ID, \/\/ Android ID\n DeviceDataInfo.APP_PACKAGE_NAME, \/\/ App package name\n DeviceDataInfo.APP_VERSION_CODE, \/\/ App version code\n DeviceDataInfo.APP_VERSION_NAME, \/\/ App version name\n DeviceDataInfo.BRAND, \/\/ Device manufacturer\n DeviceDataInfo.GAID, \/\/ Google Ad ID\n DeviceDataInfo.LANGUAGE, \/\/ Language\n DeviceDataInfo.MCC, \/\/ Mobile Country Code\n DeviceDataInfo.MNC, \/\/ Mobile Network Code\n DeviceDataInfo.MODEL, \/\/ Device model\n DeviceDataInfo.ORIENTATION, \/\/ Screen orientation\n DeviceDataInfo.OS_VERSION_CODE, \/\/ OS version code\n DeviceDataInfo.OS_VERSION_NAME, \/\/ OS version name\n DeviceDataInfo.TIMEZONE, \/\/ Timezone\n DeviceDataInfo.USER_AGENT, \/\/ User Agent\n DeviceDataInfo.NETWORK_TYPE, \/\/ Network type\n DeviceDataInfo.INSTALLER \/\/ App install source\n);\n```\n\n<\/div>\n\n

\n\n```java\n\/\/ Call this code before SDK initialization to restrict the reporting of device privacy data. The passed information will be restricted from reporting.\nTUSDK.deniedUploadDeviceInfo(\n DeviceDataInfo.DEVICE_SCREEN_SIZE, \/\/ Screen resolution\n DeviceDataInfo.ANDROID_ID, \/\/ Android ID\n DeviceDataInfo.APP_PACKAGE_NAME, \/\/ App package name\n DeviceDataInfo.APP_VERSION_CODE, \/\/ App version code\n DeviceDataInfo.APP_VERSION_NAME, \/\/ App version name\n DeviceDataInfo.BRAND, \/\/ Device manufacturer\n DeviceDataInfo.GAID, \/\/ Google Ad ID\n DeviceDataInfo.LANGUAGE, \/\/ Language\n DeviceDataInfo.MCC, \/\/ Mobile Country Code\n DeviceDataInfo.MNC, \/\/ Mobile Network Code\n DeviceDataInfo.MODEL, \/\/ Device model\n DeviceDataInfo.ORIENTATION, \/\/ Screen orientation\n DeviceDataInfo.OS_VERSION_CODE, \/\/ OS version code\n DeviceDataInfo.OS_VERSION_NAME, \/\/ OS version name\n DeviceDataInfo.TIMEZONE, \/\/ Timezone\n DeviceDataInfo.USER_AGENT, \/\/ User Agent\n DeviceDataInfo.NETWORK_TYPE, \/\/ Network type\n DeviceDataInfo.INSTALLER \/\/ App install source\n);\n```\n\n<\/div>","pure_content":"\u25cf GDPR\n\nSince May 25, 2018, the European Union's General Data Protection Regulation has officially taken effect. To protect the interests and privacy of developers and users, we have updated the \"TopOn Privacy Policy\". At the same time, we have also added privacy permission settings in the SDK. Please check the SDK configuration according to the following content.\n\n1. Configure GDPR in the TopOn SDK\n1.1 Set the TopOn GDPR Level via the TopOn SDK API\n(After setting, the SDK internally uses this level to configure the GDPR reporting level for third-party ad networks):\n\nATSDK.setGDPRUploadDataLevel(context, level);\n\n\/\/ The following options are available for level\nATSDK.PERSONALIZED, \/\/ Device data is allowed to be reported\nATSDK.NONPERSONALIZED, \/\/ Device data is not allowed to be reported\nATSDK.UNKNOWN \/\/ Unknown level, can only be obtained via the getGDPRDataLevel method, cannot be set via the setGDPRUploadDataLevel method\n\n\n\nTUSDK.setGDPRUploadDataLevel(context, level);\n\n\/\/ The following options are available for level\nTUSDK.PERSONALIZED, \/\/ Device data is allowed to be reported\nTUSDK.NONPERSONALIZED, \/\/ Device data is not allowed to be reported\nTUSDK.UNKNOWN \/\/ Unknown level, can only be obtained via the getGDPRDataLevel method, cannot be set via the setGDPRUploadDataLevel method\n\n\n1.2 Set the TopOn GDPR Level via the Authorization Page Provided by TopOn\n(The authorization page sets the reporting level based on the user's selection):\n\nATSDK.showGDPRConsentDialog(context, new ATGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n ATSDK.init(context, \"your app id\", \"your app key\");\n }\n});\n\n\n\nTUSDK.showGDPRConsentDialog(context, new TUGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n TUSDK.init(context, \"your app id\", \"your app key\");\n }\n});\n\n\n2. Recommended GDPR Configuration Process for the EU Region\n\nIt is recommended to add the following GDPR setup process. If you have not configured GDPR, the TopOn SDK will use the ad network's default GDPR settings when the user is in the EU region.\n\n\nATSDK.showGDPRConsentDialog(context, new ATGDPRConsentDismissListener() {\n\t@Override\n\tpublic void onDismiss(ConsentDismissInfo consentDismissInfo) {\n\t\tATSDK.init(context, \"your app id\", \"your app key\");\n\t}\n});\n\n\n\nTUSDK.showGDPRConsentDialog(context, new TUGDPRConsentDismissListener() {\n\t@Override\n\tpublic void onDismiss(ConsentDismissInfo consentDismissInfo) {\n\t\tTUSDK.init(context, \"your app id\", \"your app key\");\n\t}\n});\n\n\n\n\n\u25cf CCPA\n\nThe California Consumer Privacy Act (CCPA) provides various privacy rights to California consumers. Businesses subject to CCPA will fulfill multiple obligations to these consumers, including information disclosure, consumer rights similar to the EU General Data Protection Regulation (GDPR), the right to \"opt out\" of specific data transfers, and the \"opt-in\" requirement for minors.\n\nPlease go to the TopOn Dashboard - App page, then click the \"Edit\" button to configure CCPA, as shown below:\n\n\n\u25cf COPPA\n\nThe Children's Online Privacy Protection Act (COPPA) primarily targets the online collection of personal information from children under 13. According to the COPPA FAQ, developers are responsible for determining whether their app is targeted at children under 13, considering, but not limited to, the following factors: \"the subject matter of the application, visual content, use of animated characters or child-oriented activities and incentives, music or other audio content, age of models, presence of child celebrities or celebrities appealing to children, language or other characteristics of the website or online service, and whether the advertising promoted or appearing on the website or online service is targeted at children.\"\n\n\nPlease go to the TopOn Dashboard - App page, then click the \"Edit\" button to configure COPPA, as shown below:\n\n\n\nPass the user's age in the following way before initializing the TopOn SDK:\n\n\n\u26a0\ufe0f When the user's age passed is under 13, it will comply with the relevant COPPA regulations.\n\n\nMap customMap = new HashMap();\ncustomMap.put(\"age\", \"User's age\"); \nATSDK.initCustomMap(customMap); \n\n\n\nMap customMap = new HashMap();\ncustomMap.put(\"age\", \"User's age\"); \nTUSDK.initCustomMap(customMap); \n\n\n\n\u25cf About Pangle's PAConsent\n\n\u26a0\ufe0f Note\n\n\nPangle removed COPPA and CCPA settings starting from v7.1.x.x, unifying them under PAConsent\n\nTopOn SDK supports the use of PAConsent in v6.4.88 and above\nIf not set as follows, the Pangle SDK default value Consent will be used\nIt is recommended to set this before TopOn SDK initialization\n\n\n\n\/\/ Consent\nPangleATInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_PA_CONSENT_TYPE_CONSENT);\n\n\/\/ Do not consent\nPangleATInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_GDPR_CONSENT_TYPE_NO_CONSENT);\n\n\n\n\/\/ Consent\nPangleTUInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_PA_CONSENT_TYPE_CONSENT);\n\n\/\/ Do not consent\nPangleTUInitManager.getInstance().setPAConsent(PAGConstant.PAGPAConsentType.PAG_GDPR_CONSENT_TYPE_NO_CONSENT);\n\n\n\n\u25cf Privacy Information Switches\n\n\n\nTo ensure that your app successfully passes detection, in line with the current regulatory focus, you can place the TopOn SDK initialization after the user agrees to the privacy policy.\n\n\nIf you have higher requirements, you can use the following methods for control. Restricting user device data reporting may affect ad fill. Please use with caution.\nFor details on data collected by the TopOn SDK, please see: Privacy Compliance Guide\n\n\nThe TopOn SDK provides APIs for you to restrict the reporting of these privacy data. When restricting the reporting of device data, it may affect the normal use of TopOn features, such as: traffic grouping, cross-promotion, TopOn Adx, etc. Please set with caution.\n\n\nWhen GDPR is set to not consent, only the following will be collected: phone OS version name, screen orientation, and the TopOn SDK version number integrated in the app.\n\n\n\n\n\/\/ Call this code before SDK initialization to restrict the reporting of device privacy data. The passed information will be restricted from reporting.\nATSDK.deniedUploadDeviceInfo(\n DeviceDataInfo.DEVICE_SCREEN_SIZE, \/\/ Screen resolution\n DeviceDataInfo.ANDROID_ID, \/\/ Android ID\n DeviceDataInfo.APP_PACKAGE_NAME, \/\/ App package name\n DeviceDataInfo.APP_VERSION_CODE, \/\/ App version code\n DeviceDataInfo.APP_VERSION_NAME, \/\/ App version name\n DeviceDataInfo.BRAND, \/\/ Device manufacturer\n DeviceDataInfo.GAID, \/\/ Google Ad ID\n DeviceDataInfo.LANGUAGE, \/\/ Language\n DeviceDataInfo.MCC, \/\/ Mobile Country Code\n DeviceDataInfo.MNC, \/\/ Mobile Network Code\n DeviceDataInfo.MODEL, \/\/ Device model\n DeviceDataInfo.ORIENTATION, \/\/ Screen orientation\n DeviceDataInfo.OS_VERSION_CODE, \/\/ OS version code\n DeviceDataInfo.OS_VERSION_NAME, \/\/ OS version name\n DeviceDataInfo.TIMEZONE, \/\/ Timezone\n DeviceDataInfo.USER_AGENT, \/\/ User Agent\n DeviceDataInfo.NETWORK_TYPE, \/\/ Network type\n DeviceDataInfo.INSTALLER \/\/ App install source\n);\n\n\n\n\/\/ Call this code before SDK initialization to restrict the reporting of device privacy data. The passed information will be restricted from reporting.\nTUSDK.deniedUploadDeviceInfo(\n DeviceDataInfo.DEVICE_SCREEN_SIZE, \/\/ Screen resolution\n DeviceDataInfo.ANDROID_ID, \/\/ Android ID\n DeviceDataInfo.APP_PACKAGE_NAME, \/\/ App package name\n DeviceDataInfo.APP_VERSION_CODE, \/\/ App version code\n DeviceDataInfo.APP_VERSION_NAME, \/\/ App version name\n DeviceDataInfo.BRAND, \/\/ Device manufacturer\n DeviceDataInfo.GAID, \/\/ Google Ad ID\n DeviceDataInfo.LANGUAGE, \/\/ Language\n DeviceDataInfo.MCC, \/\/ Mobile Country Code\n DeviceDataInfo.MNC, \/\/ Mobile Network Code\n DeviceDataInfo.MODEL, \/\/ Device model\n DeviceDataInfo.ORIENTATION, \/\/ Screen orientation\n DeviceDataInfo.OS_VERSION_CODE, \/\/ OS version code\n DeviceDataInfo.OS_VERSION_NAME, \/\/ OS version name\n DeviceDataInfo.TIMEZONE, \/\/ Timezone\n DeviceDataInfo.USER_AGENT, \/\/ User Agent\n DeviceDataInfo.NETWORK_TYPE, \/\/ Network type\n DeviceDataInfo.INSTALLER \/\/ App install source\n);","is_draft":"0","editor_type":"2","file_path":"","add_time":"1725613424","update_time":"1783072534"},"pure_content":"\u25cf GDPR\n\nSince May 25, 2018, the European Union's General Data Protection Regulation has officially taken effect. To protect the interests and privacy of developers and users, we have updated the \"TopO"},{"id":"160031","string_id":"QgJxom","status":"1","parent_id":"68423","slug":"Google-UMP-SDK-Gudelines-oThF","order":"0","name":"Google UMP","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Google UMP","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1727680734","add_time":"1725867560","update_time":"1783072627","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"160031","content":"## 1. Background\n> Starting January 16, 2024, publishers and developers using Google AdSense, Ad Manager, or AdMob to serve ads to users in the European Economic Area or the United Kingdom must use a Consent Management Platform (CMP) that is certified by Google and integrated with [IAB's Transparency and Consent Framework](https:\/\/iabeurope.eu\/transparency-consent-framework\/) (TCF).\n\nStarting from SDK version **6.2.87**, the TopOn SDK provides a method compatible with the UMP SDK to configure the GDPR level. The TopOn SDK internally uses this level to configure the GDPR reporting level for third-party ad networks.\n\n---\n\n## 2. UMP Usage Process\n### 2.1 Enable UMP in the AdMob Console\n\n> \u2460 Visit the AdMob Console, log in to your AdMob account \u2014 Add your app in AdMob (if you have not added the app yet).\n> \u2461 Click \"Privacy & messaging\".\n> \u2462 Click \"European regulations - Manage\".\n> \u2463 Click \"Create message\" and wait for the GDPR message page to open.\n> \u2464 On the GDPR message page, click \"Select apps\" in the top right corner and select the app for which you want to display the GDPR message.\n> \u2465 Select the language in which you want to display the message.\n> \u2466 In the \"Targeting\" section, select the \"Countries subject to GDPR (EEA and UK)\" option.\n\n> The following configuration can improve the probability of users consenting to GDPR:\n> \u2460 Under \"User options - Close (do not consent)\", select Close.\n> \u2461 Style adjustment: Select the \"Style\" section\n> \t* Under the button section, adjust the \"Secondary color\" to white (#ffffff).\n> \t* Under the button section, adjust the \"Secondary font color\" to gray (#6e6e6e).\n> \t\n> The overall effect after adjustment is shown in the image below. Finally, click \"Publish\" in the top right corner. ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/sDwunE\/65c1e088849de.png)\n\n### 2.2 Self-Specified Ad Partners\n> **Note**: By default, Google may not display all ad networks integrated in your project in your GDPR message. Failure to include these ad networks may adversely affect your ad revenue. Please follow the steps in this section to ensure that all ad networks integrated in your project appear in the GDPR message.\n\nCustomize which ad partners are displayed in the GDPR message:\n\n(1) In the AdMob console, under \"Privacy & messaging\", click \"GDPR Settings\" to open the GDPR settings.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/sDwunE\/65c1e088e884a.png)\n\n(2) Click the edit icon (![\u270e](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/sDwunE\/65c1e0894cc93.png)) under the \"Review your ad partners\" section.\n\n(3) Refer to the table below and check all ad networks integrated in your project.\n\n| Google Name | TopOn SDK Network |\n| :-: | :-: |\n| Facebook | Meta |\n| AppLovin Corp | AppLovin |\n| ironSource Mobile | IronSource |\n| InMobi Choice | InMobi |\n| BIGOAds | Bigo |\n| Chartboost | Chartboost |\n| UnityAds | Unity Ads |\n| Ogury Ltd | Ogury |\n| Google | AdMob |\n| StartApp | Start.io |\n| Verve Group | Verve |\n| Tapjoy | Tapjoy |\n| Liftoff | Vungle |\n| F@N communications | Nend |\n| Fyber | Digital Turbine(Fyber) |\n| Kidoz | Kidoz |\n| Mobvista\/Mintegral | Mintegral |\n\n> **Tips**: For ad networks not listed in this table, such as Pangle, Maio, Appnext, MyTarget, Yandex, Helium, etc., since they are not in the AdMob GDPR ad partner list, TopOn will internally use the popup consent result to set the GDPR reporting level for these ad networks.\n\n(4) Click \"Confirm\".\n\n(5) Click the \"Save\" button at the bottom of the GDPR settings page.\n\n> **Note**: If a popup asking \"Re-consent all eligible users?\" appears, select \"Re-prompt\".\n\n**![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/sDwunE\/65c1e089a14f7.png)**\n\n### **2.3 Enable UMP in the Project**\n\n(1) First, add the Google User Messaging Platform SDK dependency to the module's app-level Gradle file (usually `app\/build.gradle`).\n\n```Groovy\ndependencies {\n implementation(\"com.google.android.ump:user-messaging-platform:3.1.0\")\n}\n```\n\n(2) Add `gms.ads.APPLICATION_ID` in AndroidManifest.xml, with the value being the app ID created in the AdMob console.\n\n```manifest\n\n \n \n <\/application>\n<\/manifest>\n```\n\n(3) Add the following configuration to the obfuscation configuration file `proguard-android.txt`:\n\n```\n-keep public class com.google.android.ump.*\n```\n\n

\n\n(4) Call `ATSDK.showGDPRConsentDialog` and perform SDK initialization within the `onDismiss` callback. Internally, `ATSDK.showGDPRConsentDialog` determines whether the UMP SDK is integrated. If integrated, it uses the UMP SDK API to display the GDPR information dialog. If not integrated, it uses the TopOn GDPR information dialog in the EU region for the user to select the GDPR level.\n\n> **Note**:\n>\n> * You need to initiate ad requests only after SDK initialization.\n> * **Please ensure that the phone's network can access external networks** (Google servers) to avoid UMP SDK popup failures due to network issues.\n\n```java\nATSDK.showGDPRConsentDialog(activity, new ATGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n ATSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n```\n\n(5) During the testing phase, you can use the following sample code to simulate a UMP GDPR popup appearing in the EU region.\n\n> **Note**: This test code must be removed before release.\n\n```java\n\/**\n * deviceId: Obtain by calling ATSDK.showGDPRConsentDialog and filtering the keyword \"addTestDeviceHashedId\" in logcat.\n *\/\nATSDK.setDebuggerConfig(activity, \"\", \n new ATDebuggerConfig.Builder().setUMPTestDeviceId(\"deviceid\").build());\n```\n\n<\/div>\n\n

\n\n(4) Call `TUSDK.showGDPRConsentDialog` and perform SDK initialization within the `onDismiss` callback. Internally, `TUSDK.showGDPRConsentDialog` determines whether the UMP SDK is integrated. If integrated, it uses the UMP SDK API to display the GDPR information dialog. If not integrated, it uses the TopOn GDPR information dialog in the EU region for the user to select the GDPR level.\n\n> **Note**:\n>\n> * You need to initiate ad requests only after SDK initialization.\n> * **Please ensure that the phone's network can access external networks** (Google servers) to avoid UMP SDK popup failures due to network issues.\n\n```java\nTUSDK.showGDPRConsentDialog(activity, new TUGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n TUSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n```\n\n(5) During the testing phase, you can use the following sample code to simulate a UMP GDPR popup appearing in the EU region.\n\n> **Note**: This test code must be removed before release.\n\n```java\n\/**\n * deviceId: Obtain by calling TUSDK.showGDPRConsentDialog and filtering the keyword \"addTestDeviceHashedId\" in logcat.\n *\/\nTUSDK.setDebuggerConfig(activity, \"\", \n new TUDebuggerConfig.Builder().setUMPTestDeviceId(\"deviceid\").build());\n```\n\n<\/div>\n\n\n### 2.4 Add a Link in the App to Allow Users to Withdraw Consent\nVersion 6.5.50 added the showGDPRConsentSecondDialog method to allow modification of the consent solicitation process, enabling a second GDPR selection.\n

\n \n```java\nATSDK.showGDPRConsentSecondDialog(activity, new ATGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n ATSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n```\n<\/div> \n

\n \n```java\nTUSDK.showGDPRConsentSecondDialog(activity, new TUGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n TUSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n```\n<\/div> \n\n> **Note**: Withdrawing consent is the process by which users in the European Economic Area (EEA), the United Kingdom, and Switzerland can withdraw their consent after having consented to personalized ads. A corresponding link must be provided in the app's menu to allow users who wish to withdraw their consent to do so, and then the user consent message will be shown to them again.\n\nFor details, please refer to [here](https:\/\/support.google.com\/admob\/answer\/10113915?hl=zh-Hans&ref_topic=10113206&sjid=8371632926513349913-AP).\n\nPlease refer to the [Google AdMob Ads SDK Developer Documentation](https:\/\/developers.google.com\/admob\/android\/privacy?hl=zh-cn#privacy_options) to implement the privacy settings option.\n\n---\n\n## 3. FAQ\n\n**(1) The UMP SDK is already integrated in the project. How to handle updating TopOn to version 6.2.87 or above?**\n\nSince the TopOn SDK will prioritize reading the GDPR-related settings configured by the UMP SDK during initialization to set the GDPR reporting level for third-party ad networks, developers need to ensure that the \"Ad Partners\" list in the AdMob console GDPR settings includes **all ad networks integrated in your app** (excluding Pangle, Huawei, Maio, Appnext, MyTarget, Yandex, and Helium platforms). Refer to [Self-Specified Ad Partners](https:\/\/help.toponad.net\/docs\/Google-UMP-SDK-Gudelines-oThF#2.2%20Self-Specified%20Ad%20Partners) above for configuration. \nIn addition, it is recommended to use the TopOn SDK's showGDPRConsentDialog to replace the original UMP SDK API call code. Refer to the sample code above and perform SDK initialization in the onDismiss callback. If you wish to retain the original UMP SDK API call logic in the project, you need to refer to the example in the [AdMob UMP Usage Guide](https:\/\/developers.google.com\/admob\/android\/privacy?hl=zh-cn#request-ads), and initialize the TopOn SDK in the OnConsentFormDismissedListener#onConsentFormDismissed() callback or after determining that consentInformation.canRequestAds is true.\n\n**(2) The project already has UMP SDK integrated, but later the app update removed the UMP SDK usage. How to handle updating TopOn to version 6.2.87 or above?**\n\nSince the TopOn SDK will prioritize reading the GDPR-related settings set by the UMP SDK during initialization, even if the UMP SDK is removed, the old GDPR configuration cache files still remain locally. Developers need to call the following code to remove the cached data when removing the UMP SDK version. Sample code is as follows: \nNote: After removing the UMP SDK GDPR local cache using this method, it may affect AdMob's ability to serve ads to users in the EEA or UK.\n\n```java\nSharedPreferences sharedPreferences = PreferenceManager.getDefaultSharedPreferences(context);\nSharedPreferences.Editor editor = sharedPreferences.edit();\neditor.remove(\"IABTCF_TCString\");\neditor.remove(\"IABTCF_AddtlConsent\");\neditor.remove(\"IABTCF_VendorConsents\");\neditor.remove(\"IABTCF_PurposeConsents\");\neditor.commit();\n```","pure_content":"1. Background\n\nStarting January 16, 2024, publishers and developers using Google AdSense, Ad Manager, or AdMob to serve ads to users in the European Economic Area or the United Kingdom must use a Consent Management Platform (CMP) that is certified by Google and integrated with IAB's Transparency and Consent Framework (TCF).\n\nStarting from SDK version 6.2.87, the TopOn SDK provides a method compatible with the UMP SDK to configure the GDPR level. The TopOn SDK internally uses this level to configure the GDPR reporting level for third-party ad networks.\n\n2. UMP Usage Process\n2.1 Enable UMP in the AdMob Console\n\n\u2460 Visit the AdMob Console, log in to your AdMob account \u2014 Add your app in AdMob (if you have not added the app yet).\n\u2461 Click \"Privacy & messaging\".\n\u2462 Click \"European regulations - Manage\".\n\u2463 Click \"Create message\" and wait for the GDPR message page to open.\n\u2464 On the GDPR message page, click \"Select apps\" in the top right corner and select the app for which you want to display the GDPR message.\n\u2465 Select the language in which you want to display the message.\n\u2466 In the \"Targeting\" section, select the \"Countries subject to GDPR (EEA and UK)\" option.\n\n\nThe following configuration can improve the probability of users consenting to GDPR:\n\u2460 Under \"User options - Close (do not consent)\", select Close.\n\u2461 Style adjustment: Select the \"Style\" section\n\nUnder the button section, adjust the \"Secondary color\" to white (#ffffff).\nUnder the button section, adjust the \"Secondary font color\" to gray (#6e6e6e).\n\nThe overall effect after adjustment is shown in the image below. Finally, click \"Publish\" in the top right corner. \n\n2.2 Self-Specified Ad Partners\n\nNote: By default, Google may not display all ad networks integrated in your project in your GDPR message. Failure to include these ad networks may adversely affect your ad revenue. Please follow the steps in this section to ensure that all ad networks integrated in your project appear in the GDPR message.\n\nCustomize which ad partners are displayed in the GDPR message:\n(1) In the AdMob console, under \"Privacy & messaging\", click \"GDPR Settings\" to open the GDPR settings.\n\n(2) Click the edit icon () under the \"Review your ad partners\" section.\n(3) Refer to the table below and check all ad networks integrated in your project.\n\n\n\n Google Name\n TopOn SDK Network\n\n\n\n\n Facebook\n Meta\n\n\n AppLovin Corp\n AppLovin\n\n\n ironSource Mobile\n IronSource\n\n\n InMobi Choice\n InMobi\n\n\n BIGOAds\n Bigo\n\n\n Chartboost\n Chartboost\n\n\n UnityAds\n Unity Ads\n\n\n Ogury Ltd\n Ogury\n\n\n Google\n AdMob\n\n\n StartApp\n Start.io\n\n\n Verve Group\n Verve\n\n\n Tapjoy\n Tapjoy\n\n\n Liftoff\n Vungle\n\n\n F@N communications\n Nend\n\n\n Fyber\n Digital Turbine(Fyber)\n\n\n Kidoz\n Kidoz\n\n\n Mobvista\/Mintegral\n Mintegral\n\n\n\n\nTips: For ad networks not listed in this table, such as Pangle, Maio, Appnext, MyTarget, Yandex, Helium, etc., since they are not in the AdMob GDPR ad partner list, TopOn will internally use the popup consent result to set the GDPR reporting level for these ad networks.\n\n(4) Click \"Confirm\".\n(5) Click the \"Save\" button at the bottom of the GDPR settings page.\n\nNote: If a popup asking \"Re-consent all eligible users?\" appears, select \"Re-prompt\".\n\n\n2.3 Enable UMP in the Project\n(1) First, add the Google User Messaging Platform SDK dependency to the module's app-level Gradle file (usually app\/build.gradle).\ndependencies {\n implementation(\"com.google.android.ump:user-messaging-platform:3.1.0\")\n}\n\n(2) Add gms.ads.APPLICATION_ID in AndroidManifest.xml, with the value being the app ID created in the AdMob console.\n\n \n \n \n\n\n(3) Add the following configuration to the obfuscation configuration file proguard-android.txt:\n-keep public class com.google.android.ump.*\n\n\n(4) Call ATSDK.showGDPRConsentDialog and perform SDK initialization within the onDismiss callback. Internally, ATSDK.showGDPRConsentDialog determines whether the UMP SDK is integrated. If integrated, it uses the UMP SDK API to display the GDPR information dialog. If not integrated, it uses the TopOn GDPR information dialog in the EU region for the user to select the GDPR level.\n\nNote:\n\nYou need to initiate ad requests only after SDK initialization.\n\nPlease ensure that the phone's network can access external networks (Google servers) to avoid UMP SDK popup failures due to network issues.\n\n\nATSDK.showGDPRConsentDialog(activity, new ATGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n ATSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n\n(5) During the testing phase, you can use the following sample code to simulate a UMP GDPR popup appearing in the EU region.\n\nNote: This test code must be removed before release.\n\n\/**\n * deviceId: Obtain by calling ATSDK.showGDPRConsentDialog and filtering the keyword \"addTestDeviceHashedId\" in logcat.\n *\/\nATSDK.setDebuggerConfig(activity, \"\", \n new ATDebuggerConfig.Builder().setUMPTestDeviceId(\"deviceid\").build());\n\n\n\n(4) Call TUSDK.showGDPRConsentDialog and perform SDK initialization within the onDismiss callback. Internally, TUSDK.showGDPRConsentDialog determines whether the UMP SDK is integrated. If integrated, it uses the UMP SDK API to display the GDPR information dialog. If not integrated, it uses the TopOn GDPR information dialog in the EU region for the user to select the GDPR level.\n\nNote:\n\nYou need to initiate ad requests only after SDK initialization.\n\nPlease ensure that the phone's network can access external networks (Google servers) to avoid UMP SDK popup failures due to network issues.\n\n\nTUSDK.showGDPRConsentDialog(activity, new TUGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n TUSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n\n(5) During the testing phase, you can use the following sample code to simulate a UMP GDPR popup appearing in the EU region.\n\nNote: This test code must be removed before release.\n\n\/**\n * deviceId: Obtain by calling TUSDK.showGDPRConsentDialog and filtering the keyword \"addTestDeviceHashedId\" in logcat.\n *\/\nTUSDK.setDebuggerConfig(activity, \"\", \n new TUDebuggerConfig.Builder().setUMPTestDeviceId(\"deviceid\").build());\n\n\n2.4 Add a Link in the App to Allow Users to Withdraw Consent\nVersion 6.5.50 added the showGDPRConsentSecondDialog method to allow modification of the consent solicitation process, enabling a second GDPR selection.\n\nATSDK.showGDPRConsentSecondDialog(activity, new ATGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n ATSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n\n \n\nTUSDK.showGDPRConsentSecondDialog(activity, new TUGDPRConsentDismissListener() {\n @Override\n public void onDismiss(ConsentDismissInfo consentDismissInfo) {\n \/\/ Note: SDK initialization must be performed in this callback, and ads must be loaded after initialization.\n TUSDK.init(activity, appId, appKey);\n }\n},\"appId\");\n\n \n\nNote: Withdrawing consent is the process by which users in the European Economic Area (EEA), the United Kingdom, and Switzerland can withdraw their consent after having consented to personalized ads. A corresponding link must be provided in the app's menu to allow users who wish to withdraw their consent to do so, and then the user consent message will be shown to them again.\n\nFor details, please refer to here.\nPlease refer to the Google AdMob Ads SDK Developer Documentation to implement the privacy settings option.\n\n3. FAQ\n(1) The UMP SDK is already integrated in the project. How to handle updating TopOn to version 6.2.87 or above?\nSince the TopOn SDK will prioritize reading the GDPR-related settings configured by the UMP SDK during initialization to set the GDPR reporting level for third-party ad networks, developers need to ensure that the \"Ad Partners\" list in the AdMob console GDPR settings includes all ad networks integrated in your app (excluding Pangle, Huawei, Maio, Appnext, MyTarget, Yandex, and Helium platforms). Refer to Self-Specified Ad Partners above for configuration.\nIn addition, it is recommended to use the TopOn SDK's showGDPRConsentDialog to replace the original UMP SDK API call code. Refer to the sample code above and perform SDK initialization in the onDismiss callback. If you wish to retain the original UMP SDK API call logic in the project, you need to refer to the example in the AdMob UMP Usage Guide, and initialize the TopOn SDK in the OnConsentFormDismissedListener#onConsentFormDismissed() callback or after determining that consentInformation.canRequestAds is true.\n(2) The project already has UMP SDK integrated, but later the app update removed the UMP SDK usage. How to handle updating TopOn to version 6.2.87 or above?\nSince the TopOn SDK will prioritize reading the GDPR-related settings set by the UMP SDK during initialization, even if the UMP SDK is removed, the old GDPR configuration cache files still remain locally. Developers need to call the following code to remove the cached data when removing the UMP SDK version. Sample code is as follows:\nNote: After removing the UMP SDK GDPR local cache using this method, it may affect AdMob's ability to serve ads to users in the EEA or UK.\nSharedPreferences sharedPreferences = PreferenceManager.getDefaultSharedPreferences(context);\nSharedPreferences.Editor editor = sharedPreferences.edit();\neditor.remove(\"IABTCF_TCString\");\neditor.remove(\"IABTCF_AddtlConsent\");\neditor.remove(\"IABTCF_VendorConsents\");\neditor.remove(\"IABTCF_PurposeConsents\");\neditor.commit();","is_draft":"0","editor_type":"2","file_path":"","add_time":"1725867560","update_time":"1783072626"},"pure_content":"1. Background\n\nStarting January 16, 2024, publishers and developers using Google AdSense, Ad Manager, or AdMob to serve ads to users in the European Economic Area or the United Kingdom must use a Cons"},{"id":"160150","string_id":"UKtqRc","status":"1","parent_id":"68423","slug":"Google-Data-Security-Guidelines","order":"0","name":"Google Data Security Guidelines","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Google Data Security Guidelines","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1727680659","add_time":"1725870766","update_time":"1783072664","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"160150","content":"[According to Google Data Safety](https:\/\/support.google.com\/googleplay\/android-developer\/answer\/10787469) requirements, you need to disclose the data collected by your app and all SDKs integrated in your app.\n\nThe following lists the data collected by the TopOn SDK, which can be used to answer Google's Data Safety questionnaire.\n\n> Note:\n>\n> 1. This information is only used to answer Google's Data Safety questionnaire. For the specific TopOn Privacy Compliance Guide, please read the [TopOn Privacy Compliance Guide](https:\/\/help.toponad.net\/cn\/docs\/ByIf1V).\n> 2. The following describes the data automatically collected by the TopOn SDK, but does not include data collected by any third-party ad network SDKs.\n\n## 1. Data Collection and Security\n\n| Does the SDK collect or share any required user data types? | Is all data collected by the SDK encrypted in transit? | Does the SDK provide a method for users to request deletion of their data? |\n| :---: | :---: | :---: |\n| Yes | Yes | Yes |\n\n---\n\n## 2. Data Types\n\n| Data Type | Scope | Collected | Shared | Purpose of Collection and Sharing |\n| :---: | :---: | :---: | :---: | :---: |\n| Location | Not Applicable | No | No | Not Applicable |\n| Personal Information | Not Applicable | No | No | Not Applicable |\n| Financial Information | Not Applicable | No | No | Not Applicable |\n| Health Information | Not Applicable | No | No | Not Applicable |\n| Messages | Not Applicable | No | No | Not Applicable |\n| Photos or Videos | Not Applicable | No | No | Not Applicable |\n| Audio Files | Not Applicable | No | No | Not Applicable |\n| Files and Docs | Not Applicable | No | No | Not Applicable |\n| Calendar | Not Applicable | No | No | Not Applicable |\n| Contacts | Not Applicable | No | No | Not Applicable |\n| App Activity | Default Use | Yes - App interactions; <\/br>Other actions (interactions with ads) | Yes - App interactions; <\/br>Other actions (interactions with ads) | App interactions: Analytics; <\/br>Other actions: Analytics, Fraud Prevention, Security and Compliance; Advertising or Marketing. |\n| Web Browsing | Not Applicable | No | No | Not Applicable |\n| App Info and Performance | Not Applicable | No | No | Not Applicable |\n| Device ID and Other IDs | Selective Use | Yes | Yes | Analytics, Fraud Prevention, Security and Compliance; Advertising or Marketing. |","pure_content":"According to Google Data Safety requirements, you need to disclose the data collected by your app and all SDKs integrated in your app.\nThe following lists the data collected by the TopOn SDK, which can be used to answer Google's Data Safety questionnaire.\n\nNote:\n\nThis information is only used to answer Google's Data Safety questionnaire. For the specific TopOn Privacy Compliance Guide, please read the TopOn Privacy Compliance Guide.\nThe following describes the data automatically collected by the TopOn SDK, but does not include data collected by any third-party ad network SDKs.\n\n\n1. Data Collection and Security\n\n\n\n Does the SDK collect or share any required user data types?\n Is all data collected by the SDK encrypted in transit?\n Does the SDK provide a method for users to request deletion of their data?\n\n\n\n\n Yes\n Yes\n Yes\n\n\n\n\n2. Data Types\n\n\n\n Data Type\n Scope\n Collected\n Shared\n Purpose of Collection and Sharing\n\n\n\n\n Location\n Not Applicable\n No\n No\n Not Applicable\n\n\n Personal Information\n Not Applicable\n No\n No\n Not Applicable\n\n\n Financial Information\n Not Applicable\n No\n No\n Not Applicable\n\n\n Health Information\n Not Applicable\n No\n No\n Not Applicable\n\n\n Messages\n Not Applicable\n No\n No\n Not Applicable\n\n\n Photos or Videos\n Not Applicable\n No\n No\n Not Applicable\n\n\n Audio Files\n Not Applicable\n No\n No\n Not Applicable\n\n\n Files and Docs\n Not Applicable\n No\n No\n Not Applicable\n\n\n Calendar\n Not Applicable\n No\n No\n Not Applicable\n\n\n Contacts\n Not Applicable\n No\n No\n Not Applicable\n\n\n App Activity\n Default Use\n Yes - App interactions; Other actions (interactions with ads)\n Yes - App interactions; Other actions (interactions with ads)\n App interactions: Analytics; Other actions: Analytics, Fraud Prevention, Security and Compliance; Advertising or Marketing.\n\n\n Web Browsing\n Not Applicable\n No\n No\n Not Applicable\n\n\n App Info and Performance\n Not Applicable\n No\n No\n Not Applicable\n\n\n Device ID and Other IDs\n Selective Use\n Yes\n Yes\n Analytics, Fraud Prevention, Security and Compliance; Advertising or Marketing.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1725870766","update_time":"1783072664"},"pure_content":"According to Google Data Safety requirements, you need to disclose the data collected by your app and all SDKs integrated in your app.\nThe following lists the data collected by the TopOn SDK, which ca"}],"content":{"icon":"","desc":"","content_id":"68423","add_time":"1707205615","update_time":"1727680571","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}