The privacy promise of GLP 1 Tracker App is simple to the point of bluntness: no account, no server, everything you log stays on your phone. That architecture buys a lot of safety, and it raises one fair question. If the data never leaves the device on its own, how does it ever leave on purpose, when you want it to?
Export is the answer, and it is the one feature in the app whose entire job is letting information out the door deliberately. Because the door is usually locked, it is worth understanding exactly what an export is, what is inside the file, and what the copy is good for once you have it. That is this article.
What an export is, and what it is not
An export is a copy of your log in a standard file format, produced on your phone. In GLP 1 Tracker App it is a Premium feature, part of the optional subscription alongside unlimited history and trend charts. When you run it, the file is handed to the standard iPhone share sheet, which means it can go wherever the share sheet can send it: the Files app, a message to one person, an email attachment, whatever destination you pick.
It is worth being precise about what an export is not, because the word is used loosely elsewhere. An export is not a transfer. The app cannot import an export back in, so an export is not a way to move your log into a new install or onto a new phone. It is a copy for you and for the people you choose to give it to. Think of it like a printout of your medical record: useful in exactly the places a printout is useful, and not a mechanism for loading the record back into a system.
That framing matters because people sometimes export for the wrong reason and are disappointed for the right one. The file you get is a document. Documents are for reading, sharing, and keeping. They are not a second brain you can restore from.
Timing is the other thing worth knowing, and it is forgiving. An export takes whatever you have logged so far, which means you do not need to plan it in advance or maintain a schedule around it. Export the day before an appointment, the morning an insurer asks for documentation, or once a season for the archive, and each export will simply reflect the log as it stood that day. There is no penalty for exporting often and no bonus for exporting rarely; it is a read operation, not a ceremony.
Two formats, one decision
The app offers two export formats, and the choice between them is smaller than it sounds, because both carry the same underlying logs.
The spreadsheet option is the human one. It produces one CSV file per log type, zipped together, and CSV is the format that opens directly in Numbers or Excel. If you want to open a table, sort dates, filter a column, or build your own chart, this is the format that gets you there with no ceremony. Each log type is a separate file inside the zip, which keeps the columns of each table clean rather than blending dose records with water entries.
The JSON option is the complete one. It produces a single structured file with everything in it, organized the way software expects rather than the way spreadsheets expect. For most people its role is archiving: one file, held somewhere, containing the whole log in a format that any technically minded person or future tool can read. If you are handing data to a developer or a data-curious relative, JSON is the version they will ask for.
A reasonable rule of thumb: CSV when someone will read it, JSON when something might read it. And there is no rule against doing both.
GLP 1 Tracker AppLog everything free. When you need a copy for an appointment or an archive, export is one tap away.
Get the app
What is inside the file
The export contains your logged data, type by type. Specifically:
- Dose logs: date and time, medication, dose, injection site, and any note you attached.
- Weight entries: the reading, its source, and any note.
- Food entries: the food, the meal it belonged to, servings, calories, protein, carbohydrate, fat and fiber.
- Water: amount and source.
- Activity: type, minutes, steps, energy, and source.
- Side effects: name, severity, and note.
- Your profile, with your current targets.
The quality of each section follows the quality of the logging behind it. Food entries carry what you actually recorded, which is one argument for keeping the daily log honest, the habit we describe in What to Log Every Day on a GLP-1: A Two-Minute Routine. Side effect entries export with their severity ratings, which is what makes them useful in the settings where a severity pattern, not a bare mention, is what gets looked at; more on keeping that diary well in How to Track GLP-1 Side Effects (and What to Show Your Doctor).
One deliberate exclusion: progress photos are not part of the export. The file covers your logged entries and your profile, and photos stay where they are.
What an export is for
The uses cluster into a handful of situations, most of them occasional and all of them legitimate:
- An appointment. A dietitian or a new prescriber can learn more from a table of your actual weeks than from any form you fill in the waiting room, and what to bring, and what clinicians actually ask about, is its own subject.
- Insurance paperwork. Prior authorizations and appeals run on documented history: doses taken, dates, response.
- A second opinion. Bringing your own records means starting the consultation from evidence instead of memory, and not every clinician you consult will use the same portal.
- A personal archive. Some people simply want a copy of their own history, produced once a quarter or once a year, held somewhere they control.
- Your own analysis. A spreadsheet of weight and food entries answers questions no app screen was designed for, and some people enjoy the spreadsheet more than the app.
Notice the common thread: every use is you, deciding, on purpose, to hand a copy of your data to a recipient you chose. That is the entire difference between export and the background syncing that privacy-conscious design avoids, and it is why the feature routes through the share sheet rather than through an account.
After the file leaves the app
The moment you export, the privacy story changes shape, and it is worth being clear-eyed about it. Inside the app, your data lives on your phone, with no account and nothing collected. Once exported, the copy is outside the app, and it behaves like any other document you share: it sits where you put it, it travels where you send it, and anyone who obtains it can read it.
So the reasonable posture is to treat an export like any health record, because that is what it is. Send it to the people who need it, through channels you trust. Store it somewhere deliberate rather than wherever the share sheet happened to suggest first. Think for a second before attaching it to a group chat, uploading it to a service you know nothing about, or leaving it lying in a Downloads folder on a shared computer.
In practice, the share sheet makes the careful path easy. Saving to the Files app gives the export a home you can see and manage. Sending it in a message to one specific person gives it one recipient instead of an audience. The destinations that deserve a second thought are the ones where the file ends up somewhere you no longer control, and the share sheet does not hide those from you; it hands you the full menu, which is exactly why a beat of thought is worth taking before you pick.
None of this is a reason to avoid exporting. It is the reason exporting is a decision rather than a setting. The same design that keeps your log private by default is what makes each export meaningful: a copy that exists because you made it, for a purpose you chose, on its way to exactly one destination.
Your data, when you need a copyFree logging, all of it on your phone. Premium export turns it into a file you can hand over on purpose.
Download
Frequently asked questions
What is actually in an export from GLP 1 Tracker App?
Everything you have logged, organized by type. The export includes dose logs with date and time, medication, dose, injection site and any note; weight entries with reading, source and note; food entries with the food, meal, servings, calories, protein, carbohydrate, fat and fiber; water amounts and sources; activity with type, minutes, steps and energy; side effects with name, severity and note; and your profile with your current targets. Progress photos are not included.
Should I export my data as CSV or JSON?
Choose CSV if you want to open the data and look at it: the export arrives as one spreadsheet file per log type, zipped together, and opens directly in Numbers or Excel. Choose JSON if you want a single complete copy in one structured file, which suits archiving or handing to someone technically minded. Both contain the same underlying logs, so the choice is about shape, not substance.
Can I use an export to move my log to a new phone?
No. The app cannot import an export back in, so an export is not a way to move your log into a new install. It is a copy for you and for the people you choose to give it to: a doctor, an insurer, or your own archive. Treat it as a document you own, not as a transfer mechanism.
Are my progress photos included in an export?
No. Progress photos are not part of the export. The exported file covers your logged entries: doses, weight, food, water, activity, side effects and your profile with its current targets. If photos matter to your record, plan for them separately, and remember that any photo you do share deserves the same care as the exported file itself.
Is my data still private after I export it?
The app's privacy story is that everything stays on your phone, and an export deliberately ends that story for the copy you make. Once shared, the file sits outside the app, in whatever destination you chose, and anyone who gets it can read it. So treat an export like any health record: send it only where it needs to go, and store it somewhere you trust.