1. How We Collect and Use Your Personal Information

Hi Yan (hereinafter referred to as "we") will strictly follow national laws and regulations requirements and use security technologies to ensure data security. At the same time, we place great importance on your personal information and privacy protection and are committed to defending everyone's privacy rights. Therefore, we adhere to the principles of legality, legitimacy, transparency, and the minimum necessity.

1.1 What Personal Information We Collect

Business Scenario	Collection Purpose	Types of Personal Information	Collection Method	Personal Information Fields
Device Management	Establish Bluetooth connection, manage device configuration, complete software upgrades, display data sources, and count device activation	Account information, device information, network information, contact information, communication information, voice information, location information, application information, transaction information, calendar and schedule information, exercise information, health information	App collection	Account information, device identifier (including MAC address, IMEI), wearable device information, device usage information, system basic information, device name, device logs, wearable device measurement data, and device-related information (battery level, screen size, country code, settings configuration, Bluetooth configuration), network status.

1.2 How We May Use Your Personal Data

1.2.1 Personal Data Management

To manage your personal data and improve the accuracy of exercise data, we need to collect your personal data, including gender, date of birth, height, weight, and exercise settings data. You can go to "Mine" > "Personal Data" to fill in or modify it. If you do not provide this information, it will affect the accuracy of exercise data calculation, but it will not affect your local use of personal data management functions.

1.2.2 Binding of Smart Wearable Devices

To support the binding of your smart wearable devices and the application, we will collect the identifier information of your smart wearable devices, the identifier information of your mobile device (encrypted IMEI, IMSI, MAC address, MEID, Android ID, device hardware serial number, SIM card identifier), mobile phone model, system version number, Bluetooth information of smart wearable devices, and wearable device model. At the same time, we will collect the current running application process information to determine whether the current application is running in the foreground and process the corresponding business according to different processes.

1.2.3 Interaction Features of Wearable Devices

(1) Message Notification Function: If you enable the notification push function, the push messages on your phone will also be pushed to the wearable device. Please rest assured, we will not read your notification messages, and your notification messages will only be used for display on the watch. We will not save your notification messages. You can manage the synchronization push settings in the application.

(2) Call Reminders and Answering Calls: You can control phone calls with the wearable device. When you enable the call reminder function in the application, and the watch and phone are connected, the wearable device can display the incoming call number of the connected phone and vibrate to remind you. At this time, you can choose to reject the call or mute the phone ringer. Please rest assured that your incoming call number will only be used for display on the watch, and the wearable device will not store your incoming call number or upload it to the cloud. If your device supports making and receiving calls, you can use the wearable device to answer or make calls. To achieve this function, we need to collect your call records. Your call records will be stored on the wearable device and will not be uploaded to the cloud. If you enable the permission to read the address book in the application, you can wake up the voice assistant on the wearable device to make a call to a specified contact. To achieve this function, the application will synchronize the incoming call number and contact name to your wearable device for display. If your device supports emergency contact call functionality, you can make an emergency call by pressing the button on the lower right side of the wearable device three times after enabling this feature in the application. To achieve this function, we need to synchronize and save your emergency contact information (including name and phone number) to the firmware end.

(3) Payment Function: If your device supports the payment function, you can enable the smart device payment function provided by a third-party payment service provider that we cooperate with on the wearable device. After enabling this function, you can complete payment behavior directly by scanning the QR code on the device. Please note that this function is provided by the third-party payment service provider. Therefore, when enabling it, we strongly recommend that you carefully read the relevant agreements of the third-party payment service provider. When you use Alipay for payment, please carefully read Alipay's "Smart Device Service Agreement" and "Alipay Privacy Policy." To provide you with the ability to use Alipay for payment, we will collect your Alipay nickname and account name, as well as the Alipay payment barcode. Please rest assured that this information will only be stored on the wearable device, and we will not upload it to the cloud.

(4) Alarm Clock Function: You can use the alarm clock function provided by the wearable device. To achieve these functions, we need to collect your setting information. Please rest assured that this information will only be stored on the wearable device and will not be uploaded to the cloud. You can choose to synchronize your system alarm information to the wearable device. After synchronization, the wearable device will provide alarm reminders, and you can control the system alarm to turn off or delay on the device.

(5) Controlling Music Playback on the Mobile Phone: After the wearable device is connected to the application, you can control the music application on your mobile phone through the wearable device, such as pause/play, previous or next track, and volume control. When you use the watch's smart center, you can control other devices (including speakers, TVs, headphones), including pause/play, previous or next track, and volume control. Therefore, we will obtain your smart center device list and device names. Please rest assured that we will not save your control operations or upload them to the cloud.

(6) Remote Photography Function: If your device supports the remote photography function, after the wearable device is connected to the application, you can control the camera application on your mobile phone to take photos and delay photos through the wearable device. After the photo is taken, you need to view the photo on the mobile phone. Please rest assured that the wearable device will not collect your control operations or upload them to the cloud.

(7) Find Phone Function: You can use the wearable device to find your mobile phone. When you trigger the find phone function from the wearable device, the wearable device will send a command via Bluetooth, and the phone will play a ringtone after receiving the command.

(8) Wearable Device Settings Function: You can manage the settings of the wearable device. You can set functions such as changing the watch face, adjusting brightness, always-on display, do-not-disturb mode, activity reminders, etc., on the wearable device.

(9) Watch Face Market: To ensure that your watch face data is not lost when you change your mobile phone or reinstall the application, we will collect the watch face ID you downloaded, the order of the watch faces, and the latest saved picture content and style in the album watch face function. To ensure the connection experience of Bluetooth headsets, we will collect the device model, MAC address, connection status, and Bluetooth version information.

1.2.4 Third-Party SDK List

We will conduct strict security checks on SDKs or other similar applications and require partners to take strict measures to protect your personal data. When new service needs and business functions change, we may adjust the third-party SDKs we access and promptly disclose the latest situation of accessing third-party SDKs in this statement. Please note that the data types of third-party SDKs may change due to version upgrades, policy adjustments, etc. Please refer to their official announcements for the latest information. The third-party SDKs currently accessed by this application are as follows:

(1) Tool SDKs

Third-Party SDK Name: Huawei Unified Scan SDK (also known as Scan Kit)
Company: Huawei Software Technologies Co., Ltd.
Purpose: Provide scanning functions, such as QR code recognition, barcode scanning, etc., to assist users in quick operations or information acquisition.
Method: The Huawei Unified Scan SDK indirectly collects relevant information through the developer's integration of the SDK in their application. This information is primarily processed and used on the device to improve scanning success rates and user experience.
Scope: Does not directly collect personal information, but scanning results may contain personal information, which should be handled compliantly.
Data Scope: Scanning function: To provide scanning capabilities, the SDK will collect information about the developer's application calling the SDK interface. Necessary personal information processed includes data you voluntarily submit (such as images) and sensor information (such as accelerometer and light sensor). The accelerometer is used to sense the state of screen rotation to adjust the scan interface orientation; the light sensor is used to turn on the flashlight in low light, providing a better scanning experience. Code generation function: To provide code generation capabilities, the SDK will collect information about the developer's application calling the SDK interface. Necessary personal information processed may include strings of data you voluntarily submit.
Third-Party SDK Privacy Statement or Developer Guide:
Privacy Statement: https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/sdk-data-security-0000001050043971
SDK Compliance Guide: https://developer.huawei.com/consumer/cn/doc/HMSCore-Guides/sdk-compliance-guidelines-0000001654738081

(2) Statistical Analysis SDKs

Third-Party SDK Name: UC Woodpecker
Company: Guangzhou UC Computer Technology Co., Ltd.
Purpose of Collecting Personal Information: It has a high crash collection rate, and the generated logs contain a lot of important information for analyzing and solving problems.
Types of Personal Data Collected: Device information (such as IMEI/IMSI, SIM card serial number/MAC address, android_id, SSID, BSSID, basic device information [model/manufacturer, etc.])
Third-Party SDK Privacy Statement or Developer Guide: https://open-uc.uc.cn/agreement/secret

Third-Party SDK Name: Umeng Statistics SDK
Purpose of Collecting Personal Information: Provide statistical analysis services, application performance, and user behavior control.
Types of Personal Data Collected (Scope): Our product integrates Umeng+ SDK. Umeng+ SDK needs to collect your device Mac address, unique device identifier (IMEI/androidID/IDFA/OPENUDID/GUID/SIM card IMSI information/ICCID/OAID) to provide statistical analysis services, and calibrate report data accuracy through location information, collect device information (IMEI/MAC/AndroidID/IDFA/OpenUDID/GUID/SIM card IMSI/ICCID/location, etc.) to uniquely identify the device for application performance monitoring services; provide basic anti-cheating capabilities by collecting location information to exclude cheating devices and identify application crash causes.
Method: Indirectly collects OAID, hardware serial number (for device identification), and sensor data (for user behavior analysis) through Umeng SDK interface.
Third-Party SDK Privacy Statement or Developer Guide: https://www.umeng.com/page/policy

(3) Map SDKs

Third-Party SDK Name: Amap SDK
Company: Amap Software Co., Ltd.
Purpose of Collecting Personal Information: To provide accurate and successful positioning services, track, troubleshoot, diagnose, and statistically analyze various issues in services, ensure the safe and normal operation of products and services, provide location services, map, and search services, track, troubleshoot, diagnose, and statistically analyze various issues in services, ensure the safe and normal operation of products and services.
Usage Scenarios: When users use location-based service recommendations, send location information, or use other location-related functions.
Types of Personal Data Collected (Scope): Location information (latitude and longitude, precise location, rough location), device identification information (IMEI, IDFA, IDFV, Android ID, MEID, MAC address, OAID, IMSI, hardware serial number), current application information (application name, application version number), device parameters and system information (system attributes, device model, operating system), operator information, request for storage permission, location permission method: Indirectly collects OAID, hardware serial number (for device identification), and sensor data (such as accelerometer, gyroscope, etc. for location calibration) through Amap SDK interface.
Method: Indirectly collects OAID, hardware serial number (for device identification), and sensor data (such as accelerometer, gyroscope, etc. for location calibration) through Amap SDK interface.
Additional Scope Instructions:
OAID: Used to provide location services while protecting user privacy, track, troubleshoot, diagnose, and statistically analyze various issues in services.
Hardware serial number: Used to uniquely identify the device to provide personalized services.
Sensor information (vector, acceleration, pressure, direction, geomagnetic, gyroscope, temperature, light, nema signal): Only used to improve the accuracy and stability of location services.
Third-Party SDK Privacy Statement or Developer Guide: https://lbs.amap.com/pages/privacy/

1.3 How We Use Your Personal Information

1.3.1 Hi Yan Device Management

To manage your Hi Yan devices (such as smartbands, smartwatches, and other wearable devices produced and sold by affiliated companies, as well as third-party devices), we need to collect your device identification information (basic system information, device name, device identifier, IMEI, MAC address, system logs, system usage information, device usage information, IMSI, Android ID, Android Advertising ID, OAID, hardware serial number, SIM card identifier, etc.), hardware information of the device, device usage information, basic system information, and network information. The purpose of collecting this information is to establish a Bluetooth connection, manage device configurations, complete software upgrades, display data sources, and track device activation status. This data will also be used to improve network connection experience.

In addition, to support the interaction between wearable devices/headphones and phone information, it is necessary to read the phone calendar schedule and basic system information onto the wearable device. We connect to Hi Yan devices via Bluetooth to obtain device health data, log information, location information, and device information (basic system information, device name, device identifier, IMEI, MAC address, system logs, system usage information, device usage information, IMSI, Android ID, Android Advertising ID, OAID, hardware serial number, SIM card identifier, etc.). You can terminate the collection of such data by disconnecting or unbinding the device.

After connecting some Hi Yan devices, to provide more accurate data monitoring, the gender, age, height, and weight you entered in "My" > "Profile" in the "Hi Yan" app will be synchronized to the device (such as a smartband or smartwatch).

Some wearable devices with call functions need to display phone contact information and call logs to facilitate making and receiving calls on the wearable device.

When connecting our Hi Yan devices, "Hi Yan" only provides the path for device upgrades, the firmware version is provided by the device manufacturer, and the manufacturer is responsible for the quality and results of the upgrade. Your device name, device identification information (basic system information, device name, device identifier, IMEI, MAC address, system logs, system usage information, device usage information, IMSI, Android ID, Android Advertising ID, OAID, hardware serial number, SIM card identifier, etc.), and device usage information will also be uploaded to our server to complete activation statistics and analyze wearable device issues.

After successfully pairing the wearable device, third-party applications that interact with the paired wearable device through "Hi Yan" can obtain your device's random identifier (resettable and unique to each application), device name, hardware information and status (charging or in use), and other data. Third-party applications can also send messages or notifications to your paired wearable device; with your explicit authorization, these third-party applications can access device sensor data, sleep status, activity types (walking, running), wearing status data, log information, location information, and device information (basic system information, device name, device identifier, IMEI, MAC address, system logs, system usage information, device usage information, IMSI, Android ID, Android Advertising ID, OAID, hardware serial number, SIM card identifier, etc.).

If your wearable device supports weather forecasting functions, we will send your location information to the weather service provider to obtain and display the weather information for your area on the wearable device. You can terminate this sharing by turning off the weather forecasting function in the device management section of this application at any time.

When you use our services, we may automatically collect detailed usage information about your use of our services, which is saved as network logs. For example: your login account, IP address, browser type, telecom operator, network environment, language used, access date and time, duration of stay, and refresh records.

1.3.2 Additional Services Based on Device Permissions

To provide you with more convenient and high-quality products and/or services and to enhance your experience, we may collect and use your personal information in the following additional services. If you do not provide this information, it will not affect your use of basic services such as recording and displaying exercise and health information on our platform, but you may not enjoy the user experience brought by these additional services. These additional services include:

(1) Additional services based on location permissions: If you enable the "Weather Sync" feature, you can view the weather information synced from the app on your wearable device. To provide this feature, we will collect your location information or the city information you manually enter on the app. Rest assured, this information will only be used to provide weather information, and your location and weather information will not be uploaded to the cloud.

(2) Additional services based on camera permissions: You can scan QR codes to bind smart wearable devices by enabling the app's camera permissions.

(3) Additional services based on calendar read and write permissions: If you want to set your habits, after you enable the app's calendar read and write permissions, you can sync the habits you add in the app to the system calendar. If your device supports calendar and reminder functions, you can actively add schedule information and reminders, which will be used to provide you with timely reminders.

(4) Additional services based on read and write external storage permissions (for Android versions below 10): If you want to use pictures from your phone or save pictures to your phone, after you enable read and write external storage permissions, we will read pictures from your phone when you set watch face pictures, or save the pictures you share to your phone when you share pictures.

(5) Additional services based on reading contacts and call logs permissions: If you want to display the caller's number and contact name on the smart wearable device, after you enable reading contacts and call logs permissions, we will sync the caller's number and contact name to the wearable device when you use the "Display Contacts" function.

(6) Additional services based on making and receiving calls permissions: If you want to control phone calls through the wearable device, after you enable making and receiving calls permissions, we will provide you with services to control phone calls through the device when you use the call reminder function.

(7) Photo permissions (iOS): If you want to use the photo album watch face feature, you need to enable photo permissions, and we will access the photos to provide the photo album watch face service.

(8) WLAN permissions: If you want to use network-related functions, including uploading exercise and health data to the cloud, you need to enable WLAN permissions.

(9) Floating window permissions (Android version): If you want to use this application as a floating window, you need to enable floating window permissions.

(10) Notification permissions: If you want to use the message notification function through this application, you need to enable notification permissions.

(11) Do Not Disturb permissions: If you want to use the Do Not Disturb synchronization function through this application, you need to enable Do Not Disturb permissions. You can disable the above permissions at any time to stop using the related functions. For more information of this kind, please refer to the "Your Rights" section below. After you disable the relevant permissions, you may not be able to continue using the additional business functions based on permissions, but it will not affect your use of other services of this product.

(12) Nearby device permissions: When you perform Bluetooth scanning for nearby devices or device reconnection, we will request this permission to obtain nearby device information. If you disable this permission, it will not affect the use of other services.

You can manage this application's permissions by accessing the system "Settings" at any time. The system permissions required by different devices may vary, and services not provided on the device will not obtain the corresponding sensitive permissions. The names of permissions may vary for different operating systems.

Application Permissions Explanation:

Storage Permission:

Purpose: Used to access and modify files on the device. When you use functions like sharing, vibrating step counting, or logging into your account, you can choose to enable this permission to read or write application usage information, images, videos, and intermediate data such as cached files and user-generated content.

Method: Accessed through the device's file system.

Scope: Collected only when the application needs to store or retrieve files, and used solely for the application's normal operations. If you do not need such services, you can disable this permission at any time without affecting other services.

Camera Permission:

Purpose: To provide photo or video recording functionality. When you connect devices via QR code scanning, change avatars, upload dials, bind public transport cards, or use group functions, we request and obtain this permission to complete photo shooting.

Method: Accessed through your device's camera.

Scope: Collected only when you actively use related functions, stored on your device or our servers. If you do not need such services, you can disable this permission at any time without affecting other services.

Location Permission:

Purpose: To provide location-based services. When you use functions such as generating trajectory images for single sports, Bluetooth pairing, weather alerts, or other location-related searches, you can choose to enable this permission to determine your current location information.

Method: Obtained through GPS, Wi-Fi, or other network positioning technologies. For example, for generating sports trajectories and synchronizing weather functions, the app requests access to map and location information permissions through Android's map and location APIs, and obtains and uses this information upon user consent.

Scope: Collected only when authorized and when related functions are activated, and may be used to provide location-related services or for statistical analysis. If you do not need such services, you can disable this permission at any time without affecting other services.

Bluetooth Usage Permission:

Purpose: To connect to Bluetooth devices, transmit data, or discover nearby Bluetooth devices, such as obtaining low-power Bluetooth device battery levels.

Method: Connected and data transmitted through your device's Bluetooth function.

Scope: Collected only when authorized and when related functions are activated, and used only for specified Bluetooth device connections and data transmission as requested by you.

Network Permission:

Purpose: Used to access the internet for data transmission, content loading, or communication with other servers. For example, used for application error log collection, application version update detection, authorization activation, account login, etc.

Method: Accessed through the device's network interface.

Scope: Continuously collected during application runtime to ensure normal network access and communication.

Access Device Information Status:

Purpose: To verify user device information to ensure compatibility and security of the application and services on specific devices. Necessary information is collected to provide personalized services, improve application functionality and performance, and for system analysis, troubleshooting, statistics, and anti-cheating mechanisms.

Method: Obtained through the device's system interface and embedded application mechanisms to obtain basic system information, device name, device identifier, etc. Relevant device information is collected when the device is first used or specific functions are triggered.

Scope: Collected information includes basic system information (such as operating system version), device name, device identifier (such as IMEI, Mac address, Android ID, Android Advertising ID, OAID, etc.). It may also include system logs, system usage information, device usage information (such as application installation list, usage statistics), and SIM card identification (such as IMSI). Information collection and use are strictly limited to the purposes stated in the privacy policy and comply with relevant legal requirements.

Phone Permission:

Purpose: Used for making or answering calls, or performing operations related to calls. When pairing with associated devices, using call functions on wearable devices, receiving incoming call information, etc., you can choose to enable this permission to access phone status.

Method: Accessed through the device's phone application.

Scope: Collected only when the application needs to make calls or perform related call operations, and used only for specified functions and services. Not consenting to this permission may affect other communication functions of the device.

Microphone Permission:

Purpose: Used for voice input. When issuing voice commands on wearable devices, using call functions, or transmitting data through audio interfaces, some Hi Yan devices require access to the microphone.

Method: Accessed through the device's microphone for recording.

Scope: Collected only when you use related functions. If you do not need such services, you can disable this permission at any time without affecting other services.

Call Log Permission:

Purpose: Used for contact search, making calls, or providing related social functions. When using wearable devices for missed call number pushing, controlling volume and call channels, etc., you can choose to enable this permission to display missed call numbers on paired devices and synchronize phone call status.

Method: Accessed through the device's call log application.

Scope: Collected only when you agree and provide authorization, and used for specified functions and services. If you do not need such services, you can disable this permission at any time without affecting other services.

Contact Permission:

Purpose: When using wearable devices and adding contacts to groups, you can choose to enable this permission to quickly import phone contacts for initiating calls or adding member information.

Method: Accessed through the device's call log application.

Scope: Collected only when you agree and provide authorization, and used for specified functions and services. If you do not need such services, you can disable this permission at any time without affecting other services.

SMS Permission:

Purpose: Used to read messages, MMS, or other forms of message content. When receiving SMS on wearable devices, rejecting incoming calls and sending messages, you can choose to enable this permission to send messages to designated contacts.

Method: Accessed through the device's messaging application.

Scope: Collected only when you agree and provide authorization, and used for specified functions and services. If you do not need such services, you can disable this permission at any time without affecting other services.

Notification Push Permission:

Purpose: Allows applications to obtain notification messages displayed on the user interface and push them to wearable devices for reminding users to perform certain operations or display important information.

Method: When installing or first using the application, the system prompts the user to grant or deny this permission. Users can authorize operations through the system settings or within the application's permission management interface.

Scope: Collected only when you agree and provide authorization, and used for specified functions and services. If you do not need such services, you can disable this permission at any time without affecting other services.

Notification Permission:

Purpose: Used to send notifications related to exercise reminders, health advice, achievement of exercise goals, health data updates, system messages, application updates, etc., so that users can promptly understand relevant information.

Method: When you enable health/exercise reminders, the app requests notification permissions through Android's notification API and sends notifications upon user consent.

Scope: Limited to sending notifications related to user exercise and health, without sending irrelevant or harassing information.

Background Running Permission:

Purpose: Ensures that the app continues to run in the background to provide continuous health monitoring, data synchronization, notification reminders, etc.

Method: When starting the sports/home location function, the app requests background running permissions through Android's battery and process management settings and maintains background processes upon user consent.

Scope: Limited to necessary operations and data processing while the app is running in the background.

Floating Window Permission (Android):

Purpose: Used to display floating windows on the screen, such as sports pedometers, timers, etc., allowing users to view and interact at any time.

Method: The app requests floating window permissions through Android's floating window API and displays floating windows on the screen upon user consent.

Scope: Limited to displaying floating windows related to app functions on the screen and allowing users to interact with them.

Calendar Permission:

Purpose (specific scenarios, such as event reminders): To add user sports plans or activities to the calendar for easier tracking and management.

Method: When setting up to-do reminders

1.4.2 Your Rights to Your Personal Information

You can contact us via email at 1694471633@qq.com.

(1) No Account Information Collection: This application is designed to be used without requiring users to register an account, so it does not collect personal identification information such as users' names, email addresses, or phone numbers.

(2) Device Information: To provide basic services, this application may need to access sensor data from the device (such as accelerometers). This data is only used for local processing and is not uploaded to any server or third party.

(3) Usage Data: To provide basic services, this application may need to access sensor data from the device (such as accelerometers). This data is only used for local processing and is not uploaded to any server or third party.