US Consumer Health Data Privacy Policy

Health data includes medication names and dose/timing records, notes, body measurements including weight, meals and nutrition, and reference-only health inferences such as dose estimates. Encrypted synced records and linked account, sync, access and health-service-use metadata may also qualify. The server cannot read end-to-end-encrypted records. If you turn on the AI record assistant (Pro) and confirm sending, we also treat as health information the dose counts, weight change, counts of each kind of symptom and meal and protein totals built from what you entered, meal kinds, preferences, allergies and disliked foods chosen from predefined lists, and app-help questions and current conversation history. This content is not end-to-end encrypted. The DoseWeek server and Google can read this content while an answer is being made; the DoseWeek server does not keep it. Google can also read it for as long as Google holds it: in memory for up to 24 hours, or for up to 90 days when Google’s abuse checks flag a request, which authorized Google staff may then review. Information read from HealthKit or Health Connect is not sent to the AI record assistant.

Sources are records you enter and readings you choose to allow from Apple Health (HealthKit) or Health Connect. Apple/Google sign-in and Store notices supply account/purchase metadata. We do not obtain health data from data brokers.

We use this data to display and manage your records, make reference-only calculations, provide sync and backups you request, and protect service security. We do not use it for diagnosis, treatment recommendations or health-derived ads or analytics. On request, we also use it to create AI summaries and general nutrition ideas. AI answers are not a diagnosis or a treatment recommendation.

Infrastructure processors Cloudflare and AWS handle the encrypted health records described above and necessary account/connection metadata for transfer, hosting, protection and backups. They must act under our instructions and contractual safeguards; we do not authorize independent health-data use. AI record assistant requests are processed by Google, a processor, on Google Cloud to create the answer. Google does not use the content to train AI models; how long Google may hold it is described in the Privacy Policy.

Apple and Google handle sign-in/payments in their own roles; DoseWeek sends no recorded health content through those paths. Google AdMob/Firebase receive the technical data described in the privacy policies, not recorded health content. Technical data revealing health-service use receive applicable health-data protections. We do not share health data with corporate affiliates. If you choose export, calendar integration or your own cloud backup, chosen recipients and file/calendar/cloud providers receive the selected details or encrypted file and may make onward copies. If technical information would reveal that you use a health service, we ask for your separate consent before sending it to AdMob or Firebase.

We do not sell health data. We do not send recorded health content for advertising or use health-derived ad targeting. We do not use geofencing around healthcare locations to identify or track people, collect health data, or send health-related messages or ads. We do not sell health information sent to the AI record assistant either, and we do not share it for advertising.

Optional health sync uses explicit consent. Collection/use or sharing without consent is limited to what is necessary for your requested service. This exception never covers optional ads or analytics.

Sharing outside the requested service requires separate consent from collection consent. Refusal leaves local recording available. You can withdraw as easily as granting consent: disable sync in Settings or contact us. For the AI record assistant we ask for consent on a separate screen when you first turn it on, and we ask you to confirm again each time records are sent. You can withdraw at any time in Settings > AI record assistant.

Ask to confirm collection, access your health data and its categories, sources and recipients, withdraw consent, or delete data through app Settings or wonyoung@wonyoungchoi.dev. We use only the minimum information needed to verify identity.

After verification, account or server-copy deletion starts immediately even with an active subscription; it does not wait for subscription expiry. We notify processors and any other health-data recipients to delete. Deleted information is also removed from backups and copies within 7 days. Restoring a backup must not expose deleted data again.

Local records and your exported files need separate deletion. Store subscription cancellation is separate. Do not email passwords, recovery codes, health records or purchase tokens.

Washington: response within 45 days from receipt; one justified 45-day extension, with the reason given before the original deadline; appeal decision within 45 days.

Nevada: response generally within 45 days after authentication, with a justified 45-day extension; requested deletion within 30 days after authentication and recipient deletion within 30 days of notice; appeal within 45 days. Our stricter 7-day backup limit still applies.

Connecticut: response within 45 days, with a justified 45-day extension; appeal within 60 days; covered consent-based processing stops within 15 days after withdrawal. Appeal a refusal through the same email route. We give refusal reasons and, if an appeal is denied, explain how to complain to the relevant state Attorney General.

Operator: Wonyoung Labs. The general privacy policies explain retention, transfers, security and breach response. Broader health-data use or sharing requires the applicable notice and new consent.

DoseWeek is operated by Wonyoung Labs (원영랩스). Mail-order business registration number: 제 2026-부산금정-0425 호. Contact: wonyoung@wonyoungchoi.dev