Cookie Policy

This page covers both traditional browser cookies and adjacent technologies like localStorage and session storage. Together we’ll just call them “cookies” for simplicity, since the privacy expectations are similar.

We group cookies into three categories. You can change your preferences on the Cookie Settings page at any time.

• Strictly necessary. These make the Service work and cannot be turned off. They include:
  • bsc:history:v1 — your past analyses and Q&A turns, stored locally so you can revisit them.
  • bsc:medications:v1 — the medications you’ve added to the tracker (drug, dose, schedule, your personal notes), so the list is still there next time you visit.
  • bsc:symptoms:v1 — your symptom journal entries (mood, symptoms, seizures, notes) and the data needed to render the 30-day trends view.
  • bsc:appointment:v1 — your pre-appointment prep details: next visit date, provider/clinic name, visit kind, any custom questions you’ve added, and any generated questions you’ve dismissed. Used to render the prep packet at /prep.
  • bsc:carePhase:v1 — your explicit choice on the beyond-treatment view: either “set up my surveillance view” (surveillance) or “not yet, tuck this away for now” (unsure). We never infer this from other data.
  • bsc:survivorship:v1 — your surveillance rhythm (next/last MRI date, cadence, imaging facility) and your late-effects monitor entries (category, severity, notes, and which items you’ve flagged for your next visit). Used to render the beyond-treatment view and its printable care plan at /beyond-treatment.
  • bsc:consent:v1 — your current consent preferences, so we remember your choices.
  • Session cookies set by the hosting platform (Vercel) to deliver the page and prevent abuse.
• Analytics (opt-in). Aggregated usage data so we can see which parts of the Service are useful. No analytics scripts are loaded unless you consent.
• Error tracking (opt-in). If something crashes or throws an error, a report is sent so we can fix it. No error-tracking scripts are loaded unless you consent.

When we enable analytics or error tracking, we intend to use privacy-respecting providers. The actual provider names will be listed here once they are wired in. Current plan:

• Analytics: Vercel Analytics or a similar provider that supports cookie-less or aggregated collection.
• Error tracking: Sentry or a similar provider configured to strip personal data from stack traces.

When a provider is live, its scripts will only be loaded after your consent. You can revoke consent at any time; scripts will stop loading on your next page view, and you may clear any existing cookies they set using your browser’s controls.

• We do not use advertising cookies.
• We do not use cross-site tracking cookies.
• We do not sell or share your data for advertising.
• We do not set non-essential cookies before you make a choice in the banner.

The easiest way to update your choices is the Cookie Settings page. You can also use your browser’s built-in controls:

• Chrome: Settings → Privacy and security → Cookies and other site data.
• Safari: Settings → Privacy → Manage Website Data.
• Firefox: Settings → Privacy & Security → Cookies and Site Data.
• Edge: Settings → Cookies and site permissions.

Deleting strictly-necessary storage (like bsc:history:v1) will clear your past analyses — which is fine, it’s your data. You can also clear your entire local history from the Past analyses page.

We honor the Global Privacy Control (GPC) signal where we detect it, by defaulting analytics and error-tracking consent to off. The older “Do Not Track” signal is inconsistently implemented by browsers; we default to privacy-protective settings regardless.

Questions about cookies? Email info@gliowise.ai.