Export your fasting data as CSV (because it's yours)
Why data ownership matters for fasting logs, what FastHQ's CSV export contains, and how one-row-per-fast with ISO 8601 timestamps lets you analyze your own history.
Your fasting log is a record of something you did with your own body. FastHQ’s position is simple: that record is yours, and you should be able to take it anywhere. So every fast you log can be exported as a CSV — one row per fast, clean timestamps, no lock-in.
What’s in the export
The CSV is deliberately boring and complete. One row per fast, with:
- start time and end time — ISO 8601 timestamps, so any spreadsheet or script parses them correctly
- protocol — 16:8, 18:6, OMAD, 24h, or custom
- target hours and actual duration
- result — complete or broken
That’s it. No proprietary format, no export that’s really a screenshot. A file you can open in any spreadsheet.
Why this matters
For anyone who takes a quantified-self approach, the log is the point. Owning it as plain data means you can:
- chart your real fasting history over months,
- correlate it with anything else you track,
- keep a backup that doesn’t depend on us, and
- leave whenever you want and take everything with you.
The last one matters most. Export is the opposite of lock-in. An app confident in its product doesn’t need to trap your data to keep you.
Honest data, including the bad fasts
FastHQ logs every fast as you actually did it — including the ones you ended early, marked plainly as “broken.” We don’t quietly drop the fasts that would spoil a streak, because there are no streaks, and because honest data is more useful than clean data. Your CSV reflects what really happened, not a tidied highlight reel.
Privacy, briefly
Your fasting log lives in your account with row-level security — only you can read it. We never sell or share it. The CSV just makes the ownership explicit: it was always yours; export hands you the file.
Want the bigger picture of what FastHQ tracks? See the fasted-state phase timeline.