Privacy Policy

Kelva is a training app for women, run by Alain Kessler, a sole proprietorship in Switzerland. We are the controller for the data described here. Questions, requests and complaints go to kelvasupport@gmail.com.

You plan a training week and tick sessions off. If you allow it, the app adapts today's session to how recovered you actually are — read from your sleep, your cycle day and a one-tap daily check-in. The programme itself is never changed. Friends can be linked and see only whether the weeks got done.

We store your email address, a display name, and an avatar emoji if you pick one. Signing in with Apple or Google gives us only the identifier and the email address you release there — we never see the password you use with them.

If you allow it, Kelva reads two things from Apple Health: how long you slept last night, and your cycle. Both are special-category health data under Article 9 GDPR, and we treat them accordingly.

You allow each one separately. If you only want to share sleep, you do not have to hand over your cycle — and the other way round. Without either, the app still works; it simply runs on your daily check-in alone.

We never write anything back to Apple Health. The app requests read access only.

Your sleep, your cycle day and your daily check-ins are stored and calculated on your iPhone only. They are not sent to our server, not included in any backup we hold, and not passed to your partner.

That is not a statement of intent but the current shape of the app: no server endpoint exists for these values. If that ever changes, this text changes with it — and it will cost you a fresh, explicit consent.

Only whether you completed your planned week, as a count of finished sessions against the number you planned.

Not just the current week. A linked friend sees that count for every week since the two of you connected, as a history. It never reaches further back than the day you linked up — a new friendship opens nothing retroactively — and unlinking ends the access immediately.

Two further things can be released, each with its own switch, each off by default, both on the friends screen in the app: how many days in a row you have followed your plan, and your training week itself — which days and times you train, with the names you gave the sessions. A friend can then also adopt your week as her own. Turning either off clears what was shared rather than leaving the last version standing.

A friend can ask you to show her your training week. That is a request and never a release: it switches nothing on, the decision stays with you, and she can ask again at most every three days.

Nothing else. Not your cycle, not your sleep, not your check-ins, and not what or how heavy you trained.

With no friend linked, nobody but you sees any of it.

Your weekly plan also lives on the device. If you turn on calendar export, Kelva writes the sessions into a calendar of its own on your iPhone — only into that one, never into your others.

If you pair with a partner by knocking two phones together, an approximate position is sent at that moment. It is used solely to check that the other person is actually next to you rather than knocking somewhere else in the world at the same second.

The coordinates are coarse, not precise, are deleted within an hour, and are used for nothing else. Pairing by code or QR never asks for them. Without this permission only bump stops working; everything else is unaffected.

Tapping "scan a QR code" opens a viewfinder that reads one partner invite code. No frame is written to disk, kept after the read or sent anywhere. What leaves the device is the invite code you then confirm.

If you allow notifications we store a push identifier for your device, so reminders about your sessions and your partner's weekly result can reach you. You can withdraw this at any time in iOS Settings.

When the app crashes we receive a technical report — the error, the line of code, the device model and the app version. It is used to fix the crash and nothing else. It carries no health data, because none of it is on our servers to carry.

Kelva Plus is handled entirely by the App Store. We never receive or store your payment details. Through RevenueCat we learn only whether an active subscription exists for your account. Subscription management and cancellation happen in your Apple ID settings.

Each one receives only what its job needs:

• Supabase — account and database, hosted in Frankfurt, Germany (eu-central-1)
• Apple — sign in, billing, push delivery
• Google — sign in, if you choose that route
• RevenueCat — whether a subscription is active
• Expo — delivering notifications to your device
• Sentry — crash reports, on our own server

There is no advertising, no tracking across other apps or websites, no data broker, and no sale of your data. We do not use the App Tracking Transparency framework because there is nothing to track.

Account data stays for as long as your account exists, and goes when you delete it. Bump coordinates are swept within the hour. Crash reports are kept only as long as they are useful for fixing the crash they describe. Health and training data are on your device only, so they are not ours to keep — they go with the app when you delete it.

Under the GDPR and the Swiss FADP you may request access, correction, deletion, restriction of processing, and a copy of your data in a portable form. You may also object to processing and complain to a supervisory authority.

You can delete your account entirely from inside the app — Settings → Delete account. That removes your account, your partner links and your weekly counts. For anything else, an email to kelvasupport@gmail.com is enough.

Kelva is not directed at children. You must be at least 16 to have an account, or the minimum age of digital consent in your country if it is higher.

If what we process changes, this page changes with it and the date at the top moves. Anything that widens what we collect — in particular any health value leaving your device — is announced in the app and asks for your consent before it happens, not after.