Third-Party SDK and System Platform Services Notice

Last Updated: September 19, 2026
Effective Date: September 19, 2026

Shenzhen Fixon Information Technology Co., Ltd. (“we” or “Fixon”) integrates certain third-party software development kits (“SDKs”) and uses services provided by operating systems or app-store platforms in the Fixon Yaoyue mobile application to support app operation, sign-in, sharing, payments, and map-based location selection.

This Notice forms part of our Privacy Policy. The SDKs and platform services actually enabled vary by device, operating system, app version, region, and the features you use. Not every service listed below operates on every device. Except for components required for basic app operation, a service is invoked when you actively use the corresponding feature. Where a system permission such as camera or location access is required, we request authorization under the operating system’s rules.

The information below is based on Fixon’s current implementation, packaged components, and the providers’ published disclosures. Specific fields vary by operating system, SDK version, device capabilities, and permission status. A provider’s handling of information is also governed by its own rules.

1. DCloud App Engine (uni-app / HTML5+)

Provider: Digital Heaven (Beijing) Network Technology Co., Ltd. (“DCloud”)
Platforms: iOS and Android
Function and purpose: Provides the cross-platform runtime, page rendering, access to native capabilities, app stability, and fault-diagnosis support.
When and how used: Embedded as the App’s runtime and used while the App starts and runs. When you use camera, QR-code scanning, location, sharing, or payment features, Fixon calls the corresponding system capability or configured service through its interfaces.
Types of information processed: Local files you select or create; device and app information such as device brand, model, operating system, and app version; network information such as network type and IP address; app startup, runtime, and error logs; and, when available and permitted by the device or authorized by you, identifiers such as IMEI, Android ID, DEVICE_ID, IMSI, IDFA, and OAID.
Permissions: Internet and network-state access are required for basic operation. Camera, location, photo, or file permissions are requested only when you use the corresponding feature.
Related rules: DCloud App Engine Privacy Policy; DCloud Android Module Privacy Compliance Notice

Components bundled with the DCloud runtime

The DCloud App Engine may bundle open-source or low-level components required for basic operation, including Apache Weex (page and native-component rendering), Fresco, Glide, and android-gif-drawable (image or GIF loading, decoding, display, and caching), and OkHttp (network requests initiated by the App). These components support the runtime and App features and have no separate Fixon business purpose. Components that only render, decode, or cache data locally do not, for that reason alone, send personal information to their open-source maintainers. Networking components process request data as directed by the App, and destination servers receive necessary network information such as an IP address as part of a normal connection. The components and versions present depend on the installed package.

2. Mobile Security Alliance Unified Device Identifier SDK (MSA OAID SDK)

Provider: China Academy of Information and Communications Technology Tel Terminal Labs and the Mobile Security Working Committee
Platform: Android
Function and purpose: Integrated through the DCloud Android runtime to read OAID and related supplemental device identifiers on supported devices for anonymous device recognition, runtime compatibility, and security analysis.
When and how used: The Android runtime calls it on supported devices after you accept the Privacy Policy. Whether it is called depends on the installed package, device manufacturer, and operating-system version.
Types of information processed: OAID, VAID, AAID, and the app package name, signing information, or app-store App ID needed to generate or validate an identifier. According to the provider’s published policy, the SDK reads this information locally and does not itself store or transmit the data over a network.
Permissions: It does not independently request location, camera, or storage permission.
Related rules: MSA OAID SDK Privacy Policy; Compliance Notice

3. WeChat OpenSDK

Provider: Shenzhen Tencent Computer Systems Company Limited
Platforms: iOS and Android
Function and purpose: Enables WeChat authorization sign-in, WeChat Pay, and sharing content with WeChat contacts or Moments.
When and how used: Only when you actively choose WeChat sign-in, WeChat Pay, or WeChat sharing. The SDK communicates with the WeChat app or WeChat services.
Types of information processed: Authorization results, authorization codes, and an account identifier supplied by WeChat; order and payment parameters, transaction status, and payment results; text, links, images, or other content you choose to share; and network information or local files needed to complete the selected feature.
Permissions: Internet and network-state access are required. A local file is accessed only when you choose to share that file or content.
Scope: Sign-in, phone-number authorization, and payments in the WeChat Mini Program are provided by the Mini Program platform and are not an OpenSDK embedded in the App.
Related rules: WeChat Privacy Protection Guidelines

4. Alipay Payment SDK

Provider: Alipay (China) Network Technology Co., Ltd.
Platforms: iOS and Android
Function and purpose: Enables Alipay payments and supports the security and stable operation of accounts, transactions, and payment services.
When and how used: Only when you actively choose Alipay as the payment method. The SDK communicates with the Alipay app or Alipay services.
Types of information processed: Order number, product or transaction description, payment amount, signed payment parameters, and payment status and result; and device identifiers, IP address, network type, WLAN status, and carrier information required for payment security, risk detection, and network connectivity. Specific fields depend on the device platform and SDK version.
Permissions: Internet and network-state access are required. Fixon does not obtain your full bank-card number or Alipay account password through this SDK.
Scope: Payments in the Alipay Mini Program are provided by the Mini Program platform and are not made through a payment SDK embedded in the App.
Related rules: Alipay Payment SDK Privacy Notice

5. Tianditu JavaScript API v4 and Web Service API

Provider: National Geomatics Center of China, operator of the National Platform for Common Geospatial Information Services (“Tianditu”)
Platform: App pages that use map-based location selection
Function and purpose: Displays maps, searches for places, resolves an address from coordinates, and helps you select a location.
When and how used: When you open the location picker, search for a place, tap the map, or request your current location. The App loads the Tianditu JavaScript API over HTTPS and sends place-search or address-lookup requests to its web services.
Types of information processed: Place-search keywords you enter; the map center and coordinates you tap or select; current-location coordinates obtained with your permission and used for location selection or address lookup; and the IP address, network-request information, and application developer key included in requests.
Permissions: The App obtains your current location only after you use the feature and authorize access. Coordinates or search terms are sent to Tianditu when required to display a map, search for a place, or look up an address.
Website: Tianditu

6. System Platform Services (Not Embedded Third-Party SDKs)

The following capabilities are provided by the device operating system or app-store platform and are not separate third-party SDKs embedded in Fixon. They are listed to give you a complete view of the relevant information processing.

Provider: Apple Inc.
Function and purpose: Allows you to sign in to Fixon using your Apple Account.
When used: Only when you actively choose “Sign in with Apple.”
Types of information processed: The identity token returned by Apple, an app-specific account identifier, and any name or email information that you permit and Apple returns. Apple may also use account and device-use patterns for security and fraud prevention.
Related rules: Sign in with Apple & Privacy

6.2 Apple In-App Purchase (StoreKit)

Provider: Apple Inc.
Function and purpose: Completes membership or in-app product purchases, validates transactions, and restores eligible previous purchases.
When used: Only when you actively initiate a purchase or restore purchases on an iOS device.
Types of information processed: Product identifier, quantity, transaction identifier and status, transaction date, transaction receipt, and an account or order-correlation value supplied by the App. Apple handles the Apple Account and actual payment credentials; Fixon does not receive your complete bank-card details from StoreKit.
Related rules: Apple Privacy Policy

7. Your Choices, Updates, and Contacting Us

You may choose not to use WeChat sign-in, WeChat or Alipay payments, map-based location selection, or Apple platform services. The corresponding feature may then be unavailable, but features that do not depend on that service remain unaffected. You can also manage or withdraw camera, location, and similar permissions in your device settings.

SDKs and platform services may change as features, providers, or versions change. We will update this Notice to reflect applicable law and the services actually integrated. If a change materially affects your rights, we will notify you through an appropriate channel.

For details about how Fixon processes and protects personal information and how you may exercise rights such as access, correction, deletion, or withdrawal of consent, read our Privacy Policy. If you have questions about this Notice, contact us at:

Email: feedback@fixon.cc