Zest Consumer Health Data Privacy Policy

This Consumer Health Data Privacy Policy is published by Launchpoint Dev Inc., DBA Zest (“Zest,” “we,” “our,” or “us”) for the Zest Connected Health experience.

Connected Health collects a fixed read-only wellness bundle: Steps, Workouts, Sleep, Hydration, Weight, Resting heart rate, Heart rate variability, Active energy, Exercise minutes, and Workout heart rate. Zest does not collect additional HealthKit or Health Connect categories through this feature. On Android, Health Connect import is limited to weight, sleep, and hydration under Google Play Health Connect minimum-scope. Steps, workouts, resting heart rate, heart rate variability, active energy, exercise minutes, and workout heart rate remain available via manual tracking on Android and via Apple Health on iOS.

AI/provider sharing is a separate purpose and requires a separate, current consent (recorded on successful Connect Health; withdraw in Connected Health settings): Share Connected Health day-series values, multi-signal wellness samples, and descriptive peptide-to-health comparison payloads with an AI/model provider solely for health-derived Ask context — descriptive association only, never causal claims — and only when a separate, current AI/provider-sharing consent is accepted. Connected Health data is not used for advertising or sale. Import consent never accepts AI/provider sharing.

Sleep stage breakdown (for example asleep, core, deep, REM, awake, and in-bed intervals) may be preserved from the granted Sleep category and, when a separate, current AI/provider-sharing consent is accepted, may be included in health-derived Ask context. This does not request any additional HealthKit or Health Connect permission beyond Sleep.

Import runs only after you accept the fixed Connected Health consent and grant OS-level access. Sync runs on foreground entry, cold start, or explicit manual refresh only.

A named deployed processor inventory is not listed in this policy because that inventory remains externally blocked until verified contracts and Production Release Gate evidence exist. We do not invent processor names.

Imported Connected Health data is retained while your Zest account remains active and the data has not been deleted through a Connected Health deletion request, account deletion, or another approved deletion path. A specific day-count retention period is not stated here because that figure remains externally blocked until counsel and operations evidence lock it. Disconnect stops future import and does not itself delete already imported history.

Backup deletion timing is not stated as an operational SLA in this policy until backup-deletion evidence is verified. Where applicable law imposes an outer bound (including a maximum of six months for certain backup deletions), we will follow that bound once operations evidence confirms the actual process.

You may exercise Connected Health consumer rights (access/export, deletion of imported health data, withdrawal of import or AI/provider-sharing consent, appeal, and status/receipt requests) through the authenticated in-app Connected Health and Settings surfaces when available, or by emailing privacy@zestfreshtracking.com. Public intake instructions live at https://zestfreshtracking.com/legal/consumer-health-data/rights. Do not include health sample values in email requests.

To appeal a denied request, reply to the decision notice or email privacy@zestfreshtracking.com with the subject line “Connected Health rights appeal,” including your request reference if you received one. Where applicable law provides a regulator contact mechanism after an appeal denial, we will include that mechanism in the appeal response.

Disconnect stops future import and AI/provider sharing that depended on Connected Health consent, and requests provider revocation where supported. Disconnect preserves already imported history until you separately delete imported health data, delete your account, or another approved retention/deletion rule applies.

Delete Imported Health Data is a separate destructive action that targets provider-imported rows and derived artifacts. It does not delete manual health entries.