Privacy policy

Last updated: November 2026

1. Who is responsible

CATALYX AI, David Vrieze, Albert-Einstein-Straße 9H, 14473 Potsdam, Germany. Email: hello@catalyx-ai.com.

2. What this is about

Latu is a training coach for cycling and running. To advise you, the app processes data about you and your training. This page explains what that data is, why we need it, who else sees it and what you can do about it.

There is no corporation behind Latu, just me, David. If anything here is unclear, write to me. I answer myself.

We do not sell data and we show no ads. There is no tracking across other apps or websites, and nobody but you gets a profile of you.

3. What we process and why

Account. Email address, password (as a hash), name. Purpose: sign-in, access to your data. Legal basis: contract (Art. 6(1)(b) GDPR). When you sign up, you can tell us how you heard about Latu. We store only how often each answer was chosen on a given day, never with your account. Legal basis: legitimate interest in learning which paths lead to Latu (Art. 6(1)(f) GDPR). When you agreed to which version of the terms of use (version, time, and whether at sign-up, in the app or with an order), we store as proof that they apply to you. After an account deletion this proof stays, locked, until the end of the fourth year after it. Legal basis: contract and legitimate interest in being able to prove claims under the contract (Art. 6(1)(b), (f) GDPR).

Profile. Date of birth, sex, weight, height, thresholds (such as FTP or threshold heart rate), health conditions, the location of your training area. Purpose: computing training zones, judging load, adapting plans. Legal basis: for health information, your explicit consent (Art. 9(2)(a) GDPR), separately per purpose (weight, sleep and how you feel, injuries and limitations, nutrition, energy check). You give each one under Settings › Your permissions and withdraw it there at any time; without it Latu does not use this information. Otherwise contract (Art. 6(1)(b) GDPR).

Training. GPS recordings of your rides and runs, sensor data (heart rate, power, cadence), planned and completed sessions, how they felt, nutrition entries, photos you attach to a session. Purpose: analysis, training control, navigation, recap. Legal basis: contract; for heart rate and your perceived effort, your explicit consent (Art. 9(2)(a) GDPR), which you give under Settings › Your permissions and withdraw there at any time.

Background location. During an outdoor recording, the iOS app records your location even with the screen locked so the recording does not break. This happens only while a recording is running. You can revoke the permission in iOS settings at any time.

Where you are right now. Only if you turn it on under Settings › Your permissions: when the app opens, it asks your device for your approximate location. It reaches Latu's server only rounded to about 10 km: once after you turn this on, then only once you have moved more than 25 km, or once a day. When you are more than 60 km from your training location, Latu stores this one place with its name and time zone, so weather, route suggestions, times and the morning check-in follow it; the place name and time zone are then also part of the coach's context. There is no history of your places: a new place replaces the old one, it is deleted when you are less than 40 km from your training location again or turn this off, and no longer used after a week without a report. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.

Conversations with the coach. What you write to the coach, its replies and the summaries it keeps as memory. Purpose: advice, planning. Legal basis: contract; that your information goes to the AI provider for this (section 4), only with your consent (Art. 6(1)(a), for health information Art. 9(2)(a) GDPR). You give it before the first conversation and withdraw it under Settings › Your permissions at any time.

Technical data. IP address, device type, browser, error reports. Purpose: operation and debugging. Legal basis: legitimate interest in a stable service (Art. 6(1)(f) GDPR). For the short addresses on flyers and stickers (such as latu.app/mittwoch), Latu only counts how often each address was opened on a given day: a number, with no IP address, device or account.

Push notifications. Only if you switch them on. We then store the address your device receives messages at. Legal basis: consent, revocable at any time in settings.

Feedback. When you send feedback in the app, we store your message, its kind (idea, bug, praise) and, unless you switch it off, the app version, the screen you came from (without IDs), your device and language. Screenshots you attach are not stored in Latu. They are sent once by email, with your message, to our mailbox at STRATO and stay there until we delete that email. If we reply, we use your account's email address, and only if you allowed it. On the website you can write without an account; we keep an email address only if you give one so we can reply. Legal basis: our legitimate interest in improving Latu (Art. 6(1)(f) GDPR); for the reply address, your consent (Art. 6(1)(a)). You see your feedback in Settings; it is part of the data export and is deleted with your account. We delete website feedback on request. If we mark an idea or a reported bug as done, we send you a short email, but only if you allowed replies. Mail goes out via Lettermint (the Netherlands).

Android wait-list. On latu.app you can sign up without an account so that we email you once when the Android app comes out. For this we store your email address (encrypted), the language of the emails, which consent text you saw, and when you signed up and confirmed. We do not store your IP address with it, and it is not linked to an account. First you get an email with a link to confirm. If you do not confirm, we delete the address after seven days. Otherwise we delete it with the one email about the app coming out, but no later than twelve months after you confirmed. We use the address for nothing else, not for an invitation to test the app either; we ask about that separately. You can leave at any time with the link in every email; that withdraws your consent. Legal basis: your consent (Art. 6(1)(a) GDPR). The entry is tied to no account and so is not part of the data export. If you want to know what we store for your address, or want it deleted right away, write to hello@catalyx-ai.com from that address. Mail goes out via Lettermint (the Netherlands).

4. Who else processes the data

We do not run Latu alone. These providers process data on our behalf and only on our instructions, unless stated otherwise for one of them:

  • Supabase (database, sign-in, file storage) for everything stored.
  • Vercel (hosting, data centre in Ireland, EU) for delivering the app.
  • Amazon Web Services (Amazon Web Services EMEA SARL, Luxembourg) for the coach's replies and the texts in your recap. AWS runs the language model Claude by Anthropic for us (Amazon Bedrock), only in data centres in the EU. What is sent is the conversation and the training and health details the coach needs for an answer, and only with your consent ("The coach is an AI"). AWS does not store requests or answers permanently, does not pass them on to Anthropic and does not train any model with them. AWS keeps only the start of a request, the part that stays the same until the next answer, ready for up to five minutes, so the coach answers faster.
  • Amazon Web Services (as above, data centre in the EU) also for the coach's memory: the short notes the coach keeps about you are converted into a searchable form so that it can find them again later.
  • Microsoft Azure (speech output and input, EU data centre). For the coach's spoken cues, only the text to be spoken is transmitted. When you dictate to the coach in the browser, the recording goes to Azure and is turned into text there. In the iPhone app, the phone recognises your speech itself where it can, and the recording stays on the device. If the phone can't make out what you said, for example because you spoke the other language, Latu sends the recording to Azure once. That only happens if you have allowed the AI coach. Azure works out by itself whether you spoke German or English.
  • OpenFreeMap (maps; Hyperknot Software Kft., Hungary) for the map tiles in navigation and on the route pages. OpenFreeMap delivers them through Cloudflare's network. Both see which map areas your device loads and, for technical reasons, your IP address. OpenFreeMap says it does not store IP addresses in its logs. For the map without signal, your device also loads the areas along your planned route from OpenFreeMap before a session (with its consent) and keeps them until the session is over. OpenFreeMap provides the maps itself as a free service and does not work on our behalf.
  • Mapterhorn (terrain heights; an open data project maintained by Oliver Wipfli) for the 3D view of the map on the route pages. Mapterhorn delivers the height data through Cloudflare's network. Both see which map areas your device loads and, for technical reasons, your IP address. Mapterhorn says it stores, among other things, the IP address, referrer and browser details of each request for up to 30 days. Navigation loads no height data from Mapterhorn. Mapterhorn provides the height data itself as an open project and does not work on our behalf.
  • Cloudflare (Cloudflare, Inc., USA; stored in Western Europe) for the how-to videos and their preview images at latu.app/tutorials, where the "How it works" links on the start page and in the app lead. When a page loads a video or preview image, Cloudflare sees your IP address, for technical reasons, and which file is loaded. We use only its storage (R2) there, with no tracking and no cookies. Cloudflare is certified under the EU-US Data Privacy Framework.
  • Cloudflare (Cloudflare, Inc., USA) for the name service (DNS) of latu.app and for forwarding e-mails to hello@latu.app and support@latu.app. When you write to us, Cloudflare sees the sender, recipient and content of the mail while forwarding it; it stores only delivery data (sender, recipient, time) for up to 30 days, not the content. Cloudflare is certified under the EU-US Data Privacy Framework. The mail ends up in our mailbox at STRATO GmbH (Germany).
  • BRouter (route calculation) for computing routes. We run the open-source software BRouter ourselves, on a server from Hostinger International Ltd. (Cyprus) in Frankfurt am Main. Start, destination and waypoints of a route are transmitted; no other service receives them. For a route “from here” in the coach chat, that is your position, if you share it there. Latu uses it for that one calculation only and does not store it; the route that starts there stays in the chat history. When a route is set to start from wherever you are when you set off, your position goes to BRouter once when you start the session; the route from there is saved as that session's route.
  • Geoapify (address search; KEPTAGO LTD, Cyprus) for the address search when planning a route and for the street names of your waypoints. A search sends the search text and one point the results are ranked by (the last waypoint you set, otherwise your training location, rounded to about a kilometre); the name of a point you set on the map sends that point itself. This goes from Latu's server, never with your IP address. Latu uses only Geoapify's EU endpoint; under the data processing agreement, processing takes place only in the EU (BunnyCDN, Slovenia; Hetzner, Germany and Finland). Geoapify generally keeps requests for at most 24 hours. When you name places for a route to the coach (an address, a town, a stop), Latu looks them up the same way: the place name goes to Geoapify, ranked by your shared position or your training location, rounded to about a kilometre. For water and food along a route, the route's line (simplified) goes to Geoapify; Latu stores the places found, from OpenStreetMap, with the route. For the name of the place you are at (only with your consent to "Where you are right now"), the place, rounded to about 10 km, goes to Geoapify once per trip. For the names of the climbs of a route, a few points on each climb go to Geoapify (its top and up to three points along it); for a session on a planned route Latu takes the climb names from the route and asks nothing; for a free ride or run it never asks. Latu stores the name found, from OpenStreetMap, with the route or the session.
  • Open-Meteo (weather and place search) for the forecast around your training and for finding your training area. The coordinates or the place name you typed are transmitted. When you are travelling and have turned on "Where you are right now", the forecast is for the place you are at, rounded to about 10 km.
  • Sentry (error reports) for debugging. Error reports contain no names and no IP addresses.
  • Lettermint B.V. (email delivery, the Netherlands) sends Latu's emails: sign-in and confirmation links, invitations, the reminder before your trial week ends, order confirmations, confirmations of your cancellation or withdrawal, the reminder before a yearly subscription renews, the notice about a payment that failed, emails about new terms of use and about deleting your account, the Android wait-list emails and replies to your feedback. We pass on your email address and the content of the mail. Lettermint stores the emails in the EU and deletes them after 28 days.
  • Strava, Inc. (USA), as an independent controller, only when you connect your account. With "On tap" you send each finished activity yourself. If you choose "By themselves" and agree once, Latu sends every finished ride and run by itself. Recorded location and performance data, including heart rate, may be included. The legal basis is your explicit consent (Art. 6(1)(a), Art. 9(2)(a) GDPR). Switching back to "On tap" withdraws your agreement to "By themselves" at any time, and "Disconnect Strava" ends all sending. See Optional export to Strava below.
  • Stripe Payments Europe, Ltd. (Ireland) for payment on the web, only if you subscribe there. You enter your payment details directly with Stripe; we never see full card or account numbers. Stripe receives your e-mail address, name and billing address (for VAT), the payment details and technical data for fraud prevention. The payment form only loads once you choose “Continue” on the subscription page. From Stripe we receive the payment status, invoices and the identifiers that tie your subscription to your account. Stripe is responsible on its own for fraud prevention and its own legal duties. Stripe also transfers data to Stripe, LLC in the USA, based on the EU-US Data Privacy Framework and standard contractual clauses. Invoices stay stored at Stripe even if you delete your account, because we have to keep them. We then remove your e-mail address, name, phone number, address and Latu ID from your customer record at Stripe. The invoices keep the details printed on them. What Stripe stores itself about your payment method and for fraud prevention, Stripe keeps under its own rules.
  • Garmin Würzburg GmbH (Germany), as an independent controller, only if you connect your Garmin account: Latu puts your planned sessions and their routes into your Garmin Connect calendar, and, if you switch on "From Garmin", brings back the rides and runs you record on your Garmin from then on, as files, with their routes. Garmin may use what Latu sends there under its own terms.
  • Wahoo Fitness, LLC (USA), as an independent controller, only if you connect your Wahoo account: Latu puts your planned sessions and their routes into your Wahoo account, and, if you switch on "From Wahoo", brings back the rides and runs you record on your Wahoo device from then on, as files (for now without position data). Wahoo may use what Latu sends there under its own terms, including outside the EU/EEA.

Some of these providers are based in the United States or belong to companies based there: Amazon Web Services, Vercel, Supabase, Microsoft, Sentry, Cloudflare, Apple, Stripe and Strava. Where data may reach the United States, transfers rely on the EU Commission's standard contractual clauses and, where certified, on the EU-US Data Privacy Framework.

If you turn notifications on, they are delivered through your device maker's push service. In the browser this is encrypted: the service (Apple or Google) sees that a message arrives, not what it says. In the iPhone app delivery runs through the Apple Push Notification service (Apple Inc., USA); Apple carries the notification's title and text, for example "A short question from your coach about your day", and your device's identifier, no other data from your training.

5. How long we keep data

For as long as your account exists. We delete conversations with the coach once nothing has been written in them for 90 days. Your sessions, plans and the coach's notes stay. If you delete your account, your data is permanently deleted after 30 days, except for the records in the next paragraph. Within that period you can undo the deletion. Our provider deletes error reports after 90 days at the latest.

Tax and commercial law require us to keep some records of a subscription for longer. They contain no training or health data, are stored separately and locked, and are used for nothing else. We keep your order with its order confirmation and your cancellation or withdrawal for six years. Which subscription you had, on which terms, and when it ended, we keep for three years after the contract ended. Each period starts at the end of the calendar year. Instead of your account ID and your e-mail address, your order and subscription details carry only a code derived from them that cannot be turned back into either. It lets us find those records if you ask about them. We keep your cancellation or withdrawal as we received it, with your name, e-mail address and account ID. Invoices and payment records are kept by Stripe or Apple (see 4).

Further periods: we also keep a copy of invoices and refund records in our bookkeeping for eight years (§ 147 AO, § 14b UStG). If you cancel or withdraw on latu.app and we find no account for your e-mail address, we delete your declaration after 90 days. For each such declaration we store only a code derived from your IP address, not the address itself, to spot repeated submissions. We delete notices from Stripe and Apple about payments and subscriptions after 180 days. We delete your browser's notification address once the browser has not checked in for 60 days. We delete your iPhone's address once Apple reports it as invalid. Our providers delete server logs with your IP address after seven days at most. The legal basis for keeping these is our legal obligations (Art. 6(1)(c) GDPR) and our legitimate interest in being able to prove payments and declarations (Art. 6(1)(f) GDPR).

6. Your rights

At any time you can:

  • export all your data (under Settings, Account & data, Export your data),
  • delete your account (under Settings, Account & data, Delete account),
  • ask us to delete individual data without deleting your account,
  • request access, correction, restriction of processing or transfer of your data,
  • withdraw a consent at any time; what we processed on its basis until then stays lawful,
  • complain to a data protection authority, including the authority where you live. The authority responsible for us is the State Commissioner for Data Protection of Brandenburg.

Your right to object: Where we process data on the basis of legitimate interest (Art. 6(1)(f) GDPR; we name each of these places in section 3 or 5), you can object at any time on grounds relating to your particular situation (Art. 21 GDPR). We then stop processing that data for that purpose, unless we have compelling legitimate grounds that override yours, or need it to establish, exercise or defend legal claims. A short email to hello@catalyx-ai.com is enough.

For your account we need your email address, a password, your name, your sport and your date of birth (Latu is 18+). Without them we cannot conclude a contract with you. For your sex (for the training zones) you can choose “Prefer not”. Everything else is up to you, especially any health details. If something is missing, the feature that needs it may work only in part or not at all. You are under no legal obligation to give us data.

The coach analyses your training automatically and makes suggestions from it. That is profiling in the sense of the GDPR. No machine alone makes a decision that has legal effects on you or affects you similarly significantly (Art. 22 GDPR): the coach only proposes every change to your plan, and you decide.

Write to me at hello@catalyx-ai.com. You get an answer from me, not from a form.

7. Cookies

Latu stores on your device only what it needs to run (§ 25(2) no. 2 TDDDG), so it does not ask separately. Cookies: your sign-in, your chosen language, your device's time zone so the times are right, the calendar view you last chose, a key that keeps your account's saved pages apart from other accounts' on the same device, a check value for the few minutes while you connect Strava, Garmin or Wahoo. There are also small markers so that what you dismissed doesn't come straight back: a notice, the question "Ready for today?" if you skipped it or declined its consent, and sessions you put aside for later in the calendar, until you close the app. Browser and app storage also hold what Latu needs without a network: pages and images you opened, map tiles, above all along your planned route, spoken cues, a running recording and anything you enter offline, until it is saved. On top of that come settings that belong to this device (appearance, map, paired sensors, notifications), drafts you haven't sent yet, markers for which explanations you have already seen, and, only with your consent "Where you are right now", the rough area you were last in. No advertising or analytics cookies.

Optional export to Strava

Latu sends a completed activity to Strava, Inc. only when you have connected your Strava account, and only the way you chose. "On tap": you send it yourself. The first time, you confirm what is transferred. After that, one tap on "Send to Strava" is enough, and each time exactly that one activity goes. "By themselves": after your one-time agreement, Latu sends every finished ride and run as soon as you close its recap, otherwise the next time you open Latu. With "Not this time" you hold an activity back, and you can switch back to "On tap" at any time. After you disconnect, Latu asks again when you next connect and send. This includes recorded location and performance data, including heart rate where present. The description also carries one fixed line about Latu ("Planned and done with Latu · latu.app" or "Done with Latu · latu.app") unless you switch it off when sending. The transfer is based on your consent (Article 6(1)(a) and, for health data, Article 9(2)(a) GDPR). Strava processes the copy under its own privacy policy, including processing outside the EU/EEA; your Strava settings control its visibility. Latu stores encrypted connection credentials and export receipts with the confirmation version and date, but does not import Strava activities. Disconnecting removes the credentials and stops future exports. Receipts remain until the activity or Latu account is deleted. Copies already sent to Strava must be managed or deleted there; disconnecting does not remove them.

Strava privacy policy

Garmin

If you connect your Garmin account, Latu puts your planned rides and runs into your Garmin Connect calendar. From there they reach your Garmin watch or Edge. If you also switch on "From Garmin", the rides and runs you record on your Garmin come back to Latu. Both are off until you switch them on under Settings → Connections → Garmin. Latu uses Garmin's interfaces for workouts, courses and activities.

What Latu sends: your planned rides and runs for today and the next six days, by themselves or on your tap. For each session its title, its day and its parts with duration, target (watts or pace) and name, and the route as a course with its points, heights, distance and ascent. Latu does not send heart rate, weight, how you feel, notes, conversations with the coach or finished sessions.

What Latu stores for this: your Garmin user id, the sign-in tokens encrypted, when they expire and which permissions you granted at Garmin. For each sent session Garmin's ids for workout, date and course and a fingerprint of what was sent. That way a change replaces the session at Garmin, and nothing arrives twice. If Garmin refused a session, a short reason is kept with it.

The recipient is Garmin Würzburg GmbH, Leightonstraße 7, 97074 Würzburg, Germany, as an independent controller. Purpose: your planned sessions on your Garmin watch or Edge. Legal basis: contract (Art. 6(1)(b) GDPR), at your request. Garmin may use what Latu sends under its own terms; Garmin's privacy statement applies there.

What comes back, only with "From Garmin" on: each ride and run you record on your Garmin watch or Edge from that moment. The data comes from your Garmin Connect account: Garmin tells Latu that an activity is finished, with its type, the name of your device and an address where Latu fetches its file once. Until the session is stored, Latu keeps that address and then the file, encrypted, for at most 14 days. Latu takes the times, duration, distance with the route, that is your positions, elevation, power and cadence from it, and heart rate only with your consent "Heart rate and effort" (Art. 9(2)(a) GDPR); without it, Latu leaves the heart rate out. If you correct the duration or distance in Garmin Connect, Latu takes that over, as long as you haven't changed the session in Latu. Latu does not read what you create or upload by hand in Garmin Connect, other sports, anything from before, or health data such as sleep or stress. The session is stored in Latu like an imported file, with the name of your Garmin device. Latu keeps Garmin's id of each activity, so nothing comes in twice. Latu does not pass these sessions on to Strava. Who processes them besides Latu is in section 4: Supabase and Vercel as for every session, and only if you have allowed the AI coach, Amazon Web Services (Amazon Bedrock in the EU) and Microsoft Azure as described there. Legal basis: contract (Art. 6(1)(b) GDPR), at your request, and your consent for heart rate and for the AI coach.

Taking it back: switch "From Garmin" off, and Latu reads nothing more from Garmin; your consent to it is withdrawn. With "Disconnect" under Settings → Connections → Garmin, Latu takes its sessions and courses out of your Garmin calendar, ends its access at Garmin and deletes the sign-in tokens, the send records and any files still waiting at Latu. Sessions that came back stay in Latu until you delete them; deleting your account deletes them with everything else. If you remove Latu in Garmin Connect under "Connected Apps" instead, Garmin tells Latu: "From Garmin" goes off, and Latu's sessions stay in your Garmin calendar; you then remove them there by hand. If you only stop sharing your activities in Garmin Connect, "From Garmin" goes off too.

AI transparency for data from Garmin. Latu's coach is an AI system: the language model Claude by Anthropic, which Amazon Web Services runs for Latu in the EU (section 4). If you have allowed the AI coach, it reads the rides and runs that come from Garmin like any other session, to answer your questions, put your training in context and adjust your plan; it only proposes changes to your plan, and you decide. For this, the values it needs for an answer go to the AI provider. Before anything from Garmin reaches Latu, Latu asks you explicitly when you switch on "From Garmin", with this explanation, and records when and for which version you agreed. You can take it back at any time: switch "From Garmin" off or disconnect Garmin, and the AI coach under Settings › Your permissions. Latu never uses data from Garmin, or anything derived from it, including conversations with the coach about it, to train, test or improve AI models, and gives it to no one for that. If laws or Garmin's requirements on this change, Latu updates this section and asks you again if anything changes for you.

Wahoo

If you connect your Wahoo account, Latu puts your planned rides and runs into your Wahoo account. From there they reach your Wahoo ELEMNT bike computer or RIVAL watch. If you also switch on "From Wahoo", the rides and runs you record on your Wahoo come back to Latu. Both are off until you switch them on under Settings → Connections → Wahoo. Latu uses Wahoo's Cloud API for plans, workouts, routes and finished workouts.

What Latu sends: your planned rides and runs for today and the next six days, by themselves or on your tap. For each session: its title, its day (with its start time if it has one), its parts with duration, target (watts or pace) and name, and the route as a file with its points, elevation, distance and ascent. Latu does not send heart rate, weight, how you feel, notes, conversations with the coach or finished sessions.

What Latu stores for this: your Wahoo user id, your sign-in tokens (encrypted), when they expire and which permissions you gave Latu at Wahoo. When you connect, Wahoo also hands over your name, height, weight and date of birth; Latu does not keep them. For each session it sent, Latu stores Wahoo's ids for plan, workout and route and a fingerprint of what was sent. That way a change replaces the session at Wahoo, and nothing arrives twice. If Wahoo refused a session, Latu keeps a short reason with it.

The recipient is Wahoo Fitness, LLC, 90 West Wieuca Rd NE #110, Atlanta, Georgia 30342, USA, as an independent controller. Purpose: your planned sessions on your Wahoo device. Legal basis: contract (Art. 6(1)(b) GDPR), at your request. For the transfer to the USA, Latu asks for your explicit consent when you connect, after telling you the risks (Art. 49(1)(a) GDPR): Wahoo is not certified under the EU-US Data Privacy Framework, and Latu has no standard contractual clauses with Wahoo. You can withdraw it at any time with "Disconnect". Wahoo may use what Latu sends under its own terms, including outside the EU/EEA; Wahoo's privacy policy applies there.

What comes back, only with "From Wahoo" on: each ride and run you record on your Wahoo from that moment, as the file Wahoo keeps of it, read with your Wahoo sign-in. Latu takes the times, duration, distance, elevation, power and cadence from it, and heart rate only with your consent "Heart rate and effort" (Art. 9(2)(a) GDPR); without it, Latu leaves the heart rate out. For now Latu keeps no positions from Wahoo, so these sessions have no map. Latu reads no workouts from other apps, nothing from before and no other data from your Wahoo account. The session is stored in Latu like an imported file; if you have allowed the AI coach, it sees it like any other session. Latu keeps Wahoo's id of each workout it brought in, so nothing comes in twice and Latu can find these sessions if Wahoo asks for its data to be deleted. Legal basis: contract (Art. 6(1)(b) GDPR) and, for heart rate, your consent.

Taking it back: switch "From Wahoo" off, and Latu reads nothing more from Wahoo. With "Disconnect" under Settings → Connections → Wahoo, Latu takes its routes and today's planned session off your Wahoo and ends its access at Wahoo. Wahoo says it then removes the plans Latu created and any upcoming workouts you haven't done yet. At Latu, the sign-in tokens and send records are deleted. Sessions that came back stay in Latu until you delete them; deleting your account deletes them with everything else. If you remove Latu in your Wahoo account settings instead, Wahoo removes the same plans and workouts; Latu takes its routes off only when you disconnect in Latu.

Apple Watch and Apple Health

In the iPhone app you can use Latu with your Apple Watch, with AirPods Pro 3 or Powerbeats Pro 2, and with Apple Health. Each part stays off until you switch it on in Latu and iOS agrees. Latu uses Apple's interfaces WorkoutKit (sending) and HealthKit (reading, and starting a workout for heart rate during a session) for this.

Sending sessions to the watch: Latu puts the plan of a session, that is its parts, duration and targets, into Apple's workout scheduling on your iPhone. From there it reaches your watch. Latu reads nothing from Apple Health for this.

Bringing in rides and runs: with "Bring in rides and runs from the watch" on, Latu reads, whenever you open it, every ride and run you recorded with Apple's Workout app on the watch since you switched it on. Latu doesn't read workouts that other apps wrote to Apple Health. For this, Latu asks iOS for these data types: workouts (time, duration, distance), workout routes (GPS track), cycling power and cadence and, only with your consent "Heart rate and effort", heart rate. You allow or refuse each data type in iOS separately.

Heart rate without a chest strap: if you pick the Apple Watch or AirPods Pro 3 / Powerbeats Pro 2 under Devices & sensors, Latu starts a workout on the watch or the iPhone during a Latu session and reads your heart rate from it. iOS requires permission to write workouts for this. The workout is saved to Apple Health only if you turn on "Save to Apple Health". The heart rate goes to the session in Latu only with your consent "Heart rate and effort", like heart rate from a chest strap.

Recovery from Apple Health: with your consent "Recovery from Apple Health", Latu reads on your iPhone how long you slept last night and your resting heart rate from yesterday, and compares both with your usual from the last four weeks. The values stay on the iPhone. With your morning check-in Latu stores only the result: "shorter than usual", "higher than usual" or "as usual".

Purpose: marking the session as done, working out its load, showing the recap with its map, and telling you in the morning check-in how your sleep and resting heart rate compare with your usual. Legal basis: contract; for heart rate, sleep and resting heart rate your explicit consent (Art. 9(2)(a) GDPR). The coach sees duration, distance, power and load of these workouts, but never the route and never a heart rate Latu read through Apple Health, not even as load. It sees the words from "Recovery from Apple Health" only if you have allowed the AI coach.

Latu uses data from Apple Health only for your training in Latu, never for advertising or marketing, and does not sell it. It is stored with the session in Latu like a recording of its own, with our service providers from section 4, not in iCloud.

Withdrawing: under Settings → Apple Watch and Health you switch sending and bringing in off and delete everything that came from the watch; planned sessions are then planned again in the calendar, and rides without a plan disappear completely. You set heart rate without a chest strap to "Off" under Devices & sensors. You withdraw "Recovery from Apple Health" under Your permissions, and Latu then deletes the stored words. You withdraw Apple's permissions in the Health app (profile picture → Apps → Latu) and in the Watch app on your iPhone (Workout → Connected Apps). If you withdraw the consent "Heart rate and effort", Latu also deletes the heart rate from workouts from the watch. Everything in Apple Health stays as it is.

8. Changes

If something changes, we update this page and the date at the top. For material changes we tell you in the app.