Privacy Policy

Glucose Log collects only the data you explicitly enter into the app:

• Blood glucose readings (value, date, time, context, notes)
• Reminder preferences and notification settings
• App settings and display preferences

When you contact support, the following technical information may be included in your message to help us assist you:

• Device model (e.g. iPhone 15)
• Operating system version (e.g. iOS 17.4)
• App version
• System language

This information is only sent if you choose to contact support and is used solely to resolve your issue.

If you subscribe to Pro, your subscription/purchase status is processed on our behalf as described in Section 5, Third-Party Services.

Separately, the app collects a device identifier, a pseudonymous app instance ID, and app events — such as first launch, completed purchase, screen views, and onboarding progress — for advertising measurement, product analytics, and crash reporting. These are handled by Adapty, Meta, and Google as described in Section 5, and never include your glucose readings, notes, or any other health data.

We do not collect:

• Your name, email address, or any account information
• Location data
• Any health data for advertising, marketing, or analytics purposes

Your data is used solely to provide the app's core functionality:

• Displaying your glucose history, charts, and statistics
• Generating reports (CSV/PDF) that you can share with your doctor
• Sending local reminders you have configured
• Responding to support requests you initiate

Your health data is never used for advertising, analytics, data mining, or any purpose other than improving your personal health management within the app.

All data entered in Glucose Log is stored exclusively on your device using the platform's secure local storage. None of it is transmitted to our servers or any cloud service.

• On iOS, data is protected by the iOS Data Protection API
• On Android, data is stored in the app's private sandbox
• If you delete the app, all your data is permanently deleted
• We do not have access to the data you enter at any time

Glucose Log handles sensitive health information. We comply fully with Apple's App Store Guidelines (Section 5.1.3) regarding health data:

• Health data is not used for advertising or marketing
• Health data is not disclosed to third parties, including the subscription, advertising, analytics, and crash-reporting partners named in Section 5
• Health data is not used for data mining or any secondary purposes
• The app only reads data from Apple HealthKit or Android Health Connect when you choose to start an import, and only requests read access to blood glucose values — it never writes to or modifies your Health data

The app integrates four third-party services, provided by three companies. None of them receives your glucose readings, notes, or any other health data — that data never leaves your device.

Adapty — subscription management. When you purchase or restore a subscription, Adapty processes your Apple App Store / Google Play purchase and subscription-status information together with an anonymous device identifier, solely to activate, verify, and restore your Pro access. Adapty's own privacy policy is available at adapty.io/privacy.

Meta (Facebook SDK) — advertising measurement. We run ads for this app on Meta platforms, and the SDK tells us whether those ads led to an install or a purchase. For this purpose it processes a device identifier (including the Apple advertising identifier, where you have allowed it) and standard app events automatically recorded by the SDK, such as first launch and completed purchase. Meta may use this data for advertising measurement, analytics, and ad targeting, and may link it to an existing Meta profile. Meta's data policy is available at facebook.com/privacy/policy.

We do not send Meta any custom events, and no event we record contains glucose values, diabetes type, notes, or anything else derived from your health data.

Google Analytics for Firebase (Google LLC) — product analytics. It shows us how the app is used in aggregate, so we can see where people get stuck — in onboarding, for example — and make the app easier to use. It processes:

• An app instance ID — a pseudonymous identifier generated by the SDK. The app has no user accounts, so it is not tied to your name or email address.
• Device and app information: device model, operating system version, app version, language, and approximate country or region. The region is derived from your IP address; Google Analytics does not store the IP address itself.
• Usage events: app opens, screen views and time spent on a screen, progress through the onboarding steps and the usage goals selected there, paywall impressions and the plan chosen, the fact that a subscription checkout was started, creating, enabling or deleting a reminder, the fact that a reading was saved, usage streaks, and the outcome of the notification and tracking (ATT) permission prompts.
• User properties, recorded only as categories and buckets: whether you have a paid subscription, your measurement units (mmol/L or mg/dL), app language, number of reminders (as a range), number of readings (as a range), whether onboarding is complete, and notification permission status.

Firebase Crashlytics (Google LLC) — crash reporting. When the app crashes or hits an error, it sends a stack trace together with the device model, operating system and app version, the state of the app at the moment of the crash, and a Crashlytics installation identifier. Crashlytics is disabled in debug builds.

We use this data to understand how the app is used, to find the points where people drop off, to improve usability, and to find and fix crashes. It is not sold, and it is not used to profile you by health status.

How long it is kept. Event and user data in Google Analytics is retained for 14 months and then deleted automatically. Crash reports in Crashlytics are kept for Firebase's standard retention period of up to 90 days.

Google LLC processes this data as a processor acting on our behalf, and it may be transferred outside your country, including to the United States. Google describes how it handles this data at policies.google.com/technologies/partner-sites and firebase.google.com/support/privacy.

The App Tracking Transparency choice described above applies to advertising identifiers. It does not switch off the analytics and crash reporting described in this section. You can ask us to delete the data associated with your app instance identifier — see Section 7, Your Rights.

The app contains no advertising of its own — you will never see ad banners or sponsored content inside Glucose Log.

Core app functionality — logging, history, statistics, reminders, backups, and reports — works fully offline: you can record and review your readings with no connection at all. An internet connection is needed to purchase or restore a Pro subscription, and, whenever the device is online, the services described above transmit the limited non-health data set out in this section.

Glucose Log is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has used the app, please note that all data is stored locally on the device and can be deleted by removing the app.

Since all data is stored locally on your device, you have full control at all times:

• Access: All your data is visible inside the app
• Export: Use the Reports feature to export your data as CSV or PDF
• Delete: Delete individual entries within the app, or delete the app to remove all data permanently
• Portability: Export your data at any time using the built-in report feature

Analytics and crash data. The data described in Section 5 is held by our processors rather than on your device, so deleting the app does not remove it. To request deletion of the data associated with your app instance identifier, email us at support@glucoselog.app.

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically. Continued use of the app after changes constitutes acceptance of the updated policy.

If you have any questions about this Privacy Policy or how your data is handled, please contact us: