Does a GLP-1 App Need Your Weight? A Data-Minimization Check

Does a GLP-1 app need your weight? Only for the features that use it: a weight chart, progress toward a goal, or trends you want to show your prescriber. A shot log, injection site rotation and dose reminders work fine without it. The general rule, called data minimization, is simple: share each piece of data only when you want the feature it powers.

That rule is not just our opinion. The FTC's advice to health app developers starts with asking whether they need to collect and keep data at all, and it puts the benefit bluntly: if you don't collect data in the first place, you don't have to secure it. The same logic works from your side of the screen.

What is data minimization, in plain English?

UK data-protection guidance describes it as personal data being "adequate, relevant and limited to what is necessary" for the purpose. It warns against collecting data "on the off-chance that it might be useful in the future."

Translated for a GLP-1 tracker: every field the app asks you to fill in should connect to something the app does for you. If you cannot name the feature, you can probably skip the field.

Which features need which data?

Feature	Needs	Does not need
Shot or pill log	Medicine, dose as prescribed, date and time	Weight, photos, location
Dose reminders	Your schedule, notification permission	Weight, contacts
Injection site rotation	Which site you used	Anything else
Weight trend chart	Weight entries	Your exact birth date
Goal progress	Starting and goal weight	Photos
Side-effect log	Symptoms and dates	Location
Food logging	What you ate	Photo library access (unless you scan photos)
Meal photo scan	The photo you take or pick	Photo location data, your whole camera roll
Progress photos	The photos you choose	Location data in those photos
Apple Health or Health Connect sync	Only the data types you switch on	Every health type at once
Account and sync	An email or sign-in	Phone number, home address

Notice what is missing from the "needs" column: precise location, contacts, and your advertising identifier. Those rarely have anything to do with tracking a GLP-1 medicine.

Does an app need your weight at all?

It depends on what you want from it:

• You want a shot log and reminders. Weight is optional. Some people deliberately keep the scale out of their tracker, especially if weigh-ins feel stressful.
• You want to see progress. Weight helps, but it is not the only measure. Waist measurements, how clothes fit, energy and progress photos all count. Our guide to tracking progress beyond the scale has ideas.
• You want something to show your prescriber. A weight trend is often useful at appointments, but your clinic weighs you too.

If an app will not let you past setup without a weight, that is a design choice, not a law of nature. It is fair to enter a rough figure, or pick a different app, if that matters to you.

What about age, sex and height?

Some apps use these for calculations like BMI or calorie estimates. Ask yourself whether you want those calculations. If you do not, consider whether the app needs your exact birth date or just an age range. "Year of birth" and "birth date" are different levels of detail.

What does "optional" really mean?

On Google Play's Data safety section, a data type can be labeled Optional only if every user, regardless of device or region, can avoid providing it. On the App Store, Apple has narrow rules for data that does not need to be disclosed at all, such as occasional, clearly labeled form submissions outside the app's main purpose.

Inside the app, look for:

• Skippable fields during onboarding, with a "Skip" or "Later" button.
• Features that switch on only when used, rather than permissions requested all at once on first launch.
• Privacy-protective defaults. The FTC's example: if a fitness app lets you share workouts, the default should be "private," not "public."

How do you check minimization in practice?

Run this five-question check on any app before you commit:

1. What does setup ask for? List every field. Which can you skip?
2. What permissions appear on first launch? Each one should tie to a feature you want today. (Our guide to camera, photos and notification permissions explains each.)
3. What does the store privacy label list? Is there anything you never typed in, like location?
4. What leaves your phone for AI features? Only the needed data, or your whole history?
5. How long is it kept? Data that is deleted on a schedule cannot pile up.

If an answer surprises you, the privacy policy should explain it. Our privacy policy checklist shows what a clear explanation looks like, and the 5-minute privacy scorecard helps you compare two apps.

Minimization by design: what to look for

Some of the best minimization happens invisibly. Good signs include:

• Photos downscaled and stripped of location data on your phone before upload.
• Uploaded meal photos deleted on a schedule once the estimate is done.
• AI features that send a summary of what is needed rather than everything you have ever logged, without your name or email.
• Sensitive extras, like letting an AI read your journal, off by default.

These examples are from our own privacy policy for GLPily: scanned food photos are downscaled with metadata removed and deleted 30 days after the scan, and the setting that lets our AI helper Pily read your journal is off by default. We list them not as a victory lap but because they are specific, checkable promises, which is what you should expect from any app.

When is sharing more data worth it?

Minimization does not mean sharing nothing. More data can genuinely help:

• Symptoms with dates make it easier to spot patterns around dose changes, which you can bring to your prescriber.
• Food and protein logs can help when appetite is low.
• Health app sync saves typing if you already weigh in on a smart scale.

The point is that you choose, feature by feature, with your eyes open.

Common questions

Can I use a GLP-1 tracker without entering my weight?

Often yes, for shot logging and reminders. Whether an app requires it at setup varies; check before you invest time.

Is it safer to enter fake or rounded data?

Rounded data, like a weight to the nearest five pounds, still works for trends. Fake data defeats the point of tracking. If an app asks for something you are not comfortable sharing, it is usually better to skip the feature or choose another app.

Why would a GLP-1 app want my location?

Sometimes for fraud prevention, regional pricing or language. The store privacy label and policy should give the purpose. If none is given, ask.

Does deleting a field later remove it from the company's servers?

Usually editing or deleting an entry in a synced app updates the server copy, but backups can take time. Check the app's retention section.