Privacy Policy

1. Quick Summary

The core of Diabetes Tracker: BP Monitor works locally on your device. However, the current app also offers optional account, backup, purchase, weather, and AI features that rely on third-party services. This policy describes those flows explicitly so the app's published privacy disclosures can match the real behavior of the product.

2. Data We Process

2.1 Data stored locally on your device

The app stores the following data in its local database or local device storage:

• Blood sugar readings, units, meal context, timestamps, and notes.
• Blood pressure readings, pulse, timestamps, and notes.
• Heart rate entries, including manual entries and camera-based measurements.
• Cholesterol, weight, hydration, and step records.
• Medication schedules, reminder times, and medication adherence history.
• Assessment answers, assessment results, targets, units, onboarding answers, and local settings.
• Display name and app preferences stored with SharedPreferences.
• A guest session ID or local device identifier used to separate data before account creation.

2.2 Camera-based heart rate measurement

If you use the heart rate feature, the app requests camera access and processes live camera frames on your device to estimate heart rate from fingertip color changes. The app does not intentionally upload or store your camera frames, photos, or videos on our servers.

2.3 Account and profile data

If you create an account, sign in, reset your password, or sign in with Apple, we may process:

• Email address.
• Name you enter, or name Apple shares on first sign-in.
• Supabase user ID and authentication session data.
• Profile metadata such as avatar URL if you set one.
• Subscription status, tier, and subscription expiration date.

If you choose Sign in with Apple, Apple may provide a relay email address instead of your direct email, depending on your Apple account settings.

2.4 Cloud backup data

If you are a signed-in Premium user and use cloud backup, the app may upload JSON backup files that can include your health records and medication-related data, including blood sugar, blood pressure, heart rate, cholesterol, weight, hydration, steps, medications, and medication adherence.

The app currently keeps up to two backup versions in remote storage for your account: a latest backup and a previous backup.

2.5 AI feature data

If you use AI features such as wellness insights, trend analysis, weekly digest, or "Ask Your Data" chat, the app may send selected health summaries, recent readings, timestamps or dates, trends, calculated statistics, your prompts, and locale/language context to Google Gemini to generate a response.

We do not intentionally store AI prompts or AI outputs on our own servers as part of this feature. However, the third-party AI provider may process submitted content under its own terms and privacy practices.

2.6 Purchase and subscription data

If you make a subscription purchase or restore a purchase, the app may process:

• Product ID and purchase status.
• Receipt and verification data supplied by Apple or Google.
• Transaction date and verification metadata.
• Result of server-side validation and subscription entitlement state.

Payment card data is processed by Apple or Google, not by us directly.

2.7 Weather feature data

The app does not currently request Apple's GPS-based location permission. To display weather, it uses your network IP address with an IP-based location provider to estimate approximate location and then requests weather data for those coordinates.

This means weather requests may disclose your IP address to the location provider and approximate latitude/longitude to the weather provider. We do not use that flow for advertising or cross-app tracking.

2.8 Notification and export data

• If you enable notifications, reminder content such as medication names or health reminder text may appear on your device lock screen depending on your device settings.
• If you export, copy, print, or share reports, CSV files, PDFs, clipboard content, or health summaries, the data you choose to share leaves the app and is then governed by the destination app, email provider, printer, clipboard manager, or sharing channel you choose.

3. How We Use Data

• To provide local tracking, charts, reminders, reports, settings, and account functionality.
• To authenticate users, manage profiles, and migrate guest data to an account.
• To create, store, restore, and manage optional cloud backups for eligible users.
• To validate purchases and manage Premium entitlements.
• To generate AI-powered summaries, trend observations, weekly digests, and health data chat responses.
• To display weather information based on approximate IP-derived location.
• To comply with legal obligations, enforce our terms, prevent abuse, and secure the service.

4. When Data Leaves Your Device and Third Parties Involved

Apple requires privacy policies to clearly identify third parties that receive user data and how that data is used. In this app, off-device processing may involve the following service providers and platforms:

We share only the data reasonably needed for the feature you use, and we expect service providers that receive user data for app functionality to protect it under their own published privacy commitments and applicable contractual obligations.

4.1 Supabase

Supabase is used for authentication, profile records, remote guest-data migration, cloud backup storage, and purchase receipt validation infrastructure. Supabase may process account identifiers, profile data, backup files, and purchase verification requests needed to operate those features.

4.2 Apple

Apple may process sign-in data when you use Sign in with Apple and purchase data when you subscribe or restore purchases through the App Store.

4.3 Google Gemini

Google Gemini is used for optional AI features. If you use those features, selected health summaries, readings, prompts, and response context may be sent to Google to generate AI output.

4.4 Weather providers

The app currently uses IPinfo to estimate approximate location from your IP address and Open-Meteo to fetch weather conditions for those coordinates.

4.5 No sale, no ad network, no app tracking

We do not sell your personal data. The app does not currently include a third-party advertising SDK and does not use app tracking for cross-app or cross-website advertising.

5. Your Privacy Choices

5.1 Use the app without an account

Core tracking features can be used in guest mode. Account creation is optional unless you want features that require sign-in, such as remote backup or account-based recovery.

5.2 Control permissions

• Camera permission can be granted or revoked in iOS Settings.
• Notification permission can be granted or revoked in iOS Settings.
• The app does not request Apple's GPS location permission for weather.

5.3 Control cloud backup

You can disable auto-backup in the app. You can also manually delete available backup files from the app's backup and restore area.

5.4 Delete local data, exports, and account data

• You can delete entries inside the app.
• Deleting the app removes local app data stored on the device, subject to device and OS behavior.
• The app includes an account deletion flow that removes associated app data such as profile records and remote app data we control.

The current in-app deletion flow removes app-associated remote data, but a minimal authentication record may remain with the authentication provider unless and until separately removed through backend or provider-level processes.

5.5 AI features are optional

If you do not want health data sent to Google Gemini, do not use AI insights, AI digest, or AI chat features.

5.6 Contact us

If you want help with deletion, access, correction, or privacy questions, contact us at alinomi1@gmail.com.

6. Data Retention

6.1 Local data

Local records remain on your device until you delete them, reset your device, restore over them, or remove the app.

6.2 Account and profile data

Account and profile data may be retained for as long as your account remains active and for a limited period afterward where needed for security, legal compliance, dispute resolution, or fraud prevention.

6.3 Cloud backup data

Remote backup files remain in cloud storage until they are replaced, deleted, or removed as part of an account/data deletion workflow.

6.4 Purchase verification data

Purchase providers retain their own transaction records. Our validation infrastructure may process and retain limited operational metadata as needed for entitlement enforcement, troubleshooting, and security.

6.5 AI and weather requests

We do not intentionally store AI prompts, AI outputs, or weather request payloads on our own servers as part of the core app experience, but the third-party providers that receive those requests may keep logs or process data under their own policies.

7. Security

We use reasonable technical and organizational measures designed to protect data we control. Local app data is stored inside the app's sandbox on your device. Remote requests for account, backup, weather, AI, and purchase validation use network transport to external services. No system or service is perfectly secure, and you are responsible for using a device passcode, keeping your device updated, and choosing how you share exported health information.

This app is not offered as a HIPAA-covered service unless we explicitly agree otherwise in writing.

8. International Processing

If you use cloud, AI, purchase, or weather features, your data may be processed in countries other than your own by the third-party services that support those features. By using those features, you understand that cross-border processing may occur.

9. Children's Privacy

This app is not directed to children under 13. We do not knowingly collect personal data from children under 13 through the remote services we control. If you believe a child has provided us data in connection with an account or support request, contact us and we will review the request.

10. Medical and Safety Disclaimer

11. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date, and for material changes we may also present notice inside the app or through another appropriate channel.