Who we are
Runvic is made by Marek Novák, an individual developer based in the Czech Republic. For the purposes of the EU General Data Protection Regulation (GDPR), Marek Novák is the "controller" of your data.
- Controller: Marek Novák, a self-employed individual (IČO: 09377832)
- Address: Hochmanova 3, 628 00 Brno, Czech Republic
- Privacy contact: dev@novakmarek.cz
- Policy URL: [PLACEHOLDER: public URL where this page is hosted, added once the website is live]
Runvic is for iPhone only (iOS 26 or later) and is currently available in English only.
What we collect and why
2.1Your account
When you sign up with e-mail and password, Sign in with Apple, or Google Sign-In, we (through Google's Firebase Authentication) store:
- Your e-mail address. If you use Sign in with Apple and choose "Hide My Email", we only get a private relay address from Apple.
- Your password, stored in hashed form by Firebase. The app never keeps it.
- Your name and profile photo link, if Apple (name, first sign-in only) or Google (name, photo) provides them. Firebase saves these to your account automatically. Runvic doesn't use or show them. The name you see in the app is the one you typed in onboarding.
- A random user ID that links the rest of your data to your account.
- Sign-in method, account creation time and last sign-in time.
Sign-in tokens are kept in the iOS Keychain on your phone so you stay signed in.
An account is required to use Runvic. There is no guest mode.
2.2Your profile (onboarding)
During onboarding you can tell us your name (you can type anything), how long you've been running, what you're training for, how many days a week you run, and optionally an upcoming race. These answers are stored with your account. They are optional in the sense that you decide what to type, but the app asks for them to adapt to you. At the moment, you can't edit these profile answers in the app after sign-up. Write to us if you'd like them changed.
2.3Trainings and races
We store the runs you plan and the races you add:
- Trainings: date and time, type, distance, your notes, weekly repeat and end date, and which days you've marked done or skipped.
- Races: name, date and time, distance, location, goal time, priority, plan length, and your race-day checklist.
Your running plans are fitness information, and some people may consider them health-related. We treat them with care. Past trainings and races stay in your account until you delete them or the account, so you can look back at them with Runvic Pro. Without Pro, the app only loads current ones. Upcoming races that need Pro to be seen also stay stored.
Please don't put other sensitive information in free-text fields (notes, race names, locations, checklist items, meal names or your name). Whatever you type is stored as you typed it.
2.4Carb loading, body weight and food log (health data)
If you turn on carb loading for a race, we store your body weight, the target you chose, the reminder setting and time, and a log of what you eat (meal name, grams and time).
This is health data, which has extra protection under GDPR. We only process it with your explicit consent, which we ask for with a checkbox the first time you set up carb loading. We save your consent with the date and the version of this policy. You can withdraw your consent at any time with the "Health data" switch in Profile, which deletes your stored body weight and food logs and turns off carb reminders. You can also delete your account. Withdrawing doesn't affect what we did before you withdrew. If you don't consent, you can still use the rest of Runvic, except carb loading.
Runvic's carb targets are simple calculations (grams per kilo of body weight). They are guidance, not medical or nutrition advice, and nothing is decided about you automatically.
2.5Runvic Pro purchases
Runvic Pro is optional. When you buy it:
- Apple handles your payment. Your card, billing address and Apple ID details go to Apple only. Runvic and RevenueCat never see them.
- RevenueCat (our purchase-management provider) receives your app user ID, which is the same as your Runvic user ID once you're signed in (before that, an anonymous ID), and your purchase information: product, dates, renewals, cancellations, refunds, trial use, price, country or currency, and App Store transaction IDs. It also receives standard device and app information from its SDK, such as iOS version, app version, language/region and IP address.
- We use this to unlock Pro, restore your purchase, and make Pro follow your account to a new phone. We don't send RevenueCat your e-mail or your name.
You manage and cancel subscriptions in iOS Settings → Apple ID → Subscriptions. Refunds go through Apple.
2.6Technical data handled by our providers
When the app talks to Google or RevenueCat, they process technical data such as your IP address and device or app information in their own service and security logs. We don't use this data ourselves.
2.7What we don't collect
Runvic does not use GPS or your location, Apple Health, Apple Watch, contacts, photos, camera, microphone, calendar or Bluetooth. It has no social features, and nothing you enter is shared with other users or made public.
What stays on your phone
Some data is kept only inside the app on your phone and is not sent to us:
- A copy of your synced data (offline cache), so the app works without internet
- Widget data: about four weeks of runs (type, distance, time, notes, done), upcoming races, and carb targets and grams logged per day. Widgets read this file and never go online.
- Your quick-add food list (banana, bagel and so on)
- The last body weight and reminder time you entered, to prefill the next race
- Settings: units, app theme, app icon, widget theme, haptics
- Scheduled reminders (race name, "Day 1 of N" and the carb target)
- Unfinished onboarding answers, until your account is created
This data is protected by iOS. If you back up your iPhone to iCloud or a computer, it may be included in that backup, which is under your control, not ours.
Notifications and your Lock Screen
Runvic asks for notification permission only when you save carb loading with the reminder on. The reminder is created on your phone (nothing is sent from a server) and looks like: "Carb loading starts today. Day 1 of 3 for City Marathon · aim for 600 g of carbs." You can turn notifications off any time in iOS Settings → Runvic → Notifications.
Please remember that notifications and widgets can show information on your Lock Screen and Home Screen, such as your race name, carb target, today's run and training notes. Anyone looking at your phone may see them. You can change what iOS shows on the Lock Screen in your iPhone settings.
Why we may use your data (legal bases)
| What we do | Data | Legal basis (GDPR) |
|---|---|---|
| Create and run your account, sign you in, reset your password | Account data | Contract, Art. 6(1)(b) |
| Store and sync your profile, trainings, races and checklist across devices | Profile, trainings, races | Contract, Art. 6(1)(b) |
| Carb loading targets, food log and reminder | Body weight, carb log | Your explicit consent, Art. 9(2)(a) and Art. 6(1)(a) |
| Runvic Pro: sell, unlock, restore, keep records | Purchase data | Contract, Art. 6(1)(b); legal obligation for accounting and tax records, Art. 6(1)(c) |
| Keep the service secure and working | Technical data in provider logs | Legitimate interest, Art. 6(1)(f) |
| Answer your privacy or support requests | Your e-mail and your request | Legitimate interest, Art. 6(1)(f), and legal obligation, Art. 6(1)(c) |
Is giving us data required? An e-mail address (or an Apple or Google sign-in) is needed to have an account. Everything else, such as your onboarding answers, races, notes and carb loading, is up to you. Body weight is only needed if you want carb loading.
We don't do profiling, we don't make automated decisions that affect you legally or in a similar way, and we don't use your data for marketing or advertising.
Transfers outside the EU/EEA
Google and RevenueCat are US companies, so your data may be processed in the United States or other countries outside the EU/EEA. Where this happens, we rely on the safeguards the providers offer, namely the EU–US Data Privacy Framework (where the provider is certified) and/or the EU Standard Contractual Clauses, which are part of the providers' data processing terms.
Your app data in Cloud Firestore (profile, trainings, races and carb loading) is stored in Google's data centres in the European Union. Account sign-in data (Firebase Authentication), purchase data at RevenueCat, and technical logs are not tied to that location, so Google and RevenueCat may process them in the United States or elsewhere, under the safeguards above.
How long we keep data
| Data | How long |
|---|---|
| Account, profile, trainings, races, carb loading | Until you delete your account |
| Past trainings and races | Kept with your account until you delete it |
| Purchase records | As long as needed to run your subscription and as long as accounting and tax law requires |
| Privacy and support e-mails | 2 years after the request is closed |
| Provider logs (Google, RevenueCat) | According to each provider's own schedule |
| Data on your phone | Until you sign out, delete your account (see sections 3 and 9), or delete the app |
Deleting your account: what's removed and what isn't
In the app, go to Profile → Delete account. You may be asked to sign in again first (Apple users confirm with Apple).
This removes:
- All your trainings
- All your races, including carb loading and the food log
- Old carb-loading data from earlier test versions
- Your profile, including past data
- Your Firebase account
- On your phone: your quick-add food list and the widget data
- For Apple accounts: Runvic's Sign in with Apple token is revoked
This does not remove (yet), and what to do:
- Your RevenueCat customer record and purchase history. E-mail us and we'll delete it. Apple keeps its own purchase records under its own policy.
- Some data on your phone: the offline cache and the last body weight and reminder time entered. Deleting the Runvic app removes them.
- Google access: Runvic signs out of Google but doesn't revoke the access grant. You can remove Runvic at myaccount.google.com → Security → Third-party connections. For Apple: iOS Settings → your name → Sign in with Apple.
- Backups you made yourself (iCloud or computer).
- Provider logs and backups at Google and RevenueCat, which expire on their own schedules.
If deletion is interrupted (for example, the app closes or you go offline halfway), some data may remain. Write to us and we'll finish it.
Your rights
Under GDPR you have the right to:
- Access your data and get a copy (Art. 15), and portability (Art. 20). Write to us and we'll send your data as a file (for example JSON). Most of it is also visible in the app.
- Correct your data (Art. 16). Edit trainings, races, carb loading and checklists in the app. For your profile answers or e-mail address, write to us.
- Delete your data (Art. 17). Use Profile → Delete account, or write to us.
- Withdraw consent (Art. 7(3)) for carb loading and health data. Use the "Health data" switch in Profile, as described in section 2.4.
- Restrict (Art. 18) or object to (Art. 21) processing based on legitimate interest. Write to us.
- Complain to a data protection authority. Ours is the Czech Úřad pro ochranu osobních údajů (ÚOOÚ), Pplk. Sochora 27, 170 00 Praha 7, www.uoou.gov.cz. You can also complain to the authority in the country where you live or work.
How to use your rights: e-mail dev@novakmarek.cz, preferably from the e-mail address of your Runvic account so we can confirm it's you. We'll reply within one month. We may ask for extra proof of identity if we have reasonable doubts.
Security
- Your data travels over encrypted (HTTPS) connections.
- Passwords are handled only by Firebase Authentication. Sign-in tokens are kept in the iOS Keychain.
- Access rules in the database let you read and write only your own data.
- Changing your password needs your current password. Deleting your account needs a recent sign-in.
- The app's logs don't contain your e-mail, name, weight or other personal content.
No system is perfectly secure, and we can't promise absolute security. We also can't claim that your data is unreadable by us: as the owner of the project, the developer can technically access the database, but we only do so to run the service, fix a problem or answer your request.
Children
Runvic is for people aged 16 or older. It's not aimed at children, and the app has no age check. If you're a parent and think your child under 16 has made an account, e-mail us and we'll delete it.
US state privacy rights
If you live in California or another US state with a privacy law, you may have the right to know what personal data we hold, to get a copy, to correct it, and to delete it. Runvic does not sell your personal data and does not share it for cross-context advertising. We won't treat you differently for using your rights. To use them, write to us as described in section 10.
Changes to this policy
We may update this policy, for example when Runvic gets new features. The "Last updated" date at the top shows the latest version. If a change matters for your rights or how we use your health data, we'll tell you in the app before it applies, and ask for your consent again if the law requires it.
Contact
Questions, requests or complaints about your data:
Marek Novák (IČO: 09377832) Hochmanova 3, 628 00 Brno, Czech Republic dev@novakmarek.cz