Privacy Policy
Effective date: September 10, 2026
This policy describes how INBO App, LLC (“INBO,” “we,” “us”) handles information in INBO, INBO Lite and related services. INBO Lite provides glucose tracking, logging, food estimates and observational insights. It does not calculate insulin doses. The private edition has additional clinical calculation features.
1. Who we are
INBO App, LLC, 1945 Overlook Drive, Mount Dora, FL 32757, United States. Contact support@inbo-app.com for privacy, access, correction or deletion requests. We operate the app and determine how its service data is used.
2. Information you provide
- Profile and account: display name, contact details, and account or installation identifiers. On a new installation, the age screen asks for birth month and year, not a full birth date; the native app stores that answer on your device.
- Health and activity: glucose readings, insulin and medication entries, meals and carbohydrate entries, exercise, notes, glucose targets, settings, pregnancy information when you use that module, and findings produced from this information.
- Photos, food and questions: photos or menu documents you select, food descriptions, restaurant searches, assistant messages and feedback you submit. Photos and text may contain personal information; choose what to include.
- People you connect: caregiver contact details, family invitations, care-team enrollment and messages. Give us another person's details only with appropriate permission.
3. Information collected through features you use
CGM connections. Connecting Dexcom Share, FreeStyle LibreLinkUp or Nightscout authorizes INBO to retrieve readings from that service. Credentials needed for background retrieval are stored on INBO's server with encryption. Readings include their value, time, trend and source. Disconnecting removes the connection credentials; it does not automatically erase readings already in your history. Retrieval and notification timing depend on your provider, network and device.
Device and service activity. We process installation identifiers, push tokens, app and operating-system versions, feature-use events, timestamps, request/error details and subscription verification records. Some activity events relate to meals, glucose or logged corrections and therefore contain health information. INBO uses this first-party information for the service, support, security and product reliability.
Voice input. If you enable voice input, Apple speech recognition may process audio to produce a transcript, including server processing when on-device recognition is unavailable. Device microphone and speech permissions control this feature. The transcript is sent to the assistant only when you submit it with assistant sharing enabled.
Location. With your permission, the app can use location to identify your city for restaurant search, or include location in an enabled caregiver notification feature. You can deny or withdraw device location permission. Location is not required for manual logging.
Purchases. Apple handles payment. Apple and RevenueCat provide product, transaction, subscription and entitlement information so INBO can activate access, handle renewal or expiry, and assist with purchase problems. INBO does not receive your card number.
4. Optional AI processing
Before sending content through the current app's AI features, INBO asks for explicit permission. Food sharing and assistant sharing have separate controls in Settings → INBO Assistant. Declining allows you to continue entering glucose, food, carbs and other logs yourself.
- Anthropic (Claude): assistant questions, conversation context and the relevant health records retrieved to answer a question or prepare visit topics. These records can include glucose, insulin, meals, settings and agent findings. If you ask about a linked person, their authorized records may be included.
- OpenAI and Google (Gemini): selected meal, menu or nutrition-label images, food descriptions and restaurant details used to estimate carbohydrates, read labels or find menu information.
- Cloudflare: hosts INBO's processing endpoints and database through which these requests pass.
AI requests are processed by these providers under their applicable service terms and privacy policies. Their retention and use rules differ; INBO does not promise zero provider retention. See Anthropic's privacy policy, OpenAI's business data information and Google's Gemini API terms.
Turning sharing off stops future app requests for that purpose. It cannot recall a request already sent. INBO does not offer saved assistant conversation history. If you submit a bug report, flag or feedback, its text and any included conversation excerpt are retained for follow-up. Operational AI records include request time, model, token usage and cost for limits and troubleshooting.
5. How we use information
We use information to display and synchronize your records; provide the features you select; generate observations, food estimates and alerts; connect family members or care teams you authorize; administer paid access; respond to support requests; diagnose errors; prevent misuse; and meet applicable obligations.
We do not sell personal information, serve targeted advertising or track you across other companies' apps and websites. We do not use your identifiable health records to train INBO's own models. Optional AI providers receive the information described above, subject to their terms. We do not send health records to RevenueCat for advertising or purchase management.
6. Service providers and recipients
| Provider or recipient | Information and purpose |
|---|---|
| Cloudflare (Workers, D1, R2 and networking) | Hosting, stored app data, selected content, request processing and delivery. |
| Apple and Expo Push | App distribution, device push tokens and notification payloads. Enabled alerts may include a glucose value. |
| RevenueCat and Apple | Installation/customer identifiers, purchase transactions and subscription/access status. |
| Anthropic, OpenAI and Google | Optional AI content and context, as described in section 4. Google also provides restaurant information. |
| Twilio | Caregiver phone numbers and message content for enabled, consented messaging. |
| Resend | Email addresses and transactional correspondence, including consent and privacy communications. |
| Apify | Public restaurant URLs and menu content for menu retrieval. |
| Family, caregivers and care teams you connect | The health records, notifications or messages authorized through those connections. |
Service providers may process information in the United States and other countries where they operate. Data protection rules differ between countries. We may disclose information where required by law or to address fraud, security incidents or threats to people's safety. If ownership of the service changes, information may transfer with it, subject to applicable notice and legal requirements.
7. Retention
Your device retains local app records until you remove them or delete app data. INBO retains server account, logging, settings, purchase and support information while it is needed for the service, support, fraud prevention or applicable obligations.
Automated server housekeeping currently removes glucose history older than 180 days, agent execution and dispatch logs older than 90 days, rate-limit records older than 7 days, and completed/cancelled pending evaluations older than 30 days. Other record types are not covered by those short housekeeping windows. Food caches expire according to their cache period. Deleting an account initiates removal of its associated records from INBO's live service; backups, provider logs and records independently held by recipients may have different retention periods. Contact us for help with a specific retained record or provider request.
8. Sharing and notifications
Caregiver and family features are optional. Review the people you link and the information you share. A caregiver's receipt of SMS requires the recipient's applicable opt-in; SMS availability also depends on provider and carrier configuration. See the SMS terms. Recipients may keep information they already received.
Device notification permissions, Focus, Silent Mode, network availability and system scheduling affect delivery. INBO's current public release does not promise an alarm that overrides mute. These features supplement the monitoring and treatment plan established with your care team.
9. Children and parental involvement
INBO asks for birth month and year before onboarding can continue on a new installation. The native app stores the answer and age band in device secure storage; it does not upload this age-check answer. A person under 13 cannot independently complete new onboarding, and new parent-managed child setup is not available in this version.
Existing records are not automatically deleted by an app update. A parent or guardian may contact support@inbo-app.com to request access, correction, export, withdrawal of permission or deletion of a child's information. We verify the requester's authority before disclosing records. If you believe a child is using the service without the required permission, contact us. We will not open new child enrollment until the parental verification and controls are ready.
10. Your controls and deletion
You can edit entries, disconnect CGM services, manage linked people and notification permissions, and turn off optional AI sharing. You can request account deletion inside the app under Settings → Account → Delete account. The app reports whether server deletion succeeded before clearing local account data. Deleting the app alone does not delete server records or cancel an Apple subscription. Manage or cancel subscriptions in your Apple account's subscription settings.
You may contact support@inbo-app.com to request access, correction, deletion, restriction, objection or portability where applicable. We may need to verify that a request belongs to you or an authorized parent. Depending on your location, you may also complain to the relevant data-protection authority. We use information to provide requested services, with permission for optional sharing, for legitimate security and service needs where applicable, and to meet legal obligations.
11. Security and changes
We use access controls and encryption in transit, and encrypt stored CGM credentials. No system can guarantee absolute security. Protect your device and account, and contact support if you suspect unauthorized access.
We update this policy when practices change. Material changes will be communicated through the app, website or appropriate direct notice. New optional sharing requires the relevant permission. The effective date appears above.