M4S Converter Third-Party SDK Sharing List

1. Third-Party SDK Sharing List

The App does not integrate advertising SDKs, does not display third-party ads, and does not collect, use, or share device identifiers for ad delivery, attribution, or personalized advertising.

SDK Name: Bugly Android SDK
Provider: Shenzhen Tencent Computer Systems Co., Ltd.
Package/Identifier: com.tencent.bugly
Purpose: Crash monitoring, exception reporting, and stability analysis
Collection method: When you use the relevant feature or platform version, the SDK collects necessary information under its interface rules; system permissions are subject to system authorization and on-screen notices
Information collected: Device information, app information, crash stacks, logs, and network information
Necessary: Necessary when you use the corresponding feature or platform version
Processing method: The third-party SDK processes information under its privacy policy; we evaluate integrations and review versions under data-minimization principles
Public information status: View public record (version 4.1.9.2)
SDK privacy policy: https://privacy.qq.com/document/preview/fc748b3d96224fdb825ea79e132c1a56

SDK Name: WeChat OpenSDK for Android
Provider: Shenzhen Tencent Computer Systems Co., Ltd.
Package/Identifier: com.tencent.mm.opensdk
Purpose: WeChat login, sharing, or payment
Collection method: When you use the relevant feature or platform version, the SDK collects necessary information under its interface rules; system permissions are subject to system authorization and on-screen notices
Information collected: WeChat authorization information, payment results, device information, and app information
Necessary: Necessary when you use the corresponding feature or platform version
Processing method: The third-party SDK processes information under its privacy policy; we evaluate integrations and review versions under data-minimization principles
Public information status: View public record (version 6.8.15)
SDK privacy policy: https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/RYiYJkLOrQwu0nb8

SDK Name: MMKV Android SDK
Provider: Shenzhen Tencent Computer Systems Co., Ltd.
Package/Identifier: com.tencent.mmkv
Purpose: Locally store app settings, account state, and feature state
Collection method: When you use the relevant feature or platform version, the SDK collects necessary information under its interface rules; system permissions are subject to system authorization and on-screen notices
Information collected: Key-value data processed only on the device
Necessary: Necessary when you use the corresponding feature or platform version
Processing method: The third-party SDK processes information under its privacy policy; we evaluate integrations and review versions under data-minimization principles
Public information status: No clearly matching public record was found; related information is based on the SDK provider's public documentation and privacy policy
SDK privacy policy: https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/aY5BAtRiO1BpoHxo

Note: Third-party SDK names, developers, versions, and privacy policies may change as providers update their services. We periodically review and update this list based on the SDKs actually integrated in the app and public information from the providers.

2. Open-Source Component Libraries (No User Data Collection or Sharing by the Libraries Themselves)

The App uses open-source libraries to improve feature stability. These libraries are used inside the App and do not independently collect or share user data.

Network communication: android-async-http, cos-android-nobeacon, okhttp3
Information involved: Network information, IP address, MAC address where required by network communication
Permissions: Network and storage where needed
Function: Asynchronous HTTP requests and Tencent Cloud object storage SDK capabilities
Providers: GitHub and Tencent Cloud open-source communities

Image processing: Glide, Photoview, cropiwa
Information involved: Stored files selected by you
Permissions: Storage and network where needed
Function: Image loading/caching, gesture zoom, and image cropping
Providers: GitHub, bumptech, and open-source communities

Multimedia processing: ijkplayer-java, FFmpeg
Information involved: Stored files selected by you
Permissions: Storage
Function: Video playback, editing, processing, and conversion
Providers: bilibili and the FFmpeg open-source community

UI components: DialogX, QMUI, MultiSlider, ColorPicker, MultiTouchImage
Information involved: Stored files where used by UI preview components
Permissions: Storage where needed
Function: Dialogs, UI components, sliders, color picker, and multi-touch image controls
Providers: GitHub, Tencent QMUI team, and open-source communities

Utility libraries: ButterKnife, Gson, GreenDao, EventBus, MMKV, Share2, LeakCanary
Information involved: Stored files or local app data where used by the App
Permissions: Storage where needed
Function: View injection, JSON parsing, database ORM, event bus, key-value storage, sharing, and memory leak detection
Sharing note: Local components such as MMKV mainly process settings, cache, account state, or files you select on the device, and do not upload personal information as independent third-party services
Providers: Jake Wharton, Google, greenrobot, Tencent, Square, and open-source communities

Open-source privacy note: These components are used for local feature implementation. File operations are performed on files selected by you and are not uploaded to our servers by these libraries. Network components require basic network permission but do not independently collect user privacy data.

3. Principles and Measures for Information Sharing

• Necessity: We share only information necessary to achieve the service purpose.
• Lawfulness: We require information sharing to comply with applicable laws and platform rules.
• Minimization: We limit the scope and amount of shared information where possible.
• Encrypted transmission: Shared information is protected during transmission where technically feasible.
• Contractual restrictions: We require third parties to comply with data processing, confidentiality, and security obligations.
• Security assessment: We evaluate third-party SDKs for security and privacy risks.

4. Third-Party SDK Management

• Due diligence: We review third-party providers before integration where appropriate.
• Periodic review: We periodically review SDK privacy policies and usage.
• Technical controls: We use technical measures to limit SDK access to information where possible.
• Version updates: We update SDKs to safer versions where feasible.

5. User Controls

• Permission management: You may manage app permissions in system settings.
• Information inquiry: You may contact us to understand how we share information with third parties.

6. Contact Us

If you have questions about this Third-Party SDK Sharing List, contact us at: feedback@hshstech.com

Hushan Hushan (Shenzhen) Technology Co., Ltd.