Skip to main content

Flutter Dynamic Compliance Guide

To help developers and operators using the Conch Dynamic SDK (hereinafter "you") integrate and use third-party SDKs in compliance with personal information protection laws, regulations, policies, and standards, Conch Dynamic (hereinafter "we") has prepared this Conch Dynamic SDK Integration and Usage Guide (hereinafter "this document") to help you meet compliance requirements when using the Conch Dynamic SDK. Please read this document thoroughly before integrating and using the Conch Dynamic SDK.

1. Integrate/Upgrade to the Latest SDK Version That Meets Regulatory Requirements

We prioritize SDK feature optimization, personal information security, and protection. We will upgrade SDK versions as needed to improve product security and stability and ensure compliance with the latest laws, regulations, and standards.

We strongly recommend upgrading to the latest SDK version to use the latest features and avoid adverse impacts from delayed updates (such as app takedown notices).

After SDK updates, we will notify you via official announcements, SDK changelogs, or other appropriate channels so you can stay informed about the latest version.

You can also access the latest SDK download link: Changelog

2. Disclose Third-Party SDK Information in Your App Privacy Policy

Ensure your app has a Privacy Policy that meets regulatory requirements. You must clearly inform end users that your app integrates third-party SDK services.

Add information about this SDK's purpose, methods, and scope of personal information collection and use to your Privacy Policy, including the SDK developer/operator name and privacy policy link.

On the app login/registration page and at first launch, inform users of the Privacy Policy through clear, accessible means such as pop-ups, text links, and attachments, using plain language, so users can make informed, voluntary choices.

We provide sample disclosure text below for reference. You may inform users via text or table.

SDK versions may differ in features and required fields based on developer choices and configuration. Refer to the SDK privacy policy and your actual integration to fully inform users and obtain consent.

Third-party SDK name: Conch Dynamic SDK

Third-party SDK provider: Shenzhen Tencent Computer Systems Company Limited

Purpose and use cases: Provides dynamic delivery capabilities for the Flutter framework, enabling developers to update or fix issues online

Personal information processed: Device ID

Permissions required: Network access

Third-party SDK privacy policy: https://privacy.qq.com/document/preview/9e95e04797794517b0b924e96117ded2

Third-party SDK website: https://shiply.tds.qq.com/

Processing methods: 1. SSL and HTTPS encryption for security; 2. Encryption and de-identification for desensitization

To meet legal and regulatory requirements, initialize the SDK only after obtaining user consent. The SDK collects personal information or requests permissions according to your configuration only after users trigger specific SDK features and you complete the configured API calls.

  1. Ensure users read the app Privacy Policy and grant authorization before calling ConchLoaderAPI.init() to initialize the SDK at an appropriate time based on app functionality. If users do not agree to the Privacy Policy, do not call the initialization API. This API only performs initialization and does not collect personal information.
  2. Do not request sensitive device permissions involving personal information before users agree to the Privacy Policy. Do not collect or report personal information before consent (especially Android_ID, OAID, IMEI, MAC address, hardware serial number, installed app list, etc.). Do not request SDK services when the app is inactive (e.g., running in the background).

4. Optional Information Configuration Switches

The SDK provides control switches for optional personal information and permissions. Configure them based on the SDK features your app needs.

4.1 Configure Optional Personal Information

The SDK does not require optional parameters. Basic SDK functionality works even without them.

You may configure optional parameters to use additional SDK features. Call SDK methods at appropriate times before requests to obtain declared parameters with user authorization.

Personal informationPurposeProcessing methodRequired
Device IDWhen fetching artifacts, the backend uses device ID allowlists to determine deliveryEncrypted and sent to SDK backend for rule evaluation; not storedOptional

Configuration example:

// Build ConchLoader business parameters
ConchParams params = ConchParams(
appId: "760f8bca6b",
appKey: "82787958-a6cc-4408-9897-814a0e7afd21",
deviceId: "12345",
);
// Initialize ConchLoader component
ConchLoaderAPI.init(params);

4.2 Guidance

When installing, running, and using your app, comply with applicable laws, regulations, and standards. Do not:

  1. Collect any personal information without user consent.
  2. Force the app to exit or close when users deny non-essential permissions without reasonable justification.
  3. Repeatedly request permissions unrelated to the current service after users clearly deny them.
  4. Request permissions without clearly stating purpose and use.
  5. Request sensitive permissions before the related feature or service is used.
  6. Collect personal information beyond what is necessary for business functions.

5. Contact

We have a dedicated personal information protection team and officer. For questions, complaints, or suggestions about this policy or personal information protection:

  1. Tencent Customer Service: https://kf.qq.com/
  2. Email: Dataprivacy@tencent.com
  3. Mail: Data Privacy Protection Department, Tencent Binhai Tower, 33 Haier 2nd Road, Nanshan District, Shenzhen, Guangdong, China 518054

We will review issues promptly and respond within 15 business days or as required by law.

6. Notes

6.1 Compliance Self-Check Before Integrating Conch Dynamic SDK

We recommend a compliance self-check before integration to ensure you have end-user authorization and follow personal information protection requirements.

  1. Review and update your app Privacy Policy per this document.
  2. Configure delayed initialization—initialize the SDK only after user consent.
  3. When Conch Dynamic SDK is updated for legal or regulatory requirements, upgrade your app's integrated SDK promptly upon notification.
  4. Comply with other applicable laws, regulations, and standards.

6.2 Reference Compliance Documents

  1. Personal Information Protection Law of the PRC
  2. MIIT Notice on Further Improving Mobile Internet App Service Capabilities
  3. MIIT Notice on Information and Communication Service Perception Enhancement Action
  4. MIIT Notice on Deepening APP User Rights Protection Special Rectification
  5. MIIT Notice on APP User Rights Protection Special Rectification Work
  6. Methods for Identifying Illegal Collection and Use of Personal Information by Apps
  7. Cybersecurity Standard Practice Guide—Self-Assessment Guide for App Personal Information Collection and Use
  8. Provisions on the Scope of Necessary Personal Information for Common Types of Mobile Internet Applications
  9. GB/T 35273-2020 Information Security Technology—Personal Information Security Specification
  10. Cybersecurity Standard Practice Guide—Security Guide for App Use of SDKs
  11. Cybersecurity Standard Practice Guide—Guide for App System Permission Requests
Was this page helpful?