Privacy Policy

1. Who we are

"DiaFitus", "we", "us" and "our" means the team that operates the DiaFitus iPhone and Apple Watch app (the "App") and the website diafitus.com (the "Website"). We are the controller of the personal data described in this policy. You can reach us at support@diafitus.com.

DiaFitus offers general fitness and nutrition guidance for people living with diabetes. It is not a medical device and does not provide medical advice, diagnosis or treatment.

2. What we collect

You choose what to enter, connect and allow. The table lists everything the App can collect, why, and whether it leaves your device.

Category	What it includes	Where it goes
Account	A DiaFitus account is created with Sign in with Apple. We receive a unique user ID, your email address (or Apple's private relay address if you choose to hide it) and, only the first time you sign in and only if you allow it, your name.	Our servers (Supabase)
Profile and health information you enter	Diabetes type, diabetes medication type (for example insulin, metformin, GLP-1), health conditions (for example neuropathy, retinopathy, heart or kidney disease, high blood pressure, joint pain), goals, fitness level, where and how often you train, session length, preferred glucose unit and target glucose range.	On your device and, in your account backup, on our servers. If sharing is on, your training profile is visible to our coaching team (see below).
Health and fitness logs	Blood glucose entries, insulin entries, weight, workouts (exercises, sets, reps, weights, duration, calories, heart rate, glucose before and after, how you felt, notes), logged meals and their nutrition (carbs, fibre, protein, fat, calories), journal notes, custom exercises and programs, and app settings such as glucose alerts.	On your device and, in your account backup, on our servers
Meal photos	Photos you attach to a logged meal. Photos you only scan for analysis are handled as described in section 5.	Your device and a private storage area on our servers that only your account can access
Apple Health data (with your permission)	Read: blood glucose, steps, active energy, exercise minutes, body weight, heart rate, workouts and workout routes. Written: workouts, blood glucose, weight, active energy, nutrition (carbohydrates, calories, protein, fat, fibre) and insulin delivery.	Stays in Apple Health on your device. Workout summaries you complete or import into DiaFitus become part of your backup. Steps, activity totals and CGM readings are shown on your device and are not uploaded.
CGM readings (optional)	If you connect FreeStyle Libre (LibreLinkUp) or Dexcom (Dexcom Share), the App fetches your readings directly from Abbott or Dexcom and stores them on your device. Your CGM login is stored only in your iPhone's Keychain.	Your device only. Readings and CGM passwords are not sent to our servers.
Camera and photos	The camera is used when you scan a meal or nutrition label. Photos are read only for pictures you select. If you choose to save a workout summary image, the App requests add-only access to your photo library; it cannot view your library.	Your device; scan photos are sent for analysis as described in section 5
Push notification data	If you allow notifications: an Apple device token, whether the build is test or production, your diabetes type (so we can send relevant messages), your time zone and the App version. Linked to your account when you are signed in.	Our servers; delivered through Apple Push Notification service
Coach messages and check-ins	Messages you receive, your answers to check-in forms, and private notes our coaching team may write about your coaching.	Our servers
Support and feedback	The message and type you send under Settings → Help & feedback, your email, the App version and build, device model and iOS version (device details are optional and can be switched off before sending), plus any email you send us.	Our servers and email
Technical data	Our hosting provider receives your IP address and request metadata whenever the App contacts our servers. We do not use analytics, crash-reporting or advertising SDKs.	Our servers (transient security and operational logs)

What we do not collect: your precise location, contacts, advertising identifier, browsing history or any data for advertising. Workout routes are read from Apple Health on your device to draw a map; they leave your device only if you choose to post that workout to Strava.

3. Apple Health and health data

• We access Apple Health data only after you grant permission, and you can change that any time in Settings → Privacy & Security → Health → DiaFitus.
• Data from Apple Health is used only to provide health and fitness features to you in the App.
• We do not use Apple Health data for advertising or marketing, and we do not sell it or disclose it to data brokers, advertising platforms or information resellers.
• We do not store Apple Health data in iCloud.
• The training profile you share with our coaches is limited to the fields listed above. You can turn this off in Settings → Coach account; then we see only your name and email. Your glucose, insulin, meal and workout logs are not displayed in our admin tools, and the backup is protected by database access rules so that only your own account can read it.

4. How we use information

• To provide the App: create and sync your account, build your personal plan, run workouts, show glucose and progress, restore your data on a new phone.
• Safety features: glucose checks before and after workouts, low/high alerts, delayed-low reminders and condition-specific exercise warnings.
• Coaching and communication: send coach messages, personal programs, check-in forms and notifications you have allowed.
• Support: answer questions, investigate bugs and reply to feedback.
• Security and integrity: keep the service secure and prevent abuse.
• Legal compliance.

We do not use your information for advertising, we do not build advertising profiles, and we do not use it to train AI models.

5. AI meal scanner

When you scan a meal or nutrition label, the photo (and any note you type, such as a portion size) is sent over an encrypted connection to a function on our servers, which forwards it to Google's Gemini API to estimate carbohydrates, fibre, protein, fat and calories. The result comes back to you to review and edit. A text-only request (for example, to break a recipe into ingredients) works the same way.

• We do not store scan photos or the AI's reply on that path; they exist only for the duration of the request.
• We use Google's paid Gemini API, under which Google states that submitted content is not used to improve its products or train its models. Google may process requests in the United States and other countries.
• Only the photo and optional note are sent; your name, email and account ID are not.
• If you save the meal with its photo, that saved copy is part of your account backup (section 2).
• AI estimates can be inaccurate. Never rely on them alone to calculate an insulin dose.

6. Connections you control

• FreeStyle Libre (LibreLinkUp) and Dexcom (Share): you sign in with your own LibreLinkUp or Dexcom credentials. They are kept in your iPhone's Keychain and sent only to Abbott (LibreView) or Dexcom to download your readings. They never pass through our servers. Their handling of your data is governed by their own privacy policies. You can disconnect in Settings at any time.
• Strava (optional): if you connect Strava and post a workout, we send Strava the workout you chose (title, time, duration, exercises, sets and reps, muscles trained, heart rate, before/after glucose in the description, and for outdoor activities the route and distance, plus an image). Strava's privacy policy applies to that data. You can disconnect at any time, which also revokes access.
• Apple Watch: the watch app sends workout and heart-rate data to your iPhone and Apple Health.
• Sharing images: if you share a workout image via the iOS share sheet, it goes to the app you choose.

7. Who we share data with

We share personal data only with service providers who process it on our behalf, and only as needed to run the App:

Provider	Purpose	Data
Supabase, Inc.	Hosting, database, authentication, file storage and server functions	Account, profile, backup, photos, messages, feedback, push tokens
Apple Inc.	Sign in with Apple, push notifications (APNs), App Store, HealthKit on your device	Account identifier, push token
Google LLC (Gemini API)	Meal and label analysis	Photo and optional note you submit for a scan
Hostinger	Hosting for this Website	Standard web server logs
Strava, Abbott, Dexcom	Only if you connect them (section 6)	As described in section 6

We may also disclose information if required by law or valid legal process, to protect the rights, safety and security of our users or the public, or in connection with a merger or sale of the business (in which case we will ensure this policy's protections continue to apply or give you notice and a choice). We do not sell personal data and we do not share it for cross-context behavioural advertising.

8. Tracking and advertising

DiaFitus does not track you. We do not use third-party advertising or analytics SDKs, we do not access your advertising identifier (IDFA), and we do not combine your data with other companies' data for advertising or share it with data brokers. For that reason the App does not show the App Tracking Transparency prompt. The App's Privacy Manifest declares no tracking.

9. Legal bases (EU/UK GDPR)

• Contract (Art. 6(1)(b)): to provide the App and your account.
• Explicit consent (Art. 9(2)(a)): for health data. We ask for your consent in the App when you enter health information, grant Apple Health access or connect a CGM. You can withdraw it any time by deleting the data, revoking permissions or deleting your account. Withdrawal does not affect earlier processing, but the related features will stop working.
• Legitimate interests (Art. 6(1)(f)): security, abuse prevention, support and improving reliability, balanced against your rights.
• Legal obligation (Art. 6(1)(c)): where the law requires us to keep or disclose information.

10. International transfers

Our providers may process data outside your country, including in the United States. When personal data from the EEA, UK or Switzerland is transferred, we rely on safeguards such as the European Commission's Standard Contractual Clauses and, where available, the EU-US Data Privacy Framework.

11. Retention and deletion

• Account data and backups are kept for as long as your account exists.
• Deleting your account: open Settings → Coach account → Delete account. This permanently deletes your account, profile, backup (including meal photos), personal programs, messages, check-in answers, coach notes, feedback and push tokens. Copies in our providers' routine backups are overwritten on their normal cycle.
• You can also delete individual logs inside the App, and data you have saved to Apple Health can be removed in the Health app.
• If you cannot access the App, email support@diafitus.com from your account email and we will delete the account. See how to delete your account.
• Support emails are kept as long as needed to help you and meet legal obligations.

12. Your rights and choices

Depending on where you live, you may have the right to access, correct, delete or export your personal data, to restrict or object to processing, to withdraw consent, and to lodge a complaint with your local data protection authority. Most of these you can do yourself in the App (edit your profile and logs, delete data, delete your account, change Apple Health and notification permissions). For anything else, email support@diafitus.com. We will respond within 30 days and may need to verify your identity.

13. US state privacy rights

Residents of California, Colorado, Connecticut, Virginia, Washington, Nevada and other states may have rights to know, access, correct, delete and port their data, and to opt out of sale, sharing for targeted advertising and profiling. We do not sell personal information, we do not share it for targeted advertising, and we use sensitive and consumer health data only to provide the services you request. We will not discriminate against you for exercising your rights. To exercise them, contact support@diafitus.com. If we decline a request you may appeal by replying to our response.

14. Children

DiaFitus is intended for adults. It is not directed to children under 16, and we do not knowingly collect personal data from them. If you believe a child has given us data, contact us and we will delete it. Parents or guardians of younger people with diabetes should use the App only together with their care team.

15. Security

All connections use encryption in transit (HTTPS/TLS). Backups and photos are protected by per-user access rules, so one account cannot read another's data. CGM passwords and sign-in tokens are stored in the iOS Keychain. No system is perfectly secure, so please also protect your device with a passcode.

16. This website

diafitus.com is a static information site and blog. It does not use cookies, analytics, advertising or third-party scripts or fonts. Our hosting provider keeps standard server logs (such as IP address, time and requested page) for security and operation. If you email us, we use your address to reply.

17. Changes to this policy

We may update this policy as the App changes. We will post the new version here with a new date and, for material changes, tell you in the App before they take effect.

18. Contact us

Questions, requests or complaints: support@diafitus.com.

Appendix: Apple App Privacy summary

This mirrors our App Store "App Privacy" disclosure. Nothing is used for tracking, and all data below is linked to your account for App Functionality only.

Apple data type	Examples in DiaFitus	Linked to you	Used to track you
Contact Info: Name, Email Address	Sign in with Apple name and email	Yes	No
Health & Fitness: Health	Diabetes type, medication, conditions, glucose, insulin, weight, heart rate	Yes	No
Health & Fitness: Fitness	Workouts, exercises, activity, goals	Yes	No
User Content: Photos, Other User Content, Customer Support	Meal photos, journal notes, custom programs, check-in answers, feedback	Yes	No
Identifiers: User ID, Device ID	Account ID, push notification token	Yes	No