Unity Minigame Host SDK Privacy Policy
Effective Date: March 6, 2026
Last Updated: March 6, 2026
Introduction
Welcome. You ("App Developer") have chosen to use the host software development kit ("SDK") provided by U3D Technology (Shanghai) Co., Ltd. ("we", "us", or "our"). This SDK is intended to enable your mobile application ("Host App") to load and run third-party minigames.
This Unity Minigame Host SDK Privacy Policy ("Policy") explains how this SDK processes the personal information of developers and end users ("Users"). Before registering for, integrating, or using this SDK, both App Developers and end users should read this Policy carefully. If you are a developer, you should ensure that you fully understand and agree to this Policy before integrating this SDK, and you should make this Policy publicly available to end users so that they can read and understand it before using any products and/or services developed, adapted, integrated, or loaded by you with this SDK. If you do not agree to this Policy or cannot fulfill the applicable personal information protection obligations described in this Policy, you must immediately stop integrating and using this SDK. At the same time, you should integrate this SDK and process end-user personal information only after obtaining end-user consent.
If you are under the age of 14, stop using the service immediately. If you are a parent or guardian and become aware that your child has provided us with personal information, contact us immediately. Once we learn that we have collected personal information from any person under the age of 14 ("child") without parental or guardian consent, we will take steps to delete that data from our servers.
Important notice for App Developers:
- You are responsible for ensuring that your Host App complies with all applicable laws and regulations throughout the integration and use of this SDK, including but not limited to creating and publishing a privacy policy regarding personal information protection.
- You must clearly and completely disclose in your Host App's Privacy Policy how this SDK collects and processes users' personal information, and provide a valid link to this Policy.
- You must not initialize this SDK until you have clearly and truthfully disclosed the SDK's personal information processing activities to users in a legally compliant manner, prompted users to read this Policy, and obtained their consent to your Host App Privacy Policy. If specific SDK features described below require separate consent, you must obtain the user's express authorization before calling those features.
- You must ensure that the above disclosures are consistent with this Policy. Otherwise, we reserve the right to require you to revise the relevant disclosure documents. If user complaints or other adverse events arise from inaccurate or incorrect disclosure on your part, we reserve the right to stop providing this SDK to you and seek compensation for any losses caused to us.
- You must provide end users with an easy-to-use mechanism that satisfies legal requirements for exercising their rights, and inform end users how to access, copy, modify, and delete personal information, withdraw consent, restrict processing, transfer personal information, obtain a copy of personal information, and close accounts.
1. How This SDK Collects and Uses Personal Information
- To provide the SDK's functions, this SDK needs to collect and use the following user information in specific scenarios:
| Operating System | Personal Information Types and Fields | Purpose |
|---|---|---|
| Android | ANDROID_ID, OAID, userID | To provide, measure, and optimize advertising effectiveness in minigames |
| iOS | IDFV, userID | To provide, measure, and optimize advertising effectiveness in minigames |
| PC | Hostname, userID | To provide, measure, and optimize advertising effectiveness in minigames |
| Android, iOS | SDK and app information (SDK version, Host App AppId) | To ensure compatibility between the SDK and the Host App and provide stable services |
| Android, iOS | Network information (client IP address) | To establish and maintain the necessary network communication session between the SDK and the host server |
| Android, iOS | Session identifiers (HostSessionId, GameSessionId) | To create, manage, and verify the technical sessions required to run the host and minigames |
| Android, iOS | Ad display information (ad shown, ad closed) | To provide, measure, and optimize advertising effectiveness in minigames |
This SDK also collects the following additional information, which usually does not directly identify a user.
To ensure the secure and stable operation of this SDK and to analyze and optimize minigame performance and startup experience, we collect the following technical diagnostic information:
| Operating System | Information Types and Fields | Purpose |
|---|---|---|
| Android, iOS | Performance and diagnostic data (frame rate, CPU usage, memory usage, stutter information, and rendering data such as drawcall, trigonometric, and Vertex) | To collect runtime performance metrics for performance analysis and experience optimization |
| Android, iOS | Runtime and startup data (host and game start, pause, and exit events, as well as timing information for each startup stage such as resource loading, rendering preparation, WASM download/compilation, and first-frame rendering) | To analyze and optimize the minigame startup process and loading time, and improve user experience |
| Android, iOS | Network and error data (network request URLs for game resources, package size, request results, error information, as well as various runtime exception logs and host runtime logs) | To optimize the network download module, diagnose and fix crashes, compatibility issues, and adaptation problems during SDK operation, and improve SDK stability |
To support in-game payment and settlement, when a user initiates a purchase or conducts a payment transaction in a minigame, this SDK collects the following payment-related information in order to verify transaction validity, process settlement, and ensure transaction security:
| Operating System | Information Types and Fields | Purpose |
|---|---|---|
| Android, iOS | Transaction and order information (order ID, event type such as payment initiation or payment success, platform or payment channel, total order amount, exchange rate) | To identify and track specific transaction orders and verify payment status |
| Android, iOS | Product details (product ID, product name, product type, quantity) | To record what the user purchased so that items or services can be delivered correctly in the game and for data analysis |
- To provide the SDK's functions, the SDK requires the following permissions:
System Permissions Required for Basic Operation
To ensure baseline SDK operation, network connection quality, and account security, the SDK needs to request the following system permissions during initialization or runtime. If you or the user refuses authorization, the SDK may not be able to provide services properly:
| Operating System | Permission Name | Description | Purpose |
|---|---|---|---|
| Android | READ_PHONE_STATE | Read phone state | For account security verification, risk control, and ensuring uniqueness of user identity |
| Android | ACCESS_NETWORK_STATE | Access network state | To optimize game resource download strategy and network connection quality |
| Android | ACCESS_WIFI_STATE | Access Wi-Fi state | To optimize game resource download strategy and network connection quality |
| iOS | NSLocalNetworkUsageDescription | Local network usage description | To optimize game resource download strategy and network connection quality |
System Permissions Required for Specific Game Features
This SDK provides a rich set of game capability integrations. These permissions are not required by default for the SDK to run. The SDK requests the relevant permission through the Host App only when the specific minigame being run needs to use the corresponding hardware or feature, such as a camera for AR gameplay or a microphone for voice chat.
Please note as an App Developer: for the permissions below, you should ensure that compliant permission prompts are configured at the Host App level, and you may allow the SDK to invoke the related interfaces only after obtaining separate user consent. If the user refuses, only that specific minigame feature will be affected; other core SDK services should remain unaffected.
The system permissions we may call and their purposes are as follows:
| Feature Category | Permission Name (Android) | Permission Name (iOS) | Purpose and Scenario |
|---|---|---|---|
| Camera | CAMERA | NSCameraUsageDescription | Photo capture: used when the minigame needs to access the current camera feed or take pictures |
| Microphone | RECORD_AUDIO | NSMicrophoneUsageDescription | Voice interaction: used when the minigame needs to capture live audio, such as in-game voice chat or recording |
| Location | ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION | NSLocationWhenInUseUsageDescription | Location services: requested only when the minigame involves location-based gameplay and needs device location information |
| Bluetooth | BLUETOOTH | NSBluetoothAlwaysUsageDescription | Device connection: used when the minigame needs to obtain Bluetooth status or connect to nearby Bluetooth devices |
| Sensors | Usually no special permission required | NSMotionUsageDescription | Motion control: used when the minigame needs acceleration or gyroscope data for motion-based interaction |
Additional Notes:
- Android systems: Some sensors, such as the gyroscope and accelerometer, usually do not require runtime permission under standard Android systems. We access such data only when the game calls related APIs such as
startGyroscope. - Permission management: Users may disable the above permissions at any time in device Settings. After disabling them, only the specific minigame features that depend on the permission will stop working. Other minigame functions and the normal operation of the Host App will not be affected.
2. How This SDK Shares and Discloses Information
This SDK is a tool embedded in the Host App. We share information only in the following limited circumstances:
- Sharing with the Host App (that is, you): Information collected by the SDK, such as session IDs and crash logs, may be exchanged locally between the SDK and the Host App so that you can provide functions to users or troubleshoot issues.
- Sharing with minigame providers: When a user launches a minigame, the SDK may share information necessary to run that minigame, such as the Game Session ID, the user's identifier in the Host App as provided by you, and minigame runtime performance analytics data, with the minigame developer in order to enable minigame functionality.
- Other circumstances: Except for the situations described above and as otherwise required by laws and regulations, this SDK will not share or transfer users' personal information to any third party. If personal information needs to be transferred due to merger, split, dissolution, bankruptcy declaration, or similar reasons, we will inform end users of the recipient's name and contact information and require the recipient to continue performing the obligations of a personal information processor. If the recipient changes the original purpose or method of processing, we will require the recipient to obtain user consent again. Where required by laws, legal procedures, litigation, or compulsory requests from government authorities, we may publicly disclose end-user personal information.
3. End-User Rights
If you are a developer, you should provide end users with clear means to access, copy, correct, supplement, delete, and transfer personal information, withdraw consent, restrict personal information processing, obtain a copy of personal information, and close accounts.
We take end users' rights to manage their personal information seriously and strive to help them manage their personal information, including rights of access, copying, correction, supplementation, deletion, withdrawal of consent, transfer, restriction of processing, obtaining a copy, account closure, and privacy settings.
For personal information processing activities based on end-user consent, end users have the right to withdraw that consent. If you are an end user, please understand that certain business functions or services can only be completed if you provide the information required for those services. After you withdraw consent, we will no longer be able to provide the corresponding functions or services, and we will no longer process the corresponding personal information. Your decision to withdraw consent does not affect any personal information processing previously carried out based on your authorization.
4. Information Security and Storage
We undertake to strictly comply with applicable laws and regulations and adopt necessary and appropriate security measures to store, manage, and transmit users' personal information, ensure the accuracy and integrity of such personal information, and prevent tampering, disclosure, or loss.
We use specific physical, administrative, and technical safeguards designed to protect the personally identifiable information we collect from accidental or unlawful destruction, loss, unauthorized alteration, disclosure, access, misuse, and any other unlawful form of personal information processing. We use reasonable and feasible means, including encryption technologies no less protective than those generally adopted in the industry, to protect end-user personal information, and we use security mechanisms to prevent malicious attacks. We have established management systems, processes, and organizational measures dedicated to personal information security. We also regularly assess and update these measures to ensure their effectiveness in protecting users' personal information and preventing unauthorized access, use, or disclosure.
Although we have taken the above reasonable and effective measures and complied with relevant legal requirements, due to technical limitations and the possible existence of various malicious methods, we will do our best to ensure the security of the personal information we process. If a personal information security incident unfortunately occurs, we will notify developers by email in a timely manner as required by law.
In principle, personal information collected and generated within the territory of the People's Republic of China is stored within China in accordance with applicable legal requirements. Where necessary, we may provide your personal information outside China only for purposes necessary to perform our contract with you or on another lawful basis for processing. In such cases, we will assess the situation and make our best efforts to ensure that your personal information receives protection equivalent to that provided within China, as required by Chinese law. If business needs require us to transfer your personal information overseas, we will comply with laws, regulations, and regulatory requirements, inform you in relevant service agreements or authorization agreements on specific feature pages of the overseas recipient's name, contact information, processing purpose, processing method, categories of personal information, and the ways and procedures for exercising related rights against the overseas recipient, and obtain your separate consent where applicable. Before providing personal information overseas, we will take measures such as security assessments, personal information protection certification by professional institutions, or entering into standard contracts formulated by the national cyberspace authority with overseas recipients, so as to satisfy the legal conditions for cross-border provision of personal information.
We retain your personal information only for the period necessary to achieve the purpose of processing or to meet legal requirements. The retention period depends on the purposes for which we collected and used the data and the time we need to keep it to comply with applicable laws, including any legal, regulatory, tax, accounting, or reporting requirements. Where personal information is retained solely to meet legal requirements, we will take measures to prevent further processing. Once personal information is no longer necessary for the purpose for which it was collected, we will delete it.
5. Children's Privacy
This SDK does not actively collect children's personal information.
You, as the App Developer, are responsible for preventing children from using any product and/or service that integrates this SDK, and you must not provide us with any child's personal information. If you become aware that you have provided us with any child's personal information, contact us immediately. We will take measures to delete such data from our servers.
6. Updates to This Policy
We reserve the right to update this Policy from time to time. If revisions to this Policy materially reduce end-user rights under this Policy, we will provide notice before the changes take effect, for example through website announcements. If you are an App Developer and the updated Policy changes how end-user personal information is processed, you should update your privacy policy in a timely manner and notify end users by pop-up and obtain their consent. If end users do not agree to accept this Policy, stop integrating this SDK.
You, as the App Developer, are responsible for reviewing updates to this Policy promptly and updating your Host App Privacy Policy accordingly to remain compliant.
7. Contact Us
If you have any questions, comments, or suggestions regarding this Policy or related matters, contact us using the following method. We will generally reply within fifteen business days:
Email: legal_china@unity.cn