Last updated: 23 September 2026 · Applies to Trainlog for Android, iOS, Wear OS and the Apple Watch
The rest of this page explains that in detail. It is written to be read, not to protect us.
Trainlog is published by Berrhout Solutions, Calandplein 14, 2521 AE Den Haag, the Netherlands (KvK 42139755). In data-protection terms we are the "controller" for the small amount of information described below.
You can reach us at trainlogfeedback@gmail.com, or through Send feedback in the app (Profile → Feedback).
Trainlog records what you enter so it can show it back to you:
When you log sets or keep score on an Apple Watch, Trainlog saves the session to Apple Health as a workout — strength training while you are logging sets, and the sport itself while you are scoring a match. This is what lets the watch keep your place instead of returning to the clock: watchOS gives an app no other way, and a workout session is the only kind that honestly describes training or playing a sport. The screen still dims when your wrist drops — nothing here keeps the display switched on.
What is written is the activity, the start time and the end time. Nothing else. Trainlog asks only for permission to save a workout; it never asks to read your health data, and it records no heart rate, calories or any other measurement. You can decline the permission and carry on using the watch exactly as before — you will only lose the staying-put part.
The workout stays on your device, in Apple Health, under your control. If you have switched on iCloud syncing for Health in your own iOS settings, Apple syncs it the way it syncs the rest of your Health data; that is a setting of yours and Apple's, not something Trainlog does or can see.
All of this is stored only on your device, in a database encrypted with AES-256. The key is generated on your phone and held in the Android Keystore or the iOS Keychain — hardware-protected on most devices. It is never sent anywhere and never included in a backup.
What this means in practice: we have no copy of your training data. If you write to us and ask what we hold about you, the honest answer is nothing. It also means that if you uninstall the app or reset your phone, the data is gone for good, because the key goes with it.
Trainlog has no field for your name, your email address or your gender. Early versions asked for gender; we removed it, because nothing in the app used it and collecting health-related data you do not need is exactly what a privacy policy should not have to excuse.
| What | When | Who receives it |
|---|---|---|
| A backup file Your profile, plan and history |
Only when you tap Export data | Wherever you send it — your email, your cloud drive. Not us. |
| Feedback Your message, the kind you picked, the app version, and whether you use Android or iOS |
Only when you tap Send feedback | Us, through Netlify, which hosts this page and forwards it to us — see section 9 |
| Subscription status Whether Premium is active |
If you subscribe | Apple or Google, and RevenueCat — see below |
| A session as a workout Activity, start time, end time |
If you log sets or score a match on an Apple Watch | Apple Health on your own device. Not us, and never the internet. |
| Plan and sets | Continuously, if you use a watch | Your own watch, over the direct link it already has with your phone. Never the internet, and never through us. |
That is the complete list. There is no analytics SDK, no advertising network and no crash reporter in Trainlog.
If you subscribe to Premium, the payment is handled entirely by Apple or Google. We never see your card details, your billing address or your name.
We use RevenueCat to check with the store whether your subscription is active. RevenueCat receives an anonymous identifier generated on your device and the receipt from the store. It does not receive your training data, your body metrics, your name or your email — we never log you in, so there is nothing to link.
You can cancel at any time in your Google Play or App Store settings. Cancelling does not delete anything on your phone.
A backup file contains your full training history and your body details. Once you export it, it is in your hands and this policy no longer controls where it goes — that is the point of it being yours.
Because people email these files to themselves and drop them in cloud drives, Trainlog offers to encrypt the file with a passphrase you choose. If you use one, the file is unreadable without it. We cannot recover a forgotten passphrase, and neither can anyone else.
Trainlog is not intended for children under 13, and the app does not accept an age below 13.
Under the GDPR you have the right to see, correct, export and delete your personal data. Trainlog gives you all four directly in the app, without asking us:
Because your training data never reaches us, there is nothing there for us to hand over or erase on your behalf — it is already entirely in your hands. The one exception is feedback you have sent us, which we will delete on request; see section 9. If you disagree with how we have handled your data, you can complain to your national data-protection authority (in the Netherlands, the Autoriteit Persoonsgegevens).
Feedback is the one thing that reaches us directly. When you tap Send feedback, the app sends your message straight from the app — no mail app, no account.
What is sent: the message you typed, the kind you picked (a bug, an idea, something else), the app version, and whether you use Android or iOS. Nothing else: no training data, no body details, no device identifier. There is no field for your name or email address; if you want an answer, you can put your email in the message yourself, and then we have it because you gave it to us.
How it travels: the message is received by Netlify, Inc. (United States), the company that hosts this page, which processes it on our behalf. Netlify filters out spam, keeps the message in our site dashboard and forwards it to us by email. Like any website, Netlify can see the internet address the request comes from; we do not use it.
We use your feedback to answer you and to fix what you reported, nothing else. It is never used for marketing, never added to a mailing list and never shared. We delete feedback within 12 months — from the Netlify dashboard and from our inbox — and sooner once the issue it describes is resolved. If you would like your message deleted before then, ask and we will do it.
If we change what Trainlog does with your data, we will update this page and the date at the top. If a change is significant — anything that would send more of your data off your device — we will tell you in the app before it takes effect, and ask first.
Use Send feedback in the app (Profile → Feedback), or email us at trainlogfeedback@gmail.com. Our postal address is in section 1.