Privacy, in plain language.
What Glucose Connect uses, where it goes, and the controls you have.
Last updated: September 26, 2026. This page describes the current prerelease 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 through Glucose Connect removes its stored LibreLinkUp credentials and session. Signing out is not a deletion of glucose records or your Abbott account.
Readings on your devices
The app stores recent glucose readings locally and prunes readings older than 30 days from its recent-reading store. It can separately import older glucose history from Apple Health to support Rewind. That imported archive is not subject to the recent store’s 30-day window.
To remove the imported archive, use Settings → History → Remove imported history. This removes only the imported copy. 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 blood glucose readings to Apple Health. If you allow reading, it can import older glucose history for display. 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 and sends snapshots to the paired Apple Watch. The widget extensions use these snapshots rather than signing in to LibreLinkUp themselves.
Widgets and complications may display glucose information on a locked device. You choose whether to add them, and can remove them at any time.
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 → 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. A public support contact has not been established for this prerelease.