Privacy, in plain language.
What Glucose Connect uses, where it goes, and the controls you have.
Last updated: October 12, 2026. This page describes the current app and this website. It will be updated if their behavior changes.
Your LibreLinkUp connection
Glucose Connect connects to Abbott’s LibreLinkUp service to sign in and retrieve the glucose readings shared with your follower account. Your login and requests are sent to that service over HTTPS. This connection depends on Abbott’s systems and their data practices.
Your LibreLinkUp email, password, and session are stored in the iPhone’s Keychain. The app needs access after the phone’s first unlock so it can retrieve readings in the background. Signing out removes the app’s stored LibreLinkUp credentials and session, clears the saved widget/shortcut snapshot, and sends a clearing update to the paired Watch. You can choose to keep local readings or sign out and remove them. Neither option deletes your Abbott account or records in Apple Health.
Readings on your devices
The recent-reading store holds 30 days of glucose readings. As older readings leave that store, the app retains them in a local history archive for Rewind. With your permission, it can also import older glucose history from Apple Health. The archive is separate from the recent store’s 30-day window.
To remove the imported archive, use Settings → Apple Health → History → Remove imported history. This clears the local history archive, including the app’s own archived readings older than 30 days. It does not remove your recent readings or anything in Apple Health.
The current app has no developer-operated glucose server and includes no advertising or analytics SDK. Local settings, connection diagnostics, and app data support the app’s operation.
Apple Health is under your control
With your permission, Glucose Connect writes sensor glucose readings to Apple Health. The Log screen also writes fingerstick readings and insulin doses you enter, with their time and any optional note. Insulin entries include basal or bolus type and an insulin name when supplied. These entries are marked as user-entered in Health. The app offers a brief Undo that deletes the saved entry; you can manage it later in Apple Health. If you allow reading, it can import older glucose history for display. With separate read permission, it also reads Dietary Carbohydrates to show meal timing below the Day and Routine charts. Carb entries are held in memory for this display; the app does not write meal entries to Apple Health. You can manage these permissions in Apple Health under your profile’s Apps and Services → Glucose Connect.
Revoking permission does not delete readings already saved in Apple Health or copies already imported into Glucose Connect. Manage Health records in Apple Health and remove the imported archive separately in the app.
Widgets and Apple Watch
The app saves a compact local snapshot for its iPhone widgets, Control Center control, and Current Glucose shortcut, and sends snapshots to the paired Apple Watch. The widget extensions use these snapshots rather than signing in to LibreLinkUp themselves.
Widgets, controls, and complications may display glucose information on a locked device. Siri can speak a reading when you run the Current Glucose shortcut. You choose whether to add them, and can remove them at any time.
Sharing you choose
The chart share button creates a temporary image of the chart and passes it to Apple’s share sheet. The app removes its temporary export after sharing is dismissed; a copy you save or send is handled by the destination you choose. You can also export the local consent log from Settings → About → Disclaimer. Its contents include your agreement, timestamps, and app and device information.
Supporter Art and tips
Optional Supporter Art purchases and Buy Me Test Strips tips use Apple’s in-app purchase system. Apple handles payment and purchase records; Glucose Connect uses StoreKit to check the art entitlement and restore purchases. No glucose readings or LibreLinkUp credentials are part of these purchases.
Consent records and backups
When you accept the in-app disclaimer, Glucose Connect records the agreement locally. The record includes the disclaimer text and version, your acknowledgements, the time, and app and device information. You can view and export it from Settings → About → Disclaimer.
The consent record is included in device and iCloud backups. Other local app data may also be included in device backups according to your Apple settings. Backup and Health syncing behavior is controlled by Apple and your device configuration; local storage does not mean data can never be backed up.
Removing the app, removing an imported archive, signing out, and deleting Health records are separate actions. Do not assume that removing the app also removes Keychain entries, existing backups, records in Apple Health, or data held by Abbott.
This website
This site has no analytics scripts, advertising, signup forms, or application cookies. It does not request or receive your LibreLinkUp login or glucose readings. Fonts and images are served with the website rather than through third-party font or image services.
The site is prepared for hosting on Cloudflare Pages. The hosting provider may process ordinary request information, such as IP addresses and browser details, to deliver and secure the site. That infrastructure processing is separate from the app’s handling of glucose data.
Need help with the controls?
The setup and support guide explains Health permissions, account connections, and imported history. For anything else, get in touch.