MiniClock Privacy Notice

Effective Date: December 02, 2025

“MiniClock” is developed and operated by Zhuhai Jinxin Interactive Technology Co., Ltd. This Privacy Notice is intended to help users understand how we collect and process personal information when you use “MiniClock”. In addition to this Privacy Notice, for other matters related to our collection and processing of personal information, please refer to our Privacy Policy.

“MiniClock” is a utility application available on Android, iOS, and HarmonyOS devices, providing features such as alarm reminders and anniversary reminders. We hope that through the following explanations, you can better understand how MiniClock obtains and uses your information so as to better protect your privacy.

1. Collection and Processing of User Information

We collect and process your information for the following purposes:

1) Account Registration and Login: You may register or sign in using your mobile phone number, WeChat, QQ, or other supported third-party accounts. If you choose to register or log in with your phone number, we will collect your phone number. If you choose a third-party account, we will obtain your basic profile information, such as your nickname and avatar, as authorized by the third-party platform. We also collect necessary device information for account security, data synchronization, and login. If you do not provide such information, some account-related features may not function properly. To delete your account, please refer to Section 4 "Account Deletion" of this Privacy Notice.

2) Product Operation and Feature Improvement: To continuously improve our products and user experience, we collect necessary usage information, including page views, feature interactions, app version, device model, and operating system version.

3) The information above is used solely to analyze feature usage, improve product functionality and user experience, troubleshoot issues, enhance app stability, and compile operational statistics. It is not used to identify you personally or for targeted advertising.

4) The above information is transmitted securely and processed using encryption, anonymization, or de-identification where appropriate, in accordance with the principle of minimum necessary collection.

When you use these features on your mobile device, we also need to obtain certain device information for purposes such as account security verification, data synchronization, and account login. If you do not agree to provide such information, data synchronization and account login may be affected.

If you wish to cancel your account, please follow the instructions in Section 4 “Account Cancellation” of this Privacy Notice.

2. Permissions and Their Purposes

2.1 Permissions Requiring User Authorization

When you use MiniClock on your mobile device, we may request certain device permissions. The permissions and their purposes are as follows:

Android Application:

Permission Name	Acquisition Method	Purpose
Access Phone State	Dynamically requested, requires user authorization	To obtain device identifiers for installation statistics, user data synchronization, and account login.
Display Over Other Apps	Dynamically requested, requires user authorization	To allow the alarm interface to appear over other applications when an alarm is triggered.
Allow Notifications	Dynamically requested, requires user authorization	To display notifications in the status bar when the alarm is ringing or to remind users that the alarm is active.
Vibration Permission	Dynamically requested, no user authorization required	To enable vibration during alarms when the user has enabled vibration in the ringing interface.
Read External Storage	Dynamically requested, requires user authorization	To allow users to select ringtones and other media from their device for alarm sounds.
Read Device Wallpaper Information	Dynamically requested, requires user authorization	To obtain the current wallpaper as the preview background for widgets.

2.2 Permissions Obtained in Specific Usage Scenarios

1) When the mobile system starts: Receive system boot completion broadcasts to automatically start the alarm service.

2) When using alarm and reminder features: Vibration permission, alarm permission, exact alarm permission, foreground service, and foreground media playback permissions are used to provide reminder services.

3) When using user settings and preferences: External storage permission is used to store user-selected notification sounds.

4) When using widget features: External storage permission is used to obtain the user’s wallpaper to better display widget effects.

3. Third-Party Services

To ensure the proper operation of MiniClock or to implement related features, we may integrate third-party services through SDKs, APIs, or plugins. Prior to integration, we conduct strict security testing and privacy assessments to safeguard user privacy and personal information security.

These third-party service providers are independent information controllers and shall bear full responsibility for their own information collection and processing activities. You may click on the relevant third-party SDK links to learn more about their specific data collection and processing practices.

3.1 Bugly SDK

Partner Entity: Shenzhen Tencent Computer Systems Company Limited

Purpose: To collect crash reports and error logs for timely troubleshooting

Usage Scenario: When an exception occurs during app operation

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device identifiers and system version. If the app crashes while running in the background, the SDK may collect the above personal information to assist in crash diagnostics.

Data Processing Method: Encryption, anonymization, and other security measures

Official Website: https://bugly.qq.com/v2/

3.2 Security Authentication / One-Click Login

3.2.1 Jiguang Security Authentication SDK

Partner Entity: Shenzhen Hexun Huagu Information Technology Co., Ltd.

Purpose: To provide one-click verification, security risk control, and auto-start services

Usage Scenario: One-click login with the local phone number

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device information and network information, including necessary identifiers (such as IDFA, Android ID, GAID, OAID, UAID, ICCID, ODID, AAID, or other device identifiers), device hardware information (model, screen resolution, manufacturer, product name), operating system information (OS version, system name, system language), network information (network type, carrier name, IP address, Wi-Fi status), and mobile phone number.

Optional information may include device identifiers (IMEI, MAC, IMSI), base station information, location-related information, and software list information, which are used for risk analysis, fraud prevention, and improving account security.

Data Processing Method: De-identification, encrypted transmission, and other security measures

Official Website: https://www.jiguang.cn

3.2.2 China Unicom One-Click Login

Partner Entity: China United Network Communications Group Co., Ltd.

Purpose: One-click login

Usage Scenario: When users quickly register or log in with a Unicom mobile number

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device platform, manufacturer, brand, model, system version, device identifier (OAID), anonymized phone number, and network information

Official Website: http://www.chinaunicom.com.cn/about/about.html

3.2.3 China Mobile One-Click Login

Partner Entity: China Mobile Internet Co., Ltd.

Purpose: One-click login

Usage Scenario: When users quickly register or log in with a China Mobile number

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device platform, manufacturer, brand, model, system version, device identifier (OAID), anonymized phone number, and network information

Official Website: https://cmic.chinamobile.com/

3.2.4 China Telecom One-Click Login

Partner Entity: Century Dragon Information Network Co., Ltd.

Purpose: One-click login

Usage Scenario: When users quickly register or log in with a China Telecom number

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device platform, manufacturer, brand, model, system version, device identifier (OAID), anonymized phone number, and network information

Official Website: https://id.dlife.cn/api?initialSrc=/html/api_detail_634.html

3.3 Push Notification Services

3.3.1 Jiguang Push SDK

Partner Entity: Shenzhen Hexun Huagu Information Technology Co., Ltd.

Purpose: To provide push notification services to app users

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device identifiers, hardware information, operating system information, network information, and push logs necessary to ensure compatibility, accuracy, and delivery of push notifications. Optional information may be used to improve delivery accuracy and relevance.

Official Website: https://www.jiguang.cn/

3.3.2 Huawei Push SDK

Partner Entity: Huawei Software Technologies Co., Ltd.

Purpose: To deliver notifications via Huawei channels

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device information, app information, operating system version, push token, and notification status

Official Website: https://www.huawei.com/cn/

3.3.3 OPPO Push SDK

Partner Entity: Dongguan Yongsheng Communication Technology Co., Ltd.

Purpose: To deliver notifications via OPPO channels

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Push message content

Official Website: https://www.oppo.com/cn/

3.3.4 vivo Push SDK

Partner Entity: Vivo Mobile Communication Co., Ltd.

Purpose: To deliver notifications via vivo channels

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Push message content

Official Website: https://www.vivo.com.cn/

3.3.5 Meizu Push SDK

Partner Entity: Zhuhai Meizu Communication Equipment Co., Ltd.

Purpose: To deliver notifications via Meizu channels

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device information, app information, notification settings, push message status and content, hardware serial number, and carrier information

Official Website: https://www.meizu.com/

3.3.6 Xiaomi Push SDK

Partner Entity: Beijing Xiaomi Mobile Software Co., Ltd.

Purpose: To deliver notifications via Xiaomi channels

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device information, app information, network information, and push message content

Official Website: https://www.mi.com/

3.3.7 Honor Push SDK

Partner Entity: Shenzhen Honor Software Technology Co., Ltd.

Purpose: To deliver notifications via Honor channels

Usage Scenario: When sending notifications to users

Collection Method: Automatically collected by the SDK

Personal Information Involved: Device information and device identifiers

Official Website: https://developer.honor.com/

3.4 WeChat Open Platform SDK

Partner Entity: Shenzhen Tencent Computer Systems Company Limited

Purpose: WeChat login, account binding, and sharing to WeChat

Usage Scenario: When logging in, binding, or sharing via WeChat

Collection Method: Automatically collected by the SDK

Personal Information Involved: None

Official Website: https://open.tencent.com/

3.5 Tencent Open Platform SDK

Partner Entity: Shenzhen Tencent Computer Systems Company Limited

Purpose: QQ login, account binding, and sharing to QQ contacts or QQ Zone

Usage Scenario: When logging in, binding, or sharing via QQ

Collection Method: Automatically collected by the SDK

Personal Information Involved: IDFA, OAID, clipboard information (iOS only)

Official Website: https://open.tencent.com/

3.6 Alipay App Login (Lite SDK)

Partner Entity: Alipay (China) Network Technology Co., Ltd.

Purpose: Alipay login

Usage Scenario: When logging in via Alipay

Collection Method: Automatically collected by the SDK

Personal Information Involved: None

Official Website: https://open.alipay.com/

3.7 Third-Party Payment SDK (Alipay Payment)

Partner Entity: Alipay (China) Network Technology Co., Ltd.

Purpose: To enable in-app payments via Alipay

Usage Scenario: When users make payments

Collection Method: Automatically collected by the SDK

Personal Information Involved: Android ID, OAID, Wi-Fi name, Alipay app installation information, device serial number, WLAN access point information, and IP address

Official Website: https://open.alipay.com/

3.8 Third-Party Payment SDK (WeChat Pay)

Partner Entity: Tenpay Payment Technology Co., Ltd.

Purpose: To enable in-app payments via WeChat Pay

Usage Scenario: When users make payments

Collection Method: Automatically collected by the SDK

Personal Information Involved: Android ID, OAID, Wi-Fi name, WeChat app installation information, device serial number, and IP address

Official Website: https://www.tenpay.com/v4/index.html

4. Account Deletion

1) If you registered using a mobile phone number, you may delete your account within the MiniClock app by navigating to: “My” → “About Us” → “Delete Account”.

2) If you logged in via QQ or WeChat or Alipay, you may revoke MiniClock’s authorization from your QQ or WeChat or Alipay account center.

3) If you are unable to delete or unbind through the above methods, you may contact us at support@jinpaw.cn. We generally respond within 15 days.

5. How to Contact Us

If you have any questions, comments, or suggestions regarding this Privacy Notice, you may contact us through the following methods:

1) Registered Address: Room 8-1-404, No. 8 Cuiwei West Road, Xiangzhou District, Zhuhai City, China

2) Contact Information:

Email: support@jinpaw.cn

6. Updates to This Privacy Notice

As MiniClock is updated, we may add, adjust, or remove related features from time to time.

When there are significant changes to our policies regarding the collection and processing of personal information, we will update this Privacy Notice accordingly.

If you have any questions about MiniClock’s privacy practices, please contact our privacy officer at support@jinpaw.cn. We generally respond within 15 days.