1. Purpose, Scope & Covered Parties
This Confidentiality Policy sets forth binding confidentiality, technical data protection, and non-disclosure standards across the HealthDash ecosystem. It applies comprehensively to:
- Personalized Cloud Dashboard (PCD) Users: Pro, Premium, and enterprise subscribers accessing dedicated tenant visualizers, personal wellness data relays, and private CRUD analytics modules.
- Third-Party Integrators & Developers: Partners, software vendors, and independent developers building client applications or backend bridges utilizing HealthDash REST APIs, companion libraries (libhacontimig), webhook relays, or health data connectors.
- Companion Mobile Application Deployments: Supported Android editions including HealthyMe, HealthyMe Pro, HealthSync, and HealthSync Pro across Google Play, Huawei AppGallery, and Samsung Galaxy Store.
2. Definition of Confidential Information Governance Standard
"Confidential Information" encompasses all proprietary technical, financial, operational, and user health data disclosed by HealthDash or accessed via PCD and associated interfaces, including without limitation:
| Category | Specific Protected Elements | Classification |
|---|---|---|
| User Health & Activity Data | Raw and aggregated physical activity records, step timeseries, daily sleep hypnograms, sleep stage duration (REM, deep, light), heart rate variability (HRV), continuous glucose monitoring (CGM) streams, relaxation scores, and on-chain Health Diagram NFT minting metadata (Ethereum & Sui). | Restricted / Confidential PII |
| Authentication & Tokens | Okta OIDC access tokens, refresh tokens, Google OAuth 2.0 bearer credentials, Samsung Health Partner approval certificates, Huawei HealthKit SDK credentials, Oura personal access tokens, Strava API v3 keys, and session cookies (CD12_CookieAcceptv12022). | Strictly Confidential Credentials |
| Architecture & Tenant Configuration | Proprietary multi-tenant Kubernetes orchestration configs, closed/private PCD DEMO CRUD modules, ingress relay topologies, circuit-breaker threshold parameters, and backend service URLs. | Proprietary Trade Secret |
| R&D Documentation | Unpublished specifications, architecture diagrams, internal benchmarking logs, integration test suites, and master Office roadmaps (docs/RnD.docx). | Internal Confidential |
3. Integrator & Developer Obligations
Third-party integrators, external developers, and partners granted API or SDK access acknowledge and agree to the following obligations:
- Strict Non-Disclosure: Confidential Information shall not be disclosed, transferred, or made available to any unauthorized third party without express prior written consent from HealthDash.
- Purpose Limitation: Integrators shall access and process Confidential Information strictly for the authorized purpose of synchronizing, analyzing, or displaying personal wellness data for the end user who granted explicit consent.
- Zero Hardcoded Secrets Standard: Under no circumstance may private tenant endpoints, API keys, Okta client secrets, or user tokens be committed to public code repositories, embedded into unminified client-side scripts, or exposed via debug logging. Configuration must be strictly externalized through environment variables.
- Mandatory Mock Data Usage in Non-Production: Development, unit testing, and sandbox verification must only use sanitized mock data (sanitizedMockPcdData and sanitizedDemoMetrics). Real user health data from connected wearables must never be used in development or staging environments.
4. PCD User Health Data Safeguards
Personalized Cloud Dashboard (PCD) users entrust their personal wearable data to the HealthDash platform. We enforce strict data handling safeguards:
- Tenant Isolation: Dedicated PCD subscriber health data is partitioned via multi-tenant access boundaries, ensuring one subscriber's health cards, HRV graphs, and Beer Bank records cannot be queried or exposed to another tenant.
- Role-Based Access Control (RBAC): Health data retrieval endpoints require valid Okta authentication tokens and verify user-matching claims prior to serving data streams.
- Consent-Driven Synchronization: Data is synchronized to and from external third-party platforms (Samsung Health, Huawei Health, Oura, Google Fit, Strava, MyFitnessPal) strictly upon active user configuration and manual or scheduled trigger.
5. Security, Encryption & Breach Protocol
All parties handling Confidential Information within the HealthDash ecosystem must uphold industry-leading security practices:
- Transport Layer Security: All API communication, health data transmissions, and authentication flows must occur exclusively over HTTPS utilizing TLS 1.3 (or minimum TLS 1.2).
- Encryption at Rest: Cached tokens and database records must be encrypted at rest using AES-256 or equivalent cryptographic standards.
- 72-Hour Security Incident Notification: Any integrator or partner that detects or reasonably suspects unauthorized access, credential leakage, API key compromise, or data exposure must report the incident to HealthDash security (hx@inbox.lv) within seventy-two (72) hours of discovery.
6. Prohibited Commercial & AI Usages
To preserve user trust and protect proprietary technologies, the following actions are strictly prohibited:
- No Health Data Brokering or Resale: User health data, sleep scores, and activity records may not be packaged, resold, leased, or licensed to data brokers, insurance underwriters, or advertisers.
- No Unauthorized AI Model Training: Confidential user health data accessed through PCD or companion APIs may not be ingested into or used to train third-party foundation or generative AI models without explicit, documented consent.
- No Reverse Engineering: Integrators may not decompile, disassemble, or reverse-engineer closed/private PCD modules, proprietary relay logic, or licensing controls.
7. Term, Access Revocation & Deletion
Confidentiality obligations remain in effect for the duration of the party's use of HealthDash services and continue indefinitely with respect to trade secrets and user health data.
- Revocation: HealthDash reserves the right to immediately revoke API credentials, disable OAuth client integrations, or suspend PCD tenant access upon any breach of this Confidentiality Policy.
- Right to be Forgotten (GDPR Art. 17): Upon termination of integration status or receipt of a user deletion request, integrators must securely delete and purge all cached tokens, user health data, and proprietary references within thirty (30) days and provide written certification of destruction upon request.
8. Governing Law, GDPR & Contact
This Confidentiality Policy is governed by and construed in accordance with the laws of the Republic of Latvia and the regulations of the European Union (including GDPR Regulation (EU) 2016/679). Any disputes arising under or in connection with this Policy shall be subject to the jurisdiction of the courts of Riga, Latvia.
- Data Controller & Developer: Linards Liepiņš
- Ecosystem: HealthDash & Personalized Cloud Dashboard (PCD)
- Confidentiality Inquiries & Incident Reports: hx@inbox.lv
- Official Portal: https://healthdash.lv