Pulscore2 ("the Application", "we", "us", or "our") is a personal health and fitness analytics application developed by deiG (asc.hk). Pulscore2 computes an adaptive Cardio Load fitness score based on intraday continuous heart rate and resting heart rate data collected from your wearable devices.
We value your trust and are deeply committed to safeguarding your privacy and personal data. This document details our data collection, usage, retention, deletion practices, and our strict adherence to the Google API Services User Data Policy and Google APIs Terms of Service.
1. Information We Access and Collect
When you authorize Pulscore2 using your Google Account, the application requests read-only access to specific fitness and profile data points solely to calculate and display your Cardio Load metrics:
-
Continuous Heart Rate Data: 1-minute rollup averages of continuous heart rate measurements (beats per minute) via the
heart-rate data type (Scope: googlehealth.health_metrics_and_measurements.readonly).
-
Resting Heart Rate (RHR): Daily baseline resting heart rate readings via the
daily-resting-heart-rate data type (Scope: googlehealth.health_metrics_and_measurements.readonly).
-
Heart Rate Variability (HRV): Nightly and daily root mean square of successive differences (RMSSD) via the
daily-heart-rate-variability data type (Scope: googlehealth.health_metrics_and_measurements.readonly).
-
User Profile & Settings: Basic profile fields (age, biological sex, membership date, and UTC timezone offset) via Google Health and Google userinfo endpoints (Scopes:
googlehealth.profile.readonly, googlehealth.settings.readonly, openid, profile, email). These are used exclusively to accurately compute Maximum Heart Rate (MHR), establish Heart Rate Reserve (HRR) zones, and align sample timestamps to your local time zone calendar day.
-
Device Synchronization Information: Tracker model and the timestamp of your last device synchronization via paired devices endpoints to determine whether recent health data is up-to-date.
2. How We Use Your Information
All data accessed via Google Health APIs is utilized exclusively to provide and improve user-facing features of Pulscore2:
- Calculating your daily heart rate reserve exercise scores based on scientifically established Cardio Load models.
- Displaying an interactive 10-day bar chart showing current scores, target goal streaks, and historical trends.
- Displaying Heart Rate Variability (HRV) trends and resting heart rate recovery metrics.
- Providing an exportable CSV archive of your historical heart rate statistics for your own personal records.
Google API Services User Data Policy Compliance:
Pulscore2's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
3. Prohibited Uses & AI Compliance Affirmations
In strict compliance with the Google API Services User Data Policy and Google APIs Terms of Service:
-
No Generalized AI/ML Model Training: Pulscore2 does NOT use, transfer, or disclose Google user data to develop, train, or improve generalized or non-personalized Artificial Intelligence (AI) and/or Machine Learning (ML) models.
-
No AI NCII (Non-Consensual Intimate Imagery): In strict compliance with the Google APIs Terms of Service, Pulscore2 does NOT use Google APIs, Google services, or user data to create, generate, host, distribute, or facilitate AI-generated Non-Consensual Intimate Imagery (AI NCII) or any prohibited synthetic content.
-
No Sale of User Data: We never sell, rent, lease, trade, or transfer your personal or health data to third parties, data brokers, or information resellers under any circumstances.
-
No Advertising or Marketing: Your health data is never used to serve advertisements, target advertisements, build advertising profiles, or monetize your usage.
-
No Credit or Lending Evaluations: Your data is never disclosed to credit bureaus, financial institutions, insurance providers, or lending agencies.
-
No Human Inspection: No human reads or inspects your personal health data unless you explicitly request technical support and provide prior affirmative consent.
4. Data Storage, Protection, and Security
We maintain rigorous administrative and technical security procedures to protect user data:
-
Encrypted Communications: All communications between Pulscore2, your browser, and Google APIs occur strictly over encrypted HTTPS/TLS (TLS 1.2 / TLS 1.3) connections.
-
Isolated Local Storage: Pulscore2 operates as a self-hosted health tracker. OAuth credentials and daily score summaries are stored securely on the private host server in restricted local storage directories. No data is shared with external cloud databases or third-party tracking services.
-
Token Security: OAuth access tokens and refresh tokens are stored with restricted file system permissions and are never exposed publicly or sent to the client browser.
5. Data Retention and Deletion
We retain your personal data only for the minimum period necessary to fulfill the purposes outlined in this Privacy Policy:
-
Retention Period: We retain your locally cached health metrics, daily scores, and authentication tokens for as long as you maintain an active account with Pulscore2 to provide historical Cardio Load trends and comparison streaks.
-
Inactivity Expiration: If an account remains inactive for 12 consecutive months without any synchronization or login, all cached tokens and health records associated with the user will be automatically deleted.
-
Revoking Access: You can revoke Pulscore2's access to your Google account at any time through your Google Account Third-Party Access settings. Once revoked, the application can no longer retrieve data from Google Health.
-
User-Initiated Deletion: You can request complete and permanent deletion of all stored health metrics, logs, and authentication tokens at any time. Simply send an email request to the developer at taojiang.sz@gmail.com. All associated data will be completely and irreversibly purged from the server within 30 days of receipt of your request.
-
Session Termination: Clicking "Log out" inside Pulscore2 immediately terminates your active browser session and removes session cookies.
6. Children's Privacy
Pulscore2 is not directed toward children under the age of 13 (or under 16 in the European Economic Area). We do not knowingly collect or solicit personal information from children. If we become aware that a child has provided us with personal information, we will delete such data immediately.
7. Changes to this Policy
We may occasionally update this Privacy Policy to reflect improvements in our application or changes in applicable regulations. Any updates will be posted to this page with an updated revision date.