VUNTA, the iPhone app
Privacy policy
Last updated: 15 November 2026
This is a translation. The German version is binding.
1. Controller
run4dev
Steinweg 4, 93059 Regensburg, Germany
Email: info@run4dev.com
This policy covers the iPhone app VUNTA, the account you have for it on our server, and the website vunta.de (section 16). Until November 2026 the app was called VYRO; this policy covers older versions with that name too. For the website www.run4dev.com, the run4dev privacy policy (in German) applies.
2. The essentials
- VUNTA is for people aged 16 and over. The app asks your age before you sign in. Under 16 it creates no account and sends nothing (section 3).
- Your data lives on your iPhone. A copy is backed up in your account on our server, so your training, food and plan are back after a reinstall or on a new iPhone. We back up health details only with your consent (section 6), and never for anyone under 18.
- To use the app, you sign in with Apple. There is no password. The app asks for your name only if you use the friends feature.
- Values from Apple Health, your calendar events and your gym's location and address stay on your iPhone. From 18, the coach sees how today's training follows your recovery, for example "light" (section 8).
- Two features use an AI from Anthropic: the coach chat and the meal photo scan. Both are optional and start only after you agree. Anthropic may also process the data in the USA (sections 8 and 18).
- When you scan the barcode of a package, our server asks Open Food Facts about the product. Open Food Facts learns only the barcode, not who you are (section 9).
- With the friends feature you find others by their username, write to them and share your training plan. Your friends see your name and username. The server deletes messages after 90 days. You can block and report anyone; reports are read only by our moderator, never by an AI (sections 10 and 11).
- With "Report a problem" in your profile you send us your message, the app's logs and a copy of your app data, only when you tap "Send". Health details are included only if you switch that on. The server deletes the report after 30 days (section 5).
- If you agree, the app sends its technical logs of the last 7 days to our server about once a day, without health details and without your own texts (section 15).
- The app and this website contain no ads. The app contains no analytics or tracking services. The website sets no cookies and counts visits only with our own statistics without cookies (section 16).
- With "Delete account" in the app you delete your account and your data on the server yourself (section 17).
3. 16 and over
VUNTA is for people aged 16 and over. Before you sign in, the app asks your age. If you are under 16, the app stops there: no account is created, and from that answer on the app sends nothing more to our server, not even a connection check. On the iPhone it keeps only when you answered, not your age: after 24 hours you can enter your age again. If you already had an account, you can still delete it with "Delete account", which deletes your account and your data on our server. What stays after that is in section 17. Otherwise it keeps your age on your iPhone and sends it along when you sign in (section 4).
You state your age yourself. We do not check it against an ID. So that a later change cannot get around the age limit, after sign-in our server remembers for your account the latest birth date your age statements allow (section 8, "Your age").
At 16 and 17, special safety rules apply in the app. Section 12 sums them up.
4. Sign in with Apple and your account
The app can only be used with an account. The account is created when you sign in with Apple. The app sends our server the identity token and the authorization code that Apple issues, and your age (section 3). Under 16, our server refuses the sign-in. Our server checks the token with Apple and exchanges the code with Apple for a refresh token. The app does not ask Apple for your name. Apple is based in the USA, see section 18.
For this we store in our database:
- the user identifier Apple assigns to you for this app,
- the email address Apple passes on (your own or an Apple relay address),
- when the account was created and when you last signed in,
- one session per sign-in: the random session key your iPhone gets from us at sign-in is stored only as a hash (SHA-256), with timestamps. A session ends 180 days after its last use, at the latest 365 days after sign-in,
- Apple's refresh token, encrypted. We need it to revoke the connection with Apple when you delete your account.
The legal basis is providing the app you want to use (Art. 6(1)(b) GDPR). Without sign-in we cannot provide the app.
If you stop using "Sign in with Apple" for this app in your Apple settings, Apple tells our server. We then sign you out everywhere and keep your data until you delete the account. If you delete your Apple account, Apple tells us that too, and we delete your account.
5. Backup and "Report a problem"
The app stores your data in a file on your iPhone. A copy goes to our server: after sign-in, shortly after changes and when you leave the app. The copy contains:
- your profile from setup (goal, sex, age, height, training days, experience) and the name of your gym,
- your training plan and your workouts with weights and reps,
- your meals and food entries,
- your history and your settings in the app.
Body weight, diet, how you felt after training, your notes on exercises and the other health details in section 6 are in the copy only with your consent.
The app compresses the copy and the server stores it encrypted as one package. It does not analyse the content. You get the copy back when you reinstall the app, sign in on a new iPhone, or another iPhone with your account has changed something. If two versions conflict, the newer one wins and the app keeps the other on the iPhone as a backup.
Not in the copy: values the app reads from Apple Health or your calendar, the links to Apple Health and the calendar, the coach notification settings, your gym's location and address (only its name is backed up), the coach chat, photos and voice recordings. Your friends, your messages to friends and shared plans are on our server anyway (section 10).
The legal basis is providing the app (Art. 6(1)(b) GDPR). For health details, see section 6.
"Report a problem". When you choose "Report a problem" in the app's profile and tap "Send", the app sends our server: your message, your age for the server's age check (section 8), the app's logs from up to 7 days, a copy of your app data as the backup holds it, and from the iPhone only the app version, iOS version, device model, language, time zone and the time of sending, whether calendar and Apple Health are connected, and today's training times from the calendar (times only, no events). The report is linked to your account.
We send your message as you write it; the app does not check it. Do not put health details in it if you do not want to. The logs contain technical events of the app, such as errors, exercises with weight and reps, and foods as an ID number with an amount, but no chat messages, no sign-in data, no food names and no text you type yourself.
Health details the app adds itself, including today's recovery from Apple Health, are included only if you switch on "Include health details" on the "Report a problem" screen. It starts switched off. The app shows it only if you agreed to back up your health details (section 6) and are at least 18.
Every report also contains a yes or no on whether you are at least 18 according to your age and your safety check in the app, even with the switch off. We need this to find faults, because the app behaves differently for people under 18.
We use the report only to find and fix the fault. Only we read the report; it goes to no AI. The server stores its content encrypted and deletes it after 30 days, at once with your account; in the backups (section 13) it may stay as long as described there. A report we download to find a fault is deleted there after 30 days at the latest too.
The legal basis is your request for help with the app (Art. 6(1)(b) GDPR), and for health details also your explicit consent (Art. 9(2)(a) GDPR), which you give by switching on the switch and tapping "Send".
6. Health details and your consent
Some things you enter in the app are health data (Art. 9 GDPR). They include:
- the answers from the safety check at setup (eating disorder, pregnancy, insulin, under 18),
- your body weight and all weigh-ins,
- your diet, for example lactose-free or no pork,
- what you note about the day: pain, illness, an urgent symptom, a short or bad night and its reason, and the remembered note on pain or illness,
- how you felt after training,
- your notes on exercises,
- the mark to train normally despite low recovery.
We upload these only if you explicitly agree with "Yes" in the app (Art. 9(2)(a) and Art. 6(1)(a) GDPR). The app asks before any of it is uploaded: after setup if you are new, and at the next start if you already use the app. The question is called "Your health details"; you answer "Yes, back up health details" or "No, only on this iPhone". Without your yes, these details stay on your iPhone and are not in the copy in your account. Consent is voluntary. You can use the app without it.
We store your answer (yes or no, the version of the question and the date) with the copy on the server, so your other iPhones with the same account take over the latest answer. Storing your answer serves as proof of your consent (Art. 6(1)(c) with Art. 7(1) GDPR).
You can withdraw consent at any time in the app's profile with the switch "Back up health details". At the next backup, the copy on the server no longer contains these details. They may usually stay in the backups (section 13) for up to about 30 days. Withdrawal applies to the future; processing until then was lawful (Art. 7(3) GDPR).
Anyone who answers "under 18" in the safety check or enters an age under 18 is never asked. Their health details from the app then never go into the copy in the account, even after an earlier yes. The app does not send them with a problem report either (section 5), nor to the coach. What they write in the chat themselves goes to Anthropic as written. What our server stores in their account for the safety rules at 16 and 17 is in section 8.
Your yes to the backup does not send health details with a problem report. The "Report a problem" screen has its own switch for that (section 5).
7. What happens only on your iPhone
These features come from Apple and run on your iPhone. The app asks for permission first, and you can withdraw it at any time in the iPhone settings.
- Apple Health: the app reads only sleep, heart rate variability and resting heart rate, so training fits your recovery. The values themselves are not uploaded. From 18, the coach sees how today's training follows them, for example "light" and with fewer sets (section 8). Only a problem report can, if you switch that on, contain today's recovery value (section 5). The app writes to Apple Health only if you turn on saving workouts, in your profile with "Save workouts" or after a workout. The switch starts off. The app then saves each finished workout to Apple Health as strength training, with its start and end time, without calories. The app sends nothing to our server for this. Its logs on the iPhone do note the steps, for example that a workout was saved and how many minutes it took, or that you turned saving on or off. We get these logs only if you send "Report a problem" or agreed to the daily log upload (sections 5 and 15). You can turn saving off in your profile at any time, or withdraw the permission in the iPhone settings. Workouts already saved stay in Apple Health, where you can delete them.
- Calendar: the app reads today's events so training and meals fit your free time. The events themselves are not uploaded. A problem report contains only the times of today's training (section 5).
- Location and gym search: the app asks for your location while you use it and searches gyms with Apple Maps (MapKit). Apple gets your search term and the rough area of your location. Of the gym you choose, we back up only the name. Location and address stay on the iPhone.
- Camera: for the barcode scan, the iPhone itself reads the code in the camera image. The camera image does not leave the iPhone; only the code goes to our server (section 9). For the photo scan and photos in the coach chat, see section 8.
- Food search: food search runs in a nutrition table inside the app (the German Federal Food Code, BLS). Your search terms do not leave the iPhone.
- Speech: when you speak to the app, Apple's speech recognition turns it into text. If your iPhone can, this happens on the device; otherwise Apple processes the speech on its servers.
- Language model: if the app does not understand a sentence from the input bar, typed or spoken, Apple's language model on your iPhone reads it, if your iPhone supports it. No server is involved.
- Reminders: these are notifications your iPhone shows itself. There is no push server.
- Widgets and Siri: widgets on the home and lock screen and Siri show, for example, your recovery value and today's training time. This happens on the iPhone. On the lock screen, anyone holding your iPhone can see it without unlocking. If you stated an eating disorder in the safety check, widgets and Siri show no calories, protein or weight.
The coach chat and the photo scan do not run on your iPhone but through our server at Anthropic. See section 8.
The app keeps its data in a file protected by iOS data protection, and your sign-in in your iPhone's keychain. The file with your app data is part of your iPhone backup in iCloud or on a computer if you have that backup switched on; Apple's terms apply to it. The app also writes a log of technical events of the last 7 days on the iPhone. It is not part of that backup and leaves the iPhone only with a problem report (section 5) or, if you agree, with the daily log upload (section 15).
8. Coach chat and photo scan with AI
The coach chat and the meal photo scan use Claude, an AI from Anthropic. Both are optional. Before you use either for the first time, the app explains what goes to Anthropic and asks for your consent. Without it you use the app as before and log food by search or barcode. The app stores your answer only on this iPhone and only for your Apple account; another iPhone asks again. You can withdraw consent at any time in the app's profile.
Coach chat. In the coach chat you write with an AI, never with a person. Every answer is marked as AI in the app. The app offers the chat from 16, and not if you stated an eating disorder in the safety check. With every message, the app sends to Anthropic through our server:
- your message and the chat so far,
- today's date and, depending on what you entered at setup, a short note for the coach, for example "no calorie deficit", never the reason,
- depending on the question, what the coach looks up in the app for it: your profile (age, height, diet), your goal, your weight history, your plan and your training, including how today's training follows your recovery from Apple Health, what you ate, your daily targets for calories and protein, and your day notes, for example on pain, illness or sleep.
At 16 and 17, the app sends the coach no health details from the app: no weight or weight history, no diet, no day notes on pain, illness or sleep, nothing from Apple Health, and no height, no daily targets, no calories and no note from the safety check. The coach then does not log your weight, such day notes or your diet either; you do that yourself in the app. Your own messages go to Anthropic as you write them.
Your name, email address and location do not go to Anthropic, nor does any identifier of your account. Weight, diet, day notes, how your training follows your recovery and anything you write about your health are health details (section 6). By agreeing to the chat, you explicitly consent to them going to Anthropic for it, including to the USA (see below). At 16 and 17 that consent covers only what you write yourself and the safety rules (see below). This consent is separate from your backup choice in section 6.
The chat history is only on your iPhone and in Apple's backup of your iPhone if you have it switched on (section 7). It is not part of the copy in your account. The app keeps at most 200 messages from the last 90 days. You delete the history in your profile with "Delete chat history", and "Delete account" deletes it too. Our server does not store your messages; they are only in memory during the request. What the coach logs or changes at your request, for example a meal or your weight, the app changes on your iPhone. It is backed up like your other data (section 5).
Photos in the coach chat. You can attach a photo to a message to the coach, for example of your food, a machine or a training plan. Before you send your first photo, the app asks for your consent separately ("Send photos to the coach"). Your consent to the chat alone is not enough. At 16 and 17 a separate consent applies. You can withdraw it in your profile. The app makes a reduced copy of the photo (at most 1280 pixels on the long edge) without location or other metadata and sends only this copy through our server to Anthropic, only with that one message. In later messages only "[Foto]" stands in its place. Our server does not store the photo. It is held in memory only during the request. On your iPhone the app keeps a small preview (at most 512 pixels) in the chat history, not the photo itself. The preview is neither part of your iPhone backup nor of the copy in your account. The app deletes it with "Delete chat history", with "Delete account" and when its message drops out of the history (90 days, 200 messages). If a photo shows more than food, a machine or a plan, for example a person, from 18 that goes to Anthropic too. The coach never comments on anyone's body, figure, weight or looks in a photo. Each person can send 10 photos in 24 hours. The legal basis is your consent (Art. 6(1)(a) GDPR), from 16 your own (Art. 8(1) GDPR); where a photo shows health data, your explicit consent (Art. 9(2)(a) GDPR).
Photo scan. In the photo scan, the AI estimates what is on your plate: foods, amounts and nutrients. The photo scan is available from 16 and is not offered if you stated an eating disorder in the safety check. The app makes a smaller copy of your photo without location and other metadata and sends only that through our server to Anthropic. Our server does not store the photo; it is only in memory during the request. With the photo scan, the app does not keep the photo either. If the photo shows more than your food, for example a person, that goes to Anthropic too. You check the result before you take it over. Entries you take over are stored like any other meal (section 5).
Under 16. The coach chat and the photo scan start at 16. The app also does not offer them if you answered "under 18" in the safety check but entered an age of 18 or more. If such a request with an age under 16 arrives anyway, our server refuses it and sends nothing to Anthropic. It creates no usage entry for it (see below); the log shows only the refusal (section 14).
At 16 and 17, special safety rules apply:
- The app asks for your consent separately and explains the safety rules and what we store for them. A consent you gave as an adult does not count for this.
- The coach gets extra instructions: no diet, no calorie deficit, no weight goal and no pace for losing or gaining. It gives calorie and macro targets only to hold weight or build muscle, at most 300 kcal above need and never under 1600 kcal a day. Also no supplements, nothing sexual, and it does not ask where you live, your school, phone number or social media names.
- Our server checks every message you write and every coach answer before it goes on: first with fixed word lists, then with a second, smaller AI model from Anthropic (Claude Haiku). That model gets only the one message or the one answer, without the chat so far, without your profile and without any identifier of your account. For an answer, that is its text, the coach's reasoning if it goes to the app with it, and the texts of the changes the coach wants to make or suggest in the app. The model names only the safety rule the text breaks, or that it is fine. The app shows the coach's answer only once it is fully checked. The details the app sends the coach from your data when it asks are checked by the word lists too. If they hit, the request does not go to the coach and you get a fixed text.
- If your message points to self-harm or an eating disorder, or is sexual, it does not go to the coach, not even later as part of the chat so far. You get a fixed text instead, for self-harm and eating disorders with numbers where you get help: Nummer gegen Kummer 116 111, TelefonSeelsorge 0800 111 0 111, in danger 112. If a coach answer breaks a safety rule, you get a fixed text instead. If the check cannot decide, nothing goes out unchecked: you get a fixed text and can try again shortly after. Other word list hits, such as on alcohol or a crash diet, do not hold your message back.
- If three of your messages within 24 hours did not go to the coach because they pointed to self-harm or an eating disorder or were sexual, the coach chat pauses for 24 hours and shows the help numbers. Only messages the daily limits allow count. Not counted: coach answers that were replaced, messages where the check could not decide, and app details the word lists blocked. For the pause, our server stores in your account only the time of each such message, never the text and never which of the three kinds it was. It deletes the time after 48 hours, at once with "Delete account". How long the log keeps its lines on this is in section 17. It is not in our daily database backups. In Hostinger's weekly backup of the whole server it may stay for up to about 30 days (section 13).
- So we can see how well the safety rules work, the server counts per day how often each rule fired: day, chat or photo, message or answer, the rule, whether it counts toward the pause, and the number. The count holds no account and no time. It is deleted after 90 days and leaves the backups as described in section 13. The legal basis is your consent (see below).
- In the photo scan, the AI is told to say nothing about weight, diet or the body in its note on the photo, and nothing about a person in the photo. If it does anyway, our server removes the note. A food name the word lists block is sent empty, and you name the food yourself. The foods and nutrients found stay. The photo scan has no check by a second AI model and no pause. A hit only goes into the daily count and, without the rule, into the log (section 14).
- For photos in the coach chat, Apple's image recognition (Vision) checks on your iPhone, without any server, whether the photo shows a face or a person. If it does, or if the check cannot tell, the app does not send the photo and tells you so. The photo then reaches neither our server nor Anthropic. The coach is also instructed never to say anything about a person or a body in a photo. Our server checks your words and the reply as described above; the second AI model does not receive the photo itself. That a photo was stopped is noted only in the app's log on your iPhone (without the photo), which reaches us only with a problem report or the daily log upload (sections 5 and 15).
Your age. At sign-in (section 4), with every chat message, every photo, every backup and every problem report (section 5), every log upload (section 15) and every action in the friends feature, sharing plans included (section 10), the app sends the age from your profile to our server. For your account, the server remembers only the latest birth date your age statements allow, and when it created and last changed it, not your age itself. At sign-in it only checks the age limit and stores no age. The age the app sends separately with a problem report is checked and not stored in the report. The copy of your app data in the report does hold the age from your profile (section 5). It does not believe a later statement more than a year above that, so a profile change cannot get around the age limit; for the friends feature the youngest age you ever stated always counts. The date is deleted with your account and leaves the backups as described in section 13. The legal basis is our legitimate interest in keeping to the age limits (Art. 6(1)(f) GDPR).
What our server stores for this. For the daily limits and to watch costs, our server stores an entry without content for every chat message and every photo: time, computing amount used (tokens), cost, duration and result. For the chat it adds the names of the app functions the coach called and a hash of your message from which the text cannot be recovered. For the photo scan it adds the size of the photo and the number of foods found, for a photo in the chat its size and its dimensions in pixels. At 16 and 17, the chat result may say that the safety rules replaced your message, app details or the answer, or that the check could not decide, and what the check cost. Which rule it was is never there. The safety rules replace your message or app details only for one of the three kinds above (self-harm, eating disorder, sexual). Instead of your account number, the entry has a pseudonym. The server deletes these entries after 48 hours; they leave the backups as described in section 13. The legal basis is our legitimate interest in preventing abuse and uncontrolled costs (Art. 6(1)(f) GDPR), and for the safety rule details at 16 and 17 your consent (see below).
For our overview, the server also counts for each day how many accounts used the app and how many were new, how many chat messages and photos there were and what they cost. The count holds no account and no time of day. The server deletes it after 400 days, and it leaves the backups as described in section 13. The legal basis is our legitimate interest in seeing how the app is used and what it costs (Art. 6(1)(f) GDPR).
Anthropic. Anthropic processes messages, details and photos on our behalf, only to create the answer or, at 16 and 17, to check it, and may not use them to train AI models. This applies to the requests our server sends to Anthropic: coach chat, photo scan and the safety check. For chat and photo scan we use the Claude Sonnet model. If it declines a request, Anthropic may have another Claude model answer it; it then still stays with Anthropic under the same terms. Anthropic may also process the data in the USA, based on the European Commission's standard contractual clauses (section 18). By its own account, Anthropic deletes requests and answers within 30 days. If Anthropic's automated review rates a request as a breach of Anthropic's usage policy, Anthropic keeps it longer: request and answer up to 2 years, the scores of that review up to 7 years.
The legal basis for the coach chat and the photo scan is your consent (Art. 6(1)(a) GDPR), from 16 your own (Art. 8(1) GDPR). For health details in the chat it is your explicit consent (Art. 9(2)(a) GDPR), and for the transfer to the USA also the standard contractual clauses (Art. 46(2)(c) GDPR). From 18, your consent covers the details from the app and what you write yourself. At 16 and 17 it covers only what you write yourself and the safety rules: the check of every message and answer, the pause and the entries about it in your account, the usage entry, the log (section 14) and the safety rules' daily count, because they can hint at your health or sex life. Withdrawal applies to the future; processing until then was lawful (Art. 7(3) GDPR).
9. Barcode scan
When you scan the barcode of a food package, the app sends only the barcode number and the app's language to our server. Our server asks Open Food Facts, a free food database, about the product and returns the name and nutrients to the app. Open Food Facts sees only our server and the number, not your IP address, your account or any identifier of you.
So we do not ask Open Food Facts again for every scan, our server remembers the result for a number without storing who scanned it: a product found for 30 days, a number without a result for 1 day. Each person can scan 100 times a day; the server counts this in memory. Our server's log notes a scan with the number and no account; the web server's access log has the request address with the number and your IP address (section 14). What you take over, the app stores like any other meal (section 5).
The legal basis is providing the feature you use (Art. 6(1)(b) GDPR).
10. Friends, friend chat and shared plans
The friends feature is optional and can be used from 16. The youngest age you ever stated in the app counts. Before you use it for the first time, the app shows the rules for friends, and you agree with "I agree". We store the version of the rules and the date you agreed.
Your profile. Then you enter a name (2 to 24 letters) and choose a username (3 to 20 characters). If you choose none, the server makes one from your name. You also get an 8-character friend code and a random identifier under which others see you. The server checks names and usernames with fixed word lists, so they hold no insults, links or names on other apps.
Who finds you and what others see. Others find you by your username, your friend code or a link with one of them. Search finds adults by the start of their username, people aged 16 and 17 only by the whole username. A search shows at most 10 results, and one person can search at most 120 times an hour. Whoever finds you, anyone you send a request to and your friends see your name, your username and your random identifier, never your email address, your account number or your other data from the app. A link of the form /f/code or /u/username opens a simple page on our server that looks nothing up and only opens the app. Adults and people aged 16 and 17 can be friends.
On our server we store your agreement to the rules, your profile (name, username, code, identifier), your friendships and open requests, and whom you blocked, each with a date. These are not separately encrypted. They belong to your account and are deleted with it.
Friend chat. With friends you exchange text messages of up to 1000 characters. Our server stores every message encrypted. Who wrote to whom and when, how far each has read, and whether a message got a note with help numbers are stored unencrypted next to it. The server deletes messages after 90 days, and the whole chat at once when one of you ends the friendship, blocks or reports the other, or deletes their account. In this chat you write with people, not with an AI, and no AI reads these messages.
Before a message arrives, our server checks it in every chat with fixed word lists, not with an AI, for hate, threats and harassment. If a person aged 16 or 17 is in the chat, it also blocks links, email addresses, phone numbers, names on other apps and sexual content. A blocked message is not stored, and you see a notice. If a message in such a chat points to self-harm or an eating disorder, it arrives together with numbers where help is available. Each person can send 30 messages a minute and 500 a day.
Shared plans. You can send your training plan to a friend. Only the day names, the exercise names and the sets with reps and weight go along, never your profile, your gym, your body weight or your notes. The server stores the plan encrypted; who sent whom a plan, when, and whether it was opened are stored unencrypted. A card for it appears in the chat. A plan stays until you take it back, your friend deletes it, you send them a new one, or the friendship ends.
For Apple's review of the app, we run an account of our own with the username vunta_testfreund that accepts friend requests by itself until it has 50 friends and sends every new friend a fixed greeting and a sample training plan. Search finds it only by its whole username, not by its start. It is a normal account, with the same rules and the same storage as any other. Anyone who adds this account as a friend shares with us what they share with any friend: name, username, messages and plans.
Our server's log notes events of the friends feature only with a short code of your account number, for requests, friendships, blocks, reports, shared plans and a search by friend code also with the short code of the other person, never a name, username, code, message or plan (section 14).
The legal basis is providing the friends feature you want to use (Art. 6(1)(b) GDPR). Checking messages and names and the limits on search and messages rest on our legitimate interest in protecting you and others from harassment, abuse and contact with young people (Art. 6(1)(f) GDPR). If you write friends about your health, that is your own choice; we do not analyse it.
11. Reporting, blocking and moderation
Blocking. You can block anyone. This ends a friendship or request and the chat, and you no longer find each other. The blocked person is not told. You undo blocks under Friends.
Reporting. You can report a person, their name, a chat message or a shared plan. A report also blocks the person. You choose a reason (for example harassment, sexual content, hate or danger) and can write a note of up to 500 characters. If you report a message, the server saves it and up to 10 messages before it, from both of you, as evidence in the report, before the block deletes the chat. If you report a plan, it saves the plan.
The report holds, encrypted, your note, the reported person's name, your name and the evidence. Unencrypted next to it are the kind and reason of the report, whether a person aged 16 or 17 is involved, whether the reported person had blocked you before, the random identifiers of you both, the dates and how the report was closed. If either person deletes their account, the report stays; only the link to the deleted account is removed. So a report cannot be dodged by deleting the account.
Who reads reports. Reports are read only by our moderator in the app, never by an AI. For every new report, and again if it is still open after 20 hours or after 3 days, our server sends a notification over our own private, encrypted network to a computer of ours. It holds only the report's number, its kind and the time, no text, no names and no identifiers. Our server gives it to no third party. We look at every report within 24 hours. The moderator can close a report as handled or suspend the reported person. A suspended person can no longer use the friends feature, and others no longer see them.
How long. An open report stays, with no time limit, until the moderator closes it. The server deletes a closed report 30 days after it came in. If it is closed only after that, the server deletes it within an hour. In the backups (section 13) it may stay as long as described there.
The legal basis is our legitimate interest in protecting the users of the friends feature, investigating and acting on breaches of the rules, and meeting the App Store's requirements for user content (Art. 6(1)(f) GDPR). This also covers the details about the reported person.
12. Protecting young people
VUNTA is for people aged 16 and over. We comply with the child-safety and data protection laws that apply to us, in particular the GDPR and the German Youth Protection Act (Jugendschutzgesetz). For people aged 16 and 17 we do the following:
- Age limit: the app asks the age before sign-in and lets no one under 16 in (section 3). The age is self-declared; we do not check it against an ID. Our server believes a later, higher age only within limits (section 8).
- AI made clear: in the coach chat every answer is marked as AI. Before first use, the app explains what goes to Anthropic and asks young people for their consent separately (section 8).
- Safety rules for the AI: the coach gets its own instructions for young people (no diet, no weight targets, nothing sexual, no questions about where they live or contact details). Every message and every answer is checked first, and signs of self-harm or an eating disorder lead to help numbers instead of an AI answer (section 8).
- Less data: we back up no health details of anyone under 18, and the app sends them neither to the coach nor with a problem report (sections 5, 6 and 8).
- Friends: in search, young people can be found only by their whole username. In chats with them, the server blocks links, contact details, names on other apps and sexual content. Anyone can be blocked and reported, and we look at every report within 24 hours (sections 10 and 11).
- No ads, no tracking: the app shows no ads and gives no data to advertising or analytics services.
- Help: the app names numbers where young people get free help: Nummer gegen Kummer 116 111, TelefonSeelsorge 0800 111 0 111, in danger 112.
If you have a concern about the safety of young people in VUNTA, as a young person, a parent or for any other reason, write to us at info@run4dev.com. We answer as soon as we can.
13. Hosting and location
Our server runs at Hostinger (Hostinger International Ltd., Larnaca, Cyprus) in a data centre in Vilnius, Lithuania (EU). Hostinger processes the data on our behalf (Art. 28 GDPR). The app interface and the website vunta.de run on this server. The database cannot be reached from outside; only our app interface talks to it.
Every day we put a backup of the database on the same server. The next backup deletes copies older than 14 days. In addition, Hostinger makes a weekly backup of the whole server and keeps the last two. These also hold our daily database copies. So deleted data may usually stay in backups for up to about 30 days.
14. Server log files
With every call to our app interface, the web server automatically stores your IP address, date and time, the full address called, the status code, the amount of data, the page visited before and your device details (user agent). The full address can contain the number of a scanned barcode (section 9), a friend's random identifier and, for a friend link, a username or friend code (section 10), never the content of a message, a backup or a photo. The web server writes errors to an error log of its own. It starts a new file every day and deletes the oldest when there are more than 14. So entries usually disappear after 14 days; on days without calls it starts no new file, and a file can then hold older entries too. A protection program on the server (fail2ban) reads these log files and blocks addresses that attacks come from for a while.
The app interface also writes a log of events such as sign-in, errors, deletion and every stored copy, with your account number (for a copy also its size), but without the content of your data and without session keys. For the coach chat and the photo scan, the log holds the duration, cost and result of each request, for a photo also its size, in the chat also its dimensions in pixels, with a short code of your account number. We do not write the text of a message or the photo to the log. For every chat message, photo and backup, it also holds the age group (under 16, 16 to 17, 18 and over) with the same code. If the server refuses a request because of age, the reason is there with the same code: under 16 or 16 to 17. If the server does not believe a higher age (section 8), the stated and the remembered number of years are there for chat, photo scan, backup and the friends feature; these are the only lines with an age. For sign-in it notes only whether an age came with it. At 16 and 17, for chat and photo scan, it notes that the request ran under the safety rules and, with the same code, whether the safety rules affected a message, app details for the coach, an answer, or for a photo the note or a food name, whether the hit counts toward the pause, and whether and until when the chat is paused, never exactly which rule and never the text. If a hit blocked your message or app details or counts toward the pause, it was one of the three kinds in section 8 (self-harm, eating disorder, sexual). For a problem report, the log holds its code, its size, the app's build number, how many days of logs it holds and whether it holds health details, with a pseudonym of your account number, never its content. For the app's logs (section 15), it holds, with the code of your account number, how many days were stored, replaced or not stored, their size and the build number, for a refusal the reason (for age, with the age group), when switched off how many days were deleted, and for every read by us the day, its size and how often it was read, never a line of the logs. For the friends feature, it holds events such as a request, a block, a report or a message sent, with the code of your account number, for a request, friendship, block, report, shared plan or a search by friend code also with the code of the other person, for a report its kind, its reason, whether a person aged 16 or 17 is involved, whether the reported person had blocked you before and how many reports are open at that moment, for a message its length and its number, when a chat is read the number of messages and whether there are more, for a search the length of the search term, the number of results and how many results were not shown for which reason (for example because of a block), never a name, username, code, search term or text. If the filter refuses a message to a friend, it holds only the kind of reason: hate, threat, harassment, link, email address, phone number, name on another app or sexual content. For the chat it never holds whom you write with, and never whether a message got a note with help numbers. It does not note separately whether a person aged 16 or 17 is in the chat, but the reasons link, email address, phone number, name on another app and sexual content only exist in such chats. For a barcode scan it holds the number without an account, and the code when a limit was reached. If someone reached the sign-in limit (see below), the IP address is in it too. The log keeps at most 3 files of 10 MB each and then overwrites the oldest.
Against abuse, we limit calls to the sign-in interface (all calls under /auth, except Apple's notices) to 10 per minute per IP address, for IPv6 per network (/64). The server counts the calls in memory.
The legal basis is our legitimate interest in secure and stable operation, in fending off attacks and in finding faults (Art. 6(1)(f) GDPR), and for the safety rule details at 16 and 17 your consent (section 8).
15. App logs
If you explicitly agree in the app, the app sends its technical logs of the last 7 days to our server by itself about once a day, with the app's build number and your age for the server's age check (section 8). It sends only lines written since you signed in on this iPhone. We need the logs only to find and fix faults, and we read them only when you tell us about a problem, for example with "Report a problem" (section 5) or by email. Only we read the logs; they go to no AI.
The logs hold technical steps of the app, including training details such as exercises with weight and reps, and foods as an ID number with an amount. They do not hold chat messages, sign-in data, food names, text you type yourself or your email address. The app removes health details (for example body weight, pain, illness, sleep) before sending, even if you agreed to back up your health details (section 6).
The logs are stored encrypted on our server at Hostinger in Vilnius (Lithuania, EU, section 13). The server keeps each account's logs of the last 7 days and automatically deletes every day older than 7 days.
The legal basis is your consent (Art. 6(1)(a) GDPR), which you give yourself from 16 (Art. 8(1) GDPR). It is voluntary. You can switch it off at any time in the app's profile: the app then sends nothing more, and the server deletes your logs as soon as the app reaches it, otherwise after 7 days as always. "Delete account" deletes them at once. They usually leave the backups (section 13) after about 30 days at the latest.
If, after agreeing, you enter an age under 16 in your profile, this counts as switching off: the app sends nothing more, forgets your consent, and the server deletes your logs. Without your consent, the logs stay on your iPhone unless you send a problem report (section 5).
16. This website
The website vunta.de consists of fixed pages. It sets no cookies, contains no ads and loads nothing from other servers, not even fonts. There are no forms. If you write to us through an email link, the run4dev privacy policy (in German) applies to your email.
Visitor statistics without cookies (Umami): to understand how the website is used and where we can improve it, we count visits with the open-source program Umami. We run it ourselves on our server at Hostinger in Vilnius (section 13), and your browser loads its script from vunta.de too. The data goes to no one else. Umami sets no cookies and stores nothing in your browser. It records the page opened (address and title), the website you came from, campaign details in the link (utm_*), browser, operating system, device type, screen size and language, and the country, region and city derived from your IP address. Umami itself does not store your IP address. To group the page views of one visit, Umami forms a pseudonymous ID from your IP address and browser details, which changes regularly. We cannot use it to follow you across other websites. The statistics requests are not in the web server's access log files. Only when Umami cannot be reached does the web server write the request with your IP address to its error log, which, like the log files, is usually deleted after 14 days (section 14). We delete the data after 26 months; from the backups (section 13) it usually disappears after about 30 days at most. The legal basis is our legitimate interest in measuring the use of the website with as little data as possible (Art. 6(1)(f) GDPR). You can object at any time: (this stores the note "umami.disabled" in your browser's local storage, with no expiry; it stays until you delete the website data in your browser).
Our own team's visits: so that our own visits are not counted, our team opens a page of vunta.de once in each of its browsers with "?vunta_internal=1" in the link. That browser then keeps the note "vunta-internal" in local storage, with no expiry: it stays until a page with "?vunta_internal=0" is opened there or the website data is deleted in the browser. Umami counts nothing from a browser with this note, nor from browsers controlled by a program, for example in automated tests. The note is only stored in a browser in which a link with "?vunta_internal=1" was opened. Legal basis: our legitimate interest in keeping our own visits out of the statistics (Art. 6(1)(f) GDPR).
When you open a page, the web server automatically stores, in one file with run4dev's other websites, your IP address, date and time, the address called and the website's name, the status code, the amount of data, the page visited before and your browser details (user agent). The same applies to these log files as in section 14: usually deleted after 14 days, and fail2ban reads them to fend off attacks. The website is on our server at Hostinger in Vilnius (section 13).
The legal basis is our legitimate interest in providing the website securely and without faults (Art. 6(1)(f) GDPR).
17. How long we keep data, and deletion
We keep your account, your copy and your friends profile as long as your account exists.
- Sign out in the app only ends the session. The account and the copy stay.
- Delete account in the app deletes your account, all its sessions, your copy, your friends profile, your friendships, blocks, chats and shared plans, your remembered age and your logs from the database at once. The data on your iPhone stays, except the coach chat history. You delete the rest by removing the app. We have to tell Apple that you end Sign in with Apple for the app. For that we keep Apple's refresh token encrypted and without any link to your deleted account until Apple confirms or finally refuses the revocation. If Apple does not answer, we try again later, in the end daily. Apple is based in the USA, see section 18.
- The server deletes problem reports (section 5) 30 days after receipt, at once with "Delete account".
- The server deletes messages to friends (section 10) after 90 days, and at once when the friendship ends, someone blocks or reports, or an account is deleted. Shared plans stay until they are taken back or deleted, or the friendship ends.
- Reports about other users (section 11) stay while they are open. The server deletes a closed report 30 days after it came in, or within an hour of closing if it is older by then, even if one of the two people deleted their account before.
- The server keeps notifications to us (sections 11 and 18) until they are delivered and deletes them 7 days later.
- The server deletes the app's logs (section 15) after 7 days, at once with "Delete account", and when you switch off sending in your profile, as soon as the app reaches the server. They may stay in the backups for up to about 30 days.
- The server deletes the entries for chat messages and photos (section 8) after 48 hours. They carry a pseudonym instead of your account number and therefore stay until then even after "Delete account", so a new account does not restart the daily limits.
- The server deletes the times kept for the safety rules for 16 and 17 year olds (section 8) after 48 hours, at once with "Delete account". The safety rules' daily count holds no account; the server deletes it after 90 days.
- The daily count for our overview (section 8) holds no account and no time of day. The server deletes it after 400 days.
- Barcode results (section 9) hold no account. The server deletes a product found after 30 days and a number without a result after 1 day.
- The web server's log files for the app interface and the website (sections 14 and 16) usually disappear after 14 days.
- We delete the website's visitor statistics (Umami, section 16) after 26 months.
- The app interface's log (section 14) has no fixed period: it keeps at most 3 files of 10 MB each and then overwrites the oldest. Its lines, including those on the safety rules, may therefore stay longer than 48 hours and beyond "Delete account" until they are overwritten.
- Deleted data usually leaves the backups (section 13) after up to about 30 days.
- An expired session stays as an entry in the database until you next sign in or delete your account.
You can also have your account and your data deleted by email to info@run4dev.com.
18. Recipients and third parties
We pass your data only to these parties, and only as far as needed to run the app:
- Apple for sign-in and for revoking the connection on deletion. Apple processes data under its own privacy policy. This also applies to the Apple features on your iPhone in section 7. Apple Inc. is based in the USA. The data our server sends Apple at sign-in and on deletion (sections 4 and 17) may be processed there. Transfers to the USA are covered by the safeguards Apple names in its privacy policy.
- Anthropic for the coach chat and the photo scan (section 8), at 16 and 17 also for checking chat messages, only if you agreed. Problem reports, logs, friend chats and reports about other users do not go to Anthropic. Our contract partner is Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland. For these requests from our server, Anthropic processes the data on our behalf under a data processing agreement (Art. 28 GDPR) and may not use it to train AI models. Anthropic may also process the data in the USA and other countries outside the EU, at Anthropic, PBC and further sub-processors. This transfer is covered by the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR), which are part of that agreement. Anthropic publishes its list of sub-processors at anthropic.com/subprocessors.
- Hostinger as host, as in section 13. The app's logs (section 15) are also only there and go nowhere else.
- Other users, if you use the friends feature: whoever finds you sees your name and username, and your friends also your messages and the plans you send them (section 10).
Open Food Facts (Open Food Facts, France) gets from our server only the number of a scanned barcode, with nothing about you (section 9). The product data is under the Open Database License (ODbL); the app names the source.
The app and our server contain no ads and no third-party software that sends data. The app contains no analytics or tracking services; the only one on our server is the website's own visitor statistics (section 16). Apart from the Apple features in section 7, the app connects only to our server, and our server only to Apple, Anthropic (for coach chat and photo scan) and Open Food Facts (for the barcode scan). Notifications to us, for example about a new report (section 11) or a failed revocation at Apple (section 17), go over our own encrypted network to a computer of ours, to no third party. They hold no text, no names and no account numbers. Links in the app, for example to outside help pages, open in the browser, where that site's terms apply.
19. Security
- The connection between app and server, and to this website, is encrypted with HTTPS.
- The copy of your app data and Apple's refresh token are encrypted with AES-256-GCM before they are stored in the database, and bound to your account.
- Problem reports, the app's logs, messages to friends, shared plans and the content of reports about other users are also encrypted with AES-256-GCM before they are stored.
- We store session keys only as a hash.
- The app interface runs with restricted rights in an isolated container.
20. Your rights
You have the right at any time to
- access the data stored about you (Art. 15 GDPR),
- have wrong data corrected (Art. 16 GDPR),
- erasure (Art. 17 GDPR) and restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- object to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR),
- withdraw consent (Art. 7(3) GDPR).
Just write to info@run4dev.com. You can also complain to a data protection authority (Art. 77 GDPR); for us that is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany.
There is no automated decision with legal or similarly significant effect (Art. 22 GDPR). The app works out your training and food plan on your iPhone. Whether a person is suspended is decided by a human.
21. Changes
If the app or the way we process data changes, we update this policy. The date at the top shows the current version. The German version at vunta.de/datenschutz is binding.