Data handling, in plain English.

Patient accounts are authenticated by email + password or Google sign-in. Sessions are stored in the browser using the Cloud auth SDK. Patient data is never queryable without a valid, signed session.

Every table that stores patient-entered data has row-level access rules enforced at the database layer: a session for patient A cannot read patient B's check-ins, reflections, medications, wearable imports, or AI conversations, even through the public data API.

All traffic between the browser, our app, and our backend is served over TLS. Data at rest, including database rows and backups, is encrypted by the underlying managed infrastructure (Lovable Cloud / Supabase / AWS-hosted Postgres). We do not maintain a separate self-hosted database.

When a clinician invites a patient into a shared cohort or reviews an exported report, the partner clinic is responsible for its own patient-consent workflow, its own EHR handling of any downloaded PDF, and its own device-level access controls. Myelina Health controls the software boundary; the clinic controls what happens after export.

Myelina Health never populates a clinician-side account with real patient data without an explicit, per-patient invitation initiated inside the app.

We use a small set of managed infrastructure providers to run the product. Current subprocessors include: Lovable Cloud (application hosting, database, edge functions, authentication), Lovable AI Gateway (LLM inference for the Myelina agent, prompts and responses are not retained for model training), Mailgun (delivery of app and account emails).

An up-to-date subprocessor list is available on request from partners@myelinahealth.com. We notify partner clinics before adding a new subprocessor that touches identifiable patient data.

Patients own their data. They can export a full CSV of check-ins, reflections, medications, and wearable imports at any time from Settings. Deleting a patient account irreversibly purges every related row, profile, check-ins, reflections, medications, wearable imports, AI conversations, buddy links, email logs, and subscription records, typically within minutes.

Aggregate cohort statistics used on the public State of MS Energy page are anonymized: individual rows are never exposed, and any tag or subgroup with fewer than 10 contributors is suppressed.

Report a suspected vulnerability or data-handling concern to security@myelinahealth.com. We aim to acknowledge reports within 48 hours. For a clinical-partner incident escalation, additionally copy partners@myelinahealth.com.

For the patient-facing version of these controls (encryption, RLS, deletion, what we never do with data), see the Security & privacy page.