Summary
- GlucoFinity does not require an account.
- We do not operate a backend that receives your health records or app logs.
- GlucoFinity does not sell personal information, show advertising, or use health information for advertising or tracking.
- Apple Health, microphone, speech, camera, and photo access are optional and controlled by your device permissions.
- You can delete individual logs or reset locally stored app data from Settings.
Information the mobile app can access
Apple Health and Health Connect
On iPhone, GlucoFinity can request read-only access to blood glucose, step count, active energy, and workout records you choose to share through Apple Health. On supported Android devices, the app can request read-only access to blood glucose records through Health Connect. The app does not add, alter, or delete records in either health store.
Health permissions are optional. You can deny individual permissions or change access later in Apple Health, iOS Settings, or Health Connect. Available readings depend on records already written by another app or device.
Information you enter
You may enter meals, reviewed nutrition estimates, meal photos, medication logs, feeling check-ins, notes, and display preferences. These entries are stored in the app's local storage on your device so that you can review them later.
Voice, speech, camera, and photos
If you choose voice meal entry on a supported iPhone, microphone audio is provided to Apple's on-device speech recognizer. GlucoFinity requires on-device recognition and does not send the recording or transcript to a developer-operated transcription server. The app uses the resulting transcript with a locally running language model to create an editable meal draft. Audio is not retained as a saved app log.
Camera and photo-library access are used only when you choose to attach a meal image. GlucoFinity does not upload the image to a developer-operated server. Your device and photo-library settings continue to govern the original image.
How information is used
Information available to the app is used to provide features you request, including:
- displaying permitted glucose and fitness records;
- organizing meals, medication logs, and feeling check-ins;
- calculating deterministic summaries and observational associations;
- creating nutrition estimates for your review; and
- remembering local app settings.
GlucoFinity does not use health information for advertising, marketing, eligibility decisions, or unrelated data mining. The app does not diagnose, prescribe treatment, or recommend medication or insulin changes.
Local processing, storage, and retention
Health-store records are queried from the selected device health service when needed. User-created app entries and preferences remain in local app storage until you delete them, reset local app data, or uninstall the app. GlucoFinity does not intentionally synchronize this app content to a developer-operated cloud service. On iOS, the local app storage used for these entries is excluded from device backup by default.
Downloaded speech assets, language-model files, and nutrition databases contain no personal health information. They may remain in app-managed or system-managed storage until the operating system clears them or the app is uninstalled.
Network requests and third-party services
The mobile app downloads the LFM2.5 model, tokenizer files, and related runtime assets from the Software Mansion React Native ExecuTorch repository hosted by Hugging Face. These download requests can expose ordinary network information, such as an IP address, to the hosting provider. The requests do not include your HealthKit records, meal transcript, medication logs, or feeling check-ins.
Apple provides HealthKit, Apple Speech, and related system services under Apple's privacy terms. Google provides Health Connect on supported Android devices. USDA FoodData Central supplies the bundled nutrition reference; nutrition lookup does not transmit your meal entry to USDA.
The public website is hosted through GitHub Pages. Its interactive demo uses fictional data and session-only browser state. When you activate browser voice features, the browser may download model files from Hugging Face; audio and transcripts remain in the browser, while the model host can receive ordinary download-request metadata. Hosting and model providers may process basic network logs under their own privacy policies.
Sharing and disclosure
We do not sell or rent personal information. Because GlucoFinity has no user account or developer-operated health-data backend, we do not have a server-side copy of your app logs to share. Information may still be disclosed when required by applicable law, but only to the extent information is actually under the developer's control.
Your choices and deletion
- Change Apple Health or Health Connect access in your device settings.
- Delete individual meals, medication logs, and feeling check-ins in the app.
- Use Settings → Reset local app data to clear locally stored entries and preferences.
- Uninstall GlucoFinity to remove its app container and downloaded resources.
Resetting GlucoFinity does not delete source records from Apple Health or Health Connect and does not change the permissions managed by those services.
Children's privacy
GlucoFinity is not directed to children under 13, and we do not knowingly collect personal information from children through a developer-operated service.
Changes to this policy
This policy may be updated when app functionality or data handling changes. The date at the top of this page identifies the current version.
Contact
GlucoFinity is developed by Damian Saelee in collaboration with Mark Betts (Bioengineering) and Chloe Wong (Pharmacy) as an educational university project. For privacy questions or app support, visit theGlucoFinity Support page. Do not include personal health information in a public support request.