SunCoach

Privacy Policy

Last updated: 2026-10-04

This Privacy Policy explains what personal data SunCoach collects, why we process it, who else processes it on our behalf, and what rights you have. We've tried to write it in plain language. If anything is unclear, email us at privacy@suncoach.app.

1. Who is responsible (Data Controller)

The data controller for SunCoach is:

Gökhan Kaya
Untere Vogelsangstrasse 205
8400 Winterthur
Switzerland
Email: privacy@suncoach.app

SunCoach is operated as a sole proprietorship. We do not have a separate Data Protection Officer; please direct all privacy questions to the email above.

2. Scope of this Policy

This Policy applies to the SunCoach mobile app (iOS and Android), the web app at app.suncoach.app, and the marketing website at suncoach.app. The primary legal framework is the Swiss Federal Act on Data Protection (revFADP / nFADP). For users in the European Economic Area, the EU General Data Protection Regulation (GDPR) applies in parallel.

3. What personal data we collect

3.1 Account data

When you create an account, we collect your email address, a display name, and a password (stored only as a salted hash by our authentication provider, Supabase Auth — we never see your plaintext password). We also store your selected language preference.

3.2 Profile and goal data

To personalize nutrition recommendations, you may provide your age, gender, height, weight, activity level, dietary preferences, and nutrition goals (e.g. target calories and macronutrients). Providing this data is optional but the app's core features depend on it. You can also tell us that your targets were set by your own doctor or dietitian, in which case the app stops suggesting changes to them. If you are under 18, we use your age to make sure the app never plans a weight-loss deficit for you.

3.3 Meal log data

When you log a meal, we store the meal name, its ingredients, the estimated macronutrients, and the timestamp.

If you log by photo or voice, that capture is sent for analysis (see section 3.8) and is not kept afterwards. We do not store your meal photos or voice recordings on our servers, and they are not visible to your coach — only the resulting text description and nutrition estimate are. The one exception is a saved ingredient, which keeps a small thumbnail if you explicitly ask it to; see section 3.11.

If you capture a meal while offline, the photo or recording is held on your own device until the app can analyse it, and is deleted from the device once it has.

3.4 Health data (optional)

With your explicit consent, SunCoach can read selected data from Apple HealthKit (iOS) or Android Health Connect, such as steps, sleep duration, body weight, workouts, and active energy. This consent is requested separately and can be revoked at any time in your device settings. Health data is treated as sensitive personal data (Art. 5 revFADP / Art. 9 GDPR) and is processed only to display your progress, adjust recommendations, and — if you enable habits — automatically evaluate your daily habits (see section 3.9).

3.5 Coach-client relationship data

SunCoach supports a two-sided model: clients can link to a coach to receive guidance. If you link to a coach, your coach can view your profile, goals, meal logs, and progress data for the duration of the link. That includes whether you are pregnant or breastfeeding, if you have told the app (section 3.13). Your coach can also see the coaching records described in section 3.17, and reports or plans you choose to share (section 3.16). Your check history, Coach AI conversations and Skin & personal care profile are not shared with your coach. Your saved ingredients and their photos are not shared with your coach. You can unlink at any time. Coaches are independent users and are not employed by SunCoach; we act as a technical service provider that makes data-sharing possible. When you link, this counts as your explicit consent to share that data with your chosen coach.

A coach can also invite you with a link. Each link carries a single-use code that expires after 14 days. We store the code, the coach who made it, when it was made and when it expires, and — once it is used — which account used it and when. Opening the link shows you the coach's name; nothing is shared until you confirm the connection in the app.

3.6 Subscription data

Subscriptions are processed by RevenueCat, which in turn uses the Apple App Store or Google Play Store for payment. We receive an anonymized subscription identifier, your subscription tier, and the active/expiring status. We never see your credit card or bank details; those are handled exclusively by Apple or Google.

3.7 Technical and device data

For operational and security purposes, we automatically collect the device type, operating system version, app version, approximate language / region, and timestamps of certain actions (e.g. login). On Android, we do not collect the advertising ID.

If you allow notifications, we also store a push token — an address issued by Apple or Google that identifies your app installation so notifications can reach it. We delete it when you sign out, and it is replaced automatically if you reinstall the app.

3.8 AI processing

Several features send content to Google's Gemini API through our secure backend (a Supabase Edge Function called gemini_handler) and show you the answer: logging a meal by photo, voice or text, or a workout by describing it; Check something for food and skincare products (section 3.14); Coach AI and Coach calls (section 3.15); Nutrient Check reports, meal plans, grocery lists and your personal guide (section 3.16); target proposals; and, for coaches, session briefs, notebook transcription and picture cards (section 3.17). Each request carries only what that feature needs: the thing being analysed, and the profile context that makes the answer personal — depending on the feature, your age and sex, height, weight, goals, activity level, daily targets, recent meals and weigh-ins, today's logged totals, training and habit data, dietary restrictions and allergies, pregnancy or breastfeeding (section 3.13), whether a health professional set your targets, notes your coach has saved for you, and, for skincare checks, your Skin & personal care profile.

Some answers address you by name, so a few features — target proposals and a coach's session brief, for example — include your first name. When a coach asks the AI about a client, the client's name or the nickname the coach uses for them can be included. We never send your email address or other contact details to Gemini. Messages between you and your coach are never used as AI context: a message is sent to Gemini only when someone taps Translate on it, or asks to translate their own draft before sending it. According to Google's terms for the paid Gemini API, your inputs are not used to train their models.

One translation happens without anyone tapping. When your coach's app is set to a different language from yours and they open your history, the text in it is translated into their language with Gemini so they can read it: your meal and workout names, the Coach AI notes on them, and the goals and notes in your profile. Only those texts are sent — not your name or any other profile details — and the translation is shown on your coach's screen, not saved. Your coach can turn it off for you with Show original.

3.9 Habit tracking data

If you use the habits feature, we store which habits you (or your coach) have selected and a daily completion log for each habit (done / not done / pending, plus whether it was checked off manually or automatically). Automatic evaluation runs on your device using data SunCoach already holds — your meal logs and, if you granted access, your synced health data (e.g. sleep or workouts). Habit results are visible to you and, if you are linked, to your coach.

3.10 Message notifications

When your coach or client sends you a message, we ask Apple or Google to deliver a notification to your device, so you see it without having to open the app. To do that, the sender's name and — unless you turn previews off — the text of the message pass through their notification services, and may appear on your lock screen.

You can switch previews off under Settings → Message previews, in which case the notification only tells you that a new message has arrived, and the message text never leaves our servers. You can also turn notifications off entirely in your device settings. Doing either does not affect the messages themselves, which are always visible in the app.

3.11 Saved ingredients and their photos

After the app estimates an ingredient for you, you can choose to save it so you can add it to future meals without scanning it again. If you do, we store the ingredient's name, its nutrition estimate, and — when you scanned it from a photo — a small thumbnail image taken from that scan, so the ingredient is easy to recognise in a list.

Apart from the pages in a coach's notebook (section 3.17), this is the only image SunCoach retains. Saving is optional and switched off by default: nothing is stored unless you turn it on for that ingredient. The thumbnail is a reduced-size copy (roughly 160 pixels wide), not your original photo, and it is kept in a private storage bucket that only your account can read. It is not visible to your coach. A copy is also cached on your own device so the list works offline.

You can delete a saved ingredient at any time from the ingredient list in the app; this removes its stored image as well. Deleting your account removes all of them. Meals you already logged are unaffected — they keep the nutrition figures, not the picture.

3.12 Barcode scanning

Instead of photographing a package, you can point the camera at the barcode on it. The barcode is read on your own device: the camera image is decoded on the phone itself and is never uploaded, never stored, and never sent to us or to anyone else.

To find out which product the barcode belongs to, the app then sends the barcode number alone to Open Food Facts — a free, open product database published by a French non-profit association of the same name, on servers in France. If the barcode turns out not to be food, the same request is made to its sister database Open Beauty Facts. The request contains the barcode digits, a header naming the app ("SunCoach" and this website, which their terms of use require), and your device's IP address, as every web request does. It contains no account identifier, no name, no email address, and nothing from your profile, your goals or your diary, so there is nothing in it that would let them connect the lookup to you as a SunCoach user.

Open Food Facts is not one of our sub-processors. They act on their own behalf rather than on our instructions, we have no data processing agreement with them, and we receive nothing back from them about you. What they do with an incoming request is governed by their own privacy policy.

The product record that comes back is cached on your device, so scanning the same product a second time makes no request at all and works with no connection. We do not keep any record of what you scan: a scanned product only reaches our servers if you go on to log it as a meal, and at that point it is an ordinary meal entry (section 3.3).

None of this happens unless you use the barcode button — logging by photo, voice or text never contacts Open Food Facts. If you scan a barcode inside Check something, the product details that come back are then sent to Gemini to produce the personalised verdict, as described in section 3.8.

3.13 Pregnancy and breastfeeding

You can tell SunCoach that you are pregnant or breastfeeding — during setup, under Body & goals, or in the Skin & personal care settings — and, if you like, your due date or your baby's date of birth. All of this is optional. It is health data, treated as sensitive personal data (Art. 5 revFADP / Art. 9 GDPR), and we process it only because you choose to enter it. You can take that back at any time by choosing Neither, which deletes both the stage and the date. We also record when you last changed it, so the app can tell whether your targets were set before or after.

We use it to:

If you are linked to a coach, your coach can see it, because it changes what a sensible target is. It is the one item on the Skin & personal care page your coach can see; the rest of that page stays private. We use it for nothing else, and never share it with advertisers.

3.14 Check something (food and skincare)

Check something gives you a verdict on a food, a meal you logged, or a skincare or personal-care product, from a photo, a scanned barcode (section 3.12) or a description. The photo is analysed and not kept; we save the answer — the product name, the verdict and its explanation — so you can find it again in your history. Your check history is visible only to you, not to your coach.

For skincare checks you can fill in a Skin & personal care profile: ingredients you react to or would rather avoid, short descriptions of your skin or hair (for example "sensitive skin"), and ingredients in your own words. It is used only to personalise these checks, is sent to Gemini with a skincare check (section 3.8), and is not visible to your coach — the one exception being pregnancy or breastfeeding, which lives on your profile (section 3.13). Your dietary restrictions and allergies are used the same way for food checks; those are visible to your coach, because they matter for the meals your coach plans.

3.15 Coach AI and Coach calls

Coach AI lets you ask questions about your meals and nutrition in writing. Your conversation is stored in your account so you can come back to it, and it is visible only to you — your coach cannot read it.

A Coach call is a spoken conversation with the same AI. When you start one, our server checks that you have minutes left and asks Google for a short-lived access token, passing along the profile context described in section 3.8. Your phone then streams your voice directly to Google's Gemini Live API, and the AI's voice streams back; the audio does not pass through our servers and we do not record it. When a client's call ends, a written transcript of what was said is saved into their Coach AI conversation, visible only to them. A coach's calls are not transcribed or saved. We record when each call started and how long it lasted, to count it against the weekly time allowance.

During a coach's call, the AI can look up that coach's own clients — their names (and any nickname the coach gave them), targets, recent meals and weigh-ins — to answer the coach's questions. It cannot reach anyone else's clients.

3.16 Nutrient Check, meal plans and guides

Nutrient Check estimates vitamins and minerals from the meals you log and saves a report you can ask questions about. Meal plans — with their grocery lists and the conversation you use to adjust them — and your personal guide are generated from your profile and targets. All of these are stored in your account. A report or meal plan you create is shared with your coach only if you choose to share it; one your coach creates for you is visible to both of you. Your personal guide is visible to you and your coach.

3.17 Coaching records

When you work with a coach, SunCoach also stores the messages you exchange (visible to both of you); the check-ins you fill in — for example energy, hunger and stress levels with an optional note (visible to your coach); scheduled sessions and planned training; and your coach's emoji reactions to your meals.

Your coach can keep notes about you, including notebook pages with drawings or photos of handwritten notes, which may be transcribed with AI (section 3.8). A coach can also have the AI turn their own words or drawing into a picture card; only what the coach wrote or drew is sent. These images are kept in a private storage area. Notes stay private to your coach unless they choose to share one with you. A coach can also generate an AI session brief — a summary of your recent meals, weigh-ins, check-ins and habits, prepared before a session — which only the coach can see, and can give you a nickname or pin you in their own client list, which only they see.

3.18 Usage and safety logs

To enforce the daily limits on AI features, we log which AI feature was used and when — not what was asked. If you report an AI answer as wrong or inappropriate, we store the answer, your reason and where it appeared, so we can review it; only we can read these reports. And to stop invite codes being guessed, we record when an invite code is entered that doesn't match — a client's code entered by a coach, or a coach's invite code entered by a client (the account that entered it, and the time).

3.19 Your consent, and the record of it

When you create a client account, we ask you to tick a box agreeing that SunCoach may process the health information you enter — such as your weight, meals, allergies or a pregnancy — as described in this policy. That is the explicit consent referred to in section 4. We keep a record of it: your account, which version of this policy you agreed to, and when. The record exists so that we can show you agreed (Art. 7(1) GDPR); it is used for nothing else, only we can see it, and it cannot be changed afterwards. You can withdraw your consent at any time, with future effect, by deleting your account or by writing to us (section 13).

4. Why we process your data (purposes and legal bases)

Purpose Legal basis (GDPR / revFADP)
Provide the SunCoach service (account, meal logging, sync) Performance of contract (Art. 6(1)(b) GDPR / Art. 31 revFADP)
Process subscription payments Performance of contract
Send service-related notifications (e.g. password reset) Performance of contract
Analyse health data, and the meal photos or voice recordings you capture Your explicit consent (Art. 9(2)(a) GDPR / Art. 6 revFADP)
Use the pregnancy or breastfeeding details you give us to set your targets and tailor the app's advice Your explicit consent (Art. 9(2)(a) GDPR / Art. 6 revFADP)
Store a saved ingredient and its thumbnail, when you ask us to Your consent (Art. 6(1)(a) GDPR / Art. 6 revFADP)
AI features you choose to use (checks, Coach AI and Coach calls, reports, plans and guides) Performance of contract; where health data is involved, your explicit consent (Art. 9(2)(a) GDPR / Art. 6 revFADP)
Look up a product you chose to scan by barcode Performance of contract (Art. 6(1)(b) GDPR / Art. 31 revFADP)
Keep a record of your consent to process health information, so we can show it was given Legal obligation (Art. 6(1)(c) together with Art. 7(1) GDPR)
Create and check a coach's invite links Performance of contract (Art. 6(1)(b) GDPR / Art. 31 revFADP)
Share data with a coach you link to Your explicit consent
Send marketing emails (only if you opt in) Your consent
Security, abuse prevention and debugging, including daily AI limits and stopping invite codes being guessed Legitimate interest (Art. 6(1)(f) GDPR)
Comply with legal obligations (e.g. tax records) Legal obligation (Art. 6(1)(c) GDPR)

5. Who we share data with (sub-processors)

We use the following service providers to operate SunCoach. Each provider is bound by a Data Processing Agreement and processes your data only on our instructions.

Open Food Facts (Association Open Food Facts, 21 rue des Iles, 94100 Saint-Maur-des-Fossés, France) is deliberately not in the list above. When you scan a barcode we send them the barcode number so they can tell us what the product is, but they are an independent third party acting on their own behalf — not a processor acting on our instructions — so there is no data processing agreement between us. Section 3.12 sets out exactly what is and is not sent. world.openfoodfacts.org/privacy

We do not sell your personal data, and we do not share it with advertising networks.

6. International data transfers

Some sub-processors listed above are based in the United States. When personal data is transferred outside Switzerland or the EEA, we rely on Standard Contractual Clauses (SCCs) and, where applicable, the EU-US Data Privacy Framework. Where offered by a provider, we choose EU data residency.

7. How long we keep your data

You can delete your account at any time — see Delete your account.

8. Your rights

Under Swiss revFADP and the EU GDPR, you have the right to:

To exercise these rights, email privacy@suncoach.app from the address linked to your account. We will respond within 30 days.

9. Children

SunCoach is not directed at children under 16. The app asks for your age and does not accept one under 16. We do not knowingly collect data from children under 16 without verifiable parental consent. If you believe a child has provided us with personal data, please contact us and we will delete it.

10. Security

We protect your data using industry-standard measures including TLS encryption in transit, encryption at rest on our hosting infrastructure, Row Level Security policies in our database to ensure you can only access your own data, and authentication via salted password hashes. No system is perfectly secure; if you become aware of a security issue, please email legal@suncoach.app.

11. Cookies and tracking

The marketing website (suncoach.app) does not use tracking cookies or analytics that identify you personally. The web app at app.suncoach.app uses essential cookies / local storage to keep you logged in. We do not use third-party advertising or behavioural tracking.

12. Changes to this Policy

We may update this Policy from time to time. When we make material changes, we'll tell you in the app. The "Last updated" date at the top reflects the most recent revision.

13. Contact

Questions about this Policy or your data? Email privacy@suncoach.app or write to the postal address above.