1. Overview & Applications Covered

This Privacy Policy governs the access, collection, use, processing, and protection of user information across the HealthDash platform, including:

  • Cloud Dashboard (CD) / Personalized Cloud Dashboard (PCD) (hosted at healthdash.lv and clouddashboard.healthdash.lv)
  • HealthyMe & HealthyMe Pro Android Applications (Current Active Release • Package IDs: com.linardsl.libhacontimig.hm.final, com.linardsl.libhacontimig.hm.finalPro)
  • HealthSync & HealthSync Pro Android Applications (Legacy Release • Production track suspended by Google; Alpha engineering tracks remain operational • Package IDs: com.linardsl.libhacontimig.alpha, com.linardsl.libhacontimig.alphaPro, com.linardsl.libhacontimig.demo)

Our service is designed to provide users with personal fitness data visualization, aggregated cross-platform wellness metrics, and synchronization across supported health and fitness services (such as Google Fit, Health Connect, Samsung Health, Huawei Health, and Oura Ring).

Base Policy & Regulatory Relationship: This document serves as the official Google OAuth & Health Data Verification Addendum complementing the HealthDash Base Privacy Policy (TermsFeed 2026 Edition) available at privacy-policy-pdf-v1y2026.pdf. Together with our Terms and Conditions (TnC 2026) and Confidentiality Policy (2026), these documents provide complete, transparent disclosure of all data processing activities across the HealthDash ecosystem.

2. Google User Data Accessed Verification Section

When you connect your Google Account via Google Sign-In, Google Fit APIs, or Android Health Connect, our application requests access only to specific categories of user data essential for health tracking and synchronization features. Specifically, our application accesses:

Google OAuth Scope Specific Data Accessed / Collected Access Type
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly Daily step counts, walking/running duration, active time intervals, distance, and exercise session metadata recorded in Google Fit / Health Connect. Read-Only
https://www.googleapis.com/auth/googlehealth.sleep.readonly Sleep session start and end timestamps, total sleep duration, sleep stage intervals (light, deep, REM, awake), and sleep score metrics. Read-Only
https://www.googleapis.com/auth/googlehealth.activity_and_fitness.writeonly Allows our application to insert step records, activity segments, and workout sessions into Google Fit / Health Connect on behalf of the user. Write-Only
https://www.googleapis.com/auth/googlehealth.sleep.writeonly Allows our application to insert sleep session records and hypnogram sleep stage breakdowns into Google Fit / Health Connect on behalf of the user. Write-Only
openid, email, profile User email address and account identifier, used strictly to associate authenticated user health data with their private dashboard profile. Identity Authentication

Note: Our application adheres strictly to the principle of least privilege. We do NOT request access to sensitive medical records, location tracking, contacts, or financial details via Google APIs.

3. How We Use Google User Data Verification Section

The Google user data accessed by HealthDash is used exclusively to deliver user-facing wellness tracking and synchronization capabilities. Specifically:

  • Read Operations (Dashboard Visualization): We retrieve sleep records, steps, and activity durations from Google Fit / Health Connect solely to display unified metrics, activity trends, and readiness comparisons on the user's Personalized Cloud Dashboard (PCD) and mobile client interfaces.
  • Write Operations (Cross-Platform Synchronization): When the user connects external hardware or platforms (such as an Oura Ring, Huawei Health, or Samsung Health device) and executes a sync, our application converts and inserts the user's recorded step counts and sleep sessions into their Google Fit / Health Connect account so their Google ecosystem remains up to date.
  • Non-Intrusive Analytics: Aggregated system performance and crash monitoring (via Google Analytics 4 and Firebase Crashlytics) to identify bugs and ensure synchronization reliability. Telemetry logs do not contain raw personal health session records.
Strict Restrictions on Data Usage:
  • We do NOT use Google user data for advertising, marketing campaigns, or retargeting.
  • We do NOT build advertising profiles or behavioral tracking models using Google user data.
  • We do NOT use health data for creditworthiness, lending assessments, or insurance underwriting.
  • We do NOT train generalized artificial intelligence or large language models on your personal health metrics.

4. Google User Data Sharing & Disclosure Verification Section

HealthDash has a strict policy regarding the sharing and disclosure of user information:

  • No Sale of Data: HealthDash does NOT sell, rent, lease, or trade Google user data to any third party, data broker, advertising network, or analytics vendor under any circumstances.
  • User-Directed Cross-Service Synchronization: Google user data is only transferred or written to another connected service (such as Samsung Health, Huawei Health, or Oura) when the user explicitly configures that service within the app settings and requests a sync operation.
  • Service Providers: We may share data with vetted cloud infrastructure providers (such as Amazon Web Services and Google Cloud Platform) strictly for database hosting, storage, and computing services required to run the platform, bound by rigorous data protection and non-disclosure agreements.
  • Legal Requirements: We will only disclose user data if required by law, subpoena, or valid legal process, or where necessary to protect our legal rights, property, or user safety.
  • Human Access: No HealthDash personnel or contractors have direct access to read your personal Google health records unless you have provided explicit written consent for troubleshooting an individual technical support incident, or where required to comply with law or investigate security violations.

5. Data Protection & Security Mechanisms Verification Section

HealthDash applies rigorous administrative, physical, and technical safeguards to secure your personal health information and sensitive OAuth credentials:

  • Encryption in Transit: All data exchanged between user clients, our backend servers, and Google APIs is encrypted in transit using industry-standard Transport Layer Security (TLS 1.2 and TLS 1.3) over HTTPS. Cleartext transmission of health data is strictly prohibited.
  • Encryption at Rest: Any persistent user data, tokens, or cached metrics stored within cloud databases are protected using AES-256 encryption at rest.
  • Secure OAuth Token Management: OAuth access tokens and refresh tokens are stored securely using Android Keystore / encrypted preferences on mobile devices and isolated, encrypted secret storage on cloud environments. Tokens are never exposed to unauthorized processes or recorded in plaintext logs.
  • Principle of Least Privilege: Cloud infrastructure access is restricted by strict role-based access controls (RBAC) and audited regularly. Production systems undergo continuous monitoring to detect unauthorized access attempts.
  • Code Hardening: Regular dependency vulnerability scanning, static code analysis, and automated builds to prevent security regressions.

6. Data Retention & User Deletion Requests Verification Section

We believe you should have complete control over your health information:

  • Retention Period: User health data is retained only for the duration that the user maintains an active account or synchronization profile with HealthDash. Cached sync records are purged automatically on rolling cycles.
  • Revoking Access: You can revoke HealthDash's access to your Google account at any time by visiting your Google Account Permissions Settings and clicking "Remove Access".
  • In-App Deletion: Users can delete their connected accounts and local sync caches at any time within the HealthDash application settings by choosing "Disconnect & Clear Data".
  • Explicit Deletion Requests: Users have the right to request complete and permanent deletion of their account and all associated health data. You can submit a deletion request by emailing hx@inbox.lv with the subject "Data Deletion Request". All associated data will be permanently wiped from our systems within 30 days without undue delay.

7. Google API Services User Data Policy Compliance

Mandatory Limited Use Disclosure:

HealthDash'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.

Specifically, our application complies with the following core principles of the Google API Services User Data Policy:

  1. Request Minimum Permissions: We only request scopes that directly power advertised user-facing features (sleep tracking, step tracking, and bi-directional synchronization).
  2. Prominent Disclosures: We provide clear in-app disclosures and user consent before initiating data synchronization.
  3. Secure Data Handling: We enforce end-to-end encryption for all Google user data.
  4. No Deceptive Practices: Data collected is never repurposed for hidden motives, surveillance, or commercial sale.

8. Contact Information

If you have questions, concerns, or requests regarding this Privacy Policy, our data handling practices, or your rights under GDPR and Google Data Protection Policies, please contact us:

  • Developer & Data Controller: Linards Liepiņš
  • Ecosystem: HealthDash / Personalized Cloud Dashboard (PCD)
  • Direct Email: hx@inbox.lv
  • Website: https://healthdash.lv
  • Jurisdiction: Riga, Latvia (European Union - GDPR Compliant)