Data, audits and exports

Your diary is a documented dataset, not a screen. Every row says where its numbers came from, so you or an agent can query it, audit it and take it with you.

Provenance on every row

• Source of each number: a label, the food database, a photo estimate or your own edit, with a confidence.
• Who wrote it (you, your assistant or the system), which op and from where (the dashboard, MCP, the CLI or the API).
• Nutrients as integers in a fixed unit per nutrient (millikilocalories, milligrams, micrograms), so sums are exact. See nutrients and units.

Asking questions

• get_diary: meals over any range, with items and ingredients.
• get_nutrition_summary: totals and daily averages of any nutrient over any range.
• query_foods: which foods and ingredients you eat, how often.

Auditing the diary

Ask “audit my diary for last week” and your assistant calls audit_diary: missing meals, items still unconfirmed, implausible portions, days without a symptom log and likely duplicates, each with the meal it points at, so they can be fixed one by one. Diary audits are part of Plus; on Free, your assistant can run the same checks itself from get_diary. The review-diary skill in the plugin does this as a routine.

Exporting everything

export_data returns your whole diary as JSON and as CSV files (meals, items, ingredients, nutrients, symptoms, programs and corrections), with a README.md data dictionary describing every file, column and unit. Exports are free on every plan. From a terminal:

npx @meterapp/gutlog export_data

Your whole history is kept on every plan. Deleting your account deletes the diary; export first if you want to keep it.

Gutlog's own analytics never see any of this: see privacy.