Docs
How it reads your data.
The coach sounds like it knows you because it does. Here is exactly how that works, and why none of it means your data lives on our servers.
Assembled on your device
When you send a message, the app builds a compact context block on your device: your phase and goals, recent training, food and protein, sleep, weight history, and the coach's memory of your preferences. That block plus your message is what the coach reasons over.
Sent to answer, not to keep
That context travels encrypted to generate the reply and is processed transiently. It is not written to a database on our side, and there is no per-user store of your logs or chats anywhere but your device. The only thing recorded server-side for a message is an aggregate usage count for fair use, never the content.
Only what the answer needs
The context is a summary, not a data dump. The coach sees enough to be specific about today and this week; it is not handed your entire history for every trivial question. Voice is transcribed and photos are analysed the same way, only in the moment you send them.
Because the picture is rebuilt fresh from local data each time, correcting the coach's memory or editing an entry changes what it sees next time, instantly. You are always the editor.