Last updated 14 September 2026
Training Journal is a personal, single-user application operated by Alexis de Coninck. It has one user: its owner. This policy describes how it handles that person's data.
With your explicit consent at sign-in, the application reads the following from the Google Health API, for your own account only:
| Category | Examples |
|---|---|
| Activity and fitness | Workout sessions, type, duration, distance, steps, calories |
| Health metrics | Heart rate, heart-rate variability, resting heart rate, respiratory rate, blood-oxygen saturation, body weight, body composition |
| Sleep | Sleep periods and sleep stages |
| Location | GPS traces recorded during workouts, used to establish which timezone a session was recorded in |
| ECG | Electrocardiogram readings recorded by the wearable |
It also stores free-text notes you type into the application yourself, such as a short description of what you ate.
Solely to display your own data back to you: charts of training volume, heart-rate zones, sleep, recovery trends and body weight, and a short written summary of what those numbers mean. There is no other purpose.
Your data is not used to train machine-learning models, build advertising profiles, perform analytics about you, or develop any product.
In a private database on a server controlled by the owner. It is not published, not indexed, and not reachable without authentication. Access requires signing in with the owner's own Google account; no other account is permitted.
It is not sold, rented or traded, ever, to anyone. It is not shared for advertising or marketing. There is exactly one third party involved:
Anthropic. To write the daily and weekly summaries, a condensed set of your recent figures, such as sleep duration, heart-rate variability, session types and durations, and any food notes you typed, is sent to the Anthropic API, which generates the summary text. This happens once or twice a day. Anthropic's handling of that data is governed by their own privacy policy and commercial terms.
If you do not want this, the summary feature can be disabled and no data leaves the server at all.
The hosting provider necessarily processes data in transit and at rest as infrastructure. Aside from that, and from Anthropic as described above, no data is transmitted anywhere.
Health data is retained for as long as the owner wants the history, since the point of the application is multi-year trends. High-resolution heart-rate samples older than 90 days are automatically discarded; only summary figures derived from them are kept.
You may revoke the application's access at any time at myaccount.google.com/permissions. Revoking access stops all further data collection immediately.
To have all stored data deleted, email the address below. The database is a single file; deleting it removes everything, and this is done on request without conditions.
Access tokens and credentials are stored with restricted file permissions and are never committed to source control. The application is reachable only over an authenticated, encrypted connection, and only the owner's account is allowed through. No payment details are handled and no passwords are stored.
Training Journal's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
This application displays consumer wearable data. It provides no diagnosis, no treatment, and no medical advice, and is not a medical device.
If this policy changes, the date at the top of this page changes with it.
Alexis de Coninck, alex@ac-design.studio