WeChat login and sharing involve device, network and shared-content data
For WeChat login or sharing in-app content with WeChat friends or Moments, the list identifies Shenzhen Tencent Computer Systems Co., Ltd.’s WeChat SDK as automatically collecting device identifiers (IMEI, Android ID and hardware serial number), the device MAC address, WLAN access points such as SSID and BSSID, shared images or content, and associated IDs. These are the information categories listed for those login and sharing uses.
Supporting quotations
WeChat SDK
Purpose of Use: WeChat login and helping users share content to third-party applications
Personal Information Involved: Device identifiers (IMEI, Android ID, hardware serial number / Serial), device MAC address, WLAN access points (such as SSID, BSSID), shared images or content, and associated IDs
Collection Method: Collected automatically by the SDK
Use Scenario: Used for WeChat login, or when the user needs to share in-app content with WeChat friends or Moments
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Sharing to Xiaohongshu involves device details and shared content
When you share in-app content to Xiaohongshu, the list identifies Xingyin Information Technology (Shanghai) Co., Ltd.’s SDK as automatically collecting operating system, system version, device model, and the shared images or content to support sharing to that platform.
Supporting quotations
Xiaohongshu Open SDK
Purpose of Use: Helping users share content to third-party applications
Personal Information Involved: Device information (operating system, system version, device model) and shared images or content
Collection Method: Collected automatically by the SDK
Use Scenario: Used when the user needs to share in-app content to the Xiaohongshu platform
Third-Party Entity: Xingyin Information Technology (Shanghai) Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Quick login and phone verification involve identifiers, precise location and software lists
For quick login or mobile phone number verification, the list identifies Shenzhen Hexun Huagu Information Technology Co., Ltd.’s Jiguang SDK as automatically collecting device identifiers, hardware details, operating system information, network information, precise location, and lists of installed and running software. The listed identifiers include IMEI, IDFA, Android ID, GAID, MAC, OAID, IMSI, MEID, UAID and ICCID; network information includes carrier, base station, IP and WiFi/SSID/BSSID details. The stated purposes are one-click login, number verification and security verification for app users.
Supporting quotations
Jiguang SDK
Purpose of Use: Providing APP users with one-click login, number verification, and security verification services
Personal Information Involved: Device identifiers (including IMEI, IDFA, Android ID, GAID, MAC, OAID, IMSI, MEID, UAID, ICCID), device hardware information (including device model, device screen resolution, device hardware manufacturer, device product name), operating system information (including operating system version, system name, system language), network information (including network type, carrier name, base station information, IP address, WiFi information, SSID, BSSID), precise location information, and software list information (including the list of installed software and the list of running software).
Collection Method: Collected automatically by the SDK
Use Scenario: Used when the user chooses quick login or undergoes mobile phone number verification
Third-Party Entity: Shenzhen Hexun Huagu Information Technology Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Huawei notifications involve device identifiers and network information
For app notifications, update reminders and other messages to Huawei phone users, Huawei Device Co., Ltd.’s push SDK is listed as automatically collecting device and network information. Device information includes model, name, SIM card serial number and identifiers IMEI, IMSI, Android ID, IDFA and OAID. This entry concerns push notifications for Huawei phones.
Supporting quotations
Huawei Push Service SDK
Purpose of Use: Push notifications for Huawei phones
Personal Information Involved: Device information [including: device model, device name, SIM card serial number, unique device identifiers (IMEI, IMSI, Android ID, IDFA, OAID)] and network information
Collection Method: Collected automatically by the SDK
Use Scenario: Used when pushing app notifications, update reminders, and other messages to Huawei phone users
Third-Party Entity: Huawei Device Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Honor notifications involve device identifiers and network information
For app notifications, update reminders and other messages to Honor phone users, Honor Device Co., Ltd.’s push SDK is listed as automatically collecting device and network information. Device information includes model, name, SIM card serial number and identifiers IMEI, IMSI, Android ID, IDFA and OAID. This entry concerns push notifications for Honor phones.
Supporting quotations
Honor Push Service SDK
Purpose of Use: Push notifications for Honor phones
Personal Information Involved: Device information [including: device model, device name, SIM card serial number, unique device identifiers (IMEI, IMSI, Android ID, IDFA, OAID)] and network information
Collection Method: Collected automatically by the SDK
Use Scenario: Used when pushing app notifications, update reminders, and other messages to Honor phone users
Third-Party Entity: Honor Device Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
OPPO notifications involve application details and in-app identifiers
For app notifications, update reminders and other messages to OPPO phone users, Guangdong OPPO Mobile Communications Co., Ltd.’s SDK is listed as automatically collecting basic application information (MCS package name, application version and OPUSH SDK version) and in-app device identifiers listed as RegistraterID, appKey and appSecret. The stated purpose is push notifications for OPPO phones.
Supporting quotations
OPPO Push Service SDK
Purpose of Use: Push notifications for OPPO phones
Personal Information Involved: Basic application information (MCS application package name, application version number, OPUSH SDK version number) and in-app device identifiers (RegistraterID, appKey, appSecret)
Collection Method: Collected automatically by the SDK
Use Scenario: Used when pushing app notifications, update reminders, and other messages to OPPO phone users
Third-Party Entity: Guangdong OPPO Mobile Communications Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
VIVO notifications involve network information and storage permission
For app notifications, update reminders and other messages to VIVO phone users, Vivo Mobile Communications Co., Ltd.’s SDK is listed as collecting information automatically. The information entry names network information and permission to read storage containing photos, media and other files; it does not establish that all such files are transmitted. The stated purpose is push notifications for VIVO phones.
Supporting quotations
VIVO Push Service SDK
Purpose of Use: Push notifications for VIVO phones
Personal Information Involved: Network information and the permission to read storage (photos, media, and other files)
Collection Method: Collected automatically by the SDK
Use Scenario: Used when pushing app notifications, update reminders, and other messages to VIVO phone users
Third-Party Entity: Vivo Mobile Communications Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Xiaomi notifications involve location, device and network information
For app notifications, update reminders and other messages to Xiaomi phone users, Xiaomi Mobile Software Co., Ltd.’s SDK is listed as collecting information automatically. The entry names device information, geographic location, network information and permission to read storage containing photos, media and other files. It does not specify location precision or establish that every stored file is transmitted.
Supporting quotations
Xiaomi Push Service SDK
Purpose of Use: Push notifications for Xiaomi phones
Personal Information Involved: Device information, geographic location, network information, and the permission to read storage (photos, media, and other files)
Collection Method: Collected automatically by the SDK
Use Scenario: Used when pushing app notifications, update reminders, and other messages to Xiaomi phone users
Third-Party Entity: Xiaomi Mobile Software Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
China Mobile authentication involves phone, network and device details
China Mobile Internet Co., Ltd.’s authentication SDK is listed as automatically collecting network type and address, carrier type, the device’s phone number, phone device type, operating system and hardware manufacturer. The stated purposes are identifying the phone number for quick login or number verification, issue inquiry, analysis and risk control. Its use scenario covers a China Mobile number used for one-click login or verification, or business risk control.
Supporting quotations
China Mobile Authentication
Purpose of Use: Identifying the user's mobile phone number for quick login/number verification, issue inquiry, analysis, and risk control
Personal Information Involved: Network type, network address, carrier type, the phone number of the device, phone device type, phone operating system, and hardware manufacturer
Collection Method: Collected automatically by the SDK
Use Scenario: Used when the user uses a China Mobile phone number for one-click login or number verification, or for business risk control
Third-Party Entity: China Mobile Internet Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
China Unicom authentication includes SIM status and phone details
China United Network Communications Co., Ltd.’s authentication SDK is listed as automatically collecting network type and address, carrier type, information about the device’s phone number, SIM card status, device type, operating system and hardware manufacturer. The purposes are identifying the phone number for quick login or number verification, issue inquiry, analysis and risk control. The use scenario covers a China Unicom number used for one-click login or verification, or business risk control.
Supporting quotations
China Unicom Authentication
Purpose of Use: Identifying the user's mobile phone number for quick login/number verification, issue inquiry, analysis, and risk control
Personal Information Involved: Network type, network address, carrier type, information about the phone number of the device, SIM card status, phone device type, phone operating system, and hardware manufacturer
Collection Method: Collected automatically by the SDK
Use Scenario: Used when the user uses a China Unicom phone number for one-click login or number verification, or for business risk control
Third-Party Entity: China United Network Communications Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
China Telecom authentication includes subscriber identity and process information
Tianyi Digital Life Technology Co., Ltd.’s authentication SDK is listed as automatically collecting international mobile subscriber identity, application process information, registered and device phone numbers, network connection type, status and address, carrier type, device type and manufacturer, and operating system type and version. The purposes are identifying the phone number for quick login or number verification, issue inquiry, analysis and risk control. Its use scenario covers a China Telecom number used for one-click login or verification, or business risk control.
Supporting quotations
China Telecom Authentication
Purpose of Use: Identifying the user's mobile phone number for quick login/number verification, issue inquiry, analysis, and risk control
Personal Information Involved: International mobile subscriber identity, application process information, registered mobile phone number, the phone number of the device, network connection type, network status information, network address, carrier type, phone device type, phone device manufacturer, and phone operating system type and version
Collection Method: Collected automatically by the SDK
Use Scenario: Used when the user uses a China Telecom phone number for one-click login or number verification, or for business risk control
Third-Party Entity: Tianyi Digital Life Technology Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Precision marketing involves identifiers, precise location and app information
For data analysis and precision marketing activities, Beijing Volcano Engine Technology Co., Ltd.’s Growth Marketing Suite SDK is listed as collecting data automatically for automated marketing management. The non-exhaustive information list includes Android ID and OAID, hardware and operating system details, network information (network type, carrier, base station, IP address, WiFi, SSID and BSSID), precise location, application information and device MAC address.
Supporting quotations
Growth Marketing Suite SDK
Purpose of Use: Automated marketing management
Personal Information Involved: Device identifiers (Android ID、OAID), device hardware information, operating system information, network information (including network type, carrier name, base station information, IP address, WiFi information, SSID, BSSID), precise location information, application information, device MAC address, etc.
Collection Method: Collected automatically by the SDK
Use Scenario: Used when conducting data analysis and precision marketing activities
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Advertising conversion analysis involves router and device identifiers
Beijing Ocean Engine Network Technology Co., Ltd.’s Ocean Engine Conversion SDK is listed as automatically collecting WiFi router information, MAC address (BSSID), device MAC address and device identifiers. The stated purpose is automated marketing management, with use when tracking advertising effectiveness and analyzing conversion paths.
Supporting quotations
Ocean Engine Conversion SDK
Purpose of Use: Automated marketing management
Personal Information Involved: WiFi router, MAC address (BSSID), device MAC address, and device identifiers
Collection Method: Collected automatically by the SDK
Use Scenario: Used when tracking advertising effectiveness and analyzing conversion paths
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Anomaly detection involves device, behavior, sensor, app and permission information
For detecting abnormal application behavior and preventing malicious operations, Hangzhou NetEase Zhiqi Technology Co., Ltd.’s NetEase Yidun SDK is listed as collecting information automatically. Its device information includes serial number, MEID, IDFV, brand, name, model, system type, settings and version. Logs include IP address, router identifiers, carrier and connection details, and power-on, click and installation behavior. The entry also lists motion, position and ambient sensors; app identifiers, name, version, signature and process name; and permissions involving the local network, network status, WiFi status and precise geolocation. The purpose is application anomaly detection; listing permissions does not itself establish collection of every item accessible through them.
Supporting quotations
NetEase Yidun SDK
Purpose of Use: Application anomaly detection
Personal Information Involved: Device information (including unique device identification codes (device serial number, MEID, IDFV), device brand, device name, device model and device system type, detailed settings and version information), log information (including network-related information: device IP address, router identifiers (BSSID, SSID, MAC), network carrier information, network connection type and status; operation information: end-user power-on, click, and installation behavior information, sensor information (motion sensors, position sensors, ambient sensors), application information (including the Bundle ID of iOS applications/the application package name of Android applications, application name and version number, application signature information, application process name); and permissions (including local network permission, network information status, WiFi status, and precise geolocation).
Collection Method: Collected automatically by the SDK
Use Scenario: Used when detecting abnormal application behavior and preventing malicious operations
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Login verification involves IP address and OAID
When human-machine verification is required during login, Wuhan Jiyi Network Technology Co., Ltd.’s GeeTest Verification SDK is listed as automatically collecting IP address and OAID. The purpose is human-machine verification for mobile phone login.
Supporting quotations
GeeTest Verification SDK
Purpose of Use: Human-machine verification for mobile phone login
Personal Information Involved: IP address and OAID
Collection Method: Collected automatically by the SDK
Use Scenario: Used when human-machine verification is required during user login
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Voice and video calls involve audio, camera, device and network information
For in-app voice or video call features, Shenzhen Tencent Computer Systems Co., Ltd.’s Tencent RTC SDK is listed as collecting information automatically. Its entry lists WiFi status, system properties, device model, IP address, camera, audio recording, acceleration sensor, the graphics hardware PCI ID, CPU and GPU information, and audio information. The stated purpose is voice and video conversations.
Supporting quotations
Tencent Real-Time Communication (Tencent RTC) SDK
Purpose of Use: Voice conversations and video conversations
Personal Information Involved: Wi-Fi status, system properties, device model, IP address, camera, audio recording, acceleration sensor, PCI ID of the graphics card hardware device, CPU information, GPU information, and audio information
Collection Method: Collected automatically by the SDK
Use Scenario: Used when providing voice call or video call features within the application
Third-Party Entity: Shenzhen Tencent Computer Systems Co., Ltd.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
App startup monitoring involves device details, activity and diagnostic logs
When the application starts, Beijing Volcano Engine Technology Co., Ltd.’s APM SDK is listed as automatically collecting information to monitor device anomalies and performance. Device information includes time zone, running-thread count, CPU frequency/model/architecture, MCC/MNC, Android ID, brand, operating system API version, battery, network traffic, ABI and ROM. Application information includes version and package name, process start and crash times, crash thread name, active page names, all current-process thread stacks, service logs, file names and sizes, disk size and an fd list. User ID, carrier and network access mode are also listed. This entry does not say application file contents are collected.
Supporting quotations
Volcano Engine APM SDK
Purpose of Use: Monitoring device anomalies and performance data
Personal Information Involved: Device information: system time zone, number of running threads, CPU information (frequency, model, architecture), mobile country code (MCC), mobile network code (MNC); Android ID, device brand, operating system API version, battery level, network traffic, device ABI, ROM; application information: application version, application package name, process start time, crash time, crash thread name, names of pages that have been active, thread stacks of all threads in the current process, application service log information, application file names, application file sizes, disk size; fd list; system and network identification information: user ID, carrier information, network access mode.
Collection Method: Collected automatically by the SDK
Use Scenario: When the application starts, monitoring device anomalies and performance data
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Voluntarily uploaded audio is used for transcription
The list identifies Beijing Volcano Engine Technology Co., Ltd.’s Intelligent Voice Technology API for transcribing audio-file content. The information involved is audio files voluntarily uploaded by the user, and the use scenario is parsing those uploaded files. Its collection method is user upload.
Supporting quotations
Volcano Engine Intelligent Voice Technology API
Purpose of Use: Transcribing the content of audio files
Personal Information Involved: Audio files uploaded by the user
Collection Method: Voluntarily uploaded by the user
Use Scenario: Content parsing of audio files uploaded by the user
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Milv Contract Review involves files and contracts you upload
When you use Kimi+ “Milv Contract Review” to review and modify contracts, the list identifies Beijing Milv Intelligent Technology Co., Ltd.’s Wuyouwulv API as involving files, contracts and other materials voluntarily uploaded by you. The stated purpose is helping users use that Kimi+ feature.
Supporting quotations
Wuyouwulv Intelligent Contract Review API
Purpose of Use: Helping users use the "Milv Contract Review" Kimi+
Personal Information Involved: Files, contracts, and other materials uploaded by the user
Collection Method: Voluntarily uploaded by the user
Use Scenario: Used when the user uses the Kimi+ "Milv Contract Review" to review and modify contracts
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
WeChat Pay involves account identifiers and payment details
For WeChat Pay on integrated portals such as the web client, the list identifies Tenpay Payment Technology Co., Ltd. and information including WeChat account identifiers, network IP address, order amount, transaction number and other payment information. The collection method is information provided by the user during payment and collected by the platform with authorization. The listed use scenarios are querying payment information, customer service and purchases of goods and services.
Supporting quotations
WeChat Pay
Purpose of Use: Helping users use the WeChat Pay service on portals integrated with WeChat Pay, such as the web client
Personal Information Involved: WeChat account identifiers, network IP address, order amount, transaction number, and other payment information
Collection Method: Provided by the user during payment and collected by the platform with authorization
Use Scenario: Querying payment information, providing customer service, and purchasing goods and services
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Voice input involves audio collection for transcription
When you make voice input, Tencent Cloud Computing (Beijing) Co., Ltd.’s Speech Recognition SDK is listed as automatically collecting audio information. Its stated purpose is recognizing the audio data you upload as text when you use voice transcription; this entry’s automatic collection method remains tied to that voice-input scenario.
Supporting quotations
Tencent Cloud Speech Recognition SDK
Purpose of Use: Recognizing the audio data uploaded by the user as text when the user uses voice transcription
Personal Information Involved: Audio information
Collection Method: Collected automatically by the SDK
Use Scenario: Used when the user makes voice input
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
AppsFlyer marketing and fraud prevention involve overseas users’ data
For data analysis and precision marketing, AppsFlyer LTD.’s iOS/Android SDK is listed as automatically collecting information of overseas users. The non-exhaustive list includes device identifiers, hardware and operating system details, network information (network type, carrier, base station, IP address, WiFi, SSID and BSSID), precise location and application information. Its purposes are automated marketing management and advertising fraud prevention. The entry uses “overseas users” without defining that group’s geographic boundary.
Supporting quotations
AppsFlyer SDK (iOS/Android)
Purpose of Use: Automated marketing management and advertising fraud prevention
Personal Information Involved: Device identifiers, device hardware information, operating system information, network information (including network type, carrier name, base station information, IP address, WiFi information, SSID, BSSID), precise location information, application information, etc. of overseas users.
Collection Method: Collected automatically by the SDK
Use Scenario: Used when conducting data analysis and precision marketing activities
Third-Party Entity: AppsFlyer LTD.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Alipay payment services involve device identifiers, sensors and network details
For Alipay services on payment portals, Alipay Payment Technology Co., Ltd.’s client SDK entry lists AndroidID, sensor information (sensor list), screen density, carrier information, WiFi parameters, network type and OAID. Its stated collection method is information provided by the user during payment and collected by the platform with authorization. The use scenarios are querying payment information, customer service and purchasing goods and services.
Supporting quotations
App Alipay Client SDK
Purpose of Use: Helping users use Alipay services on payment service portals
Personal Information Involved: AndroidID, sensor information (sensor list), device screen density, carrier information, WiFi parameters, network type, and OAID
Collection Method: Provided by the user during payment and collected by the platform with authorization
Use Scenario: Querying payment information, providing customer service, and purchasing goods and services
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Fraud detection involves location, device identifiers, apps, processes and sensors
Zhejiang Xiaodun Future Technology Co., Ltd.’s Xiaodun Device Fingerprint SDK is listed as automatically collecting information for risk identification to ensure secure and normal operation, with use in intercepting fraudulent services and performing data statistics. The list includes IDFA, Android ID, OAID (including VAID and AAID), MAC address, WiFi list and router identifiers, device type/model/system, approximate and precise location, application list, running processes, network mode and software version. It also names light, gravity, magnetic field, acceleration, gyroscope and heart rate sensors, plus device information related to the sensor list. It does not specify what readings each sensor supplies.
Supporting quotations
Xiaodun Device Fingerprint SDK
Purpose of Use: Risk identification to ensure the secure and normal operation of products and services
Personal Information Involved: Mobile terminal device identifiers IDFA, Android ID, OAID (including VAID, AAID), MAC address, WiFi list, wireless router identifiers (BSSID, SSID), device type, device model, system type, approximate location information, precise location information, application list, information on running processes, network mode, device software version number, sensors (light sensor, gravity sensor, magnetic field sensor, acceleration sensor, gyroscope sensor, heart rate sensor), and device information related to the sensor list
Collection Method: Collected automatically by the SDK
Use Scenario: Intercepting fraudulent services and performing data statistics
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
Firebase analytics and marketing involve overseas users’ data
Google LLC’s Firebase Analytics SDK for iOS/Android is listed as automatically collecting overseas users’ information for automated marketing management and product-experience optimization. The use scenario is data analysis and precision marketing. The non-exhaustive data list includes device identifiers, hardware and operating system information, network details (network type, carrier, base station, IP address, WiFi, SSID and BSSID), precise location and application information. “Overseas users” is not geographically defined in this entry.
Supporting quotations
Google Firebase Analytics SDK (iOS / Android)
Purpose of Use: Automated marketing management and optimizing the product experience
Personal Information Involved: Device identifiers, device hardware information, operating system information, network information (including network type, carrier name, base station information, IP address, WiFi information, SSID, BSSID), precise location information, application information, etc. of overseas users
Collection Method: Collected automatically by the SDK
Use Scenario: Used when conducting data analysis and precision marketing activities
Third-Party Entity: Google LLC
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.
Sharing & Disclosure · Company practice
App Store refund requests involve sending membership usage data to Apple
When you request an in-app-purchase refund through the App Store, the list says consumption and usage information is transmitted to Apple Inc. via a server API for the App Store to review and process the request. The non-exhaustive information list includes membership quota usage, consumption status, usage duration and whether there is a free trial period. This entry describes information sharing for refund review; it does not promise a refund.
Supporting quotations
Apple App Store Server API
Purpose of Use: Providing consumption and usage information to the App Store for the App Store to review and process refund requests
Personal Information Involved: Membership quota usage, consumption status, usage duration, whether there is a free trial period, etc.
Collection Method: Transmitted via server API
Use Scenario: When the user applies for a refund of an in-app purchase through the App Store
Third-Party Entity: Apple Inc.
Not stated here
The linked third-party policy is not supplied; its additional terms are not analyzed.