All policies

Lantern legal center

Consumer Health Data Privacy Policy

Separate disclosures for health, nutrition, fitness, mental-wellbeing, and inferred health-related data.

Updated October 26, 2026

Drafts published for review. These materials have been tailored to Lantern's current architecture but have not been approved by counsel. The registered operator's legal name and address, third-party processor terms, actual retention periods, consent implementation, and full cross-app scope must be verified before these can be treated as final customer agreements.

Scope and why this is separate

This notice covers consumer health data processed through Lantern and services that are within the same operating business, to the extent Washington's My Health My Data Act or similar applicable laws cover that data. Read it alongside the general Privacy Policy. It is separate because broad health-data laws can cover wellness or inferences even when an app is not subject to HIPAA.

Categories collected

Depending on the features you choose: self-reported mood, stress, emotional and mental wellbeing, coping and lifestyle concerns; health and fitness goals, weight, activity and exercise details; sleep, energy or recovery; food, meal and nutrition logs; household and social context that may relate to health; conversations with Cass describing symptoms or personal circumstances; and inferred wellbeing, burnout, capacity or behavioral indicators created by Genome or related processing. Not every account or app supplies every category.

Sources

Directly from your entries and conversations; optionally from connected fitness, calendar or productivity providers you authorize; from workout/nutrition companion apps and connected Genome modules; and from analytics or inferences produced when a requested service processes the data.

Purposes

To provide features you actively request, such as logging health-related activity, tracking meals and routines, generating workout suggestions, remembering user-provided preferences, personalizing assistance, and presenting wellbeing estimates. Internal reliability, fraud and security operations may also involve information necessary for those purposes. We must not reuse sensitive data for unrelated advertising or profiling without meeting applicable legal requirements.

Collection and sharing choices

Where a service function needs health information, the app should provide a clear explanation at the point of collection and offer affirmative choices when required. Consent to collect and consent to share are separate under applicable laws; connecting a satellite or third-party provider should make categories and purposes apparent. Current permission and consent flows require verification before a wide public launch. Withdrawal requests can be submitted via Legal Contact and should stop future consent-based use, subject to legal exceptions.

Categories disclosed to processors and affiliates

Access or disclosure may involve Base44 infrastructure and permitted AI processing services; Genome and connected Lantern companion services where permissioned; Google or Fitbit only when a user enables related integrations; and support/security subprocessors where necessary. WhatsApp/Twilio should receive only message routing information and the message content the user has chosen to send, which could itself reveal health information. Stripe receives payment-related purchase information for Prism, not an entire health profile as part of ordinary checkout. The exact legal entities, applicable contracts and inter-app transfer rules require verification.

Sale of consumer health data

We do not offer a feature that lets users sell consumer health data, and this notice does not authorize sale of consumer health data. Before making any categorical promise that no sale or sharing occurs, Lantern must complete its processor, telemetry and advertising-tag audit. Any sale that triggers a statutory authorization requirement must not occur without that valid authorization.

Access, deletion, correction and appeals

Use the Legal Contact form to request information about collected or shared consumer health data, to ask for access or deletion, to withdraw consent or to challenge a response. We may verify identity and apply lawful exceptions. Washington law specifies particular response, deletion and appeal procedures when applicable; those must be reflected in the operational request-handling process, not merely this document.

Retention and security

Retention should be limited to the permitted, necessary purpose, with access restrictions and appropriate safeguards. We are validating the precise deletion and processor-retention schedule, including backups and derived Genome data. Do not assume deleting a chat or satellite account immediately purges all connected inferences.

Request handling and contact

Submit consumer health data access, deletion, correction, consent withdrawal, and appeal requests through Legal Contact. We may verify the request before providing or deleting information. Response and appeal handling will follow applicable statutory deadlines and exceptions, subject to final operational validation.

Questions about this policy?

Submit a legal or privacy request