Privacy policy

• Your Dexcom or LibreLinkUp username and password are stored in macOS Keychain on your Mac and are sent only to the corresponding provider, Dexcom or Abbott.
• Your Mac fetches glucose readings directly from Dexcom or Abbott. Readings, saved history, and insights never reach our servers.
• Once a day, the app sends a pseudonymous heartbeat (an installation ID, app and macOS versions, and system language) so we can count active installs.
• Feedback is only sent if you choose to send it.
• We don't sell personal information or share it with advertisers.

Glucose Please is a macOS menu bar app for viewing Dexcom and FreeStyle Libre glucose readings on your Mac. It is developed and operated by Gus Gaidelevicius, an independent developer in Western Australia. In this policy, "we", "us", and "our" mean Gus Gaidelevicius.

This policy covers the Glucose Please Mac app and the glucose-please.app website. Read it alongside the terms of use.

When you set up the app, the following is stored on your Mac:

• Glucose account credentials (provider, username, password, and region), plus the selected LibreLinkUp person's identifier and name when applicable, in macOS Keychain.
• App preferences, such as glucose units, alert thresholds, and graph time window, in macOS Keychain.
• Saved history settings, including per-account saving and retention preferences, collection dates, deletion cutoffs, and an opaque account identifier, in local configuration files.
• Your terms of use agreement, recording the version you agreed to and when, in the app's preferences.
• Saved glucose history, only if you turn it on (see Saved history below).

None of this is uploaded to our servers.

Dexcom: To show your readings, the app signs in to Dexcom Share and requests readings directly from Dexcom using your stored credentials. Dexcom handles this information under its own privacy policy.

Abbott LibreLinkUp: If you choose FreeStyle Libre, the app signs in to LibreLinkUp, requests your sharing connections, and fetches readings for the person you select directly from Abbott. Abbott handles this information under its own privacy policy. Credentials and connection details are not sent to our servers.

Daily heartbeat: When the app checks for updates each day, it sends a heartbeat containing a random installation ID, the app and macOS versions, and your primary system language. Our server stores this with the request time, your IP address, user agent, and request path. The first time the app checks in, it registers its installation ID with our server so later requests can be verified.

The heartbeat is pseudonymous, not anonymous: the installation ID stays the same over time and is also attached to any feedback you send. It never includes glucose readings, saved history, or insights. It is part of the update check and can't be turned off in the app.

Feedback: If you send feedback from the app, we receive your message, any name or email address you choose to include, your installation ID, app and macOS versions, IP address, and user agent. If you include health information in your message, we receive that too.

Analytics: The website uses Vercel Analytics to measure visits with de-identified, aggregated data, such as page views and device types.

Live demo: The readings shown in the homepage demo come from a Dexcom account controlled by the developer. Visitors' Dexcom data is never requested or stored.

The website has no public user accounts.

Run the app: Your credentials and preferences let the app sign in to your selected provider and show readings the way you've set them up.

Understand usage: Heartbeats help us estimate active installs, release adoption, and which languages to support.

Respond to feedback: Feedback helps us find and fix problems, and contact details let us reply if you include them.

Improve the website: Vercel Analytics shows how many people visit and which pages are most useful.

Keep the service secure: Installation IDs, IP addresses, and request details help us verify requests from the app, limit abuse, and keep the service running.

Service providers: Vercel hosts the website and provides analytics, Neon hosts our database, and Resend delivers feedback notification emails to us. They process information on our behalf to provide these services, under their own privacy terms.

Feedback is stored in our database and may be included in a notification email delivered through Resend and our email provider so we can read and reply to it.

Legal requirements: We may disclose information if required by law, or where necessary to protect the rights, safety, or security of our users, the public, or Glucose Please.

We don't sell personal information or share it with advertisers.

We're based in Australia. Vercel, Neon, and Resend may process information in the United States and other countries where they operate. Dexcom and Abbott process your readings under their own regional services and privacy policies. Dexcom uses your chosen region, and LibreLinkUp routes requests to the region associated with your account. By using the app or website, you acknowledge that information may be processed in these locations.

History saving is off for each new account or person until you turn it on in Insights or Settings → Insights. Your previous choice is restored when you return to an existing account or person. When saving is on:

• The app saves glucose values, reading times, trends, and basic details about when each reading was fetched, in encrypted files on your Mac.
• History is kept separately for each provider account and selected LibreLinkUp person, with its own encryption key in macOS Keychain. Only the history for the currently signed-in account and person is displayed.
• Insights are calculated on your Mac. History and insights are never uploaded or synced between devices.
• When you first turn it on, the app can save available recent readings: up to 24 hours from Dexcom Share or 12 hours from LibreLinkUp. Gaps can occur when readings are unavailable or the app cannot fetch them.
• Each account or person can keep a rolling 30 or 90 days. Older readings are removed when history is accessed or during maintenance, including while signed out. Files may remain longer while the app is closed or cannot access the encrypted history or complete maintenance.

What each action does:

• Turning saving off stops new readings being saved for the selected account and person. Existing history is kept, subject to retention.
• Turning saving back on starts a new collection period. Readings from while it was off aren't imported.
• Delete all saved history turns saving off for every account and person on this Mac and deletes all their history files and encryption keys, including accounts you are signed out of. This action is available while signed out. The app records when you deleted it, so those readings are not saved again automatically.
• Signing out or switching providers, accounts, or people keeps each account's encrypted history and saving preference on this Mac. Returning to the same account and person restores the history still within retention and resumes saving if it was on. History is not displayed or collected for accounts you are signed out of.

For Dexcom, history is associated with the account and chosen region. For LibreLinkUp, it is associated with the account and selected person, and the same history is used whether the region is set to Automatic or chosen manually. Changing your password or temporary connection problems do not delete history.

Saved history is not a medical record or backup, and it can be lost if you delete it, lose your Mac, or lose its encryption key.

Deleting history doesn't delete information held by Dexcom or Abbott, feedback you've sent, our server records, or copies outside the app's control. Glucose alerts are delivered through macOS notifications, and network requests and system logs can leave caches or metadata managed by macOS. The app asks macOS to exclude history files from automatic backups where supported, but this can't prevent every copy. Uninstalling the app alone may leave support files or Keychain items behind, so use "Delete all saved history" before uninstalling.

Heartbeats and feedback don't currently have a fixed deletion period. We keep them while they help us understand usage and respond to feedback, and you can ask us to delete them (see Your choices). Short-lived security records, such as rate limits, are deleted automatically. Vercel, Neon, and Resend may keep their own operational records under their policies.

Your credentials and the separate history encryption keys are protected by macOS Keychain. Saved history uses authenticated encryption and is never deliberately written to disk unencrypted. If an account's key or files can't be read, the app preserves them and reports the problem when that history is accessed. Live monitoring is unaffected. Connections to Dexcom, Abbott, and our servers use HTTPS.

• Manage your glucose account and preferences in Settings. Signing out removes your stored credentials and keeps encrypted history on this Mac, subject to retention.
• Control saved history in Settings → Insights: turn saving on or off and choose retention for the current account and person, or use "Delete all saved history" to remove every account's history from this Mac, even while signed out.
• Block website analytics with a browser or network content blocker that stops Vercel Analytics from loading.
• Ask to see, correct, or delete your information, such as feedback you've sent or records linked to your installation ID, by contacting us. We may ask for details that help us find your records, such as the email address you used or roughly when you sent feedback.

If you're unhappy with how we've handled your information, please contact us first. If you're in Australia and still not satisfied, you can complain to the Office of the Australian Information Commissioner.

Glucose Please is intended for adults, including parents and guardians who manage a child's glucose sharing connection. It isn't directed at children under 16, and we don't knowingly collect personal information from them. If you believe a child has sent us personal information, contact us and we'll delete it.

We may update this policy to reflect changes to the app, the website, or the law. We will post every change on this page and update the date above, and for significant changes we will also let you know on the website or in the app where appropriate.

For questions or requests about this policy or your information, contact Gus Gaidelevicius through ggaidelevicius.com.