Privacy Policy KLIVA
Last Updated: 2026-11-16 (KLIVA app and website kliva.fit) Responsible developer: Enrico Cardaci (Germany) Privacy contact: support@kliva.fit
This Privacy Policy explains how the KLIVA iOS app and the website kliva.fit (section 3.4) handle personal data. It is informational and is not legal advice.
1. Overview
KLIVA is a fitness app for iOS that creates personalized workout plans and tracks your training progress locally on your device. KLIVA follows a local-first approach: your data is primarily stored on your iPhone and is not transmitted to external servers, with the limited exceptions described below.
1.1 Status and Responsible Party
KLIVA is provided as a free, non-commercial project by an individual developer based in Germany. There are no ads, in-app purchases, subscriptions, paid services, sponsored content, or backend account systems. KLIVA does not operate as a company, business, retailer, or commercial service provider.
Responsible developer: Enrico Cardaci Privacy contact: support@kliva.fit
The provider’s name and address are in the legal notice: kliva.fit/en/imprint.
2. Data We Collect
2.1 Profile Data (provided by you)
During setup and use of the app, you may provide:
- First name
- Date of birth (used to calculate age for workout intensity and to verify the minimum age of 13)
- Body weight and height (optional)
- Who shows you the exercises (a woman or a man): sets the figure in the exercise pictures and the photos
- How many push-ups and pull-ups you can do in a row, as a coarse range (for example “5 to 14”). KLIVA derives your starting level from it; it is your own estimate, not a medical assessment.
- Training goal, training days, length, reminder time and the skills you want to practise
- Available equipment and your places (for example home, hotel)
Purpose: Creating personalized workout plans. Storage: Locally on your device only. Legal basis: Contract performance (Art. 6(1)(b) GDPR). These data points are required to generate the personalized workout plan you request when you open the app.
2.2 Workout Data
During and after workouts, the following data is stored:
- Workout type (running, resistance, HIIT, mobility, skill, core)
- Duration, start and end time
- Exercises, sets, reps, weights
- Perceived exertion (RPE scale) and reasons you give (for example why you left out an exercise)
- Personal records and your challenge records
Storage: Locally on your device only. Legal basis: Contract performance (Art. 6(1)(b) GDPR). Tracking the workouts you complete is part of the app’s core training-history feature.
2.3 Location Data (running workouts only)
When you start a running workout, KLIVA collects:
- GPS coordinates (latitude, longitude, altitude)
- Speed and pace
- Distance covered
Purpose: Recording your running route, calculating pace and distance.
Only during a run: GPS tracking runs only while a running workout is active. So that distance and pace are right, it keeps counting with the screen locked or while you briefly open another app (iOS shows this), and it stops automatically when you finish the run. KLIVA never collects location data outside of a run.
Permission: You are asked through the iOS system dialog on your first run, only “While Using the App”, never “Always”. You can revoke location access at any time in iOS Settings.
Storage: Locally on your device as part of your workout history. Location data is not transmitted to external servers.
Legal basis: Consent (Art. 6(1)(a) GDPR), granted by you through the iOS location permission dialog. You can revoke it any time in iOS Settings → Privacy & Security → Location Services.
2.4 Apple Health (HealthKit)
KLIVA exchanges a limited set of data with Apple Health:
Writes (workouts saved back to Apple Health):
- Workout type, duration, estimated calories burned (calculated from MET values per workout type and your body weight, not a medical measurement)
- Distance (running workouts only)
Reads:
- Daily step count from Apple Health, used to show your steps on Progress (toward your daily goal). No other health data is read at this time.
Important:
- HealthKit data is never used for advertising, data mining, or sold to third parties.
- Syncing requires your explicit consent through the iOS Health dialog. You can revoke read or write access at any time in iOS Settings → Health → KLIVA.
Legal basis: Consent (Art. 6(1)(a) GDPR), granted through the iOS HealthKit permission sheet for each data type.
2.5 Profile Photo, Sharing and Duels (optional)
You can set a profile photo either by selecting an image from your photo library or by capturing a new one with the camera. The photo is stored exclusively on your device and is not transmitted anywhere. If you enable iCloud Backup, the local app data including the photo may be included in the Apple-managed device backup; see §3.2.
Sharing. In KLIVA you can share a picture with a short text and a link: your body on Progress, your completed week, a Quick Snack or a challenge result. Picture and text are made on your device. Where you send them is your choice in the iOS share sheet; KLIVA does not send them itself and does not learn whether or where you shared. To save to your photos, iOS asks once for permission to add photos.
What the link contains. A link to the App Store only carries one word for the place in the app you shared from (for example ct=woche), nothing about you. A duel link (kliva.fit/d/…) names the challenge in its path; after the # sign it carries your result, the exercise and, if your profile has one, your first name. A snack link (kliva.fit/s/…) names the snack and, after #, its minutes. A browser does not send the part after # to the server when it opens the link (RFC 3986, section 3.5); the website only reads it in your friend’s browser (see 3.4). The link itself is part of the message you send: whoever receives it can see it, and so can the service you send it through, as far as that service can read messages. Link previews and your friend’s browser history can also keep the full address. Share your name and result only with people you want to show them to.
Opening a duel. When you open a duel link, KLIVA reads the number, the exercise and the first name only from the link and shows them to you. They are not stored; KLIVA stores your own result locally in your training history like any challenge.
When you share or open a duel, KLIVA processes nothing outside your device: you send the picture, text and link yourself.
Legal basis for the profile photo and saving to Photos: Consent (Art. 6(1)(a) GDPR), granted through the iOS photo library permission sheet or the iOS camera permission sheet, depending on the source you choose.
2.6 Local Personalization
KLIVA automatically adapts workout suggestions based on the information you provide and your workout history. This personalization happens locally on your device and does not produce legal or similarly significant effects. KLIVA does not transmit your profile or workout history to any external service for personalization purposes.
2.7 Notifications (local only)
KLIVA may schedule reminders on your device, for example daily workout reminders. These are local notifications managed by iOS:
- KLIVA does not use Apple’s Push Notification service (APNs).
- No device push token is generated by KLIVA or transmitted to any server.
- Notification schedules are stored and triggered entirely by iOS on your device.
Permission: You are asked through the iOS notification permission dialog the first time KLIVA tries to schedule a reminder. You can revoke or change the permission at any time in iOS Settings → Notifications → KLIVA.
Legal basis: Consent (Art. 6(1)(a) GDPR), granted through the iOS notification permission dialog.
3. External Data Transfers
3.1 Sentry: Error Detection and Crash Reports
KLIVA uses Sentry for automatic detection of app crashes and for diagnostic log entries at warning, error, or fatal severity to improve app quality.
What Sentry collects:
- Crash reports with technical stack traces
- Device information (iPhone model, iOS version, app version, plus technical values such as memory, battery level, and the language and time zone of the device)
- Breadcrumbs: short labels for UI events that happened before the crash (e.g. button-tap names, view transitions). These describe what kind of interaction occurred, not the underlying workout content.
- Error and warning log messages from the app’s own logger
What Sentry does NOT collect:
- No workout content (reps, sets, weights, RPE values, exercise data)
- No HealthKit health data (step counts, calorie estimates, distance values)
- No location data (GPS coordinates, routes)
- No IP address and no IP-derived geolocation. Sentry’s organization-level “Prevent Storing of IP Addresses” setting is enabled, so the request IP is dropped before the event is stored. A project-level data-scrubbing rule additionally removes any city or country inference Sentry would otherwise derive from the source IP at ingest. The result: no location information reaches Sentry from either the device’s GPS or from network-layer metadata.
- No profile content (your name, weight, height, date of birth)
- No screenshots and no view-hierarchy snapshots. Both Sentry attachments are explicitly disabled in KLIVA’s code so screen content never leaves the device.
- No credentials, secrets, or payment data. Sentry’s default server-side pattern scrubbers (for common sensitive patterns such as passwords, API keys, and credit card numbers) and Sentry’s enhanced-privacy controls are kept enabled as a defense-in-depth measure. KLIVA does not process any such data in the first place.
Data processor: Functional Software Inc. (Sentry), a US-headquartered company. KLIVA configures the Sentry SDK so that all event ingestion targets Sentry’s EU region (ingest.de.sentry.io), hosted in Germany / the EU.
Random installation identifier: The Sentry SDK generates a random installation identifier (UUID) created in KLIVA’s app sandbox. KLIVA does not send it: Sentry’s session tracking is switched off, and the user identifier and a value the SDK derives from the device and the app are removed from every report. It is not Apple’s Advertising Identifier (IDFA), is not linked to your Apple ID or any other personal identifier, is not used for advertising, profiling, or cross-app tracking, and is regenerated if you reinstall the app.
International data transfers: Although Sentry’s parent company is based in the United States, the data described above is ingested and processed in the EU. To the extent any sub-processing reaches the United States, Functional Software Inc. participates in the EU-U.S. Data Privacy Framework (DPF) and additionally offers EU Standard Contractual Clauses (SCCs) as safeguards under Chapter V GDPR. Both mechanisms are incorporated into Sentry’s Data Processing Addendum (DPA).
Data processing agreement: KLIVA’s use of Sentry is subject to Sentry’s standard Data Processing Addendum (DPA) under Art. 28 GDPR.
Retention: Sentry’s Developer-tier data retention applies (currently 30 days for error events). Older events are automatically removed by Sentry.
Legal basis: Legitimate interest (Art. 6(1)(f) GDPR) and, where crash reports serve the operation of the service you asked for, § 25(2) no. 2 TDDDG: ensuring app stability and fast bug-fixing for a small free app, balanced against the limited non-content metadata involved.
Opt-out: Sentry only activates on app crashes and on log entries at warning, error, or fatal severity, and it does not collect personal content data, so there is no separate in-app opt-out. You can uninstall the app at any time to stop all data collection.
3.2 iCloud Backup
If you have iCloud Backup enabled on your iPhone, the local app data (including profile data, workout history, and a profile photo if you chose one) may be included in the Apple-managed iOS backup. This is controlled by Apple/iOS, not by KLIVA, and is subject to Apple’s Privacy Policy. You can disable iCloud Backup for KLIVA in iOS Settings → [Your Apple ID] → iCloud → Apps Using iCloud.
3.3 Usage Measurement (only with your consent)
KLIVA wants to understand how the app is used so we can improve the training. Examples: At which exercise do many people stop? Is the suggested plan started as it is? Do people come back after a few weeks? From the same measurements we build summary figures across everyone who shares (for example how many are still training after four weeks), which we also show to funding programs or investors. These are only totals and shares, never single installations.
Only if you agree. Near the end of the setup, before your week, we ask you once whether you want to share usage measurement (“Share usage” or “Don’t share”). Both answers are equal and lead on; the app works the same either way. If you set KLIVA up before this question existed, you are asked once on the first start after the update; the question cannot be swiped away, so you decide once on purpose, and we do not ask again. If you say no, KLIVA sends nothing and does not create an identifier for measurement on your device. Until you answer, the measurements of the setup only exist in memory and are discarded if you say no.
What is measured (only with consent):
- App and setup: app opened (after returning from the background, or at start). Which setup page was reached, whether you went back, which run it is. Your answers only as coarse choices: goal, level, the pull-up range, training days per week, whether fixed days, maximum length in minutes, how many pieces of equipment you chose, whether reminders and which skills you chose. Never your name, birthday, weight or height.
- Audience (on every event): So we can see how use differs between groups, all events carry a few coarse details from your profile: your sex (female, male, or “not given” if you did not say), your age group (for example “25 to 29”, worked out from your birthday, which never leaves the app), your goal, your level, whether you use autopilot or fixed training days, how many training days a week you plan, the calendar week in which you started with KLIVA, the kind of your current place (for example home or hotel, never where it is) and which equipment you have there (for example a pull-up bar, rings). These are the state at the time of the event. They do not belong to a name or an account, only, like all events, to the random installation identifier.
- Plan: suggested workout shown and started, and whether you shuffled it, swapped an exercise, changed its length or rebuilt it for another place first. Which exercise you swapped, with its place in the list of suggestions. A different workout chosen (kind, format, length). What Today showed (workout, rest day, goal reached, done or empty).
- Workout: start (kind, format, planned length, number of exercises, which workout it is for you, where you started it from, the full hour of the start in your local time, for example “18”; the full hour is also sent when a workout ends and when you open a tile in Explore, never the minute). Which exercises and how many sets KLIVA suggests for a workout (also when you do not start it), for the warm-up, the main part and the cool-down. Also your fitness level as KLIVA currently reads it from your training (“Brand new”, “Beginner”, “Advanced” or “Very advanced”), and how often KLIVA has moved you up to a harder variant of an exercise on its own (a number from 0 to 10). Each exercise, warm-up and cool-down included, with its catalog identifier, its place in the workout, whether it was done or skipped and how many sets; for strength exercises also for how many sets you did fewer or more than planned (only the number of sets, never the reps). If you stop: how, how many percent were done, at which exercise and after how many minutes. At the end: how the workout ended, how many percent were done, how often you paused, extended or skipped a rest, stepped back or started a step over, how many sets were under or over the target (only the count, never the reps), whether warm-up or cool-down was skipped. Also where you stand with your weekly goal, as KLIVA shows it to you: whether this workout counts toward the weekly goal (a snack, a minute challenge or a short extra does not), on how many days you have trained this week, whether your weekly goal is met and how many weeks in a row you have met it (a number up to 52; it includes weeks before your consent, but only as this one number). Without a weekly goal only the first two. These details are only numbers and yes or no, without a date. For a challenge only whether it was your first try, a record, equal or below, never the number.
- Explore and skills: which snack, challenge, classic or goal was opened and started (catalog identifier, place on the shelf), whether you confirmed a missing piece of equipment; which skill you started, paused or resumed and whether you rated your level higher or lower.
- Use: which screens are opened (from a fixed list), which body zone in Progress, whether you want an exercise more or less often, whether you open an exercise’s instructions, which settings you change (only which; the new value only for coarse choices such as goal, level, plan type or number of training days, never for personal information), What’s New opened, the share picture in Progress tapped (period, light or dark picture; whether you actually shared and where is not known to KLIVA), which achievements you unlocked, reminders allowed or not, location for runs allowed or not, opened from a reminder (which kind).
- Technical: how long it takes to build a plan, and if it fails, a keyword for why. Plus app version, iOS version, device model and whether it is a TestFlight or App Store build. When the app opens, also whether reminders are on, off or blocked by iOS.
Of an exercise only its identifier from the app’s catalog is sent (for example squat_pistol), never anything you type. Otherwise only coarse details such as the kind of workout (for example “strength”), whole numbers or yes and no. Every event carries an exact timestamp: when the app recorded it (for the setup pages before your answer: the moment you agreed).
When an exercise hurts: This is never sent. KLIVA learns it on your device only, so future workouts suit you better.
What is never measured: no name, no email, no Apple ID, no advertising identifier (IDFA), no location (neither GPS nor a derivation from the IP address, nor where your places are), no running route, no pace, no distance, no repetitions or weights, no record numbers, no birthday, no body weight, no height, no restrictions or injuries, no time of day of your reminders (only the full hour a workout starts, see above), no time zone, no language, no device name, nothing you type yourself. There is no automatic capture of screens or taps and no session recording.
Installation identifier: If you agree, the SDK creates a random identifier for this installation so events of the same installation can be counted together (for example: is the app still used after two or four weeks?). It is not Apple’s advertising identifier, not linked to an account or your Apple ID, and is created anew on reinstall. KLIVA creates no person profiles. A session identifier also connects the events of one period of use and changes after a longer pause. The identifier is pseudonymous: it connects events but does not say who you are. We cannot tie it to a person and do not collect anything further to do so (Art. 11 GDPR). If you switch the measurement off, the app deletes the identifier on your device; earlier events are then tied to no device.
Provider: PostHog Inc. KLIVA sends only to PostHog Cloud EU (eu.i.posthog.com, data center in Frankfurt). The IP address is not stored (this is set in the SDK and in the project). Use is governed by PostHog’s data processing agreement under Art. 28 GDPR. Where sub-processing takes place outside the EU, the EU Standard Contractual Clauses apply. Nothing is shared with advertising networks.
Legal basis: your consent (section 25(1) TDDDG for storing the identifier on your device, Art. 6(1)(a) GDPR for the processing). Consent is voluntary. Without it the app stays fully usable.
Withdrawal: You can switch the measurement off at any time in the app: Profile → Advanced → “Share usage data”. KLIVA then sends no more events and the identifier is deleted. Events already sent are then tied to no device and are deleted when the retention period ends.
Retention: 1 year, after which events are removed automatically.
Note on crash reports: This consent covers the usage measurement only. Crash reports (see 3.1) still rest on legitimate interest.
3.4 Website kliva.fit
The website kliva.fit (also reachable as open.kliva.fit) shows KLIVA, the legal texts and the pages that duel and snack links lead to. It is a static site with no user account, no forms and no database of its own.
Hosting: The website is hosted as static files, with no program running on the server, by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. When you visit the website, Cloudflare necessarily processes your IP address, the address you requested (without the part after #), date and time and details of your browser (for example browser type and language) to deliver the page and to protect it against attacks. We keep no access logs of our own. In our Cloudflare account we see aggregated numbers (for example visits per day) and, only for requests Cloudflare blocks as attacks, their details for that defence. Cloudflare processes these data on our behalf under a data processing agreement (Art. 28 GDPR, Cloudflare’s Data Processing Addendum); for Cloudflare’s own security purposes Cloudflare’s Privacy Policy applies in addition. Cloudflare answers requests in data centres around the world, usually close to you. Cloudflare bases transfers to the USA on its certification under the EU-U.S. Data Privacy Framework (adequacy decision of the European Commission of 10 July 2023), and alternatively on the EU Standard Contractual Clauses. You can get a copy of the safeguards at support@kliva.fit.
Legal basis: Legitimate interest (Art. 6(1)(f) GDPR) in delivering the website securely and quickly. No website can be delivered without these technical data; we build no profiles from them and measure nothing. You may object to this processing at any time on grounds relating to your particular situation (Art. 21 GDPR).
No cookies, no measurement of our own: The website sets no cookies, uses no browser storage (no local storage), embeds no analytics, advertising or tracking services and loads nothing from other servers: fonts, images and scripts all come from kliva.fit itself. We do not use Cloudflare features that set cookies (such as bot protection with challenge pages) or count visits.
Duel in the browser: On a duel page your browser reads the number, the exercise and the first name from the part of the link after #. The minute, your count and your result stay in your browser and are neither stored nor sent. A first name you choose to type there only goes into the link you send yourself through your device’s share sheet.
Links to the App Store: When you tap “Download on the App Store”, Apple’s App Store opens. From there Apple’s Privacy Policy applies. The link carries the identifier of our App Store account and one word for the place you came from (for example ct=duell), nothing about you. This lets App Store Connect show us how many downloads come from there. Apple only shows us aggregated numbers, never individual people.
Email: If you write to support@kliva.fit, we process your email address and your message to answer you (Art. 6(1)(f) GDPR; for a request about your data protection rights Art. 6(1)(c) GDPR) and delete them once the request is done and no retention duty applies. The mailbox is hosted by the email service of our domain provider Namecheap, Inc. (USA).
4. No Additional Data Transfers
Apart from the services named in section 3 (and Cloudflare when you visit the website, see 3.4), KLIVA does not transfer data to:
- Advertising networks
- Other analytics services beyond the usage measurement in section 3.3, which only runs with your consent (no Google Analytics, Firebase, Amplitude, Mixpanel, AppsFlyer, Adjust, Branch, etc.)
- Social networks
- Our own backend servers (KLIVA has no backend server)
No sale of data. KLIVA does not sell your data and will not sell it.
There is no user account, no email registration, and no user identification (for the random installation identifiers of Sentry and PostHog see 3.1 and 3.3).
No advertising identifiers, no cross-app tracking. KLIVA does not access Apple’s Advertising Identifier (IDFA), does not use the App Tracking Transparency framework, and does not embed any tracking, attribution, or advertising SDK. KLIVA’s iOS Privacy Manifest (PrivacyInfo.xcprivacy) declares NSPrivacyTracking = false with an empty tracking-domains list, which Apple verifies at App Store review.
5. Data Retention
| Data | Retention |
|---|---|
| Profile data | Until you delete it or uninstall the app |
| Workout data | Until you delete it or uninstall the app |
| Location data | Part of workout history, until you delete it |
| Sentry crash reports | 30 days (Sentry Developer-tier retention; older events removed automatically) |
| Usage measurement (PostHog, only with consent) | 1 year (PostHog plan retention; older events removed automatically) |
| Notifications | Local only, managed by iOS |
| Website (Cloudflare) | No logs of our own; Cloudflare processes technical data only as long as delivery and protection need it |
| Emails to support@kliva.fit | Until the request is done, unless a legal duty requires longer |
6. Your Rights (GDPR)
You have the following rights regarding your personal data:
- Access: know what data is stored about you
- Rectification: correct inaccurate data
- Erasure: have your data deleted
- Restriction: restrict processing of your data
- Data Portability: receive your data in a machine-readable format
- Objection: object to data processing
- Withdraw Consent: revoke any consent given at any time
Since all data is stored locally on your device, you can exercise most rights directly:
- Edit profile data: In the app under Profile
- Delete workout data: Single workouts cannot be deleted in KLIVA 1.4. You delete all data by uninstalling the app; write to us if you need help.
- Delete all data: Uninstall the app
For requests regarding Sentry or PostHog data, contact us at the email address above. We cannot tie the events of the usage measurement to a person (Art. 11 GDPR, see 3.3). You can withdraw your consent to the usage measurement at any time in the app (Profile → Advanced → “Share usage data”).
Right to Complain: You have the right to lodge a complaint with a data protection supervisory authority.
7. Children
KLIVA is not directed at children under 13. We do not knowingly collect data from children under 13. Usage measurement (3.3) is offered from age 16 only: anyone younger, or without a birthday in the profile, is not asked and not measured. If you are a parent or guardian and believe your child is using the app without your consent, please contact us.
8. Changes to This Privacy Policy
We may update this privacy policy as needed, for example when adding new features or due to changed legal requirements. The current version is always available in the app (Profile) and at kliva.fit/en/privacy.
9. Contact
For privacy-related or app-related questions, contact: support@kliva.fit.
Responsible developer details and the non-commercial status statement are listed in Section 1.1 above, name and address in the legal notice.
10. Health Notice
KLIVA helps you plan workouts at home. It is not a doctor, not a personal trainer, and not a substitute for professional medical advice, diagnosis, or treatment.
- Before you start: If you have a health condition, an injury, are pregnant, or are unsure whether exercise is safe for you, speak with a doctor first.
- While training: Stop immediately if you feel pain, dizziness, or unusual discomfort.
- Guidance: KLIVA’s workout suggestions, exercise descriptions, and progression recommendations are general guidance based on the information you provide. Form, technique, and load are your decision.
- Liability: The law applies. Liability is not excluded or limited for injury to life, body, or health, or in any other case where the law does not allow it.
You see this notice at the end of the setup, right below the button that takes you to your first workout. That you have seen it is stored locally in your user profile with a timestamp.