aiCare Privacy Policy
Last updated: October 23, 2026
Effective date: October 21, 2026
Introduction
aiCare (the “App”) is a personal health management application developed and operated by AIH LLC (“we,” “us,” or “our”). By connecting to health devices such as smart rings, blood pressure monitors, pulse oximeters, thermometers, blood glucose meters, and body composition scales, the App helps you record and review your health information. You may also choose to share health information with other users you follow or authorize, including family members or friends.
We recognize the importance of your personal information and process it in accordance with applicable law, following the principles of lawfulness, fairness, necessity, and transparency.
This Policy applies when you select the App’s Global service region. The China service region has a separate privacy policy and a different operator and authentication and push notification services. Please read this Policy carefully before using the App, especially the provisions in bold. Selecting “Agree” indicates your consent to this Policy. Before processing sensitive personal information or sharing your personal information with other users, we will explain the relevant processing and obtain your separate consent. If you do not agree, you may choose not to use the App.
Health information, reminders, and reference classifications provided by the App are for everyday health management only. They do not replace professional medical diagnosis or treatment. In an emergency, call the appropriate emergency number immediately.
This Policy explains:
- I. How We Collect and Use Your Personal Information
- II. Device Permissions and Sensitive Device Access
- III. Automatic Startup and Opening Other Apps
- IV. Third-Party SDKs and Service Providers
- V. How We Store Your Personal Information
- VI. How We Share, Entrust, Transfer, and Disclose Your Personal Information
- VII. Your Rights
- VIII. How We Protect Your Personal Information
- IX. Protection of Minors’ Personal Information
- X. Changes to This Policy
- XI. How to Contact Us
- Appendix 1: Personal Information Collection List
- Appendix 2: Personal Information Sharing List
I. How We Collect and Use Your Personal Information
We collect and use personal information only to the extent necessary for the functions described below. Before you agree to this Policy, the App does not activate personal information collection functions or third-party SDK functions that collect personal information, or send business service requests. If you choose to open the Privacy Policy or Terms of Use webpage, the website processes technical information necessary to establish the connection, such as your IP address, access time, and page request, solely to deliver the page and provide necessary security. These pages do not load analytics, tracking, or other data collection SDKs.
1. Registration and Sign-In
- Email registration and sign-in: When you register or sign in using an email address, we process your email address and password to create your account and verify your identity. Password recovery uses your email address and email verification code. Without this information, email registration, sign-in, or password recovery will not be available.
- Google sign-in: On Android and iOS, you may choose to sign in with Google. With your authorization through Google, we receive your Google account identifier and the name, email address, and profile picture made available through your authorization, together with the credentials needed to complete sign-in. Available profile information may be used to prefill your account profile, which you can edit.
- Sign in with Apple: On iOS, you may choose Sign in with Apple. With your authorization, we receive your Apple sign-in account identifier, authentication credentials, and the name and email address you choose to share. If you choose Apple’s private email relay, we receive the relay address instead of your personal email address. The availability of name and email information depends on your authorization and Apple’s sign-in process.
- Global-region account authentication is provided through Auth0 (Okta). Phone-number/SMS sign-in, WeChat sign-in, and Authing authentication described in the China-region policy are not the Global-region sign-in methods covered by this Policy. See Section IV for information about authentication providers.
2. Personal Profile
To establish your profile and calculate and display health indicators relevant to you, you are asked to provide your name, sex, date of birth, and height. You may also provide a profile picture, weight, email address, and phone number, and select display units for height, weight, temperature, and blood glucose.
- Date of birth, sex, height, and weight are used to calculate body composition, health scores, and reference ranges based on age and sex. Not providing weight may prevent calculation of certain indicators, but does not prevent use of other functions.
- To set a profile picture, you may take a photo or select one from your photo library. The App crops and compresses the selected image on your phone before uploading it to our server. The App does not read other photos in your library.
- You can review and edit this information under “Me > Personal Information.”
3. Connecting Health Devices and Recording Health Information
The health information and associated device records below are sensitive personal information. We process them to provide device connectivity, health records, trends, health scores, and alerts. Unauthorized disclosure or misuse could affect your personal or financial safety or expose you to discrimination. Before first processing your health information, we will explain the purposes, methods, categories, necessity, and potential effects on your rights, and obtain your separate consent. This also covers accessing existing cloud health records, synchronizing device history, automatic synchronization, and subsequent analysis; agreeing to this Policy alone does not replace that consent. If you do not consent, you may still use account and messaging functions that do not involve processing health information. You can contact us to withdraw consent to health information processing and request that further processing stop and relevant information be deleted, as explained in Section VII.
- Device information: When you add a device, we collect its Bluetooth MAC address, serial number, model, name, and firmware version to identify and manage devices associated with your account and distinguish the sources of your records.
- Smart ring: Heart rate, blood oxygen saturation, temperature, step count, distance, calories burned, sleep information (sleep and wake times and durations of awake, light sleep, deep sleep, and rapid eye movement sleep), and heart rate variability, together with sleep, activity, and recovery scores calculated from these data. Heart rate variability is used only locally on your phone to calculate scores and is not uploaded to servers.
- Blood pressure monitor: Systolic pressure, diastolic pressure, and pulse rate.
- Pulse oximeter: Blood oxygen saturation and pulse rate.
- Thermometer: Temperature.
- Blood glucose meter: Blood glucose readings and measurement periods, such as fasting, before a meal, or after a meal.
- Body composition scale: Weight, impedance, and heart rate where supported, and calculated body fat percentage, muscle mass, bone mass, body water percentage, protein percentage, visceral fat rating, basal metabolic rate, body age, body type, and other body composition indicators, based on weight, impedance, height, age, and sex. The scale provider’s cloud algorithm service calculates body composition; see Section VI.2. Impedance is used for body composition calculations and is not uploaded to our own business servers. Complete measurement records and pending-upload caches stored locally on your phone may contain impedance for displaying results, recalculating, and performing uploads or retry uploads you have authorized. When you connect a scale that supports offline history, the App also uses the local SDK to send account and member association identifiers, age, sex, and height to the scale for member recognition and offline records. This local SDK/device interaction is separate from cloud algorithm processing; see Section IV.
- Manual records: You can manually enter, edit, and delete heart rate, blood oxygen, blood pressure, blood glucose, weight, and temperature records.
- Ring SOS records: When you make the SOS gesture on the ring, we record the trigger time and the ring’s MAC address and serial number for you to review. An SOS record does not notify emergency services, your family, or other users. The App does not automatically make a call, send an SMS, or obtain your location in response to this gesture. In an emergency, call emergency services directly.
Measurement error reports and device synchronization diagnostics may contain information related to health measurements. Their purposes, recipients, and scope are described in Sections I.10 and IV; processing that involves health information is subject to the separate consent described above.
4. Health Goals and Measurement Reminders
- Health goals: When you set daily step, sleep duration, or target weight goals, we store the target values you set to display your progress.
- Measurement reminders: If you set reminders for blood pressure, blood oxygen, temperature, heart rate, or blood glucose measurements, the reminder times are stored only on your phone and the operating system delivers local notifications at the scheduled times.
5. Health Alerts and Emergency Numbers
- Health alerts: Our servers analyze your health information to identify situations that may need attention, such as a high blood pressure reading, and notify you within the App or by push notification. If you mark an alert as read, handled, or ignored, we store the status you select.
- Emergency numbers: When a health alert offers an emergency call option, the App reads your mobile network country or region code, which does not require a permission prompt, to display the appropriate number. Only if that code is unavailable and you have already granted location permission does the App read your most recent approximate location once, locally, to derive a country or region code. Location coordinates are not uploaded or saved; only the country or region code is used to look up the emergency number. You must actively select the number to open the system dialer. The App does not automatically place the call.
6. Following, Authorization, and Communication
- Finding other users: You can search by name or aiCare ID for other users you wish to follow.
- Following and authorizing access: Before you follow another user and authorize access to your health information, the confirmation page will identify the actual recipient by name, contact details, and organization, if any, and explain the purposes, methods, and information covered. We will obtain your separate consent. Once you consent, the recipient identified on that page may view your name, sex, date of birth, height, weight, profile picture, and all your health information, including health alerts, for the health information communication and management you choose. Your phone number and email address are excluded from this sharing. You can stop following at any time under “Me > My Doctors.” We then stop providing health information access based on that following relationship. “My Doctors” is a navigation label in the App; this Policy does not imply that every user found there holds a professional qualification. Retention of messages already sent and records lawfully retained is explained in Sections V.2 and VII.
- Messaging: When you communicate with another user you follow, we process message content, sending times, and read status to deliver and synchronize messages. The other user may send notification cards about meetings, reports, or intervention plans. Selecting a card may open another of our apps, as explained in Section III.
7. Health Sharing with Family or Friends
Search and invitations: You can search for and invite family members or friends by aiCare ID, name, or email address. Search results show only the person’s name, profile picture, and aiCare ID. We process invitations, relationships, note names, and each person’s sharing settings.
Allowing others to find you: Other users can find you by searching for your exact aiCare ID. To be found by name or email address, you must actively enable “Allow others to find me by name or email.” This setting is off by default. Search results display only your name, profile picture, and aiCare ID, without revealing your email address or phone number. You can turn this option off under “Me > General Settings > Privacy Settings.” Doing so immediately stops discovery by name or email. It does not affect existing relationships or chats and does not itself end health sharing. New relationships and health sharing still require your separate confirmation.
Providing information to family or friends: When sending or accepting an invitation, you must actively choose what the other person can view. The App does not preselect a sharing scope for you:
- “All data”: The other person can view your vital signs, sleep, activity, all measurement records, and health alerts.
- “Not allowed”: The other person cannot view your health information; you can still chat with each other.
You can change the viewing scope or end the relationship at any time under “Me > Health Sharing,” with immediate effect. For existing relationships previously set to “Alerts and summary only,” the other person can view only your health alerts and periodic health summaries (average, maximum, and minimum values), without access to individual records.
Alert notifications: Family members or friends whom you authorize to view “All data” may choose to receive notifications when you have a health alert.
Family and friend messaging: We process message content, sending times, and read status when you communicate with family members or friends.
8. Ring Message and Incoming Call Reminders
The following functions operate only when you actively enable them, and you can turn them off at any time:
- Message reminders: You must grant notification access in your phone’s system settings. The App reads only the identifier of the app that generated a new notification, checks whether it is on your selected reminder list, and, if so, makes the ring vibrate. The App does not read, store, or upload notification titles or content. When you open the reminder app selection page, the App reads your installed app list (app names and icons) once so you can choose which apps trigger reminders. This list is used only on your phone and is not uploaded.
- Incoming call reminders: You must grant phone state access. The App uses ringing, answered, and ended call states to control ring vibration. It does not read phone numbers, contacts, call content, or call history.
9. Push Notifications
The Global service uses Firebase Cloud Messaging (FCM) to deliver messages from other users, family messages, and health alerts. On iOS, delivery also uses Apple Push Notification service (APNs). We generate a random app installation identifier and upload it, together with the push token assigned for your installation, to our servers to address notifications to your device. Information processed by notification service providers is described in Section IV. You can turn off notifications for the App in your phone’s system settings.
10. Service Stability, Diagnostics, and Security
Our servers record network request logs, including access times, requested endpoints, and IP addresses, to investigate faults and protect accounts and services.
The Global service also uses Firebase Crashlytics and Firebase Analytics to diagnose crashes and measurement or synchronization failures and understand App usage. These services process installation or app-instance identifiers, device model, operating system and App versions, crash and diagnostic logs, and App usage events. Measurement error reports can include the measurement type, platform, and the raw measurement/error value received by the App. Scale history synchronization events include the scale’s reported name, device capability information, read outcome, counts of received and saved records, counts of records without timestamps, and whether saving failed. These reports help identify faults and determine whether device history functions work correctly. They are not used for advertising. Information related to health measurements remains protected as personal information and is subject to the health processing consent described in Section I.3.
11. Processing Without Consent Where Permitted by Law
Where applicable law permits or requires processing without consent, we may process personal information as necessary to perform a contract with you, comply with a legal obligation, respond to a public health emergency, or protect a person’s life, health, or property in an emergency. Processing for a legally recognized public interest or of lawfully public information will occur only within the scope permitted by applicable law. We do not treat these exceptions as blanket permission to process information for other purposes.
12. Processing We Do Not Undertake
- The App itself does not read your contacts, SMS messages, call history, or clipboard, and does not continuously obtain or upload your location. Device information processed by third-party SDKs is described in Section IV.
- We do not use your personal information for personalized recommendations, targeted advertising, displaying advertisements, or marketing. Service and health notifications described in this Policy are used to provide the functions you choose.
- We do not use your personal information for purposes outside this Policy without first obtaining your consent where required by applicable law.
II. Device Permissions and Sensitive Device Access
The App requests the following permissions only when needed for the corresponding function and explains their purpose at the time of the request. You can refuse a request or withdraw permission in system settings. Doing so affects the corresponding function without preventing use of unrelated functions. Availability and permission names depend on your phone and operating system.
| Permission / sensitive access | Purpose | Effect of refusal |
|---|---|---|
| Bluetooth / Nearby devices | Scan for and connect to your health devices and synchronize records | Device connections are unavailable; manual records remain available |
| Location (Bluetooth scanning on Android 11 and earlier) | Required by those Android versions for Bluetooth scanning; if the mobile network country code is unavailable and location permission was already granted, derive an emergency-number country or region code from an approximate location locally, without uploading coordinates | Bluetooth scanning on affected Android versions is unavailable; the location fallback for emergency-number lookup is unavailable |
| Camera | Take a profile photo | You cannot take a photo for your profile |
| Photos / Storage | Select a profile picture from your photo library | You cannot select a profile picture from the library |
| Notifications | Receive messages, health alerts, and measurement reminders | Notifications cannot be delivered or displayed as allowed by the system |
| Phone state | Detect call states for ring incoming call reminders | The ring will not vibrate for incoming calls |
| Notification access (special system access) | Read only the originating app identifier for ring message reminders | The ring will not vibrate for message notifications |
| Installed app list | Read once when opening the message reminder app selection page; used locally to choose the reminder list, without uploading it | Reminder apps cannot be selected through that list |
| Alarms and reminders / Exact alarms | Deliver measurement reminders at the time you set | Reminders may be delayed |
| Foreground service / Battery optimization exemption | Maintain the ring connection when “Background Running” is enabled so ring message and call reminders can work | Reminders may stop working when the App is in the background |
III. Automatic Startup and Opening Other Apps
To restore measurement reminders and deliver notifications, the system may start App components in the circumstances below. The App does not automatically open other apps in the background.
1. Automatic Startup
(1) Restoring measurement reminders
- Purpose: Restore scheduled local reminders after a phone restart or App update, when the system clears their schedules.
- Triggers: Device startup completion (
BOOT_COMPLETEDorQUICKBOOT_POWERON) or completion of an App update (MY_PACKAGE_REPLACED). - Component: The local notification component’s reminder restoration receiver (
ScheduledNotificationBootReceiver). - Information involved: Reads locally saved reminder times only, without additional personal information collection or network requests.
(2) Push notification delivery
- Purpose: Deliver messages and health alerts promptly.
- Triggers: After you agree to this Policy and use the Global service, FCM and, on iOS, APNs may deliver notifications while the App is in the background or start the relevant notification handling component when a notification arrives, subject to system restrictions.
- Components: Firebase Cloud Messaging and system notification services.
- Information involved: See Sections I.9 and IV.
(3) Background ring connection
- Purpose: Maintain the ring connection so message and call reminders work.
- Triggers: Only when you enable “Background Running” and ring message or incoming call reminders. During App use, Android runs a foreground service with an ongoing notification; the service stops when you close the App.
- Component: The ring connection foreground service.
- Information involved: No additional categories of personal information beyond those required for the ring functions you enabled.
(4) Notification listener service
- Purpose: Enable ring message reminders.
- Triggers: After you grant notification access, the system binds the App’s notification listener service according to its own rules.
- Information involved: Only the identifier of the app that generated a notification, as described in Section I.8.
2. Opening Other Apps
The App opens the following only when you actively select the corresponding action:
- Google or Apple sign-in pages, system sign-in interfaces, or the browser, when you select those sign-in methods;
- Our aiSpine (AIHealth) app, when you select “View in aiSpine” on a message card; if it is not installed, an app store page is opened so you can download it;
- The system dialer, when you select an emergency number;
- System settings, when you choose to manage Bluetooth, notifications, notification access, battery optimization, or related settings.
3. Your Controls
You can:
- Turn off the background connection under “Me > General Settings > Background Running”;
- Turn off measurement reminders under “Me > Measurement Reminders,” after which those reminders no longer need startup restoration;
- Turn off automatic startup, background operation, notifications, and notification access in your phone’s system settings.
These choices may affect measurement reminders, push notifications, and ring message or incoming call reminders, but do not prevent use of other functions.
IV. Third-Party SDKs and Service Providers
The App integrates the SDKs and services below to provide the functions in this Policy. Functions that collect personal information or access business services are enabled only after you agree to this Policy and process information only as necessary for the corresponding function. We assess providers’ security capabilities and require them to comply with applicable law and our arrangements with them.
In the table, “local processing” means an SDK runs on your phone or exchanges information with your connected device through Bluetooth, without thereby sending the listed information to the SDK provider. “Processing on our behalf” means a provider processes information for agreed service purposes under our instructions. For providers that process information for their own service purposes, their privacy policies also explain that processing. Account association identifiers remain personal information even when hashed or otherwise de-identified; they are not treated as anonymous merely because a name has been removed.
| SDK / service name | Package / components | Developer / provider | Purpose | Personal information processed | Processing arrangement | Privacy policy / contact information |
|---|---|---|---|---|---|---|
| Auth0 authentication | com.auth0 | Auth0 (Okta) | Global account registration, sign-in, password recovery, and identity verification | Email address, password, verification information, third-party sign-in credentials and account identifiers; technical authentication information such as IP address and device/browser information | Authentication service provider; see its policy for provider processing | https://www.okta.com/privacy-policy/ |
| Google Sign-In | — (Google authentication service) | Google LLC | Optional Google account sign-in on Android and iOS | Authorized account identifier, name, email address, profile picture, and sign-in credentials; technical information needed to complete sign-in | Information received through your authorization; Google processes sign-in information under its own policy | https://policies.google.com/privacy |
| Sign in with Apple | — (iOS system authentication service) | Apple Inc. | Optional Apple account sign-in on iOS | Sign-in identifier and credentials; name and email address you choose to share, which may be an Apple private relay address | Information received through your authorization; Apple processes sign-in information under its own policy | https://www.apple.com/legal/privacy/en-ww/ |
| Firebase Crashlytics, Firebase Analytics, and Firebase Cloud Messaging | com.google.firebase | Google LLC | Global crash diagnostics, usage and measurement/synchronization event analysis, and push notifications | Installation/app-instance identifiers, push tokens, device and operating system information, App version, crash and diagnostic logs, usage events; measurement type and raw measurement/error values in error reports, and scale history synchronization information described in Section I.10 | Cloud service processing for diagnostics, analytics, and delivery; see the provider’s service-specific privacy information | https://firebase.google.com/support/privacy |
| Apple Push Notification service (APNs) | — (iOS system push service) | Apple Inc. | Deliver push notifications on iOS | Device push token and notification delivery information | System push delivery service; used with FCM for Global notifications | https://www.apple.com/legal/privacy/en-ww/ |
| 友盟+消息推送SDK | com.umeng.message; basic component com.umeng.commonsdk, device identification component com.umeng.umzid; push channel components com.taobao.accs, org.android.agoo | 友盟同欣(北京)科技有限公司 | Push notifications for the China service. Global notifications use FCM, and selecting Global stops Umeng push | When the China push service is enabled: device identifiers (Android ID, OAID and, where phone permission and the operating system allow, IMEI, IMSI, or ICCID), device model, operating system version, manufacturer, network type, carrier information, and push token | Provider processing for the China push service; see the China-region policy if you select that service | https://www.umeng.com/page/policy |
| 友盟+移动统计SDK | com.umeng.analytics; basic component com.umeng.commonsdk, device identification component com.umeng.umzid | 友盟同欣(北京)科技有限公司 | Initialized with the China-region push service for App usage and active-use statistics and service operations analysis; Global notifications use FCM | Device and App information, device identifiers, network information, and page and App usage statistics (page names, access times, and duration); access to device identifiers is subject to your permissions and operating system restrictions | Provider processing for the China service; see the China-region policy if you select that service | https://www.umeng.com/page/policy |
| HTTPDNS-android | com.alibaba.sdk.android.httpdns | 杭州阿里云智能科技有限公司 | Domain resolution and connection reliability for China-region push-related connections, caching and updating resolution results, and resolution service usage statistics; Global notifications use FCM | Device information (brand and model), system information (operating system version), network information (network type), and technical resolution information such as requested domains and resolution results | Provider processing for the China push service; see the China-region policy if you select that service | https://terms.aliyun.com/legal-agreement/terms/suit_bu1_ali_cloud/suit_bu1_ali_cloud202112071754_83380.html?spm=a2c4g.11186623.0.0.598730e5wsglWa |
| 微信OpenSDK Android | com.tencent.mm.opensdk | 深圳市腾讯计算机系统有限公司 | WeChat account sign-in on Android for the China service; not enabled as a Global-region sign-in service | WeChat nickname, profile picture, and unique account identifier you authorize; whether WeChat is installed on the phone | Provider processing for China-region sign-in; see the China-region policy if you select that service | https://support.weixin.qq.com/cgi-bin/mmsupportacctnodeweb-bin/pages/RYiYJkLOrQwu0nb8 |
| AIZO smart ring SDK | com.eiot; built-in firmware update components: Realtek DFU com.realsil.sdk and Bluetrum FOTA com.bluetrum.fota | 深圳市研强物联技术有限公司 (AIZO) | Connect to the ring, read health information, and calculate health scores locally; ring firmware updates run locally over Bluetooth through the built-in update components, with no information sent to Realtek or Bluetrum; retrieve service configuration during ring connection and report activation when the ring first produces health information | Ring Bluetooth MAC address, serial number, model, software/hardware versions, activation time, and an identifier associated with your App account; health information is processed locally and is not uploaded through this SDK | Provider processing of configuration/activation information; local health information processing | https://cftweb.3g.qq.com/privacy/privacyPolicy?content_id=644176124d54819011c38266f5733a7d |
| Body composition scale SDK | com.peng.ppscale, com.lefu | 深圳市乐福衡器有限公司 (Lefu) | Connect to the scale by Bluetooth, exchange member profile information, read measurements and offline records, and cache records locally | Account and member association identifiers, age, sex, height, device information, weight, impedance, heart rate where supported, and measurement time | Local processing and transmission to your connected scale; this interaction does not itself send the information to the provider | https://www.lefu.cc/ |
| Body composition cloud algorithm service | — (cloud service) | 深圳市乐福衡器有限公司 (Lefu) | Calculate body composition from measurements and profile parameters | Weight, impedance, height, age, sex, other necessary algorithm parameters, and necessary network communication information; business parameters do not include your name, phone number, or account identifier, but are still protected as personal information | Processing on our behalf; see Section VI.2 | No separate SDK privacy policy is provided; processing rules are described in Section VI.2. Provider website: https://www.lefu.cc/ |
| Blood pressure monitor, pulse oximeter, and thermometer SDK | com.aojmedical.plugin | Shenzhen AOJ Medical Technology Co., Ltd. | Connect to devices by Bluetooth and read measurements | Device Bluetooth MAC address and measurement results | Local processing without sending the listed information to the provider; the SDK does not access the network | https://www.aojmedical.com/privacy-policy-a00021a1.html |
China-region Authing authentication and WeChat sign-in, including WeChat OpenSDK for iOS, are covered by the China-region policy and are not Global-region sign-in services. Switching regions changes the applicable service and privacy policy; it does not itself constitute consent to new processing.
V. How We Store Your Personal Information
1. Storage Locations and International Processing
- When you select the Global service, your account, profile, health records, and other service information are stored on our operating servers outside mainland China. The Global service and its authentication, notification, diagnostics, and device service providers may process information in more than one country or region. The processing locations may differ from your country of residence.
- We protect information transferred between countries or regions in accordance with applicable law, explain relevant recipients, purposes, methods, and information categories, and obtain separate consent or take other measures where required. This Policy does not mean that all Global information is stored in one country or that every provider uses the same storage location.
- If you switch to the China service, processing under that service is governed by its separate privacy policy. Before a change involving transfer of your information across borders, we will provide the required information and obtain your separate consent where applicable. Changing the region alone does not authorize the transfer of your existing records.
2. Retention
We retain your personal information for no longer than necessary for the purposes described in this Policy:
- Account details, profile information, health records, and messages are kept during the account’s existence to the extent needed to provide the corresponding service. When you delete a record, we delete the corresponding record in online business systems. Backup copies are removed through backup rotation and are no longer used for routine business processing.
- Complete measurement records and pending-upload caches on your phone are kept only as long as needed to display results, recalculate, and perform uploads or retry uploads you have authorized.
- Security logs are retained for the periods required by applicable law. Other diagnostic and operational logs are kept for the shortest period needed for their purpose, then deleted or anonymized. We do not apply one statutory retention period to every kind of log.
- After you request account deletion, our processing target is to complete deletion or anonymization of your personal information within 15 working days after receiving the request. If identity verification is needed, we request only the minimum necessary information; see Section VII.
- Where legally required retention has not expired, or deletion is technically difficult, we restrict processing to storage and necessary security protection. Backup copies are cleared according to rotation schedules, and effective deletion requests continue to apply if a backup is restored.
- Messages you have already sent to other users may be lawfully retained by them, and records subject to legal retention requirements follow the relevant periods. Deleting your account does not unconditionally erase messages lawfully held by another person or records an organization must retain. We stop further health information access based on your former following and sharing relationships.
VI. How We Share, Entrust, Transfer, and Disclose Your Personal Information
1. Sharing with Others
We do not sell your personal information. We do not provide it to others except in the following circumstances:
- With your separate consent, we provide your profile and all your health information to the other users you choose to follow and authorize, within the scope explained in Section I.6.
- With your separate consent, we provide health information to family members or friends you invite or accept, within the scope you actively select, as explained in Section I.7.
- Other users can find you using your exact aiCare ID. They can find you by name or email only after you actively enable that option. Search results display only your name, profile picture, and aiCare ID; see Section I.7 for controls.
- We may provide information where required or permitted by applicable law, for lawful dispute resolution, or in response to a lawful request from an authorized public authority.
Information processed directly by third-party SDK or service providers when you use the relevant functions is described in Section IV.
2. Service Providers Processing on Our Behalf
- We engage cloud infrastructure providers to supply servers and data storage for the Global service.
- We use Auth0 (Okta) for Global account authentication and Firebase services for diagnostics, analytics, and push delivery, within the purposes and information scope described in Sections I and IV.
- We engage 深圳市乐福衡器有限公司 (Lefu) to calculate body composition using weight, impedance, height, age, sex, and other necessary algorithm parameters. Although the business parameters do not include your name, phone number, or account identifier, measurement and profile parameters and necessary network communication information remain personal information. Removing your name does not make them anonymous. The provider may process the information only for the agreed calculations and necessary security, not for unrelated purposes, and retention is limited to what is necessary and legally required. Account association identifiers sent to the scale through its local SDK are separate from the business parameters of the cloud algorithm request.
For processing on our behalf, we specify the purposes, duration, methods, personal information categories, safeguards, and respective rights and responsibilities in our arrangements with providers and oversee their processing activities. A provider’s processing for its own service purposes, where applicable, is also addressed in its privacy policy.
3. Business Transfers
We do not transfer your personal information to another company, organization, or person without your separate consent, except where a merger, division, dissolution, bankruptcy, or similar transaction requires a transfer in accordance with applicable law. We will notify you of the recipient’s name and contact details and require the recipient to continue meeting this Policy’s obligations. If the recipient changes the purposes or methods of processing, it must obtain fresh consent where required by applicable law.
4. Public Disclosure
We do not publicly disclose your personal information unless you separately consent or applicable law or a binding request from an authorized authority requires disclosure.
VII. Your Rights
You can exercise your rights through the following channels, subject to applicable law:
Access and correction: Review and edit your profile under “Me > Personal Information.” View your health records on the relevant health indicator pages, and edit or delete manually entered records.
Deletion: You can delete manual records within the App. For device-synchronized health information, contact us as described in Section XI or delete your account. You may request deletion when the purpose has been achieved, cannot be achieved, or no longer requires the information; when we stop providing a service or its retention period expires; when you withdraw consent; or when we process information contrary to applicable law or our agreement.
Sharing controls: Stop following under “Me > My Doctors,” or change the viewing scope or end a sharing relationship under “Me > Health Sharing.”
Account deletion: You can use either of these methods:
- In the App: “Me > General Settings > Account Security > Delete Account.”
- By email: Write to info@aihnet.com from the email address associated with your account, with the subject “Delete aiCare Account.” If you cannot access that address, contact us for the minimum verification necessary. Our target is to complete processing within 15 working days after receiving your request.
After account deletion, your account, profile, health information, messages, and following and sharing relationships are deleted or anonymized as explained in Section V.2 and cannot be restored once processing is complete. We stop health information access through the former account and relationships. Backup rotation, legal retention, and messages already received by others remain subject to Section V.2; account deletion does not unconditionally erase messages or records lawfully held by others.
Withdrawal of consent:
- Withdraw permission for the corresponding processing by turning off Bluetooth, camera, notifications, phone state, notification access, or other permissions in your phone’s system settings.
- Withdraw consent to this Policy under “Me > General Settings > Privacy Settings > Withdraw Consent.” The App then signs you out and stops collecting your personal information. You must agree to the Policy again to resume use.
- To withdraw consent specifically for health information processing, email info@aihnet.com. You can request that further health collection, synchronization (including retry uploads), cloud analysis, and sharing based on that consent stop, and request deletion of existing health information. Turning off Bluetooth or ending one sharing relationship does not automatically withdraw consent for all other health processing. Information subject to required retention is handled under Section V.2.
- You can also withdraw all consent under this Policy by deleting your account.
Withdrawal does not affect the lawfulness of processing based on your consent before withdrawal.
Review this Policy and the lists: Under “Me > General Settings > Privacy Settings,” you can view this Policy, the Terms of Use, the Personal Information Collection List, and the Personal Information Sharing List.
Obtain a copy: Contact us using Section XI to request a copy of your personal information.
Request an explanation: You can ask us to explain the personal information processing rules described in this Policy.
Other rights under applicable law: Where the law applicable to you provides additional rights, such as restrictions on processing, objection, or data portability, you may contact us to exercise them.
We will respond within 15 working days after receiving your request, or within a shorter period if applicable law requires. To protect your information, we may verify your identity using only the information necessary for that purpose. Verification does not restart the response period. If we cannot fulfill your request, we will explain why and describe available complaint or other redress channels.
VIII. How We Protect Your Personal Information
- We use technical safeguards such as encrypted transmission (HTTPS/TLS), access controls, and authentication to protect personal information against unauthorized access, disclosure, alteration, and loss. Health information access follows your consent, the identified recipient, and the scope of authorization. Staff and provider access is restricted.
- Staff who may access personal information are subject to least-privilege access, access auditing, and confidentiality obligations.
- We maintain procedures for responding to personal information security incidents. If an incident occurs, we will notify you and relevant authorities as required by applicable law, explaining the incident, possible effects, response measures taken or planned, and actions you can take to reduce risk.
- Keep your passwords and verification codes secure. No internet service can guarantee absolute security. Contact us promptly if you notice unusual account activity.
IX. Protection of Minors’ Personal Information
The App is primarily intended to provide health management services to adults.
- If you are under eighteen, read this Policy with a parent or other guardian and obtain their consent before using the App, subject to the requirements of applicable law.
- Before processing personal information of children under fourteen, or children subject to a higher age threshold or additional protections under applicable local law, we will obtain the required consent from a parent or other guardian and establish the specific information processing rules required by that law. Guardians can contact us under Section XI to access, correct, or delete a child’s information or withdraw consent.
- If we learn that we collected a child’s personal information without the guardian consent required for that processing, we will delete the relevant information as soon as practicable.
X. Changes to This Policy
We may update this Policy. For a material change, we will display the updated Policy in a notice when you next launch the App and ask for your consent again. If you do not agree, you can stop using the App and delete your account. Material changes include changes to processing purposes, methods, or personal information categories; third-party SDKs or service providers; recipients of sharing, transfers, or public disclosure; methods of exercising your rights; or our contact information.
XI. How to Contact Us
If you have questions, suggestions, or complaints about this Policy or personal information protection, or wish to exercise your rights, contact us:
- Operator: AIH LLC
- Personal information protection email: info@aihnet.com
We will respond within 15 working days after receiving your request, or sooner if applicable law requires. Any identity verification is limited to what is necessary and does not restart that period. If we refuse a request, we will explain our reasons and available redress. If you are dissatisfied with our response, you may contact the competent data protection, consumer protection, or other regulatory authority in your jurisdiction.
Appendix 1: Personal Information Collection List
| Function | Personal information collected | Collection method | Purpose |
|---|---|---|---|
| Email registration / sign-in / password recovery | Email address, password, email verification information | Provided by you through authentication | Registration, sign-in, identity verification, and password recovery |
| Google sign-in | Authorized Google account identifier, name, email address, profile picture, and sign-in credentials | Received through your Google authorization | Sign-in and profile prefilling |
| Sign in with Apple (iOS) | Apple sign-in identifier and credentials; name and email address you choose to share, possibly a relay address | Received through your Apple authorization | Sign-in and profile prefilling where available |
| Personal profile | Name, sex, date of birth, height; optional profile picture, weight, email address, phone number, and unit preferences | Provided by you; photo taken with the camera or selected from the library | Account profile and health indicator calculations |
| Adding devices | Bluetooth MAC address, serial number, model, name, and firmware version | Read when connecting a device | Device management and record source identification |
| Smart ring | Heart rate, blood oxygen, temperature, steps, distance, calories, sleep information, and health scores; heart rate variability used only locally | Device synchronization | Health records, trends, scores, and alerts |
| Blood pressure monitor / pulse oximeter / thermometer / blood glucose meter | Systolic and diastolic pressure, pulse rate, blood oxygen, temperature, blood glucose, and measurement periods | Device synchronization | Health records, trends, and alerts |
| Body composition scale | Weight, impedance, heart rate where supported, and body composition indicators; local complete records and pending-upload caches may contain impedance, which is not sent to our own business servers; supported offline-history scales also receive account/member association identifiers, age, sex, and height | Local SDK/device exchange, local caching, and cloud algorithm calculations | Health records, member recognition, offline records, and trends |
| Manual records | Heart rate, blood oxygen, blood pressure, blood glucose, weight, and temperature | Entered by you | Health records |
| Ring SOS | Trigger time, ring MAC address, and serial number | Device synchronization | Review of SOS records |
| Health goals | Step, sleep duration, and target weight values | Set by you | Display progress |
| Health alerts | Your selected alert status | Your actions | Alert management |
| Emergency numbers | Network country/region code or a country/region code derived locally from approximate location when needed; coordinates are not uploaded | Read locally on the phone | Display an emergency number |
| Following, authorization, and health sharing | Following relationships, invitations, relationships, note names, and sharing settings | Your actions | Sharing and authorization management |
| Discoverability | aiCare ID, name, and profile picture; email may be used for matching but is not shown to searchers | Exact aiCare ID search by another user; name/email matching only after you enable it | Help users connect while showing minimal search-result information |
| Messaging between users | Message content, sending times, and read status | Messages you send | Message delivery and synchronization |
| Push notifications | App installation identifier, FCM push token, and, on iOS, APNs delivery token | Generated by the App and notification services | Deliver notifications |
| Ring message reminders | Originating app identifier and installed app list, used only locally | Local reading after your authorization | Ring vibration reminders |
| Ring incoming call reminders | Call states, used only locally | Local reading after your authorization | Ring vibration reminders |
| Policy / terms webpage display | IP address, access time, page request, and necessary connection information | Generated when you choose to open the page | Page delivery and necessary security |
| Service security | Network request logs, including access time, requested endpoint, and IP address | Recorded by servers | Fault investigation and security |
| Crash diagnostics and usage analysis | Installation/app-instance identifiers, device/OS/App information, crash and diagnostic logs, usage events; measurement type and raw measurement/error values; scale name, device capability information, synchronization outcome, record counts, and save failure status | Firebase Crashlytics and Analytics reports | Diagnose crashes, measurement failures, synchronization, and App usage |
Appendix 2: Personal Information Sharing List
| Recipient | Personal information received | Purpose | Method | Conditions |
|---|---|---|---|---|
| Actual recipient identified on the following/authorization confirmation page, including name, contact details, and organization where applicable | Name, sex, date of birth, height, weight, profile picture, all health information and alerts, and messages exchanged with you; excludes phone number and email address | Health information communication and management you choose | In-App access | Separate consent after disclosure of the actual recipient and processing scope; you can stop following at any time |
| Family members or friends you authorize | All health information and alerts within your selected scope, or no health access; messages exchanged with you | Your chosen health sharing and communication | In-App access | Your separate consent; you can change the scope or end sharing at any time |
| Other users viewing search results | Name, profile picture, and aiCare ID, without email address or phone number | Find and invite you | Display in App search results | Exact aiCare ID search; name/email search only after you actively enable the option, which is off by default and can be disabled in Privacy Settings |
| Auth0 (Okta) | Email address, password, verification information, authorized third-party account identifiers and sign-in credentials, and necessary authentication technical information | Account authentication | Authentication service | Use of Global registration, sign-in, or recovery; see Section IV |
| Google LLC (Google Sign-In) | Authorized Google sign-in information and technical information needed to complete sign-in | Google account sign-in | Google authentication interface and authorization exchange | You choose Google sign-in and authorize it |
| Apple Inc. (Sign in with Apple) | Apple sign-in information and technical information needed for authentication | Apple account sign-in | Apple authentication interface and authorization exchange | You choose Sign in with Apple on iOS and authorize it |
| 深圳市乐福衡器有限公司 (Lefu cloud algorithm service) | Weight, impedance, height, age, sex, other necessary algorithm parameters, and necessary network communication information; not anonymous merely because a name or account field is absent | Calculate body composition | Processing on our behalf | You use cloud body composition calculations and separately consent to health processing |
| Google LLC (Firebase) | Installation/app-instance identifiers, push token, device/OS/App information, crash logs, diagnostic and usage events, measurement error values, and scale synchronization information described in Section I.10 | Global notifications, diagnostics, and usage analysis | Cloud services | Agreement to this Policy and use of the relevant function; separate consent for health-related processing |
| Apple Inc. (APNs) | Device push token and notification delivery information | iOS notification delivery | System push service | Use of iOS notifications, subject to system controls |
| Third-party providers with network processing described in Section IV | Information listed for the corresponding provider in Section IV | Purposes listed in Section IV | As listed in Section IV; running a local SDK is not itself a disclosure to its provider | Agreement to this Policy and use of the corresponding function, with separate consent where required |
Developer: AIH LLC
App name: aiCare
Last updated: October 23, 2026
