This document provides information for customers (hereinafter referred to as "Customer", "you", or "your") who use Huawei's APIs and other developer services on how Huawei (hereinafter also referred to as "we", "us", or "our") stores and processes user data when the Customer is the data controller and Huawei is the data processor.
Personal Data of the Customer's End Users is stored in data centers determined based on the area of distribution selected by the Customer, or in the locations for data processing directly selected by the Customer (which may differ from the area of distribution), except for the services specifically listed below ("Exceptional Services"), for which the locations for data processing are determined subject to one or more applicable rules.
For Exceptional Services, data centers are determined based on the active regions of the Customer's End Users. The table below defines how active regions of the Customer's End Users are determined for each Exceptional Service.
| AppGallery Connect Service | Active Region of the Customer's End User |
| Map Kit | Active region of the Customer's End User is determined for these services, either (i) directly by the Customer when selecting the location where the data shall be processed on the project page or, (ii) in accordance with the detailed Huawei Global Routing Service (GRS) rules for determining the active region, with the location for data processing prioritized in the following order: (a) country/region where the End User's device was sold; (b) mobile country code (MCC) of the End User's SIM card (if available); (c) location chosen in device operating system settings (locale. region); (d) IP address of the End User's device. |
| Site Kit | |
| ML kit | |
| Nearby Service | |
| Health Kit | The active region of the Customer's End User is determined by the region selected by the Customer's End User when the End User creates a HUAWEI ID. |
| Push Kit | For some functions of the Push Kit, the data of the Customer's End User is stored in the respective region that the Customer has selected. If the active region of the End User is different from the region selected by the Customer, we will process information such as push tokens, messages, and topics in a cross-border manner when you send information to Huawei devices. The active region of each End User of the Customer is decided in accordance with the two GRS rules for Push Kit, which are ranked in the following order of priority: (a) MCC of the End User's SIM card; (b) IP address of the End User's device. Example: • First, we check whether the device of the Customer's End User has a SIM card. If we detect a SIM card, we will try to identify the country/region corresponding to the MCC of the SIM card, and we will then use such country/region as the active region of the Customer's End User. • If we are unable to obtain said country/region, or the End User's device does not have any SIM card, we will try to obtain the IP address of the End User's device, and we will then use the country/region corresponding to the IP address as the active region of the Customer's End User. |
| Analytics Kit | The Analytics Kit server provides data processing location policies. You can select the policy to manually manage and specify data processing locations, or the policy to let services match data processing locations based on the active regions of users. NOTE Currently, the policy to let services match data processing locations based on the active regions of users is available only to Android apps. When you select the policy to let services match data processing locations based on the active regions of users, the active regions of your users will be determined based on four Huawei's global routing rules. The four rules are prioritized in the following order: (1) country/region where the end user's device was sold; (2) mobile country code (MCC) of the end user's SIM card; (3) location chosen in device operating system settings (locale.region); (4) IP address of the end user's device. Note that rule (3) is applicable only when the location is China. Example: • First we try to ascertain the country where the user's device was sold. If we know which country it is, we use that country as the active region of the user. • If we cannot ascertain the country where the user's device was sold, we will check whether the user's device has a SIM card. If we detect a SIM card, we will try to obtain the MCC country of the SIM card and use that country as the active region of the user. • If the attempt to obtain the MCC country is not successful or if the user's device has no SIM card, we will check if the location chosen in the device's operating system settings is China. If yes, we use China as the active region of the user. • If we are unable to obtain the location chosen in the device's operating system settings or if the location is not set as China, we will obtain the IP address location of the user's device, and use that as the active region of the user. |
Information about the locations of data centers in different countries/regions is available at https://developer.huawei.com/consumer/en/doc/10127.
Some AGC services process your end users' personal data to provide their service. The chart below has listed how Huawei uses and handles end-user personal data when Customer is the data controller and Huawei is the data processor.
| AppGallery Connect Service | Personal Data | Processing Purpose | Retention Period |
| Auth Service | Android, iOS, HarmonyOS-Java, HarmonyOS-TypeScript, and HarmonyOS-ArkTS: Device information (AAID), user information (email address, mobile number, and password), authentication provider information (provider UID, avatar, nickname, and provider access token), Auth Service information (AppGallery Connect UID, avatar, nickname, AppGallery Connect access token, and AppGallery Connect refresh token), and app information (package name and version number) | To enable users to sign in to your app using a unique identifier in the authentication provider system, and display their personal information in the app. | The provider access token collected by the Auth Service SDK is used only to obtain user information and is not stored on the server. The AppGallery Connect access token will be deleted 48 hours after a user cancels the subscription, and the AppGallery Connect refresh token will be deleted one month after the account is deleted. Other information will be deleted once the account is deleted. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| Web, quick app, quick game, and WeChat mini program: Device information (AAID), user information (email address, mobile number, and password), authentication provider information (provider UID, avatar, nickname, and provider access token), Auth Service information (AppGallery Connect UID, avatar, nickname, AppGallery Connect access token, and AppGallery Connect refresh token), and app information (version number) | To enable users to sign in to your app using a unique identifier in the authentication provider system, and display their personal information in the app. | The provider access token collected by the Auth Service SDK is used only to obtain user information and is not stored on the server. The AppGallery Connect access token will be deleted 48 hours after a user cancels the subscription, and the AppGallery Connect refresh token will be deleted one month after the account is deleted. Other information will be deleted once the account is deleted. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Server-Java and Server-Node: User information (email address, mobile number, and password), authentication provider information (provider UID, avatar, and nickname), and Auth Service information (AppGallery Connect UID, avatar, and nickname) | To use the Auth Service Server SDK to import user information to the user data in Auth Service, so that users can sign in to your app using an identifier in the authentication provider system, and display their personal information in the app. | The information collected by the Auth Service Server SDK will be deleted once the account is deleted. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Cloud Functions | Android, iOS, HarmonyOS-Java, HarmonyOS-TypeScript, and HarmonyOS-ArkTS: App information (package name and version number) and account token of the Auth Service SDK | 1. To collect necessary data about API calls for statistical analysis. 2. To control access to Cloud Functions. | The information collected by the Cloud Functions SDK for app operations and maintenance will be deleted once you delete a function or your app. The Cloud Functions SDK obtains users' account tokens via the Auth Service SDK to control access to Cloud Functions, and these tokens are not stored on the server. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| Web, quick app, quick game, and WeChat mini program: App information (version number) and account token of the Auth Service SDK | 1. To collect necessary data about API calls for statistical analysis. 2. To control access to Cloud Functions. | The information collected by the Cloud Functions SDK for app operations and maintenance will be deleted once you delete a function or your app. The Cloud Functions SDK obtains users' account tokens via the Auth Service SDK to control access to Cloud Functions, and these tokens are not stored on the server. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Server-Java and Server-Node: N/A | N/A | N/A | |
| Cloud DB | Android, iOS, Web, quick app, quick game, mini program, mini game, HarmonyOS-Java, and HarmonyOS-ArkTS: Account token of the Auth Service SDK | To control access to cloud data. | The Cloud DB SDK obtains users' account tokens via the Auth Service SDK to control access to cloud data, and these tokens are not stored on the cloud. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| Server-Java and Server-Node: N/A | N/A | N/A | |
| Cloud Cache | Data cached by an app | Cloud Cache provides the data cache functions, to cache your app data. You or your app may add or delete data, and such data is not otherwise processed by us. | The data is stored only when your app creates data in Cloud Cache, and is deleted immediately when your app deletes the data. Your app can set a data expiration date after which the data is automatically deleted. |
| Cloud Storage | Android, iOS, Web, quick app, HarmonyOS-Java, HarmonyOS-TypeScript, and HarmonyOS-ArkTS: Account token of the Auth Service SDK | To control access to cloud data. | The Cloud Storage SDK obtains users' account tokens via the Auth Service SDK to control access to cloud data, and these tokens are not stored on the cloud. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| Server-Java and Server-Node: N/A | N/A | N/A | |
| API Gateway | User data that may be carried in requests and responses transferred through API gateway | API gateway transfers requests and responses only when requested by the Customer, and does not parse any service meaning from requests and responses. | API gateway only transparently transfers or forwards messages, and does not store any data. |
| Remote Configuration | Android: Device information (Android OS version number, language, country/region, AAID, and chip type), app information (package name and version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the Android OS version number, language, country/region, chip type, and app version number, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| iOS: Device information (iOS version number, iOS system name, language, country/region, and AAID), app information (package name and version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the iOS version number, language, country/region, and app version number, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Web: Device information (OS version number, browser version, language, and AAID), app information (version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the OS version number, language, country/region, and app version number, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Quick app: Device information (OS version number, browser version, language, country/region, and AAID), app information (version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the OS version number, language, country/region, and app version number, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Quick game: Device information (OS version number, language, and AAID), app information (version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the OS version number and language, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| WeChat mini program: Device information (OS version number, language, country/region, and AAID), app information (version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the OS version number, language, country/region, and app version number, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| HarmonyOS-Java: Device information (HarmonyOS version number, language, country/region, and AAID), app information (package number and version number), and user preference information | To allow Remote Configuration to perform filtering and deliver parameters to your app based on conditions such as the HarmonyOS version number, language, country/region, and app version number, so as to satisfy the needs of different users. | After collecting information, the Remote Configuration SDK only matches the information collected with the cloud configuration and does not store the information. The AAID will be deleted one hour after the last interaction. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| A/B Testing | AAID | A/B Testing allows only End Users with specified AAIDs to participate in an experiment. When an End User participates in an experiment, the AppGallery Connect SDK automatically reports the experiment participation event to Analytics Kit. | The data processing method is the same as that of Analytics Kit. |
| Basic app information | A/B Testing allows only End Users who have installed an app with specified app basic information (including the app ID, package name, and version number) to participate in an experiment. | The data is not stored, and is immediately deleted after End User matching is complete. | |
| Operating system settings | A/B Testing allows only End Users using a device with specified OS settings (including the language, OS version, and local time) to participate in an experiment. | ||
| User attributes | A/B Testing allows only End Users with specified user attributes to participate in an experiment. | ||
| App Linking | Android: Device information (AAID and Android OS version number), app information (package name and version number), and clipboard data | To redirect users to specified content when they tap a link of App Linking on an Android device. | The device information (Android OS version number) and app information (package name and version number) collected by the App Linking SDK are not stored on the cloud. The AAID will be stored for at most 14 months. The collected information will be deleted once you delete a link or your app. Clipboard data is used only by the on-device SDK and will not be uploaded to the cloud. After the SDK reads the clipboard and redirects users to the specified link after data matching, the clipboard data will be deleted immediately. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| iOS: Device information (AAID and iOS version number), app information (package name and version number), and clipboard data | To redirect users to specified content when they tap a link of App Linking on an iOS device. | The device information (iOS version number) and app information (package name and version number) collected by the App Linking SDK are not stored on the cloud. The AAID will be stored for at most 14 months. The collected information will be deleted once you delete a link or your app. Clipboard data is used only by the on-device SDK and will not be uploaded to the cloud. After the SDK reads the clipboard and redirects users to the specified link after data matching, the clipboard data will be deleted immediately. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| App Messaging | Android: Device information (AAID, Android OS version number, language, country/region, and chip type), app information (package name and version number), and user preference information | To allow App Messaging to perform filtering and deliver parameters to your app based on conditions such as the Android OS version number, language, country/region, chip type, and app version number, and to send personalized messages to users based on the application scenario. | The device information (Android OS version number, language, country/region, and chip type), app information (package name and version number), and user preference information collected by the App Messaging SDK are not stored on the cloud. The AAID will be stored for at most 14 months. The collected information will be deleted once you delete an in-app message or your app. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| iOS: Device information (AAID, iOS version number, iOS system name, language, and country/region), app information (package name and version number), and user preference information | To allow App Messaging to perform filtering and deliver parameters to your app based on conditions such as the iOS version number, language, country/region, and app version number, and to send personalized messages to users based on the application scenario. | The device information (iOS version number, iOS system name, language, and country/region), app information (package name and version number), and user preference information collected by the App Messaging SDK are not stored on the cloud. The AAID will be stored for at most 14 months. The collected information will be deleted once you delete an in-app message or your app. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| HarmonyOS-Java: Device information (AAID, HarmonyOS version number, language, and country/region), app information (package number and version number), and user preference information | To allow App Messaging to perform filtering and deliver parameters to your app based on conditions such as the HarmonyOS version number, language, country/region, and app version number, and to send personalized messages to users based on the application scenario. | The device information (HarmonyOS version number, language, and country/region), app information (package name and version number), and user preference information collected by the App Messaging SDK are not stored on the cloud. The AAID will be stored for at most 14 months. The collected information will be deleted once you delete an in-app message or your app. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Crash | Android: Device information (AAID, Android OS version number, device model, product brand, storage status, memory usage status, screen orientation, screen size, language, and root status), app information (package name and version number), network information (network type), and data you upload (custom user identifier, log, and key-value pairs) | To collect device, app, and network information related to the crash, so that you can better identify the app running status and crash causes. | Personal information collected by the Crash SDK includes the device information, app information, network information, and data you upload. All information can be stored for at most 14 months. The collected information will be deleted once you delete the crash-related information or your app. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. |
| iOS: Device information (AAID, iOS version number, iOS system name, device model, product brand, storage status, memory usage status, screen orientation, screen size, and language), app information (package name and version number), network information (network type), and data you upload (custom user identifier, log, and key-value pairs) | To collect device, app, and network information related to the crash, so that you can better identify the app running status and crash causes. | Personal information collected by the Crash SDK includes the device information, app information, network information, and data you upload. All information can be stored for at most 14 months. The collected information will be deleted once you delete the crash-related information or your app. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| HarmonyOS-Java: Device information (AAID, device manufacturer, device model, device architecture, device resolution, screen type, screen size, screen orientation, frame rate, CPU, memory, disk, device usage, OS, system properties, system settings, user device identifier, network type, IP address, approximate location such as the country and city), app information (name, package name, version number, SDK version, time when a crash occurred, resources when the crash occurred, crash type, process, thread, stack, foreground/background status, app custom crash logs, and custom key-value pairs), account information (developer information, including the CP ID, product ID, client ID, and app ID in AppGallery Connect) | To collect crash-related data, so you can conduct analysis based on dimensions such as the app version, device type, device model, and region. In addition, the AAID can be used to calculate the number of unique devices affected by a crash and help analyze and locate an issue reported by a single user. Through crash analysis and locating, you can improve user experience. | Account information used for authentication and isolation is stored for 90 days, and will be deleted automatically afterward. In the event that you discontinue your products or services, you need to notify users in the form of a push notification or bulletin, and delete or anonymize their personal information within a reasonable period of time. | |
| Open test | Mobile number | An invitation SMS message can be sent to End Users via their mobile numbers to invite them to an open test. The data is only used in the Chinese mainland. | The data is deleted immediately when the Customer deletes the End User's account from AppGallery Connect. |
| Email address | An invitation email can be sent to End Users via their email addresses to invite them to an open test. | ||
| User name | A user name is set by the Customer to identify different open test participants and is displayed in AppGallery Connect. | ||
| Prediction | AAID | An AAID is an anonymous device ID opened to apps. Each app is allocated with a unique AAID on the same device so that statistics can be collected and analyzed for different apps (for example, statistics on the number of active users). In addition, personal data from different apps is isolated to protect user data privacy and security | The Prediction service uses only Analytics Kit data and does not store data independently. For details about the data retention period, please refer to the retention period of Analytics Kit. |
| OS version | An OS version is provided by the Customer for prediction model training and analysis of audiences generated by the Prediction service in a visualized manner. | ||
| App version information | An app version is provided by the Customer for statistical analysis and prediction model training. | ||
| Countries and regions | Countries and regions of End Users, which are determined based on the IP addresses of devices connected to the Analytics Kit server. | ||
| Device information | Device information includes device manufacturer (such as Huawei and vivo), screen height, screen width, and device model that are provided by the Customer for prediction model training. The device model can also be used for statistical analysis. | ||
| Event information | App update event: App version updates and app launches after version updates are used to analyze user churn and conversion trends. App uninstallation event: Package names of the apps that are uninstalled and initiation time of the uninstallation are provided for statistical analysis. In-app purchase event: In-app purchases or subscriptions are provided for statistical analysis about the trend of paying user conversion. To learn more about events used for prediction model training, please refer to Automatically Collected Events. | ||
| APM | Android, iOS, and Web: App information, device information (such as system settings, system properties, device model, OS, IP address, and approximate location), network information (network type, Wi-Fi status, and carrier information), and account information | To collect performance data during app running (including the startup duration, load duration, network request duration, and ANR), so that you can perform statistical analysis based on dimensions such as the app version, device type, device model, and region. In addition, information is collected to calculate the number of unique devices affected by performance issues based on AAIDs and help you analyze and locate an issue reported by a single user. In this way, you can improve app performance, thereby enhancing user experience. | Information storage: N/A. |
| Analytics | Android: Please refer to the related data processing information. HarmonyOS (Java SDK): Please refer to the related data processing information. HarmonyOS (JavaScript): Please refer to the related data processing information. iOS: Please refer to the related data processing information. macOS: Please refer to the related data processing information. Web: Please refer to the related data processing information. Quick App: Please refer to the related data processing information. Quick Game: Please refer to the related data processing information. WeChat mini-program: Please refer to the related data processing information. | ||
| Push Kit | Android:Please refer to the related data processing information. HarmonyOS (Java SDK): Please refer to the related data processing information. | ||
| Site Kit | Please refer to the related data processing information. | ||
| Map Kit | Please refer to the related SDK Privacy Statement. | ||
| Health Kit | Please refer to the related data processing information. | ||
| ML Kit | Android:Please refer to the related SDK Privacy and Security Statement. iOS: Please refer to the related data processing information. | ||
| Awareness Kit | Please refer to the related data processing information. | ||
| Nearby Service | Please refer to the related data processing information. | ||
| FIDO | Please refer to the related data processing information. | ||
| Wallet Kit | Please refer to the related data processing information. | ||
| Keyring | Please refer to the related data processing information. | ||
| AR Engine | Please refer to the related data processing information. | ||
| Scene Kit | Please refer to the related data processing information. | ||
| Search Kit | Please refer to the related data processing information. | ||
| Audio Editor Kit | Please refer to the related SDK Privacy Statement. | ||
| Video Editor Kit | Please refer to the related SDK Privacy Statement. | ||
| Dynamic Tag Manager | Android:Please refer to the related SDK Privacy and Security Statement. Web:Please refer to the related data processing information. iOS:Please refer to the related SDK Privacy and Security Statement. | ||
How to Clear End User's Personal Data
1) The Customer can integrate the Auth SDK into their app to provide the function of deleting the End User's account. When the End User deletes their account, data will be deleted in from the Auth Service server of AppGallery Connect.
For details, please refer to the development guide of deleteUser.
2) The Customer can delete any End User's account in AppGallery Connect. Then data related to that End User will be deleted.
3) The Customer can delete their project that includes the app used by the End User in AppGallery Connect or delete their HUAWEI ID. Then data related to the End User who was registered through the Customer's app will be deleted.
How to Export an End User's Personal Data
1) The Customer can integrate Auth SDK in to their app to provide the function of exporting the personal data of the End User. The Customer can obtain all End User data by calling getCurrentUser. Then the Customer can determine what personal data to display to the End User and how to display the data.
For details, please refer to the development guide of getCurrentUser.
2) The Customer can integrate Auth Server SDK in to their server to export all End User data by calling the exportUserData function of the AGCExportServe class. (This function has not been released and is coming soon.)
Open Testing
How to Clear an End User's Personal Data
The Customer can delete End Users accounts one by one or by batch in AppGallery Connect:
• Deleting an account: Go to Users and permissions > List Management > User list. On the page that is displayed, all open test users are displayed. Click Edit for a specific user and delete the user.
• Deleting accounts in batches: Go to Users and permissions > List Management > User list. On the page that is displayed, all open test users are displayed. Select accounts to be deleted and delete them by batch.
How to Export an End User's Personal Data
The Customer can query End User information in AppGallery Connect. To do so, Go to Users and permissions > List Management > User list. On the page that is displayed, all open test users are displayed. Click Edit to view End User information.
Prediction
How to Clear an End User's Personal Data
For details, please refer to the personal data processing of Analytics Kit.
How to Export an End User's Personal Data
For details, please refer to the personal data processing of Analytics Kit.
How to Enable/Disable the Function of Collecting User Data Reported by an App
For details, please refer to the personal data processing of Analytics Kit.
If the Prediction service is required for fulfilling other data subject rights of End Users, click here to apply for assistance.