Memory-augmented health assistants
How user-owned health profiles plus retrieval-augmented context can deliver personalised guidance without surveillance. Architecture trade-offs.
An AI health assistant that does not remember you is a stranger you meet repeatedly. The architectural choice is where memory lives.
Three options
- Server-side memory. Most convenient. Highest privacy risk. The default for big tech.
- Client-side memory. Browser/device storage. Lowest privacy risk. Sync across devices is the trade-off.
- Hybrid (encrypted server, client-decrypted). Best of both. Engineering complexity is the trade-off.
DiaCare’s choice
Client-side. Health profile lives in browser localStorage and is injected just-in-time into the system prompt. We never store the profile server-side. Cross-device sync is on the roadmap as an opt-in feature with hybrid encryption.