GLP-1 App Permissions: Camera, Photos and Notifications

Why does a GLP-1 app ask for camera, photo and notification permissions? Camera access lets it take new pictures (progress photos, meal scans, barcodes). Photo-library access lets it read or save pictures you already have. Notification permission lets it remind you about shot day. Each one should match a feature you actually want, and you can usually grant the narrowest version and change your mind later in Settings.

Here is what each permission really unlocks, the smarter options iPhone and Android now offer, and where to review it all.

What does each permission actually let an app do?

Permission	What it unlocks	Typical GLP-1 app use	What it does not give
Camera	Take new photos or scan with the live camera	Progress photos, meal photo scans, barcode scanning	Access to your existing photo library
Photo library (read)	View photos already on your phone	Pick an old progress photo or meal picture	Necessarily all photos, if you choose limited access
Photo library (add only)	Save new images into your library	Save a generated image or a chart	The ability to view your existing photos
Notifications	Show alerts on your lock screen	Shot-day and dose reminders	Any access to your data
Apple Health / Health Connect	Read and/or write specific health data types you approve	Import weight or steps, write weights you log	Data types you do not switch on

Two things are worth underlining. First, camera is not gallery: an app with camera access can take new pictures, but that does not let it browse your camera roll. Second, permission to use a photo is not a promise about what happens next. Whether that image is uploaded, sent to an AI service, or deleted after 30 days is a privacy-policy question, not a permission question. For meal photos specifically, see what happens to your meal picture in AI food scanners.

Which photo option should you choose on iPhone?

Since iOS 14, Apple has let people give an app access to only the photos they select, instead of their whole library. Apple's developer guidance describes this "limited" mode as one where the app can fetch only what the user has chosen.

Apple also gives developers a private photo picker that does not require any photo library permission at all: you pick a photo, and only that photo reaches the app. And apps that only need to save pictures can ask for add-only access instead of full read access.

So when a health app asks:

• If you only plan to add the occasional photo, choose limited access and pick specific images.
• If the app never asks and just opens a picker, that is the private picker at work. No permission needed.
• If an app insists on full library access for something as simple as adding a progress photo, it is fair to ask why.

How does Android handle photos now?

Android has a system photo picker that shows your media and passes only the images you choose to the app. It is built into Android 11 and up on devices receiving Google system updates, with a backported version for older devices that support Google Play services.

Google Play has also tightened its rules. Under its Photo and Video Permissions policy, apps targeting Android 13 or later may request broad photo and video access only when system pickers cannot provide the core feature, for example a gallery app. Full compliance became mandatory on May 28, 2025. For most health trackers, that means you should see the system picker, not a request to read all your photos.

Do you need to allow notifications?

Only if you want reminders. On Android 13 and up, notifications are off by default for newly installed apps until you grant permission, and apps targeting newer Android versions can choose when to ask, so they can explain why first.

For a weekly GLP-1 shot, a reminder can be the single most useful feature of a tracker. If you turn notifications on, a few tips:

• Check that lock-screen previews show only what you are comfortable with others seeing.
• If the reminder does not arrive, the cause is often a Focus mode, battery saver or a silenced app channel rather than the app itself. Our notification checkup walks through the usual culprits.

What about Apple Health and Health Connect access?

These work differently from camera or photos: you approve specific data types, and reading and writing are separate switches. You might let an app read weight and steps but not write anything back.

• iPhone: Health app → tap your picture or initials → under Privacy, tap Apps to see which apps can read or write Health data and change each one.
• Android: Health Connect is under Settings → Security and privacy → Privacy Controls → Health Connect on Android 14 and up, where App permissions lists connected apps.

Google notes something people often miss: an app that has already read data from Health Connect keeps its own copy, so removing data from Health Connect may not remove it from that app.

How do you review or revoke permissions later?

iPhone: Go to Settings → Privacy & Security, then tap a category such as Camera or Photos to see every app that asked, and switch access off. Settings → Privacy & Security → App Privacy Report (once turned on) shows how often apps actually used those permissions over the past 7 days.

Android: Go to Settings → Apps → [the app] → Permissions, tap a permission, and choose Allow or Don't allow. Under the app's Unused app settings, Pause app activity if unused can automatically limit apps you stop using.

A permission spring-clean every few months takes five minutes and is oddly satisfying.

How GLPily handles these permissions

Since you are reading this on our blog: on iPhone, GLPily asks for camera access to take progress photos, scan barcodes and photograph meals, and asks for photo-library access to add progress photos and save images you create. On Android, it uses the system photo picker, so it never asks to read your photo library. Notifications are for injection reminders. Every one of these can be declined; the related feature just will not work until you allow it.

A simple rule for any permission pop-up

Ask three questions before you tap:

1. Which feature is this for? If you cannot tell, tap no for now.
2. Is there a narrower option? Limited photos, the system picker, read-only health access.
3. Can I find what happens to the data afterwards? That answer lives in the privacy policy and the store's privacy label; our guide to reading Apple's App Privacy labels helps with the second.

And if you want to go further, ask whether an app needs a given piece of data at all. That is the idea behind our data-minimization checklist.

Common questions

If I deny camera access, can I still use a GLP-1 app?

Usually yes. You will lose camera-based features like photo scanning, but logging shots, weight and symptoms should still work.

Can an app see all my photos if I give it limited access?

No. With limited access on iPhone, or the photo picker on Android, the app receives only the photos you choose.

Why does an app ask for notification permission on first launch?

Some apps ask early so reminders work from day one. You can say no and turn notifications on later in your phone's settings.

Does revoking a permission delete data the app already has?

No. Revoking stops future access. To remove photos or logs already uploaded, delete them in the app or follow its account deletion steps.