Savia Consumer Health Data Privacy Policy
This policy describes how [Legal entity name], doing business as Stack64, collects, uses, and shares consumer health data and how to exercise your rights. It applies to data protected by applicable consumer-health laws, including Washington's My Health My Data Act and Nevada's consumer-health law. Protection may depend on residence or where data is collected, not residence alone. Contact support@stack64.com; mailing address: [Business mailing address].
1. Categories collected and their purposes
- Health status and history: conditions, symptoms, diagnoses you report, medications, allergies, treatments, medical documents, measurements, and physical or mental-health information you supply or connect. Used for authorized analysis, answers, evidence organization, and goal support.
- Activities and bodily functions: sleep, activity, nutrition, vital signs, tracker entries, photos, goal measures, check-ins, and progress. Used to identify patterns, follow chosen plans, conduct enabled research, and recheck results.
- Reproductive and other sensitive health information: menstrual, reproductive, sexual-health, gender-affirming-care, genetic, or similar information if you choose to include it in authorized records or messages. Collection is limited to supported, requested or enabled features and applicable permissions; cycle-specific features require the relevant express selection. Listing a category does not mean Savia purchases it, infers an eligibility profile, or provides a specialized feature for it.
- Inferred or derived health information: extracted observations, research findings, possible-condition hypotheses, goal assessments, and personalization based on health-related activity. Used for the enabled wellness features and their permitted automatic actions. Inferences may be wrong and remain health data when the law treats them as such.
- Information connected to health services or interests: health-related messages and search topics, optional profile or faith/practice details associated with wellness goals, selected approximate area where related to health context, and notification, sharing, account, or support identifiers linked to the above. Used to provide the chosen functionality, communicate authorized results, maintain the service, and fulfill requests. We do not use geofences to identify visits to healthcare facilities or target health advertising.
2. Sources and processing
Sources are you; sources you authorize, such as Apple Health and connected wearables; your activity and entries in Savia and generated apps; and analyses derived by Savia and its providers from that information. We process it electronically through storage, extraction, AI analysis, research, summaries, permitted personalization, and authorized communication. Optional photos, dictation, background research, condition reports, reproductive features, area sharing, and sharing connections follow their respective permissions. We do not acquire health profiles from data brokers.
3. Categories shared, recipients, and reasons
We do not sell consumer health data or use it for targeted advertising. Collection and sharing require the applicable consent or a specific legal exception, such as processing necessary to provide a product or service you request. Where sharing consent must be separate from collection consent, we obtain it separately. Accepting service Terms is not that consent.
- AI and research providers: Google Gemini receives relevant messages, records, photos, app logs, profile facts, and findings for enabled tasks. AWS receives task data for processing and isolated analysis programs. Tavily and PubMed receive generated search queries, not attached private files; a query can reveal health concerns or unintended personal details despite instructions to generalize it.
- Storage and execution providers: Supabase and, where used for agent execution, LangChain/ LangGraph process relevant account-linked health records and working state to operate the service. Technical tracing is configured to exclude health content.
- Feature and delivery providers: Deepgram receives optional dictation for transcription; Open-Meteo receives optional town-search words and rounded area for environmental context. Expo and the applicable Apple or Google push service receive delivery identifiers and notification text, which may include your first name but excludes health details. These identifiers or topics may still qualify as health data when linked to service use.
- People and services you authorize: selected clinicians, family members, other recipients, or connected services receive only the authorized content or continuing access. AgentMail and the recipient's email service process email you direct Savia to send. Recipients can retain or forward copies.
- Support and legally required recipients: authorized personnel and contracted support systems may access necessary request details and records to address your request. Courts, regulators, or other recipients may receive the minimum required or specifically permitted by applicable law. A successor in a lawful business transfer must honor applicable privacy obligations. These categories do not create a blanket safety, business, or litigation exception to health-data consent rules.
[Confirm the support-mail provider and identify each actual affiliate receiving consumer health data, or affirm that there are none, before publication.]
We do not authorize third parties to collect consumer health data across our website and unrelated services for advertising. Providers may process technical or security data under their applicable terms; independently visited websites and recipients you choose operate under their own notices. Our service-provider arrangements do not excuse our obligations for health data.
4. Requests, withdrawal, correction, and deletion
Email support@stack64.com with "Privacy request" and the action requested, or use the corresponding in-app control. You may ask whether we collect or share your health data, access it where provided by law, obtain the required list and contact information of recipients, withdraw collection or sharing consent, or delete it without deleting your account. You can review and correct visible facts, notes, and findings in Savia; contact us for other corrections. Correcting or removing a finding does not itself delete the original records or past reports.
We verify identity with reasonably necessary information using a secure process. Start with your account contact and a description of the request, not health records or passwords. You need not create a new account. If we cannot authenticate a request after reasonable efforts, we explain that and may request necessary additional information. We do not unlawfully discriminate against you for exercising rights; a feature needing withdrawn data or permission may no longer work.
Withdrawal stops future processing dependent on that permission; it does not recall completed requests or itself erase history. Deletion covers applicable original and derived data, with required notice to processors and other recipients. We restrict any permitted retained records to the specific lawful exception. We do not delay a statutory deletion request merely to apply the app's optional account-cancellation period.
Washington: We respond without undue delay and within 45 days of receipt. If reasonably necessary, we may extend once by 45 days, explaining why within the original period. Authentication does not extend that deadline. Any permitted backup delay may not exceed six months from authentication. Information requests are free up to twice annually; any exceptional fee or refusal must meet the law's requirements.
Nevada: We respond without undue delay and within 45 days after authentication, with one necessary extension of up to 45 days on timely notice. Deletion from our records and network and notice to recipients occur within 30 days after authentication; recipients have their own 30-day period after notice. A permitted backup-restoration exception can allow delay up to two years after authentication; this is a legal maximum, not our ordinary schedule. Information requests are free at least twice a year and for additional requests that are not manifestly unfounded, excessive, or repetitive.
Where more than one law applies, we honor all applicable requirements, including the shorter applicable deadline. Our routine retention periods and any specific lawful exception must be disclosed accurately before this draft takes effect.
5. Appeals
If we decline a request, we provide the reason and how to appeal. Send "Privacy appeal" to support@stack64.com with your request reference and reasons for review. We respond in writing within 45 days of receiving a Washington or Nevada appeal. If denied, we provide the applicable regulator complaint route. You may also contact the Washington Attorney General or the Nevada Attorney General.
6. Changes to this health-data policy
This policy can change. We identify each revision and effective date and notify affected users of material changes through the app, account email, or another appropriate channel before they apply, as required by law. Before collecting or sharing additional categories, using new purposes, or adding recipients for which the law requires new consent, we provide the specific notice and obtain affirmative consent. A revised policy or continued use alone does not authorize that processing. Earlier effective versions are available from support@stack64.com.