Signal privacy policy

1. Who we are

Signal is an educational wearable insights playground operated by Doctor World Pte. Ltd. (“we”, “us”).

Signal helps invited users connect wearables (for example Care Band over Bluetooth, and Garmin Connect via OAuth) into one calm view of their own data and see educational wellness patterns — such as resting heart rate compared to their usual range, sleep patterns, and activity trends.

Signal is not Care+, CARE Claims, TPA, or any clinical / diagnostic product. CARE (wearecare.sg) remains an independent healthcare / wellness brand under the same legal entity. Signal does not sell your data and does not feed Garmin or wearable streams into CARE Claims, TPA, or fraud/waste/abuse pipelines.

2. What this policy covers

This policy describes how Signal handles personal data when you:

• use Signal (including any invited playground account);
• connect Garmin Connect via OAuth so Garmin can push Health / Activity summaries to Signal;
• connect other supported devices (for example Care Band over BLE) into Signal;
• contact us about Signal privacy.

Garmin’s own collection and use of data in the Garmin Connect service is governed by Garmin’s privacy notices and terms, not this policy. We only receive data Garmin sends us after you authorize the connection. Separately, a Personal API path may be used for an individual’s own Garmin data during early development; multi-user OAuth follows Garmin’s Connect Developer Program rules once approved.

3. Educational use — not diagnosis

Signal insights are for general wellness education and self-understanding only.

• We do not diagnose, monitor disease, treat, or provide medical advice.
• We do not claim clinical “normal / abnormal” labels.
• If you are concerned about your health, talk to a qualified clinician.

Every insight surface is intended to carry an educational / not-diagnostic disclaimer.

4. What data we collect

4.1 Account / contact data

Depending on how the playground is set up, we may hold:

• name or display name;
• email address (for invite / contact);
• opaque internal user reference (user_ref) — we avoid NRIC/FIN, passport numbers, and clinical medical record numbers in Signal datasets.

4.2 Garmin Connect data (after you authorize OAuth)

When you connect Garmin, and only for the scopes you approve, we may receive push summaries from Garmin’s Health and Activity APIs, which can include categories such as:

• Heart rate (including resting heart rate when available);
• Sleep summaries and related sleep metrics;
• Activity summaries (for example steps / activity);
• other health-related summaries Garmin includes in the Health API for your device (for example SpO₂, and optional HRV / respiration / skin temperature when units and availability allow).

On Garmin’s Starter program path: delivery is typically push-only, and historical data before you connect is not included. Baselines in Signal grow from data received after you connect.

4.3 Other wearable / app data

If you connect another supported source (for example Care Band over Bluetooth), we may store samples or nightly summaries needed to show charts and educational insights in Signal.

4.4 Technical / security logs

We may keep limited technical logs (for example connection timestamps, error codes, OAuth event metadata) needed to run and secure the service. We aim not to put live Garmin health payloads into third-party product analytics.

5. Why we use your data

Primary purpose: educational wellness insights.

Specifically, we use the data to:

1. complete Garmin (and other) OAuth / device connect flows;
2. receive, normalize, and store summaries so you can view your own dataset in Signal;
3. compute educational, self-referential insights (for example “vs your usual range”) when enough valid data exists;
4. operate, secure, and debug the playground;
5. respond to your privacy or support requests;
6. meet legal obligations where they apply.

We do not use Signal Garmin data to sell advertising, to broker health data, or to run CARE insurance claims / TPA / FWA workflows. We do not sell your personal data.

6. Legal / PDPA basis

Under Singapore’s Personal Data Protection Act (PDPA) framework, we rely on consent for connecting Garmin and processing wearable streams for educational wellness insights, and on necessity to provide the service you requested and to secure it. You can withdraw consent by disconnecting Garmin / revoking access (see section 9). Withdrawal does not affect processing already completed lawfully before withdrawal.

7. Who processes data for us

We may use service providers that process data on our instructions, for example:

• Hosting / compute — preference Cloudflare (Workers/Pages pattern); Singapore region when available. Vercel may be used as a secondary option.
• Storage — databases or object stores needed to hold encrypted tokens and normalized datasets.
• Development tooling — engineering assistants may see non-production fixtures or schemas during development. Live OAuth tokens and production Garmin payloads are not intended to be shared with AI tooling.

We do not sell your personal data.

8. Retention

• OAuth tokens: kept only while your Garmin connection remains active; deleted or invalidated when you revoke / disconnect.
• Normalized summaries / baselines: kept while your Signal playground access is active and for a limited period afterward so you can see your own history.
• Raw high-frequency streams (if ever stored): short retention preferred.
• Security logs: retained only as long as reasonably needed for security and operations.

9. Your choices — access, correction, deletion, export, revoke

You can:

• Choose not to connect Garmin or other devices — Signal’s Garmin features simply will not receive that data.
• Disconnect / revoke Garmin access (in Signal and/or in your Garmin Connect account permissions). When you revoke, we delete or invalidate stored Garmin tokens and stop processing new Garmin pushes for that connection.
• Access or correct personal data we hold about you in Signal — email [email protected] and we will respond subject to PDPA and security limits.
• Delete personal data we hold about you in Signal — email [email protected] with a deletion request. We will delete or irreversibly anonymize Signal account data, wearable summaries, and OAuth tokens we hold for you (except limited records we must keep for legal, security, or audit reasons), and stop receiving new Garmin pushes for that connection.
• Export a copy of personal data we hold about you in Signal — email [email protected] and we will provide a portable export (for example JSON or CSV of your normalized summaries and account fields we store) within a reasonable time.
• Contact us (see section 12) with privacy questions or requests.

We aim to complete verified access, correction, deletion, and export requests within 30 days (or sooner where PDPA requires). Identity verification may be required before we act on a request.

10. Security

We aim to store refresh tokens server-side, use HTTPS for production endpoints, limit access to production payloads, and keep opaque user references instead of national IDs in Signal datasets. No method of transmission or storage is perfectly secure; we work to reduce risk reasonably for a private playground.

11. Children

Signal’s invited playground is not directed at children. Do not connect a child’s Garmin account unless you are the parent/guardian and that use case has been expressly approved.

12. Contact

Doctor World Pte. Ltd.
Attention: Darrell Zhang (Signal / privacy)
Email: [email protected]
Address: 25 Tannery Lane #04-27B, Singapore 347786

13. Changes

We may update this policy as Signal evolves (for example when APIs or processors change). Material changes will be reflected on this page and, where appropriate, communicated to invited users.