Oxylittle Privacy Policy

1. Information the app processes

• Personal health records: manually entered blood oxygen and heart rate readings, symptoms, energy check-ins, hydration logs and targets, treatment and ventilation records, lab results and reference ranges, journal notes, and breathing practice sessions.
• Apple Health context: data you authorize the app to read, which may include oxygen saturation, heart rate, resting heart rate, heart rate variability, respiratory rate, sleep, activity, workouts, and other supported Health data.
• Profile and preferences: your chosen display name, personal baseline, tracked categories, units, reminder settings, and app preferences. Local app progress, including streaks and Oxy customizations, is also stored.
• Location and environment: with permission, location is used to obtain locality, altitude, and weather context for your records.
• Oxy conversations and summaries: your prompts, conversation history, generated responses, and relevant context from your records and authorized Apple Health data.
• Support: your email address, message, and any attachments or other information you choose to send us.
• Diagnostics: crash and diagnostic information you choose to share through Apple’s system settings or with support. The current app does not include a separate third-party crash-reporting SDK.

2. How information is used

Information supports logging, timelines and trends, personal summaries, breathing practice records, reminders, and your app preferences. Information you send to support is used to respond to your request. Diagnostic information helps investigate problems and improve reliability.

Oxylittle does not sell your personal health data or use Apple Health data for advertising.

3. Apple Health and permissions

Oxylittle requests access through Apple’s permission system. You decide which data types it may read or write. Authorized readings provide context alongside your manual logs; the app itself does not measure blood oxygen or heart rate.

With write permission, manually logged oxygen and pulse readings can be saved to Apple Health. Edits and deletions of those readings can update or remove the corresponding samples written by Oxylittle. Readings from other apps and devices remain managed in Apple Health.

Authorized Health context can be included in Oxy requests as described in the next section. You can revoke permissions in Apple Health or iOS Settings. Revoking access stops future access but does not delete information already stored or previously transmitted.

4. Oxy, AI chat, and Google Gemini

Oxy uses the Google Gemini API to generate responses. Requests are sent directly from the app to Google. A request can include your message, conversation history, display name, personal baseline, recent health logs, lab values, treatment details, journal notes, hydration and breathing records, and summaries of authorized Apple Health data. Available locality, weather, and activity context may also be included.

AI requests contain more than the words you type into the chat box: the app assembles the relevant context for your conversation. Responses and conversations are saved locally for display in the app.

Google processes transmitted information under the terms applicable to the Gemini API project. Provider retention and use depend on the service configuration; deleting local records does not itself delete information already sent to Google. See Google’s Gemini API terms and Google’s Privacy Policy.

Oxy’s responses can be inaccurate or incomplete. Do not rely on them as medical advice or use them to make treatment or emergency decisions. Contact us if you have questions about AI data sharing or deletion.

5. Location and weather context

If you grant location permission, the app uses Apple’s location and geocoding services to obtain your location, locality, and altitude. Coordinates are sent to Open-Meteo to obtain weather conditions, temperature, and humidity. These can be attached to a reading as daily context.

Open-Meteo receives coordinates and the technical information involved in a network request, such as an IP address. See Open-Meteo’s terms and privacy information. You can revoke location access in iOS Settings.

6. When information is shared

• Apple: for permission-based Health access, location and device services, notifications, and any device backups or diagnostic sharing you enable.
• Google: for Oxy chat and AI summaries using the Gemini API, as described above.
• Open-Meteo: for weather context using location coordinates.
• Email providers: to deliver and store messages when you contact support.
• Legal requirements: information we hold may be disclosed when required by applicable law or valid legal process.

External providers may process information in countries other than your own under their applicable terms and privacy practices.

7. Storage, retention, and deletion

Health logs, settings, chat history, and generated summaries are stored locally on your device. The app does not provide its own cloud account or cloud synchronization service. Device-level backups may contain app data depending on your Apple settings.

Use in-app editing or deletion controls where available. Deleting the app removes its local app data; offloading an app is different and retains its data. Apple Health records and device backups may remain and are managed separately through Apple’s controls. Resetting onboarding does not erase your health log.

Information already sent to an external provider is subject to that provider’s retention practices. We retain support correspondence as needed to handle your request and meet applicable obligations. For access, correction, or deletion questions, email yohannesakhaile@novarch.lol. We can help with requests concerning information we hold, but cannot remotely access or erase records stored only on your device.

8. Your choices

• Grant or revoke individual Apple Health permissions in Apple Health or iOS Settings.
• Change location and notification permissions in iOS Settings.
• Use the available app controls to correct or delete records, or delete the app’s local data.
• Review your Apple backup and diagnostic-sharing settings.
• Do not include sensitive details in support emails unless they are necessary for the issue.
• Contact support about access, deletion, or AI data-sharing questions.

9. Children and intended audience

Oxylittle is designed for people organizing their own health records. If you believe a child has sent personal information to Novarch, contact us so we can help address it.

10. These web pages

The Oxylittle marketing, privacy, and support pages do not add analytics beacons, advertising pixels, newsletter signups, or contact forms. They request public app information and images to display current content. Our hosting providers process the technical requests needed to serve the pages and files.

11. Personal awareness, not medical care

Oxylittle is not a medical device and does not replace professional medical care. It is not intended for diagnosis, treatment, emergency use, or clinical monitoring. For health decisions, speak with a qualified professional. In an emergency, contact your local emergency services.

12. Changes to this policy

We may update this policy as the app or its data practices change. We will update the date at the top of this page. Please review it when considering new features or permissions.

13. Contact Novarch

For privacy questions, support requests, or help with your data, email yohannesakhaile@novarch.lol. You can also visit Oxylittle Support.