Privacy policy

Who is responsible

The controller for data processing on this website, within the meaning of the GDPR, is:

What this site collects

The beta sign-up form. When you sign up for the beta we store your email address, the name you enter if you choose to enter one (the field is optional), the fact that the signup came from this website, and the date and time. Nothing else. There is no intake form, no questionnaire and no profile on this site.

Server logs. Our hosting providers record technical data for each request in the ordinary way — IP address, time, the page requested, browser and operating system version. These logs are used to operate and secure the service and are not combined with the sign-up data or used to identify you.

Visitor statistics. We use Vercel Web Analytics to count page views and see which sites link to us. It sets no cookie, stores nothing on your device and builds no profile of you across this or any other website. What it records is the page requested, the referring site, and coarse technical details such as country, browser and device type. It cannot be used to identify you, and we never combine it with the waitlist data.

No cookies for tracking. This site sets no advertising or analytics cookies, and embeds no advertising pixels and no social media plugins. The one cookie the site can set is a language preference (NEXT_LOCALE), written only when you switch between English and German yourself, and it records nothing but that choice. The Inter typeface is served from our own servers, so viewing this page sends no request to Google Fonts.

The demo. The “Try the demo” section on the home page loads nothing until you tap one of its two choices. Then it opens the TrainArk web app from trainark.vercel.app, also hosted by Vercel, in a frame on this page, signed in as an invented person with invented data. What you type or tap in the demo is answered inside your browser: it is not sent to our servers and is not saved to any account. Loading the demo is an ordinary request to Vercel, recorded in the server logs described above. To run, the demo keeps which demo you chose and the app's own settings in your browser's storage for that address; clearing your browser's site data removes them.

Why, and on what legal basis

Beta sign-up: to send you the links to install the TrainArk beta on iOS and Android, to keep you updated about the beta and the launch, and to let you into early access. The legal basis is your consent under Art. 6 (1) (a) GDPR, given when you submit the form. You can withdraw it at any time, with effect for the future, by emailing us — see below.

Server logs and security: our legitimate interest in operating a functional, secure website, Art. 6 (1) (f) GDPR.

Language cookie: your own choice of language, strictly necessary to provide the setting you asked for.

Demo: provided because you asked for it by tapping, and the browser storage it uses is strictly necessary to run it.

Visitor statistics: our legitimate interest in knowing whether this site reaches anyone and which pages are read, Art. 6 (1) (f) GDPR. We consider this interest to outweigh the minimal impact on you, because the measurement sets no cookie, is not tied to you, and cannot follow you to other websites.

Who processes it for us

This website is hosted by Vercel Inc. Beta sign-ups are received by our application server, hosted by Render Services, Inc., and stored in a PostgreSQL database operated by Neon Inc.

Vercel also provides the visitor statistics described above, as a processor on the same terms.

Each of these acts as a processor on our instructions under Art. 28 GDPR. Where processing takes place outside the EU/EEA, it is based on the European Commission's standard contractual clauses.

We do not sell your data, do not share it for advertising, and do not pass it to anyone beyond the providers named above.

How long it is kept

Beta sign-ups are kept until TrainArk launches and the sign-up list has been worked through, or until you ask us to delete yours — whichever comes first. Server logs are kept for a short operational period and then deleted or anonymised by the hosting provider.

Founding members. If you are among the first 50 sign-ups, we additionally keep your email address on a separate list recording that you are entitled to TrainArk Pro for life. That entry lasts as long as the entitlement does — so beyond the point at which the sign-up list itself is worked through — because otherwise it would expire at launch, which is when it is meant to take effect. It is deleted as soon as you ask, or when you delete your TrainArk account, and the entitlement goes with it.

Your rights

You have the right to access your data (Art. 15), to have it corrected (Art. 16) or deleted (Art. 17), to restrict its processing (Art. 18), to receive it in a portable form (Art. 20), and to object to processing based on legitimate interests (Art. 21). Where processing rests on consent, you may withdraw that consent at any time with effect for the future.

To exercise any of these, email the address in the section above. Deleting a beta sign-up takes one message and needs no reason.

You also have the right to complain to a data protection supervisory authority. The authority responsible for us is:

The app is separate

The TrainArk app processes considerably more — your intake answers, your training history, the food and drink you log if you use the nutrition feature, your first name shown to friends you have added, and — only if you switch it on or accept it — your completed workouts and streaks, and your progress on a goal you have taken on with one friend, and, if you turn it on, your approximate location to find gyms nearby, and — only if you connect Apple Health or Health Connect — your body weight, step count and sleep duration read from your device. That is governed by the app's own privacy policy, which explains each one, including the fact that location coordinates are rounded, never written to our database, never linked to your account, and that gym searches go to OpenStreetMap by default, falling back to Google only when OpenStreetMap is unreachable and that food logs are never shown to another user.

Changes to this policy

We will update this page when what we collect changes. The date at the top is the date of the current version.