Styxon Studio LavaFit

Privacy policy

Updated 15 November 2026

What LavaFit stores, what leaves your phone, and what you can do about it.

The short version

LavaFit stores your training data on your phone. This policy lists what the app sends to our server, when, and why.

At present that is four things. The optional cloud backup is sent when you sign in with Google or Apple, and the AI coach’s online mode when you read a notice and then send a question, ask for a programme, or import one from a photo. Anonymous usage statistics are sent by the app itself unless you switch them off in Settings — they carry no content and no identity, and they are described in full below. Each of these requests also carries the app’s version number and whether the phone runs Android or iOS, so our server can recognise an app too old to understand and ask you to update it.

The fourth is a check the app makes by itself: when it starts, and again when you come back to it after some hours, it asks our server whether there is a notice for everyone who uses LavaFit — for example about a break in service or a security incident — and shows it once. That request carries nothing but the app’s version and platform; like any request, it shows our server the phone’s internet address, and nothing about it is stored.

Apart from our server, an outdoor route’s map is fetched from Google Maps on Android and Apple Maps on iPhone; what they see then is under Permissions below.

No ads, no trackers, no selling of data. If something in this policy is unclear, write to us — the address is in the next section.

Who is responsible

Styxon Studio (sole trader Tatu Ylönen, business ID 3321575-3, Finland) publishes LavaFit and is the data controller — the one responsible for how your data is handled — for everything described in this policy.

Questions about this policy or your data: privacy@lavafit.app.

What the app stores on your phone

Everything below is either entered by you or worked out by the app from what you entered. It is kept in the app’s own storage on your phone.

Android backup

Android’s own backup is switched off for this app. Your phone does not copy LavaFit’s data into your Google account’s backup, and it does not hand it to a new phone during the device-to-device transfer at setup. Nothing of your training log leaves the phone that way.

That means a new phone starts empty unless you use the cloud backup below, or export your log as CSV first. It is off so that the app’s own backup below, which you switch on yourself, is the only place your full training log is kept outside this phone.

iPhone backup

On iPhone the app’s data is not left out of the phone’s own backup. If iCloud Backup is switched on, or you back the phone up to a computer, LavaFit’s data goes into that backup together with the data of your other apps, and comes back with it when you set up a phone from it. That backup is made and kept by Apple or on your own computer, under Apple’s terms. We do not make it, cannot see it and cannot delete it.

If you would rather LavaFit’s training log is not in it, you can leave LavaFit out of an iCloud backup in your iPhone’s iCloud settings, or switch iCloud Backup off. The cloud backup below is separate: it is the only copy of your training log that we hold, but not the only copy outside your phone — an iPhone backup is one more, kept by Apple or on your computer.

Cloud backup (optional)

If you sign in with Google or Apple, a copy of everything listed under “What the app stores on your phone” — except a workout still in progress — is sent over an encrypted connection to our server and kept there, so a new phone can restore it after you sign in again. Signing in is never required; every feature works without it.

From Google we receive your Google account’s identifier, your email address and your name. These stay on your phone, so the app can show which account is signed in. On the server the backup is filed under a scrambled version of the identifier; your email and name are not stored there. When you sign out, the phone keeps only the identifiers of the accounts that signed out of it, so that if a different Google account signs in next, the app asks before backing up the data already on the phone to it; they are removed once that sign-in is settled.

On iPhone you can sign in with Apple instead. From Apple we receive an identifier for your Apple ID that only LavaFit gets, and the first time only, the name and email you choose to share — the email can be a private relay address that Apple forwards. They stay on your phone like Google’s. The phone trades Apple’s sign-in once for a sign-in of our own, kept on the phone, that lasts up to 180 days and is checked on every backup request; before using it, the phone asks Apple whether you have stopped using your Apple ID with LavaFit, and signs you out if you have. Deleting your account (below) also ends LavaFit’s Sign in with Apple: Apple asks you to confirm once and gives your phone a one-time code, which our server passes to Apple to end the sign-in and does not keep. That takes LavaFit off the list of apps you use Sign in with Apple with; should it still be there, you can remove it yourself in your iPhone’s Apple ID settings.

A backup is sent shortly after you log training, and whenever you press Back up now. The server checks your sign-in on every request, stores the file, and hands it back only to the same account. It does not read, analyse or log the contents.

The backup is stored by Vercel, our hosting provider, in the European Union. It is kept until you delete it.

Settings → Delete cloud backup removes the server copy immediately. Signing out does not delete it, and neither does resetting the phone’s data — a reset signs you out first, precisely so that an empty backup never overwrites a full one. The copy waits until you sign in again. If you can no longer open the app, delete a Google account without it at styxon.fi/vinha-fitness/legal/delete-account.en: you sign in with Google on that page, and it deletes the server copy as Delete account does. The coach copies described below are filed under your phone, not your account, so that page cannot reach them; they are deleted automatically within 24 months. You can also sign in on any phone with the same account and delete it there.

Settings → Delete account does the same and more: it deletes the server copy, signs you out on this phone, asks our server to delete any copies the AI coach kept for you (only if you had allowed that, as described under “The AI coach”), and, for an Apple account, ends both the sign-in our own server gave it and LavaFit’s Sign in with Apple at Apple (above): your other phones signed in with Apple are signed out at their next request to our server, and a sign-in made with Apple before the deletion can no longer be used to start a new one. The training data on this phone stays; Reset all data clears that separately. The anonymous usage statistics are not tied to your account, so deleting it does not delete them; they are kept for up to 24 months, as described under “Usage statistics”. Apart from those, our server holds nothing of yours afterwards except, for an Apple account, one scrambled marker with a date, which says that sign-ins made before it have ended, so that an old sign-in cannot be used again. It also holds a random number your phone made for that request, used only to tell that phone its deletion went through. It holds no name, email or training data.

Settings → Reset all data deletes everything on this phone and signs you out. It keeps the cloud backup, which waits for you as described above, and it keeps your answer about usage statistics: if you had switched them off, they stay off.

The AI coach

The coach has two modes. In on-device mode, the default, answers are put together on your phone from your own log, and nothing leaves the device — not the question, not the answer.

In online mode, which a version of the app switches on, the app shows you a notice before your first question, and nothing is sent until you have read it. After that, each question you send carries three things: the question, the earlier messages of the same conversation, and a summary of your training.

The summary contains your recent workouts (exercise names, sets, reps, kilograms, dates, durations), your current programme and its week, your goals, your setup answers (goal, level, days per week, equipment, limitations), the coach’s own answers from the last three weeks in one sentence each, so it does not repeat advice you have already had, and — if you have logged them — your latest weight, tape measurements, height, age and gender.

It does not contain your name, your email, your Google account or any identifier of your phone. Our server sees the phone’s internet address, which it holds briefly in memory to limit how many requests one connection can make; it is not stored.

Each question, programme request and photo import also carries the anonymous purchase id RevenueCat gave this installation of the app (the one described under RevenueCat below; it is not your Google or Apple account). Our server uses it for two things only: to count how many coach requests this installation has made this month, and to ask RevenueCat whether it has Pro. It keeps a scrambled form of the id with that month’s count and RevenueCat’s answer — never beside a question — and deletes it after the following month. The id is not sent to Anthropic.

Our server forwards the question to Anthropic, the company behind the Claude model, which writes the answer in the United States. Under Anthropic’s commercial terms the data is not used to train its models and is deleted within 30 days.

We keep no copy of our own. The coach does not store your questions and answers, the programmes you ask it to build or the photos you import one from; they are sent, answered from and dropped. An earlier test version could ask for permission to keep such copies. If you said yes there, the copies filed for you are deleted automatically within 24 months of the day they arrived, and you can delete them now: the permission shows in Settings only for someone who gave it, and switching it off removes every copy kept for you.

The programme composer works the same way: when you ask the app to build a programme from a written brief, the brief and the same summary are sent along the same route.

Importing a programme from a photo also uses this route. The photo you picked is scaled down and sent so the table in it can be read; it is used for that one import and is not kept by us.

Under each answer the online coach writes there is a Report link. If you use it, the answer you reported and the reason you picked are sent to us so that a person can review it — not your question, and nothing that identifies you. The report reaches us through Slack, the messaging service we review reports in, and is deleted once it has been dealt with, at the latest after 24 months.

Usage statistics

To see whether the app works — for example whether some step of the setup is so hard that people give up there — the app sends anonymous usage events to our own server.

An event is a name and a time, plus for setup steps the step number and which path you took, and for an error report the details listed below. Never the content: no exercise name, no weight, no measurement, no question text. The full list of events is fixed in the app’s code, and the server refuses anything outside it.

If something goes wrong, the app also sends an error report, as one more of these events: a crash, an error on a screen, or a save, backup, restore, sign-in, account deletion or opening your saved data that did not work. What is sent: the type of error, where in the app’s code it happened (a position in the program, not what it was working on), which screen you were on, the app version, which operating system the phone runs and, for a failed save, backup or similar, which one failed and a short code such as “network” or “storage full”. Never sent: error messages, your training data, names, notes or anything you typed — error messages can contain exactly such things, so they are not collected at all. A crash is noted on the phone as it happens and sent the next time the app is opened. Error reports follow the same switch, go only to our own server and are kept for the same time as the other events.

Each install gets a random identifier, generated on your phone. It is not connected to your name, email, Google account or any advertising identity, and it resets if you reinstall the app.

The events go to our own server and nowhere else. They are kept for up to 24 months and then deleted automatically, and they are not shared, not sold and not used for advertising. You can switch them off at any time in Settings → Usage statistics; the app then sends nothing and throws away whatever was waiting to be sent. These are the events:

Who helps us run this

We run no servers of our own. Six companies process data for us, under contracts that bind them to handle it only on our instructions and only for the purposes described here.

Data outside the European Union

Where data goes outside the European Union — the coach traffic to Anthropic, the answers you report to Slack, your purchase record at RevenueCat, and possibly Vercel’s processing — the transfer rests on the European Commission’s standard contractual clauses, which are part of each provider’s data processing agreement with us.

Why we may process your data

The GDPR requires a lawful basis for each kind of processing. These are ours.

What the app does not do

Permissions the app asks for

The app asks your phone for very little. What it does use:

Notifications

Notifications come in three groups: while you train (the rest timer and the live session), wins and recaps after a workout, and reminders such as a weigh-in day or a training day. Every one of them is scheduled on your phone by the app itself. They are not push notifications: no server is involved and no device token exists.

Turn any group, or all of them, off in Settings → Notifications, or in your phone’s own notification settings.

Payments

If you buy Pro, the payment is handled entirely by Google Play on Android and by Apple through the App Store on iPhone. We never see your card number, billing address or any payment detail. The app learns only whether Pro is active, which plan, and until when.

The app has no free trial of its own. If a promo code or an earlier free trial still keeps Pro on, it stops on its own on the date shown in the app, nothing is charged when it ends and nothing is sent anywhere.

Feedback, rating and sharing

Send feedback opens your own mail app with our address and the app version filled in. You decide what to write. We then see your email address and your message, and keep them only as long as it takes to handle the feedback.

Rate LavaFit opens the app’s page on Google Play on Android, and Apple’s review prompt or the app’s page on the App Store on iPhone. The app itself sends nothing.

Exporting a programme or your training log as CSV, and inviting a friend, go through your phone’s share menu to the app you pick. We never see where they go.

Security

Everything that leaves your phone travels over an encrypted connection. On the server, every backup request is checked against your sign-in before anything is read or written, backups are filed under a scrambled identifier in private storage, training data is never written to logs, and request rates are limited.

On your phone, the app’s data is protected by the phone’s own lock and the separation Android and iOS keep between apps; the app adds no encryption of its own. Anyone who can unlock your phone can open LavaFit and see your training data, so keep the phone locked.

How long we keep it

Your rights

Under the GDPR you have the right to see the data we hold about you, to correct it, to delete it, to take it with you, to withdraw a consent you gave, and to object to processing based on our legitimate interest.

Most of these you exercise yourself, inside the app, without asking anyone. For the rest, write to us — we answer within a month.

Children

LavaFit is not intended for anyone under 18, and we do not knowingly process their data. Because nothing reaches us with a name attached, we cannot tell a child’s data from anyone else’s — if you believe a child has signed in for the cloud backup, write to us and we will delete it.

Changes to this policy

If this policy changes in a way that affects you, the app shows the change before it takes effect. The date at the top always tells you which version you are reading, and earlier versions are available on request.