Privacy Policy

1. Overview

The App helps users record and review health-related information such as manually entered blood pressure readings, camera-based heart rate estimates, estimated HRV, weight, height, BMI, reminder settings, and care reading content. The App is supported by advertising and uses remote configuration and advertising measurement services. This policy explains what information is processed by the App and its service providers, why it is processed, and what choices you have.

2. Information We Process

2.1 Health records you enter

• Blood pressure values, including systolic and diastolic readings.
• Heart rate estimate and estimated HRV values.
• Weight, height, BMI, dates, times, and related log details.
• Reminder times, selected days, and other settings you choose in the App.

These records are stored in local databases on your device and are used to show summaries, history, status labels, and trend-style views inside the App. The current App code does not upload these health records to our servers, Firebase Remote Config, Google Mobile Ads, or Meta.

2.2 On-device app state

The App stores information needed for normal operation on your device, including health history, reminder schedules, and cached remote settings such as feature switches, advertising unit identifiers, and advertising wait times. It also reads the device time zone to schedule local reminders. In the current version, we do not provide an account system or our own cloud sync service for your health records.

2.3 Optional camera-based heart rate estimate

If you use the heart rate estimate feature, the App requests camera access and may use the camera flash so it can detect fingertip brightness changes. Camera frames are analyzed on device for this optional wellness estimate. The current App code does not save those frames to the health database or send them to our servers, Firebase, Google Mobile Ads, or Meta.

2.4 Advertising and consent information

The App uses the Google Mobile Ads SDK to request and display app-open, interstitial, and native advertisements. Depending on your device, region, consent choices, and platform settings, Google and its advertising partners may automatically process:

• IP address and general location estimated from the IP address;
• Device, operating system, app, browser or network information;
• Advertising or app-instance identifiers, such as the iOS advertising identifier when authorized, Android advertising ID, app set ID, or similar identifiers;
• App and advertisement interactions, including app launches, taps, impressions, clicks, and video views;
• Advertising data, consent status, and choices made in a consent form; and
• Diagnostic, performance, and crash information associated with the advertising SDK.

The Google User Messaging Platform (UMP) checks whether a privacy message is required and may process consent status, coarse location or region information, interactions with the consent form, and related performance data. Advertisements may be personalized or non-personalized depending on applicable law, your consent, and platform settings.

2.5 Firebase Remote Config

The App uses Firebase Remote Config to retrieve feature switches, advertising unit identifiers, and timing settings. Firebase creates and processes a Firebase installation ID and related authentication token to identify an App installation for configuration requests. Firebase may also process service data such as IP address, app or package identifier, configuration-request information, and limited diagnostic information. We do not send your locally stored health entries or camera frames to Remote Config.

2.6 Meta App Events on iOS

The iOS version includes Meta's Facebook SDK. The current configuration enables automatic app-event logging and advertiser-identifier collection, subject to iOS permission and platform restrictions. Meta may process device identifiers, app activation or other automatically logged app events, device and network information, and limited diagnostic or crash information for advertising measurement, analytics, and App functionality.

When Google reports advertising revenue, the App sends Meta an advertising-revenue event labeled as a purchase event, including the revenue amount and currency. This event represents advertising revenue and is not a purchase made by the user. The current implementation does not include your blood pressure, heart rate, HRV, weight, height, BMI, reminder content, or camera frames in this event.

2.7 Care article and website access

When you open a care article, the App uses your system browser to load a static page from Firebase Hosting at bloodpressure-62629.web.app. Standard hosting logs may be processed by Firebase/Google, such as IP address, browser information, request time, and requested URL, according to Google's policies.

2.8 Features handled by your device or another app

If you use the sharing feature, the App passes the text you choose to your device's system share sheet and the destination app you select. If you open a care article, privacy policy, or store review page, your browser, app store, operating system, or destination app may process the request under its own privacy policy.

3. How We Use Information

• To provide manual blood pressure logging, camera-based heart rate estimates, weight, BMI, history, and summary features.
• To schedule local reminders when you choose to create them.
• To open educational care articles that may support healthier daily habits.
• To retrieve remote feature and advertising configuration.
• To display, personalize where permitted, measure, and protect against fraud in advertising.
• To measure advertising revenue and basic App events on iOS.
• To maintain, secure, debug, and improve the App, SDK integrations, and related static web pages.

Depending on where you live and the type of processing, we rely on your consent, the need to provide a feature you request, compliance with legal obligations, and our legitimate interests in operating, securing, improving, and supporting the App through advertising.

4. Health and Medical Disclaimer

The App and care articles are for general health education and personal tracking only. They do not replace professional medical advice, diagnosis, monitoring, or treatment. Do not ignore or delay medical care because of information shown in the App.

The App does not measure blood pressure using the camera, flash, microphone, touch screen, or other iOS device sensors. Blood pressure values are manually entered by the user from an external cuff or monitor. Camera-based heart rate and estimated HRV values are wellness estimates, and accuracy may vary.

If you have severe symptoms, very high blood pressure, chest pain, shortness of breath, fainting, sudden weakness, confusion, or symptoms that feel urgent, seek urgent medical care.

5. Third-Party Services

5.1 Google Mobile Ads and User Messaging Platform

Google Mobile Ads supplies and measures advertisements, and UMP manages applicable privacy and advertising consent messages. Google and advertising partners disclosed in the consent flow may process information as described in Section 2.4. Their processing is governed by their own terms and privacy policies.

Google privacy information: Google Privacy Policy and How Google uses information for advertising

5.2 Firebase Remote Config and Hosting (Google)

We use Firebase Remote Config to deliver configuration values and Firebase Hosting to host static care article pages and this website. Firebase/Google may process App installation identifiers, limited diagnostics, and technical request data needed to deliver, configure, and secure these services.

Firebase privacy information: Firebase Privacy and Security

5.3 Meta Facebook SDK on iOS

We use Meta App Events on iOS for automatic app-event logging and advertising-revenue measurement. Meta may combine information received through its SDK with other information it holds as described in its policy.

Meta privacy information: Meta Privacy Policy

5.4 Apple, system browser, share sheet, and external links

When you open an article or external link, your browser, operating system, internet provider, and any linked third-party website may process information under their own privacy policies.

The App uses Apple's system services for camera permission, tracking authorization, local notifications, sharing, and opening the App Store. Apple and any destination app you choose may process related information under their own terms.

5.5 SDKs not included

The current project does not include Firebase Analytics or Firebase Crashlytics. However, Google Mobile Ads, UMP, Firebase Remote Config, and Meta's SDK process the limited analytics, advertising, consent, installation, and diagnostic information described above.

6. Permissions

• Camera: requested when you use the optional camera-based heart rate estimate. The camera flash may also be used during measurement.
• Notifications: the current App code requests iOS alert, badge, and sound permission when you first create an enabled reminder. Reminder content and schedules are handled locally by the device. The bundled notification plugin may declare notification and vibration permissions in the Android package, although the current reminder-notification service is enabled only on iOS.
• Tracking on iOS: the App requests permission through Apple's App Tracking Transparency prompt before accessing the advertising identifier for cross-app or cross-website tracking. Refusing this permission does not prevent you from using health logging features, but advertisements may be less personalized.
• Internet: network access is used for advertisements, consent messages, Remote Config, and external care pages.

The current App code does not request microphone, contacts, HealthKit, or precise GPS location permission. Advertising and consent services may still estimate a general location from an IP address without accessing precise GPS location.

7. What We Do Not Do

• We do not sell your locally stored health records.
• We do not intentionally provide your health entries, reminder content, or camera frames to advertising or remote-configuration providers through the current App code.
• We do not provide medical diagnosis or emergency monitoring.
• We do not operate an account system for uploading your health logs to our own cloud in the current version.
• We do not request precise GPS location through the current App code.

Some privacy laws define certain advertising disclosures as a "sale," "sharing," or use for targeted advertising even when no money is exchanged for personal information. You can use the controls described below to limit this processing where applicable.

8. Your Choices

• You can choose what health readings or reminder details you enter into the App.
• You can delete individual health entries and reminders where the App provides a delete control. Uninstalling the App removes its local databases and settings from your device, subject to normal device backup behavior.
• You can deny or later change camera, notification, and iOS tracking permissions in your device settings.
• Where required, Google's UMP consent form provides choices about advertising processing. You may also use Google advertising controls and your device's advertising settings to limit ad personalization or reset or delete an advertising identifier.
• You can choose not to open care article links in the system browser.
• You can manage browser data, cookies, and site data through your browser settings.

Depending on your location, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent for personal information under our control. To make a request, contact us using Section 14. Because the App has no account system, we may not be able to associate an email address with pseudonymous records held by a third-party SDK; you may also need to use the provider's privacy controls or contact that provider directly.

9. Data Retention

Health records, reminder schedules, and settings stored on your device remain there until they are deleted by you, cleared by the operating system, or removed when you uninstall the App. Cached Remote Config values may remain locally until refreshed, cleared, or the App is uninstalled.

Google, Firebase, Meta, Apple, and advertising partners retain information under their own policies and settings. For example, Firebase retains installation IDs according to its service rules until deletion is requested through the applicable Firebase mechanism. Website hosting logs and advertising, consent, diagnostic, and event data may be kept for periods determined by the applicable provider and legal requirements.

10. Children's Privacy

The App is intended for adults and is not directed to children under 13 or the minimum age required by local law. We do not knowingly ask children to provide personal information. Parents or guardians who believe a child has used the App or provided personal information should contact us. Advertising providers may apply additional protections based on region, platform settings, and consent signals.

11. Security

Health records are stored locally within the App's device storage, which is protected by the security features of your device and operating system. Third-party SDK information is transmitted to their services using their security measures. We use reasonable measures to protect information processed by the App and static website, but no method of electronic storage or network transmission is completely secure.

12. International Users

Google, Firebase, Meta, Apple, advertising partners, and other platform services may process technical information on servers located outside your country, including countries whose data-protection laws may differ from yours. These transfers are handled under the applicable provider terms, privacy policies, and legally required transfer safeguards.

13. Changes to This Policy

We may update this Privacy Policy to reflect changes to the App, SDKs, providers, or legal requirements. When we make changes, we will post the updated policy on this page and revise the "Last Updated" date. Where required by law, we will provide additional notice or request consent before materially different processing begins.

14. Contact Us

If you have questions about this Privacy Policy or our privacy practices, please contact us at: liuqi@163.com