Summary: your lab results and your glucose history stay on your device and are never used for marketing. If you enable real-time updates, our server keeps your readings from the last few hours to deliver them to your device and, for up to 90 days, one summary per day (mean, time in ranges and how many readings arrived) to build your report. If you connect a Garmin watch, the app sends it your reading over Bluetooth, without going through our server. If you subscribe to a plan with caregivers, the people you invite see your glucose from the last few hours, with your consent. We do not sell your data. We do not share your data with third parties for advertising. If you live in the European Union or the United Kingdom, see your rights in section 12.
1 Overview
GlucoLive is developed by Fabricio Pereira and helps you track your glucose. The joint controllers of your data are Mathieu Acher and Fabricio Pereira. This policy explains what data we handle, how we use it, and your rights.
2 Data that stays on your device
- Your LibreLinkUp password — stored exclusively on your device via iOS Keychain. Never sent to our servers.
- If you use Nightscout, the address of your server and the access token you provide are sent to our server when real-time updates are on, because that's what we use to fetch your reading. See section 8.
- Your glucose readings and the lab results you import — used to display your glucose, history and reports, and stored on your device (and in your private iCloud, if enabled).
- App preferences (units, alert limits, themes) — stored locally.
We do not use your health data for marketing and we do not access your full glucose history. If you enable real-time updates (Live Activity/notifications), our server starts keeping your readings from the last few hours — what's needed to draw the card's chart — and one summary per day, for up to 90 days, which is what lets us show you period indicators in the report. See sections 8 and 9.
3 Usage analytics (anonymous)
To improve the app, we collect anonymous usage data through TelemetryDeck (privacy-first analytics): which screens and features are used, tied to an anonymous identifier. It does not include your glucose readings, your password, or your location, and is not used for advertising or cross-app tracking.
To count how many distinct devices use each version of the app, and which screens are opened, the update request sends a temporary code derived from your device identifier combined with the current day's date, and the list of screens opened since the last request (chosen from a fixed set of screen names, such as the lab results list or the report), plus a yes-or-no indication: whether the app sent a reading to a connected Garmin watch that day (without the value of the reading). This code changes every day and is used only for an aggregate count: our server counts how many distinct devices opened each screen that day and afterwards keeps only the totals. It does not identify you, cannot track your usage over time, and is not linked to your glucose readings or to the content of your lab results.
In the same request, the app may also send two diagnostic items, always taken from fixed lists: one of five values that tells how old the content of the Live Activity card was when you opened the app (on time, 2 to 5 minutes, 5 to 10 minutes, over 10 minutes, or no card), and the names of kinds of failures in the app itself, taken from a fixed list (sensor login, glucose reading, Nightscout, Live Activity, response format, and errors returned by the sensor service, such as rate limiting); for the Live Activity, the kind tells whether the app was in the background when it could not be started. We do not send glucose values, credentials or error messages, and having no internet, a sensor that is still starting or a wrong password do not count as failures. It uses the same daily code described above: our server counts how many distinct devices fell in each value that day and afterwards keeps only the totals.
4 Account and updates (optional)
If you turn on "Get updates," we use your email — from your connection (LibreLinkUp) or from Sign in with Apple — to send GlucoLive tips and news. We may also send updates via notification (push).
- It's opt-in: it only happens with your consent.
- You can opt out anytime in Settings › Account › Get updates, or via the unsubscribe link in emails.
- Your health data is never used to target these messages.
If you consent to receive updates, in addition to your email we send our email provider some data to organize the messages: your name, if you provided it, your country, the app language, whether you use iPhone or Android, which sensor you connected, and the status of your subscription. The status includes whether you are a subscriber, in the trial period or without a plan, the plan type (monthly or annual), how many caregivers your plan includes, the date your current period ends, and whether auto-renewal is on. We also share whether you were using GlucoLive before version 5.0. We use this data to let you know, for example, that your annual plan is about to renew or that your Pro is ending. It is updated when you open the app. We never send your glucose readings or your lab results.
Android waitlist. If you leave your email on our website to hear when GlucoLive launches on Android, it is kept by our email provider, in a separate list, along with the page language. We use it only to tell you about the launch. You can leave anytime through the unsubscribe link in the email or by writing to contact@glucolive.app.
5 Apple Health (HealthKit)
With your explicit permission, GlucoLive may read glucose, insulin doses and carbohydrates from Apple Health, and save to it the glucose and the insulin doses you log in the Diary. This data is used solely to display your history within the app (Diary, charts and reports). GlucoLive does not estimate carbohydrates or calculate doses, does not share HealthKit data with third parties, does not use HealthKit data for advertising, and does not use HealthKit data for any purpose other than providing the app's core functionality.
6 In-app purchases & subscriptions
GlucoLive Pro subscriptions are processed exclusively by Apple via the App Store (StoreKit). GlucoLive does not store, access, or process any payment information. Subscriptions auto-renew unless cancelled at least 24 hours before the end of the current period. Manage subscriptions in Apple ID Account Settings.
7 Pro + Caregiver (optional)
If you subscribe to a plan with caregivers, you can invite people to follow your glucose in GlucoLive, on their phone.
- Before your first invite, you confirm on a screen that you allow your glucose to be shown to the people you invite. We keep this consent with the date and the version of the text you accepted.
- People who follow you see your current reading, a graph of the last 8 hours, your first name and a notice when the data is out of date. These readings go through our server and are the same recent readings it already keeps for real-time updates. We don't create a new history.
- Followers never receive your LibreLinkUp password, your lab results, your log, your insulin records or your full history.
- An invite is a link valid for 7 days that can be used only once. In your app, we keep a partial version of the email of the person who accepted (for example, m***@gmail.com) and the date of the link, so you know who is following you.
- Followers sign in with their Apple account (on iPhone) or Google account (on Android). On the server, we keep only the sign-in type, an irreversible code derived from that account and the list of people they follow. We don't keep their name or email, and their email is never used for marketing messages.
- You can see who follows you in Settings › Caregivers and remove anyone's access at any time. Access ends immediately. If you cancel the plan, access continues until the end of the period already paid. If you delete your account, the links are deleted.
Because this is health data, sharing depends on your explicit consent (LGPD, art. 11; GDPR, art. 9), which you can withdraw by removing people's access.
8 Third-party services
The app uses, as needed, providers that process data only on our behalf:
- Abbott LibreView / LibreLinkUp or Nightscout — the source of your glucose data (at your request).
- Apple — Sign in with Apple and notifications.
- TelemetryDeck — anonymous usage analytics.
- Cloudflare — real-time updates and notifications. If you enable real-time updates (Live Activity/push), the app shares with our server on Cloudflare the access credentials for your data source: for LibreLinkUp, a session token (not your password); for Nightscout, the server address and access token you provided. With these, the server fetches your glucose and delivers it to your device even when the app is closed. To draw the card's chart, the server keeps your readings from the last few hours, along with the alert limits you configured. The server also keeps, for up to 90 days, a summary of each day: how many readings arrived, their sum (which is where the mean comes from) and how many fell in each range. That summary is what lets us show period indicators in your report. If you turn on the late-reading notice, we also keep that notice's configuration: whether it is on, the interval in minutes, the alert style, the night-time window if you set one, and your device time zone, needed to respect that window. This data is stored while the feature is on and is never used for marketing. You can turn the feature off anytime, and you can erase everything by deleting your account (section 11).
- Email provider — sending updates (only if you consent).
- Anthropic — reading your lab reports. When you import a lab report PDF, its text is sent to our server, which forwards it to that artificial intelligence service only to extract the test values. We do not store the report or its text on our server, and the extracted values stay on your device.
- Garmin (optional) — Garmin watch. If you connect a Garmin watch in Settings › Garmin Watch, the app sends it, over Bluetooth, your most recent glucose reading — the value, the trend arrow, the time of the reading and the alert limits you configured — so that the GlucoLive app on the watch can display it. It is sent from your iPhone to the watch using Garmin's development kit (Connect IQ) and the Garmin Connect app, which is used to choose the watch; it does not go through our server. The watch app keeps on the watch itself only the last reading received. What Garmin does with the data from your watch and from Garmin Connect is governed by Garmin's privacy policy. None of this happens if you do not connect a watch. To talk to the watch, the app asks for the Bluetooth permission, used only for that.
There is no third-party advertising and no cross-app tracking. GlucoLive is not affiliated with Abbott or Nightscout.
9 Data security
Your LibreLinkUp password is stored in the iOS Keychain and never leaves your device. Your glucose readings and lab results are stored on your device.
If you enable real-time updates, our server keeps the access credentials for your data source, the alert limits you configured, your readings from the last few hours and, for up to 90 days, a summary of each day, for as long as the feature is on. We do not keep your full glucose history — the daily summary holds no individual readings — and we do not use this data for any purpose other than delivering updates to your device and building your report. If you have a plan with caregivers, these recent readings are also shown to the people you authorized (section 7).
Our server keeps short-lived technical logs to diagnose delivery failures. These logs do not include your glucose values. The only exception is when a specific device is enabled for diagnostics, with the knowledge of the person using it.
Account data and usage data are transmitted over encrypted connections (HTTPS).
10 Children's privacy
GlucoLive is not directed at children under 13. We do not knowingly collect personal information from children under 13.
11 Your rights
You can turn off updates at any time in Settings › Account.
You can delete your account directly in the app, in Settings › Account › Delete account. Deletion erases from our servers: your account and your email, your consent to receive updates, your record with the email provider, the access credentials for your data source, the alert limits, the last-hours readings kept for real-time updates, the daily summaries from the last 90 days, the late-reading notice configuration, your device's notification records, and your links with the people who follow you (they lose access immediately).
Deletion does not erase what's on your device: your lab results, your log, and your glucose history stay with you. It also does not erase your data on LibreLinkUp or Nightscout — for that, contact those services directly. It also does not erase the last reading kept on a connected Garmin watch: to remove it, disconnect the watch in Settings › Garmin Watch and remove the app from the watch. Uninstalling the app removes locally stored data.
After deletion, we keep a single piece of data: an irreversible code derived from your identifier, which cannot identify you or recover any of your information. It exists only to record that the free trial has already been used, preventing account deletion from being used to renew it indefinitely.
You can also request access to your data via the contact in section 14. If you live in the European Union or the United Kingdom, see also section 12.
12 Users in the European Union, the European Economic Area and the United Kingdom
If you live in the European Union, the European Economic Area (EEA) or the United Kingdom, the processing of your data also follows the General Data Protection Regulation (GDPR) and, in the United Kingdom, the UK GDPR and the Data Protection Act 2018. This section sums up what that means for you.
Who is responsible. The joint controllers of your data are Mathieu Acher and Fabricio Pereira, individuals based in Brazil. You can reach either of us through the same contact: contact@glucolive.app.
Why we process each type of data.
- To make the app work and to manage your account and your subscription: performance of our contract with you.
- Health data, such as the glucose readings our server keeps when real-time updates are on, the glucose shown to the people who follow you and the text of the lab reports you import: only when you turn on the feature that needs them, based on your explicit consent.
- News emails and notifications: your consent.
- Anonymous usage analytics, technical logs to diagnose failures and the code that prevents renewing the free trial with a new account: our legitimate interest in keeping the app working, secure and fair. None of them use your health data.
Your rights. You can ask us to tell you which of your data we process and give you a copy; correct inaccurate data; delete your data (also directly in the app, in Settings › Account › Delete account); restrict or object to processing based on our legitimate interest; send you your data in a commonly used format; and withdraw your consent at any time, without affecting what was done before. To do so, write to contact@glucolive.app. We may ask you to confirm that the request is yours, and we reply within one month.
Automated decisions. GlucoLive does not make automated decisions that have legal effects on you or that affect you in a similarly significant way.
How long we keep data. Retention periods are in sections 8, 9 and 11. The credentials for your data source and your readings from the last few hours stay on the server while real-time updates are on. Daily summaries are kept for up to 90 days, and technical logs for a short period. After you delete your account, only the irreversible code described in section 11 remains.
Data outside your country. GlucoLive is run from Brazil, and some providers we use (section 8) process data outside the European Union and the United Kingdom, for example in the United States. In those cases, we rely on the safeguards these providers offer for international transfers, such as the standard contractual clauses approved by the European Commission. You can ask for more information through the contact above.
Complaints. If you believe we have not handled your data properly, you can complain to the data protection authority of the EU or EEA country where you live or work. In the United Kingdom, the authority is the Information Commissioner's Office (ICO). If you can, talk to us first: we would like the chance to sort it out.
Age. In some EU countries, the age to consent to data processing on your own is higher than 13, up to 16. Below that age, using GlucoLive requires permission from the person responsible for you.
13 The glucolive.app website and cookies
This website uses Google Analytics to understand how many people visit and which pages they read. Analytics cookies are only set after you click Accept in the cookie notice. Before that, or if you click Decline, Google Analytics runs with consent denied: it doesn't set cookies or identify you, and Google only receives cookieless signals to estimate the number of visits.
- Google Analytics cookies (
_gaand_ga_*): only with your consent, to count visits and pages read. We don't use advertising cookies. - Preferences stored in your browser and not sent to anyone: the site language and your cookie choice.
- YouTube videos: they only load when you tap the video, through youtube-nocookie.com. From then on, Google's privacy policy applies.
- Android waitlist: your email only goes to our email provider (Brevo) when you submit the form.
The legal basis for analytics cookies is your consent, which you can change or withdraw at any time through the Cookie preferences link in the site footer. Declining doesn't change anything about using the site.
14 Changes to this policy
We may update this policy occasionally. When a change is significant, we'll let you know in the app or by email before it takes effect.
15 Contact
Questions about this policy? Contact: contact@glucolive.app