Privacy Policy

Kelbria FitNotes is published by DEPIBIO SRL, a company registered in Romania. Kelbria is the brand; DEPIBIO SRL is the legal entity, and it is the data controller for the purposes of the GDPR.

This policy covers the Kelbria FitNotes app. The kelbria.app website has its own privacy policy, and it describes different processing — a website and an app do not do the same things. The same company is the controller for both.

Privacy policies often blur three separate matters. This one keeps them apart, because for Kelbria FitNotes the answers are different in each case.

Kelbria FitNotes writes what you enter to the app's own storage area on your device. Workout data includes active and completed workouts, History, exercises, sets, weight, repetitions, duration, distance, notes, RPE or reps in reserve, workout timing and relevant rest state.

Workout plan names, exercise order, target sets and target metrics are stored locally, together with plan-related configuration. Guided execution state remains local while a planned workout is active. Repeating a workout creates ordinary workout data, and the Workout Calendar is only a local view of History — FitNotes does not access your device calendar.

Custom exercises, Favorites and preferences are stored locally. Preferences include units, language, appearance, rest and timer settings, notification preference and Keep Screen On preference.

If you use Body & Progress, FitNotes stores the height and body-weight measurements you enter, including measurement date and time. BMI is calculated locally from your current height and recorded weight; it is not stored as an independent collected value, imported from Apple Health or measured automatically.

A raw pre-migration workout copy may be retained locally as an internal migration safeguard. It is not a current rolling backup, a user backup or a guarantee that data can be recovered after loss.

FitNotes has no account system, cloud sync or backend that receives workout, body, plan or settings data. It does not automatically upload that data, a device identifier, crash report or usage statistic to Kelbria.

The app can open public Privacy, Terms and Support pages when you tap their links. That browser navigation does not attach your locally stored fitness data.

When you choose Export data, FitNotes creates CSV files locally and then presents the iOS sharing interface. An export may contain completed workout History, plans, custom exercises and Body & Progress measurements. It excludes the unfinished active workout and derived BMI.

FitNotes does not automatically transmit exported data to Kelbria. Data leaves the app only when you explicitly choose a destination, such as Files, Mail, AirDrop or another application or service, using the iOS sharing interface.

A copy saved or sent outside FitNotes is controlled by the destination you choose and is not encrypted or password-protected by FitNotes. Choose destinations carefully. FitNotes cannot automatically find or delete those external copies, and CSV import is not available in version 1.0.

When you choose Send Feedback or Request a Feature, FitNotes opens your device's e-mail handler with our approved address and a FitNotes-related subject. The app does not automatically attach workout, body, plan, diagnostic or device data.

You control the message, any attachments and whether it is sent. If you send it, we receive and process what you chose to include as support correspondence; that is different from locally stored fitness data.

The app contains no analytics, crash-reporting, telemetry, advertising, attribution or tracking software. It does not read the advertising identifier.

Under Apple's definition, tracking means linking data from this app with data from other companies for advertising or measurement, or sharing it with a data broker. Kelbria FitNotes does none of that, so it does not ask for App Tracking Transparency permission — an app that does not track should not be showing that prompt.

FitNotes does not request access to Apple Health, location, the camera, photos, the microphone, contacts, Bluetooth, Motion & Fitness data, tracking or similar sensitive data sources in version 1.0.

FitNotes can optionally notify you when a rest timer finishes. Notification permission is not requested when you first launch the app. It is requested only if you choose to enable rest-complete notifications in FitNotes Settings.

A rest-complete notification is scheduled locally on your device. FitNotes does not use a remote push service or a Kelbria notification server, and it does not send Kelbria a push-notification token, workout data or notification content for this feature. The notification is deliberately generic and does not include workout details.

Granting notification permission is optional. If you do not grant it, workout logging and the rest timer inside the app continue to work. You can turn the feature off in FitNotes and control notification permission through iOS Settings. FitNotes does not use rest-complete notifications for advertising or marketing.

FitNotes provides no cloud backup, cross-device sync or guaranteed restore. The local storage used by the current build is excluded from iOS backup by default, so you should not rely on iCloud Backup or a device backup to restore FitNotes data. Kelbria has no access to your device backups.

Settings includes Delete All App Data. After two confirmations, it removes FitNotes-owned user data stored locally on the device, including workouts and History, active-workout recovery, plans, custom and favorite exercise state, Body & Progress records, settings and preferences, rest state, local recovery or legacy data, and FitNotes-owned export cache files.

The in-app notification preference resets and a scheduled FitNotes rest alert is cancelled, but iOS notification authorisation is controlled separately in iOS Settings and may remain granted.

App-owned fitness data stays on your device until you delete supported records, use Delete All App Data or delete the app. Kelbria does not hold an automatically uploaded copy and therefore has no server retention period to apply to it.

Support e-mail is different: we keep a message for as long as it takes to answer it and to keep a reasonable record of the exchange.

Kelbria FitNotes is a general-audience app. It is not directed at children, it has no child-specific features, and it does not ask for a date of birth or verify age. It does not automatically upload fitness data to Kelbria from children or other users.

Your training data is held in the app's storage area on your device and is protected by your device's own protections — your passcode, Face ID or Touch ID, and iOS file protection. Anyone who can unlock your device can open the app.

No system is perfectly secure, and this policy does not claim otherwise. Core workout, plan, body and History data is processed locally and is not automatically uploaded by FitNotes. A file or message you explicitly share is then protected and handled by the destination you selected.

If you write to support, your message reaches us with whatever you chose to put in it — your e-mail address, and anything else you include such as a description of a problem or a screenshot. We use it to answer you.

Our mail is handled by Google (Gmail), which delivers and stores messages on our behalf. Sending us an e-mail therefore means it passes through and is held by Google under their terms as well as ours.

Where data protection law applies to you, you have rights over personal data held about you — access, rectification, erasure, restriction, objection and portability. For data inside the app you exercise these directly: it is on your device and you control it, and we could not act on it if we wanted to. For support correspondence, write to us and we will act on it.

Support e-mail is carried by Google, which is established outside the European Economic Area, so correspondence you choose to send may be processed outside the EEA under the transfer safeguards Google operates. No such transfer arises merely from storing or using fitness data locally in FitNotes.

If this policy changes, the revised version is published at this address and the effective date above is updated. Where a change is material, it is described in the app's release notes.