Consumer Health Data Privacy Policy
Last updated November 7, 2026
TallyTic LLC (“we”, “us”) provides WellOrbs. This policy explains our collection and sharing of consumer health data and how to exercise your rights under Washington’s My Health My Data Act and other applicable consumer health data laws. Consumer health data includes information linked to a person that identifies their past, present or future physical or mental health, including information used to infer it.
Categories of consumer health data we collect
- Symptoms, severity, body locations, notes, tags, conditions and episodes.
- Daily habits and measurements, such as sleep, mood, water, caffeine, alcohol, blood pressure, weight, urination and bowel movements.
- Pregnancy information, including due dates, bleeding, movement logs and pregnancy-related symptoms.
- Medications, doses, schedules, doses taken or skipped, prescribers, pharmacies, refills, stock and change history.
- Health goals and appointments, including clinicians, appointment locations, reasons, notes and questions.
- Photos, videos, captions and file details that reveal health information. Vault contents are encrypted on your device; we receive encrypted files and metadata.
- Names, relationships, optional birth dates and sex, account identifiers, sharing records and other information associated with a health journal.
- Approximate weather locations and their history, if you enable weather features. A precise device position is rounded on your device to 0.1° before transmission.
- Charts, summaries and statistical associations derived from the information logged in a journal, including weather associations.
Sources of consumer health data
Data comes from you; people you authorize to contribute to or manage a journal; your device when you use a feature or grant a permission, including Health Connect on Android if you connect it; and weather services that supply weather and place information for an approximate location you choose. We derive charts and statistical associations from these records. We do not buy consumer health data or obtain it from advertising data brokers.
Why we collect and use it
We use consumer health data to provide the features you request: keeping a journal for yourself or someone you are authorized to represent; displaying logs, charts and educational safety information; producing insights and reports; sending reminders; storing photos and videos; adding weather context; and sharing selected journal information with people you choose. We also use information needed to authenticate users, enforce access permissions, maintain the service and investigate security problems.
We collect or share consumer health data to the extent necessary to provide a product or service requested by the relevant consumer, or with consent where required by law. If consent is required, we ask before collection or sharing and explain the data, purpose, recipients and withdrawal method. Consent to sharing is separate from consent to collection. Agreeing to our terms or acknowledging a privacy policy does not authorize unrelated uses of health data.
Categories of data shared and recipients
- People you authorize: selected logs, medications, appointments and ordinary photos, according to the permissions you choose. Log access includes weather location history. Vault contents are not shared through caregiver access. Removing access prevents future access through WellOrbs; it cannot recall copies or reports a recipient already saved.
- Processors operating the service: Supabase processes account and journal records for database, sign-in and synchronization services. Cloudflare processes requests and journal data for hosting, security, media storage and email delivery. Invitation emails include the inviter’s name and email, the journal subject’s name and the access offered. Providers process the information needed for their functions on our behalf.
- Notification providers: your browser’s notification service, such as Apple, Google, Microsoft or Mozilla, receives a push subscription and an encrypted notification payload. Discreet notifications are on by default. If you disable discreet mode, someone who can see your screen may see medication or journal details. Reminders in a native phone app, if available, are scheduled on that device.
- Weather and place services: Open-Meteo and OpenStreetMap receive an approximate location or a city search through our servers. They do not receive your name, journal contents or device IP address from us.
- Legally required recipients: information specified by a valid legal requirement may be disclosed to the relevant authority or other recipient. We notify you unless prohibited by law. We cannot provide decrypted vault contents because we do not hold the key needed to decrypt them.
- A successor business: if WellOrbs is merged, acquired or transferred, relevant account and journal records may transfer as permitted by law. We provide notice of material changes to the handling of your data and obtain consent where required.
We have no affiliates with whom we share consumer health data. We do not sell consumer health data, share it for targeted advertising, or use it to train AI models or disclose journal contents to analytics providers.
Your rights and how to use them
Email privacy@wellorbs.com to ask whether we collect, share or sell your consumer health data, obtain a copy, correct it, withdraw consent to its collection or sharing, or request deletion. You can also request a list of third parties and affiliates with whom your consumer health data has been shared, with a way to contact them. We do not sell consumer health data. You do not need to create an account to make a request.
Tell us which right you want to use and enough information to identify the relevant account or journal. Please do not send your password, vault passphrase, recovery phrase or unnecessary health details. We may ask for additional information to verify your identity or authority to act for someone else.
We handle requests without undue delay and within the deadline that applies to you. For Washington requests, we respond within 45 days of receipt; if a permitted extension is necessary, we explain why within that period and take no more than 45 additional days. For Nevada health-data deletion requests, we delete the requested data from active records within 30 days after verification, subject to applicable legal exceptions. Other applicable laws may require a shorter deadline. Access requests are free at least twice a year; any fee or refusal for an excessive or repetitive request must be permitted by applicable law.
A request to erase health data is different from hiding an entry in the app. When handling an erasure request, we also notify relevant processors and other recipients as required by law. Backup or archived copies may remain temporarily while those systems are restored or expire, subject to applicable deletion deadlines. For Washington health-data requests, any delay for backup or archived copies is limited to six months after verification. We explain any lawful exception that prevents us from deleting particular records.
If we decline a request, reply to our decision to appeal. We respond in writing within 45 days of receiving the appeal, explaining the decision and how to submit a complaint to the relevant regulator. You can contact your state Attorney General; in Washington, use the Attorney General’s complaint process. We do not discriminate against you for exercising your rights.