PRIVACY · LIVEWITHMERIDIAN.COM · 28 SEPTEMBER 2026
Meridian, livewithmeridian.com. Contact: hello@livewithmeridian.com. Jurisdiction follows the host of the public website. Health-diary content is not stored by that host in this version.
Diary, notes, experiments, Pattern Card answers kept after you open the companion, and on-device chat live in an encrypted vault in this browser (IndexedDB, AES-GCM). Optional PIN wraps the key. Idle lock runs when a PIN is set. Clearing site data or Wipe deletes this device’s vault. Meridian does not keep a copy.
Typed companion answers are generated on this device. Voice is offered only if the browser exposes on-device speech recognition. Otherwise the microphone stays off.
A backup file is yours. No PIN: the file contains the key. With a PIN: the file is only as strong as that PIN.
Visiting the marketing site or loading the PWA shell is not the same as uploading a menopause diary. Ordinary web hosting still sees request metadata.
The public host or CDN may process, for security and uptime: IP address; browser / user-agent; date and time; requested URL and referrer if sent; TLS and error logs.
Purpose: operate TLS, stop abuse, debug outages. Not used to build a health profile. Retention: the host’s access-log default (typically days to a few weeks). Processor: the VPS or CDN operator on your hosting invoice. We do not sell this data. The companion does not load a marketing analytics SDK.
Off today. If it ships, only fields you tick leave the device. Diary, notes, name, and consultation pack stay. Emergencies are not sent to a model.
Planned local processing through a native HealthKit / Health Connect shell. Daily derived fields would stay in the vault. No Meridian sensor cloud in this design.
A future employer pilot receives anonymised cohort counts, not identifiable series.
Access and deletion of health content is on your device (export, Wipe, clear site data). For website-log questions write hello@livewithmeridian.com.