Privacy

Your intake answers describe your health situation. We treat them as sensitive data: minimal collection, banded values, short retention, and a working delete button. This page describes exactly what is stored.

The identifier

Livestack sets one first-party cookie, ls_anon: a random UUID, kept for 90 days. It is the only identifier we use. There is no account unless you save a stack, and saving asks only for an email address — stored as a one-way hash plus a delivery contact for the magic link, never as a plaintext record tied to your answers.

Your intake answers

  • During the wizard, answers live in memory and in your browser's sessionStorage. They are never put in URLs.
  • Answers are banded — age band, weight band, budget band — rather than exact values.
  • Free-text fields are scrubbed for emails, phone numbers, and names before any use, and the raw text is dropped after parsing.
  • A completed recommendation is snapshotted server-side, keyed to an intake hash and your anonymous id. Snapshots from unsaved sessions are purged after 180 days.

Model calls

The language model that writes the explanation never decides your stack and never sees raw free text — only banded fields and matched catalog ids. Calls are routed exclusively to zero-data-retention endpoints, with providers that train on inputs blocked. If no such route is available, the site falls back to template copy rather than relaxing those constraints.

Analytics

No third-party analytics, pixels, or ad-tech anywhere. We use Cloudflare Web Analytics, which sets no cookies, plus a server-side event log (page-level events against the anonymous id — never intake answers). Intake data is kept out of URLs, logs, and error reports.

Deleting your data

Delete my data removes saved stacks, recommendation snapshots, and event records for your email address or a stack link, and confirms by email when an address is on file.

Security

TLS only, strict transport security, and a content security policy that keeps scripts first-party. Offers and payment happen on the merchant's site — Livestack never sees payment details.