Settings

Analysis behaviour, AI access and your data.

Analysis

These change how symptoms are attributed to meals. The defaults suit most people.

Attribution window

How long after eating a symptom can still be linked to that day. Longer windows catch delayed reactions but blur which day was responsible.

Minimum severity to count

Symptoms below this are treated as background noise rather than events.

Minimum exposure days

Below this many days of eating a food, it is reported as 'not enough data' instead of being ranked.

AI access

Optional. Only the AI analysis screen uses this.

Your API key

Accepts an Anthropic key (sk-ant-…) or an OpenRouter key (sk-or-…). Stored only in this browser's local storage and sent only to this app's own /api route.

Your data

Everything lives in this browser. Export regularly — clearing browser data will delete it.

0 entries · 0 food records · 0 symptoms

Sample data

Three months of realistic generated data, useful for seeing what the dashboards do.

Storage

This build stores data locally in IndexedDB. The repository layer is written against an interface, so switching to Vercel Postgres later is a data copy rather than a rewrite — see docs/POSTGRES_MIGRATION.md.

Danger zone

This permanently deletes everything stored in this browser.