Privacy
Information on your devices
Glucose Thread stores app data on your Apple devices and, when you enable synchronization, in your private iCloud account. LibreLinkUp, Dexcom Share, and optional AI-provider credentials are stored in the Apple Keychain. Apple Health data is accessed only with the permissions you grant.
Connected glucose and food services
When you connect LibreLinkUp or Dexcom Share, the app sends authentication information directly to that service and retrieves the readings you are permitted to access. Your email or account identifier and provider account are involved in those requests. Open Food Facts receives barcode lookup requests. These services operate under their own privacy policies; disconnecting the app does not delete your account or records with them.
Apple Intelligence and external AI
Supported features may use on-device Apple Intelligence or Apple Private Cloud Compute. You can configure and select your own OpenAI, Anthropic, or OpenRouter account. The optional Glucose Thread cloud meal-photo service described below instead uses provider credentials managed by Drive Logic. Your selected provider receives the content needed for that feature: selected food photos, meal descriptions, redacted aggregate health and fitness evidence for Deep Insights, or a voice transcript when you enable cloud voice interpretation. The external AI client sends text transcripts, not raw voice recordings. Requests are authenticated with your provider account and should be treated as linked to it.
Nutrition images are re-encoded to remove file metadata, but visible names, faces, labels, or other identifiers are not automatically removed. Crop or redact them before sending. Aggregate analysis excludes direct patient identifiers and raw readings, but health-related content remains sensitive. Do not assume that removing names makes an account-authenticated request anonymous.
OpenAI requests disable response storage, but this does not guarantee zero retention: provider security and abuse-monitoring policies may still apply. OpenRouter requests use routing controls intended to avoid data collection and require zero-data-retention providers. Provider terms, account settings, and applicable exceptions govern remote retention. Read the policies for OpenAI, Anthropic, and OpenRouter before connecting an account. Provider charges may apply separately.
Glucose Thread cloud meal-photo accounts and subscriptions
When you choose developer-funded cloud meal-photo analysis, Glucose Thread uses Convex to manage your email-based account, sign-in sessions, subscription entitlement, analysis jobs, and usage allowance. Resend processes your email address and sign-in email for magic-link delivery. Selected meal photos are uploaded temporarily to Convex and sent to the configured OpenAI or Anthropic service to estimate nutrition. The service does not receive your glucose history, Apple Health records, CGM credentials, or voice recordings through this meal-photo flow. Photos and nutrition estimates can themselves contain sensitive health information.
Account identifiers, email addresses, signed Apple purchase information, transaction and subscription identifiers, purchase status, and usage records are used to authenticate you, provide the requested service, enforce allowances, restore purchases, and prevent abuse. Apple handles payment information; Glucose Thread does not receive your card details. These records are linked to your account and are not used for advertising tracking. Core glucose tracking and manual logging do not require this cloud account or a subscription.
Uploaded cloud photos are removed when processing finishes or the job terminates. Scheduled cleanup also removes expired or abandoned uploads, with orphaned storage objects eligible for cleanup after 30 minutes. Temporary analysis results expire after 15 minutes; saved entries on your devices are separate. Cleanup timing can be delayed by service outages. AI providers may retain requests under their own security and abuse-monitoring policies; deleting our copy cannot erase an independent provider's records.
Use Delete Account in the app to revoke cloud access and remove your account, sign-in sessions, uploaded photos, temporary analysis jobs, and operational usage records. Limited Apple transaction records and a keyed email-derived recovery identifier remain to support purchase recovery and financial integrity. This identifier is pseudonymous, not anonymous. Deleting the account does not cancel an Apple subscription; manage or cancel it in your Apple Account subscription settings. See Convex's privacy policy and Resend's privacy policy.
New Relic diagnostics and usage
Glucose Thread uses New Relic for reliability monitoring and product analytics when configured in a distributed build. Data includes device or installation identifiers, app and operating-system versions, device type, app launches and feature interactions, crash reports, performance measurements, and other technical diagnostics. Because the SDK can associate events with a device identifier, these data are disclosed as linked to users. Product interactions and device identifiers support analytics; diagnostics support app functionality and reliability.
Application-defined diagnostic events exclude glucose values, other health values, patient identifiers, email addresses, credentials, photos, user-entered text, transcripts, and raw errors. New Relic also attaches its own SDK metadata. Health content sent to an optional AI provider is a separate data flow and is not part of these application-defined telemetry events. See New Relic's privacy information.
Purposes and tracking
Health and fitness information, photos, text entries, and account information are used to provide the features you request. Technical information is used for app functionality and the analytics described above. Drive Logic does not sell health information, use it for advertising profiles, or share app data with data brokers. The app does not use these data for cross-company advertising tracking. Device or account linkage does not itself mean advertising tracking.
Beta recruitment
If you use the beta recruitment form, Drive Logic stores the name, email address, Apple device, reason, consent version, and submission time you provide. This information is used only to validate and manage beta participation, contact you about Glucose Thread, prevent duplicate handling, and maintain appropriate business records. If the request passes validation, Drive Logic sends the name and email address to Apple App Store Connect to add the applicant to the Glucose Thread external TestFlight group. A dedicated email provider sends a concise summary to the Glucose Thread team and a confirmation to the applicant. The form does not request or collect glucose readings, medication information, diagnoses, medical records, or CGM credentials. Drive Logic does not sell recruitment details or use them for advertising profiles. You may request deletion through the contact page using the submitted email address.
Retention and deletion
Saved readings, entries, and photos remain in your app storage until removed through the app or Apple's storage controls. Private iCloud copies and backups may remain after you delete the app; manage those separately in your Apple Account. App deletion does not delete your LibreLinkUp, Dexcom, or AI-provider account.
Completed or canceled background AI jobs are removed locally. Failed job request payloads become eligible for removal after seven days; cleanup runs when the app next performs its maintenance. Your saved entries and accepted results are separate from temporary job payloads. Disconnecting a provider stops future requests to that provider but cannot recall a request already sent or erase its remote logs.
New Relic diagnostics and recruitment or support records are retained according to the service's configured retention and the purpose of the record, including applicable security and legal requirements. Contact Drive Logic for the retention information applicable to your request or to request access, correction, or deletion of records we control. We may need to verify your identity; do not provide health records or account secrets to do so. For data held by an independent glucose or AI provider, use that provider's own request process.
Your choices
Revoke Apple Health permissions in Apple's settings, disconnect glucose or external AI services, remove optional AI credentials, and disable private iCloud synchronization when desired. Revoke Deep Insights cloud consent from Insights; voice interpretation has its own consent controls. These choices affect future access and processing and do not erase records already held independently by another provider. For help with diagnostic-data or recruitment-data requests, contact Drive Logic.
Safety
Do not use Glucose Thread for medical decisions or insulin or medication dosing. It is not a medical alarm or emergency service. Readings and estimates may be delayed, incomplete, or inaccurate. Verify information with the official monitoring app or device and consult a qualified healthcare professional before making medical decisions. Read the Terms of Use for the full medical and service limitations.
Contact
Privacy and support questions can be sent through the Drive Logic contact page. Do not include glucose readings, medical records, credentials, or other sensitive health information.