What's in Fazon's export, and what you can do with it
Your food log, weigh-ins, Power Walks and phases, plus every check-in and why the coach kept or changed your targets. What's in it, and how to use it.
Why I made Fazon's export so detailed
I keep one set of health records, fed by every app I use, for an AI assistant to read. Fazon's export is built for it: every nutrient, every decision.
Fazon’s export is detailed because of where it goes. I keep my health records in one place, fed by every app I use, and an AI assistant reads across all of it. The more it has to read, the more it can see. So the export holds everything Fazon saves, down to the vitamins in a meal.
The here and now, and the long view
Fazon is the here and now. Today shows this day, and Trends shows the last few weeks. That is enough to decide what to have for dinner, and whether there is time for a walk.
The long view lives somewhere else. Into my health records go a full Apple Health export, an export from the app I track my gym sessions in, and Fazon’s. It is a classic second brain: everything in one place, and an assistant I can ask about it. Questions that cross apps get their answers there. How my training weeks line up with my protein. How one phase compares with the one before it. What changed in the weeks I slept badly.
What Fazon adds to the record
It is the same split again, this time in the food. Today shows the two things that decide my day: am I within my calorie target, and have I eaten enough protein? Vitamins, minerals and salt matter too, but they aren’t what I decide dinner by, so they aren’t on Today. They go in the export, and on into the second brain.
So Fazon’s part of the record is the food and the coaching, in as much detail as it has:
- Every nutrient. Each food I log goes into the file with every nutrient the food database has for it, vitamins and minerals included, not only calories and protein.
- Every coaching decision. Each weekly check-in goes in with why the coach kept or changed my targets that week.
The second one matters to me as much as the first. A target with no reason behind it is hard to trust and hard to question. Eat this much. Walk this far. When the week doesn’t go to plan, you can’t see why the number was set where it was. So I built the coach on clear, written rules, and I wanted every change it makes to come with a reason I can keep.
A coach whose reasons you can read is a coach you can understand.
What I do with a finished phase
When a phase ends, I make a file with Export all data, choose that phase’s weeks as the period, and add it to my records beside the other exports. Then I ask about it. Which weeks held steady. What changed, and what the coach saw when it did. How it lines up with my training and my sleep.
An example, made from Fazon’s demo data rather than mine: an AI assistant read the export and charted each weekly check-in, with what the coach decided.
None of that runs inside Fazon, and it doesn’t need to. Fazon makes the file. What I do with it is up to me, and the tools I choose.
A file for a program, not a person
That is also why the file is JSON. It is made for a program to read, not for a person. If the file is for a person, say your doctor, there is a better one: Export food log makes a PDF, with Headline values only or All nutrients.
Before you share it
The file holds your health data: what you eat, your weight and your phases, including things you deleted. When you upload it to an AI assistant or any other service, that service receives it and handles it under its own terms, not Fazon’s. Read them before you upload. Fazon can’t take back a file once you’ve sent it. What you share, and where, is your own call: send only what you’re comfortable with that service holding.
Your data is yours
You don’t need a system like mine to use the export. A spreadsheet works. So does reading the file once and putting it away. The point is that it’s yours, and the reasons come with it.
The help article Using your export with your own tools shows each step.
