Privacy policy
Last updatedWhat Kiloton stores
Your training stays on your phone: lifts, sets, weights, reps, effort ratings, tested maxes, bodyweight if you enter it, notes and settings. The app keeps it to plan your next set and show your history. There is no account, no sign-in and no server that holds it, so it never reaches us. Deleting the app deletes it.
What leaves your phone
Usage counts go to PostHog and crash reports go to Sentry, both on servers in the EU. The app sends nothing anywhere else.
Every request also carries your phone's internet address, as any connection does. The app asks neither company to record it, and PostHog is set to discard it.
When you first open the app, it asks whether it may count how the app is used. Nothing is counted until you answer. After that it counts either way, and your answer decides only whether it remembers you between visits.
It counts five things: opening the app, starting a session, logging a set, finishing a session, and switching between RPE and RIR. Each count carries its name, the time, random ids that tell counts apart, your screen size and the version of PostHog's library. It never carries what you lifted or typed.
- Yes. A random id is saved on your phone, so we can see when the same person comes back.
- No. The id lives in memory only and is new each time you open the app. Nothing is saved on your phone, and your visits cannot be joined.
You can change your answer in Settings → Usage counting. Switching from yes to no deletes the saved id from your phone, but not what PostHog already has.
Under yes we count with your consent. Under no we count on our legitimate interest in finding where the app lets lifters down. PostHog keeps counts for one year.
Backups and exports
A backup or a spreadsheet export is a file you make and send where you choose. It never comes to us. Your phone's own backup to Google or iCloud can include the app's data, and that copy is between you and Google or Apple.
Crash reports
When you first open the app, it asks whether it may send crash reports to Sentry, on the same screen as usage counts and as a separate answer. Nothing is sent until you say yes, and you can change the answer in Settings → Crash reports. We send them with your consent.
An error in the app's own code is rebuilt from a fixed list of fields before it is sent. The list includes the kind of error and where in our code it happened, the app's version and build, whether it is a released or a test build, the phone's make, model, chip family and system version, whether it is an emulator, the JavaScript engine's version, and recent notices such as the app opening or closing, memory running low or the connection changing. It carries no training data, no device name and no error message.
A crash deeper in the phone is put together by the phone before the app sees it, so the app cannot trim it. It carries a random installation id that Sentry's library keeps on your phone, the error's own message, and many details about the phone. On an iPhone it also carries an id that the library builds from the phone and the app. That id is worked out from the same details each time, so it comes out the same and cannot be deleted.
If you say no, the app deletes the file where the library saves the installation id. The library still remembers it until the app closes. We have not confirmed that the deletion works on an iPhone. Saying no does not delete reports Sentry already holds.
Sentry keeps crash reports for 30 days.
Children
Kiloton is not made for children. It asks no one's age.
Changes to this policy
When what the app sends changes, this page changes with it and the date above moves.
How to reach us
Kiloton is run by Mikael Järvinen, Finland, who is responsible for the data on this page. Write to support@kiloton.app.
You can ask what we hold about you and have it corrected or deleted. You can withdraw consent in Settings, and object to counting that rests on our legitimate interest. You can also complain to the data protection authority where you live.
Counts and crash reports carry ids you never see, so we usually cannot tell which records are yours.