Updated on November 25, 2025
The following privacy policy is the commitment of Shenzhen Zhongwei Intelligent Technology Co., Ltd. (hereinafter referred to as "we") to user privacy protection. Please read it carefully to Learn about our management of your personal information
When you use or enable related functions or services, we collect and use relevant information as necessary to achieve the functions and services. Unless it is necessary for the implementation of business functions or required by laws and regulations, you may refuse to provide it without affecting other functions or services. We will specify the information to be collected item by item in the privacy policy.
The following text will help you understand in detail how we collect, use, store, transfer (if applicable), and protect personal information; Help you understand the ways to query, copy, delete, correct, and revoke authorized personal information. This policy is closely related to your use of our services. We recommend that you carefully read and understand all the contents of this policy, and make the choices you deem appropriate, We have highlighted the important content of the terms regarding your personal information rights in bold, please pay special attention.
Shenzhen Zhongwei Intelligent Technology Co., Ltd. is the owner and operator of , and we are obliged to respect the privacy of anyone who visits this website. These Terms are intended to inform you of our policies and practices regarding the collection, use and disclosure of any personal and anonymous information you submit to us through . "Personal information" refers to the personal information you upload through ., including but not limited to name, address, email address, social account, GPS positioning data and exercise data collected by individuals through the App, and related to the above content Related Other Non-Public Information. \"Anonymous Information\" refers to information that is not related to or linked to your personal information; anonymous information does not allow the disclosure of personal identity. Viewing and visiting this website and downloading (App) means that you have read, understood and agreed to the full text of this Privacy Policy. If you do not agree to all contents of this Privacy Policy, your sole and exclusive remedy is to stop using this website or App immediately.
By submitting personal information through this website or App, you agree to this privacy policy and expressly agree to process your personal information in accordance with this clause. Our processing of your personal information may be carried out in the country where the information is collected, or in other countries, but no matter what, we will strictly abide by the local laws and regulations on the processing of personal information in the country where the information is processed. The personal information collected from you helps us provide the data display in the app and helps us understand website visitors, our users and potential users. By using these information, we can better optimize our products and provide better support for the upgrade of service functions, so as to provide you with better services.
The personal information you provide to us When you become a registered user of , we will collect your email account information, etc.; when you use for exercise, We will collect your height, weight, health data or GPS positioning data, etc.; when you respond to our user satisfaction survey, we will collect your name and email address; when you use to upload exercise data to us, We will collect your relevant personal information and sports data.
Personal information collected by means of technology When you browse this website or App, certain information may also be collected passively, includes your network communication protocol address ("IP address"), device serial number("ICCID"), ANDROIDID, device ID, browser type, domain name, access time, and operating system. The collected IP addresses, device serial numbers, ANDROIDUIDs, and device IDs are intended for server security and better user experience. By filtering this data, malicious software attacks (such as frequent requests in a short period of time) can be prevented. Our company promises that these data will only be processed temporarily and will not be stored or disclosed to third parties for a long time.
We also use 'cookies' and Navigation data, including Uniform Resource Locator (URL), is collected to collect your visit date and time, as well as information about your searches and browsing. Collecting these types of information can enable our products and services to provide you with more targeted assistance. In the emails we send you, some may include a click URL, For your convenience, when you click on these URLs, you will reach the target website through our web server. By tracking click through rates, we can determine your interest in specific topics and measure the effectiveness of sending user communications. The 'IP address' is a number automatically assigned to your computer when you use the network. In some cases, your IP address remains unchanged when browsing different sessions; But if you are using a consumer network access provider, your IP address may vary during different sessions. We only track the IP addresses connected to session cookies to analyze the traffic situation of our website. Cookies "are when you browse a website, A small message fragment sent by the website to your computer's hard drive. We may use session cookies (which expire once the web browser is closed) and persistent cookies (which remain on your computer until you delete them) to provide you with a more personalized and interactive website experience. According to the web browser help file guide, you can delete persistent cookies. If you choose to disable cookies, some areas of the website may not work properly. We may obtain your personal information through other resources, including email, phone, or fax. We may combine this information with the information we have collected from you through this network to improve the products and services we provide. User feedback: If you provide feedback to us on this website, We will also keep your personal information included in the feedback confidential in accordance with the provisions of this clause, and we will use this feedback information to better enhance our products and services.
Unless otherwise stated in this Privacy Policy, we generally do not exchange, rent or share your information with third parties. Unless requested by you or with your written permission. At present, we will not share your personal information with our affiliated companies (including but not limited to our parent company, subsidiaries and other companies related to us); but in the future, if we want to share your part with these affiliated companies or all personal information, we will require them to abide by this Privacy Policy.
Unless otherwise stated in this Privacy Policy, with your permission or under the following circumstances, we will not share your personal information with third parties.
Service requires disclosure. We disclose personal information to those who help provide the service, including those who perform technical, administrative and data processing tasks such as hosting, billing, fulfillment, data storage and security.
As required by law or to protect rights. We will disclose personal information if required by law, or in response to a subpoena or court order, or when we have reasonable grounds in our sole belief that disclosure is necessary to protect the property or rights of third parties or the general public.
Business transfer, bankruptcy. In the event of a merger, acquisition or bankruptcy or sale of some or all of our assets, we have the right to transfer all personal information in our possession to the successor organization.
Based on the operation considerations and needs of this site and , we may provide you with links to any other websites or addresses. This is for your convenience and does not mean that we endorse these websites or address or its content. We do not control, review, and assume no responsibility for these external sites or their content. Please note that the terms of our Privacy Policy do not apply to these external sites.
According to the update of national laws and regulations and the needs of website operation, we have the right to modify this policy from time to time. The revised privacy policy will take effect once it is posted on this site and replace Original Privacy Policy. You can log in to view the latest privacy policy content at any time. If you do not agree to the updated privacy policy, you should immediately stop accepting the services provided by this site; if you continue to use the services provided by this site, you are deemed to agree to the updated privacy policy. We recommend that you read this Privacy Policy and the announcement of this site before using this site. If any provision of these Terms is deemed to be repealed, invalid or for any reason unenforceable, that provision shall be deemed severable and shall not affect the validity and enforceability of any remaining provisions.
| Permission Classification | Permission Name | Permission Description | |
|---|---|---|---|
| Calendar | Read the calendar | android.permission. READ_CALENDAR | Permission definition: 1. Android.permission.READ_CLENDAR: Allow applications to retrieve user calendar data 2. Android.permission.WRITE_CALENDAR: allows applications to edit user calendar data Note: The read and write operations of the calendar can be viewed in the calendar application with corresponding schedules. Typical scenario examples: 1. Develop study plans and travel schedules; 2. Train ticket booking, travel booking; 3. Reminder of important event schedules such as birthdays and meetings |
| Write a calendar | android.permission. WRITE_CALENDAR | ||
| Camera | Take photos and videos | android.permission. CAMERA | Permission definition: Allow applications to use cameras Typical scenario examples: 1. Beauty photography; 2. Scan QR codes and barcodes; 3. Video recording; 4. Facial recognition; 5. Intelligent image recognition; 6. Share, used for posting on social media |
| Address Book | Read your address book | android.permission. READ_CONTACTS | Permission definition: 1. Android.permission.READ∝TACTS: Allow users to retrieve their address book data 2. Android.permission-WRITE-CONTACTS: Allow users to edit user address book data Typical scenario examples: 1. Add friends through the address book; 2. Backup cloned contacts; 3. Phone book management; 4. Add and retrieve contacts in office software |
| Modify Address Book | android.permission. WRITE_CONTACTS | ||
| Search for accounts on the device | android.permission. GET_ACCOUNTS | Permission definition: Allow applications to obtain a list of application accounts from the account service: List of Google accounts, Weibo accounts, etc., excluding WeChat accounts and QQ accounts Manually input phone numbers with users, etc | |
| Position | Accurate (GPS) | android.permission. ACCESS_FINE_LOCATION | Permission definition: 1 android.permission.ACCESS_FINE_LOCATION： Obtain accurate (GPS) location 2 android.permission.ACCESS_COARSE_LOCATION： Obtain (network-based) approximate location Typical scenario examples: 1. Trajectory scenes such as walking, cycling, and cycling; 2. Sports and health scenarios such as running and brisk walking |
| (Based on the network) approximate location | android.permission. ACCESS_COARSE_LOCATION | ||
| (Based on the network) approximate location | android.permission. ACCESS_BACKGROUND_LOCATION | ||
| Recording | Recording | android.permission. RECORD_AUDIO | Permission definition: Authorized applications can use microphones. Typical scenario examples: 1. Recording machine; 2. Voice assistant function, voice navigation; 3. Voice call, chat 4. Screen recording 5. Pronunciation Learning |
| Equipment information | Device information: Read phone status and identity | android.permission. READ_PHONE_STATE | Permission definition: Authorized applications can obtain device information such as imsi, imei, sn, etc. At the same time, this permission can also be used to obtain the status of mobile phone calls, For example, it is not recommended to use this permission during incoming calls, ringing, or calls, Please use Android ID or advertising ID as an alternative |
| Call history | Read call records | android.permission. READ_CALL_LOG | Permission definition: Authorized applications can read user call log information. Typical scenario examples: 1. Backup 2. Call log management function 3. Harassment interception: Generally, call records will be deleted |
| Write call records | android.permission. WRITE_CALL_LOG | Permission definition: Authorized applications can read user call log information. Typical scenario examples: 1. Backup 2. Call log management function 3. Harassment interception: Generally, call records will be deleted | |
| Phone | Directly dial the phone number | android.permission. CALL_PHONE | Permission definition: Authorized applications can dial numbers directly without the user clicking on authorization. It is not recommended to use this permission. It is recommended to call up the dial and manually initiate dialing by the user Typical scenario examples: 1. Make phone calls directly from the address book; 2. Make phone calls directly in the browser; 3. Contact customer service |
| Add voicemail | com.android.voicemail.permission. ADD_VOICEMAIL | Permission definition: Authorize applications to add voice attachments to emails Typical scenario examples: 1. As defined, email scenario | |
| Make/answer Internet calls | android.permission. USE_SIP | Permission definition: make/answer Internet calls Typical scenario examples: Make an Internet call with SIP protocol | |
| Reset the outgoing path | android.permission. PROCESS_OUTGOING_CALLS | Permission definition: Reset the outgoing phone number to monitor the call status Typical scenario examples: 1. Call out monitoring scenario, address book 2. Children's Watch | |
| Read phone number | android.permission. READ_PHONE_NUMBERS | Permission definition: Read mobile phone number Typical scenario examples: No typical scenarios currently available, new permissions | |
| Answer incoming calls | android.permission. ANSWER_PHONE_CALLS | Permission definition: Authorized applications can answer incoming calls Typical scenario examples: Answering phone calls in car mode | |
| Body sensors | Human body sensors (such as heart rate detectors) | android.permission. BODY_SENSORS | Permission definition: Authorize the application to access sensor data used to measure the internal condition of the user's body. Generally refers to heart rate sensor data. Typical scenario examples: 1. Sports/health-related, used to display the user's heart rate status, such as Fere fit. 2. Wearable device applications |
| SMS | Send SMS | android.permission. SEND_SMS | Permission definition: Authorize the application to send SMS messages. Typical scenario examples: 1. SMS management applications, such as China Mobile; 2. The verification code scenario when registering or logging in with a mobile phone number, such as the AcFun app, Allow users to register through their phone number and received verification code. 3. SMS payment scenarios in gaming software |
| Receive text messages (SMS) | android.permission. RECEIVE_SMS | Permission definition: Authorize applications to read SMS messages. Typical scenario examples: 1. SMS management applications, such as China Mobile and Go SMS; 2. The verification code scenario when registering or logging in with a mobile phone number, such as the AcFun app, Allow users to register through their phone number and received verification code | |
| Receive text messages (WAP) | android.permission. RECEIVE_WAP_PUSH | Permission definition: Authorize applications to receive WAP push messages. Typical scenario examples: 1. SMS management applications, such as China Mobile and Go SMS | |
| Receive text messages (MMS) | android.permission. RECEIVE_MMS | Permission definition: Authorize the application to listen to incoming multimedia message services and intercept multimedia message reception information. Typical scenario examples: 1. SMS management applications, such as China Mobile and operator series applications | |
| Read community broadcast messages | android.permission. READ_CELL_BROADCASTS | Permission definition: Authorize applications to read community broadcast messages | |
| Storage | Read the contents of your SD card | android.permission. READ_EXTERNAL_STORAGE | Permission definition: Authorize applications to read, modify, or delete the contents of SD cards. Typical scenario examples: 1. Download file scenario, such as a browser downloading files from the network to a mobile phone. 2. The photo scene requires storing the image or opening the photo |
| Modify or delete the contents of the SD card | android.permission. WRITE_EXTERNAL_STORAGE | ||
| Device Manager | Device Manager | android.permission. BIND_DEVICE_ADMIN | Display definition on other applications: This feature needs to be activated to take effect, and the entrance can be searched in the settings (Device Manager) can view this function; 1. Delete device data 2. Set lock screen password rules; 3. Screen Lock The system defaults to a non activated state and requires activation in the settings for the function to take effect Typical scenario examples: 1. Mobile phone retrieval/find my phone function, used for remote control of devices, restoring factory settings, etc |
| Monitor notification bar | Monitor notification bar | android.permission. BIND_NOTIFICATION_LISTENER_SERVICE | Definition of Monitoring Notification Service: Monitor the content displayed in the notification bar of other applications Typical scenario examples: 1. Watch wristband wearable application requires guiding notification bar information to the wearable device |
| Third party libraries | Google Play Services | READ_PHONE_STATE | The SDK has the behavior of collecting IMEI, device MAC address, software installation list, address book, and SMS Typical scenario examples: 1. When logging in to Google, the Google account and phone will be linked together, and the next login will be automatically completed. 2. When abroad, Google Maps is needed |
| Tencent Bugly | READ_PHONE_STATE | The SDK has the behavior of collecting IMEI, device MAC address, software installation list, address book, and SMS Typical scenario examples: 1. When the program crashes, Bugly will automatically capture anomalies and collect relevant information about the phone together Upload to Tencent server. Facilitate developers to troubleshoot issues | |
| Gaode SDK | READ_PHONE_STATE ACCESS_FINE_LOCATION ACCESS_COARSE_LOCATION ACCESS_BACKGROUND_LOCATION WRITE_EXTERNAL_STORAGE | In order to provide users with location-based navigation services, map displays, and location services. The SDK collects latitude and longitude, device information such as IP address, GNSS information, network type, WiFi status, WiFi parameters, WiFi list, SSID, BSSID, base station information, WiFi signal strength information, sensor information (vector, acceleration, pressure, direction, geomagnetic, gyroscope, temperature, photosensitive, nema signal), device signal strength information, device identification information (IDFA, OAID), current application information (application name, application version number), device parameters and system information (device brand and model, operating system, operator information, screen resolution). 1. Link to the Privacy Policy of Gaode Open Platform: https://lbs.amap.com/pages/privacy/ ； 2. The name of the Gaode SDK used is: AMap3DMap_7.5.0_AMapSearch_7.3.0_AMapLocation_5.0.0_20200610.jar、 SDK provider name (i.e. Gaode Software Co., Ltd.), purpose of collecting personal information Personal information collected by Gaode SDK. Please refer to the SDK Compliance Usage Plan for details（ https://lbs.amap.com/agreement/news/sdkhgsy ） | |
| GoogleMobileAds SDK | com.google.android.gms.ad | SDK exists to read a specific type of sensor list It is an SDK publicly released by Google, package name: com. Google. android. gms. ads* Typical scenario examples: 1. During initialization, the Google ad ID in the Google service will be read 2.AdMob also collects ANDROID IDs for device identification, identifying users on devices, limiting ad frequency, and preventing cheating. | |
| zxing | android.permission. CAMERA | SDK exists to read camera sensor data It is an SDK publicly released by the Google community, package name: com. king. zxing Typical scenario examples: 1. Used when scanning QR codes and barcodes, this data is not transmitted and is processed internally within the SDK | |
| WeChat login SDK | SDK exists to retrieve information about installed apps It is an SDK publicly released by Shenzhen Tencent Computer Systems Co., Ltd., package name: com. tencent.mm. opensdk Typical scenario examples: 1. When logging in with WeChat, it is necessary to check whether the WeChat app has been installed before authorizing login. Only when the WeChat app is installed can WeChat login be used | ||
| QQ SDK | SDK exists to retrieve information about installed apps It is an SDK publicly released by Tencent Computer Systems Co., Ltd. in Shenzhen, with the package name: open_stk_3.5.13.83_rc564928_ste.jar Typical scenario examples: 1. When logging in with QQ, it is first checked whether QQ is installed before logging in authorization. Only when QQ is installed can QQ be used for login. SDK exists to retrieve information about installed apps It is an SDK publicly released by Tencent Computer Systems Co., Ltd. in Shenzhen, with the package name: open_stk_3.5.13.83_rc564928_ste.jar Typical scenario examples: 1. When logging in with QQ, it is first checked whether QQ is installed before logging in authorization. Only when QQ is installed can QQ be used for login. | ||
| FaceBook SDK | SDK exists to retrieve information about installed apps It is an SDK publicly released by Mate company, package name: com. Facebook Typical scenario examples: 1. When logging in with Facebook, it is first checked whether Facebook is installed before logging in authorization. If Facebook is installed, you can log in directly through the app. If not, you can log in through web authentication. | ||
| Jinghong Kinetic Energy SDK | Device identifier (OAID, Android ID), device information (device model, device hardware information, operating system, system settings, device usage information), application information, sensor information (gyroscope, accelerometer, rotation vector sensor, magnetometer, barometer), network information, operator information, IP address, Wi Fi information (Wi Fi status, Wi Fi parameters, and Wi Fi list), location information (such as precise location information (optional, not stored) and rough location information such as Wi Fi and Bluetooth lists), advertising interaction information Programmatic advertising placement, advertising monitoring attribution, advertising fraud prevention, and operational maintenance Privacy policy link for third-party SDK: Jinghong Kinetic Energy SDK Privacy Policy | ||
| Mi Meng Advertising SDK | [Required Information] Device identifier: OAID; Basic device information: device model, operating system, screen width and height, screen density, device region, storage information, CPU information; Operating system information: Android version number, system version name, system version number, system language, SDK version number; Network information: IP address, WiFi status, operator information, network type, network connection status; Application information: application package name, version number, application front-end and back-end status, running process information; Advertising information: Interactive data on the display, clicks, and conversions of advertisements. Advertising placement and advertising monitoring attribution, anti cheating, advertising placement statistics Privacy policy link for third-party SDK: MiMeng Advertising SDK Privacy Policy | ||
| ifly SDK | com.iflytek | Using AI products from iFlytek in China Mobile device information: IMEI, IMSI, MEID (only collected on Android); IDFA (iOS only) Purpose: To detect if the number of phones bound to the product ID exceeds the limit, and if it exceeds the limit, the current product ID will be closed. | |
| aflash SDK | com.aflash | Using AI products provided by Aishan both within and outside of China Mobile device information: not obtained The billing method is based on the duration and is calculated by binding the product ID. So there is no need to obtain mobile phone information. | |
| mediatom | com.yd.saas.baidu | Mobile device information: IMEI, IMSI, MEID (only collected on Android), acceleration sensor; IDFA (iOS only) Purpose: To detect if the number of phones bound to the product ID exceeds the limit, and if it exceeds the limit, the current product ID will be closed. | |
We have established a dedicated personal information protection team and responsible person. If you are If you have any questions, complaints, opinions or suggestions regarding personal information protection, please feel free to contact us Contact us through any of the following ways:
You can also contact us for information on possible complaint channels that may be applicable. We will always collect and use your information in accordance with our privacy policy.
Push related: In order to ensure that this application can receive broadcast information pushed by the client normally when it is closed or running in the background, this application must use (self start) capability to wake up the self start or associated start behavior of this application by sending broadcasts through the system at a certain frequency, which is necessary for implementing functions and services; When you open the content and send messages (including calls, text messages, notification bars, etc., users can choose to turn them on or off), with your explicit consent, the relevant content will be redirected to open. Without your consent, there will be no associated activation.