Privacy Policy

Version 15 · Last updated: 24 October 2026

Deutsche Version English

This policy explains how personal data is processed when you use TourKit — the website at tourk.it, the associated web app, and the apps "TourKit: Maps" (for iPhone and Android), "TourKit: Rides" (for Mac, Windows, iPad, iPhone and Apple TV) and "TourKit" for Garmin Edge bike computers (see section 21). The data controller under EU GDPR is Darren Tipton (see section 1).

1. Data controller

The data controller under Art. 4(7) GDPR is:

Darren Tipton
Parkstraße 23
85604 Zorneding
Germany
Email: contact@tourk.it

For all privacy-related enquiries and to exercise your rights as a data subject, please use privacy@tourk.it.

2. Data protection officer

No data protection officer has been appointed. The thresholds requiring one under Art. 37 GDPR / § 38 BDSG are not met: TourKit is operated as a sole proprietorship with no other persons engaged in personal-data processing. This policy will be updated if the situation changes.

3. When you visit the site

When you load a page, the server automatically receives standard HTTP request data from your browser via our hosting provider:

• IP address of the requesting device
• Date and time of the request
• Name and URL of the requested file
• Bytes transferred and HTTP status code
• Browser and operating system (User-Agent)
• Referring URL (Referer)

Legal basis: Art. 6(1)(f) GDPR — legitimate interest in operating, stabilising, and securing the service and defending against attacks.
Retention: log files are deleted no later than 14 days after they are written, unless a specific security incident requires longer retention.

4. User account

Using TourKit requires a user account. At registration we process:

• Email address (used for sign-in, account verification, and transactional emails)
• Password (stored only as a secure hash — never in plain text)
• Display name (optional, free choice)
• Timestamps of registration and most recent sign-in

Legal basis: Art. 6(1)(b) GDPR — performance of the service contract.
Retention: for the duration of the account, plus a short grace period after deletion for backups and any tax-law retention obligations for payment-related data.

5. Training and health data

When you use TourKit for training planning, recording, or analysis, we process data relating to your physical performance — which under Art. 9(1) GDPR are special-category "health data":

• Functional Threshold Power (FTP), maximum and resting heart rate
• Training plans, individual workouts, and event goals
• Recorded activities (power, heart rate, cadence, speed, GPS trace, elevation profile, timestamps)
• Self-reported entries such as weight and year of birth (if provided)
• Calculated training metrics (Load / Norm Power / Intensity, fitness / form / fatigue values)
• Wellness data, if you bring it in from Intervals.icu (heart-rate variability, resting heart rate, sleep)

Legal basis: Art. 9(2)(a) GDPR — explicit consent — in conjunction with Art. 6(1)(b) GDPR (contract performance). Consent is given at registration and may be withdrawn at any time with prospective effect (see section 17).
Retention: for the lifetime of the account or until you delete the data yourself.
Recipients: these data normally stay with our hosting provider. If you enable Coach Chat (section 7) or optional third-party integrations (section 8), relevant extracts may be sent to those recipients.

Insights and training recommendations (e.g. dashboard suggestions, analysis of past sessions) are calculated by rule-based logic on our servers. No transfer to external AI services takes place for these; such a transfer occurs only when Coach Chat is active (see section 7).

Sensors (Bluetooth and ANT+)

If you choose, you connect heart-rate straps, power meters, cadence sensors and smart trainers over Bluetooth — in the browser through Web Bluetooth, in the apps through the operating system's Bluetooth, and in TourKit: Rides on the Mac and Windows also through an ANT+ USB stick. The readings (heart rate, power, cadence, speed) are read on your device and stored as part of the recorded activity (see above). TourKit controls a smart trainer during the ride (gradient, resistance, or a workout's target power). The apps keep the names and identifiers of paired devices on your device only, to reconnect them next time; they are not sent to us. Devices found nearby while searching are only shown on screen.

Riding together in TourKit: Rides

In TourKit: Rides you ride in a world — a climb or a velodrome, for example — with everyone riding that world at the same time, or in a group ride someone invited you to by link or code. This needs a public name saved in your account, which is what others see you by; without one you ride alone. Once it is saved and you are online, the app joins a world's public room automatically when you start a ride there. You can change your public name at any time or delete it in Settings.

While you ride with others, your device sends, five times a second — ten times a second in a group ride or a race: your position on the virtual road (distance covered, speed, lateral position), the road, your cadence, your effort as a percentage of your FTP and in watts per kilogram of body weight, with a workout loaded the workout and its target as a percentage of FTP, and whether your rider is shown as a woman or a man. That follows the sex in your profile unless you pick one yourself in Settings.

The other riders in the same room see these together with your name: in a world's public room the public name you choose yourself; in a group ride on the public road the public name too — a rider who has not chosen one appears as a stand-in such as "Rider4821"; in a private group ride your first name. Your real name is never shown in a public room. Your power in watts, your heart rate, your weight as a figure and any real-world location are not sent; the position is one on the virtual road, not GPS. Note, though, that watts per kilogram together with the percentage of FTP allow your FTP per kilogram of body weight to be estimated.

This passes, encrypted, through our room server (SwitchR, at Hetzner in Germany) and is only relayed while you are in the room; it is not stored there. Our server can show signed-in TourKit users how many riders are in a world's public room right now, under which public names and on which road; private group rides never appear there. Riding alone and in no group ride, none of this leaves your device. Bots (your ghost and the domestiques) are drawn only on your own screen and are not sent anywhere.

Legal basis: Art. 6(1)(b) GDPR — the ride with others that you choose by saving a public name or joining a group ride. Where the effort figures sent are health data, Art. 9(2)(a) GDPR applies as well (see above).

6. Route planner

The route planner processes location and route information:

• Waypoints you set and routes you save (geo-coordinates, elevation profile)
• GPX files you upload
• Optionally: your current location, if you explicitly grant the browser or the app access
• Search terms in place search, and the map area on screen so nearby results come first

Map rendering, route calculation, geocoding, and elevation queries run on TourKit's own infrastructure (self-developed engines hosted at a Hetzner Online GmbH data centre in Germany — see section 13). These data are not transmitted to any external map, routing, or geocoding provider — except for the satellite view and the weather forecast (see below).

Satellite view (Esri). If you choose the "Satellite" map view, your browser or the app loads the aerial tiles directly from the "World Imagery" service of Environmental Systems Research Institute, Inc. (Esri, USA). Esri receives your IP address, your browser's or app's identifier, and the map areas requested — no account data, routes or recordings. Esri processes these data as an independent controller under its own privacy notice. For the transfer to the USA see section 14. Unless you choose the satellite view, nothing is sent to Esri.

Weather on route (MET Norway). When you set a start time in the route planner, our server fetches the forecast for the route from the Norwegian Meteorological Institute (Meteorologisk institutt, "MET Norway", Oslo, Norway). All it sends is the coordinates of the ~11 km grid cells the route touches, rounded to one decimal — not your route, times, identifiers or your device's IP address; MET Norway sees only our server. We keep the forecasts we fetch, unlinked to you, for at most a day after they expire.

Shared routes. Whether a route is shared is your choice; unless you share it, it stays private. If you share a route by link or publish it in the route catalogue, anyone with the link, or anyone visiting the catalogue, sees its course, its key figures and the places along it, and your display name. The first and last stretch of the route (400 metres each) are not shown. If you have set a home zone — a point with a radius, under Settings → Privacy & Data or in TourKit: Maps under Profile — everything inside it is hidden too. You can switch the home zone off there at any time without deleting the point; then nothing around it is hidden any more.

Community heatmap. Published routes feed the anonymised community heatmap. Your recorded rides do so only if you switch it on under Settings → Privacy & Data (off by default). Each track is cropped at both ends, your home zone is removed, and a stretch appears only where enough other riders have been that no single ride can be made out. Individual rides are never shown to anyone.

Legal basis: Art. 6(1)(b) GDPR (contract performance, including the satellite view and sharing you choose) and Art. 6(1)(a) GDPR (consent) for using your location and for contributing your rides to the heatmap.

7. Coach Chat — AI training assistant

Coach Chat is an optional AI-powered training assistant. When enabled, we send the following data to our processor Anthropic PBC (United States):

• Display name
• A coarse fitness band (e.g. "intermediate") derived server-side from your FTP — the exact FTP, maximum and resting heart rate are not transmitted
• Training metrics for the last 14 days — including the ride titles you gave them — and 4-week load (intensity/load)
• Your Fitness, Fatigue and Form values and your weekly ramp — a few numbers derived server-side from your training-load history, not the history itself — and the projection calculated from them and your scheduled sessions
• The trend in your FTP, estimated FTP and VO2max — as a percentage change only; the underlying watts and ml/kg/min values are not transmitted
• Any personal records you set in the last 30 days
• If you ask about training intensity: how your training time splits across low, moderate and high intensity zones
• Training-plan structure, the past week's sessions and the next 21 days of scheduled sessions
• Your readiness score and today's recommendation — derived server-side from your wellness data; the underlying heart-rate variability, resting heart rate and sleep values are not transmitted
• Your durability trend and your current coaching insights
• If you have a route open in the planner: its title, distance, elevation gain, route type, estimated ride time, average speed and energy estimate, and the climbs on it (position along the route, length, gradient, category) — the route's path and coordinates are not transmitted
• If you ask the coach to find one of your saved routes: the titles and summary figures (distance, climb, estimated time, load) of the matching routes
• If you ask for stops or a refuelling plan along your route, or for places in a town you name: the names, opening hours and contact details of the public places found (e.g. cafés, bakeries, water points), their position along the route or distance from the place you named, and your estimated arrival time — those places' exact coordinates are not transmitted
• If you ask about the weather on your route: the forecast along it (wind, rain, temperature, sunrise and sunset) for the times you would be there, with the position along the route — where the forecast is for is not transmitted. The forecast comes from MET Norway (section 6).
• Your messages and the existing chat history

Only these derived values are transmitted — not the underlying time series. If the scope of the transmitted data changes, we obtain your consent again before any further data is sent.

These data include health data under Art. 9 GDPR. Sending them to a provider in the US constitutes a third-country transfer (see section 14).

Legal basis for the processing: Art. 9(2)(a) GDPR (explicit consent) in conjunction with Art. 6(1)(b) GDPR. Coach Chat is off by default. You activate it only by a separate, unambiguous consent given in a dialog that first informs you about the processing.
Basis for the international transfer: transfers to Anthropic PBC rely on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR), which form part of our data processing agreement with Anthropic. In addition, we obtain your explicit consent under Art. 49(1)(a) GDPR (see section 14).
Anthropic does not use API content to train their models (Anthropic API default setting). Anthropic retains processed content for up to 30 days for abuse-prevention purposes.
Retention in TourKit: chat history is automatically deleted after 14 days. You can delete history manually at any time, or disable Coach Chat entirely — both of which erase your full message history.

TourGuide — AI route assistant

TourGuide is an optional AI-powered route assistant in TourKit: Maps and on the website. It has a consent of its own, separate from Coach Chat's: turning TourGuide on does not turn on Coach Chat, nor the other way round. When you turn it on, we send Anthropic PBC (USA) only the following:

• The date, your local time and your time zone
• If you have a route open: its title, distance, elevation gain, route type, estimated riding time, average speed and energy required, and the climbs on it (where along the route, length, gradient, category) — the route's path and coordinates are not sent
• If you ask TourGuide to find one of your saved routes: the titles and summary figures (distance, elevation gain, estimated time) of the matching routes
• If you ask for stops or a refuelling plan along your route, or for places in a town you name: the name, opening hours and contact details of the public places found (e.g. cafés, bakeries, water points), how far along the route or from that place they are, and your expected arrival time there — their exact coordinates are not sent
• If you ask about the weather on your route: the forecast along the route (wind, rain, temperature, sunrise and sunset) for the times you would be there, with the position along the route — where the forecast is for is not sent. The forecast comes from MET Norway (section 6).
• Your messages to TourGuide and its earlier history

TourGuide receives no training or health data.

Legal basis for the processing: Art. 6(1)(a) GDPR (consent). TourGuide is off by default. You turn it on only by a separate consent given in a dialog that first tells you about these data. What is said above for Coach Chat applies to the transfer to Anthropic in the US, its basis, and Anthropic's retention.
Retention in TourKit: we keep TourGuide's history apart from the coach's; it is automatically deleted after 14 days. You can delete it at any time, or turn TourGuide off, which erases its history and leaves Coach Chat as it is. Until 24 October 2026 TourGuide ran under Coach Chat's consent, whose dialog named TourGuide and these data; anyone who had accepted the version then in force keeps TourGuide.

AI Transparency Statement

TourKit uses AI in two features only: Coach Chat and TourGuide. Both use Anthropic's Claude models through the Anthropic API, and Anthropic PBC processes the data as our processor.

• Only with your explicit consent: both are off by default. You turn each one on with a consent of its own, in a dialog that tells you about the data first. Without that consent, no AI system receives any of your data.
• What the AI receives: only the data listed above. For Coach Chat these include figures derived from your rides, including rides TourKit receives from Garmin Connect (section 8). The AI does not receive activity files or data streams. TourGuide receives no training or health data, and so no Garmin data.
• No training of AI models: Anthropic does not use data from Coach Chat or TourGuide to train its models. Neither we nor our service providers use Garmin data, or anything derived from it, to train, evaluate or improve AI models. We do not use your other data for that either; if that were to change, we would ask for your consent first.
• No automated decisions: the assistants' answers are suggestions, and they can be wrong. No AI makes decisions with legal or similarly significant effects within the meaning of Art. 22 GDPR.
• Withdrawal: you can withdraw either consent at any time by turning Coach Chat or TourGuide off in Settings under Privacy & Data. From then on Anthropic receives no further data, and that assistant's history is deleted.

8. Connected third-party services

TourKit can optionally be connected to external platforms (e.g. Strava, Garmin Connect, Intervals.icu) to import, export, or synchronise activities. The currently available integrations are listed in the Integrations area of the TourKit app.

The respective providers act as independent controllers under GDPR and process your data on the basis of their own privacy notices and the account you hold with them — not on our instructions. The data exchanged is determined by the permissions and actions you choose.

Connections happen only on your initiative (OAuth, credentials, or API key). You can disconnect at any time in your account settings; the corresponding tokens or keys are then deleted from our servers.

Strava: if you have connected Strava and allowed uploads, every ride you save in TourKit: Rides is uploaded to Strava automatically as a virtual ride — with the ride's data streams (power, heart rate, cadence, speed) and the course of the virtual road. You can switch uploading off in Integrations at any time.

Legal basis: Art. 6(1)(a) GDPR (consent to the connection) or Art. 6(1)(b) GDPR (performance of the service you requested), and Art. 9(2)(a) GDPR where health data is transferred. Each provider's own privacy notice also applies.

Garmin Connect

You connect TourKit to Garmin Connect on Garmin's own sign-in page; we never see your Garmin password. There you choose what Garmin shares with TourKit, and you can change those permissions in Garmin Connect at any time.

What we receive from Garmin:

• the identifier under which Garmin knows your account to TourKit, and the permissions you granted
• if you allowed your activities to be shared: your recorded activities, that is their summary (sport, start time, duration, distance, elevation gain, and figures such as power, heart rate, cadence and speed) and the activity file with its data streams and recorded GPS track
• a notification when you remove TourKit in Garmin Connect or change its permissions

What we send to Garmin, when you trigger it or set it up in Integrations: your routes as courses for your device, and workouts and the planned sessions of your training plan for your Garmin calendar.

What we use Garmin data for: only to provide TourKit's features to you, and only for you:

• your rides and their analysis: map, power, heart rate, cadence, speed, elevation profile and climbs
• your training load, and your fitness, fatigue and form over time
• personal records and estimates such as your FTP, from your own rides
• matching a ride you completed to the workout planned in your calendar
• training suggestions and, with your consent to Coach Chat, the AI assistant's answers (section 7)
• ride-time estimates for routes you plan, tuned to your own outdoor rides
• exporting and deleting your data when you ask

Not sold, not shared: we do not sell Garmin data, use it for advertising, or pass it to other platforms. Neither we nor our service providers use it, or anything derived from it, to train, evaluate or improve AI models (see the AI Transparency Statement in section 7).

Who processes Garmin data: it is stored on our behalf by Hetzner Online GmbH in Germany (section 13). Only if you have turned Coach Chat on does Anthropic PBC (USA) receive training figures derived from it, never the activities themselves (section 7). If you choose the satellite view for a ride's map, your device loads the map tiles for that area from Esri (section 6). There are no other recipients.

Disconnecting: in Settings under Integrations with Disconnect, or by removing TourKit in Garmin Connect. We then deregister your account with Garmin and delete everything we received from Garmin: the connection and its tokens, Garmin's notifications, and the activities that came from Garmin. Garmin is an independent controller for Garmin Connect itself, and Garmin's privacy notice applies there.

9. Payment processing

Paid TourKit plans (Pro/Premium) are billed through the payment processor Stripe Payments Europe Ltd. (Ireland) and its group companies. Card and bank data (card number, IBAN, CVC) is collected and processed directly by Stripe; TourKit never receives it.

We process:

• The status of your subscription and payments
• Invoice-related master data (name, billing address, email), as needed for accounting and invoicing
• Your Stripe customer ID and subscription ID

Legal basis: Art. 6(1)(b) GDPR (contract performance) and Art. 6(1)(c) GDPR (statutory record-keeping obligations under HGB/AO).
Retention: invoice and accounting records for up to 10 years (§ 147 AO). Other payment-related data until contract termination plus statutory limitation period.

10. Newsletter and product updates

You can optionally subscribe to email updates about TourKit (product news, occasional announcements). Subscription is by double opt-in: after you enter your email address, you receive a confirmation email with a link; the subscription becomes effective only when you click that link.

Every newsletter email contains an unsubscribe link. Unsubscribing removes your address from the mailing list.

Personal-record emails: You can optionally be notified when an activity beats one of your previous bests. When enabled, we email you at most once a day; the email includes the relevant training figures (e.g. 5-min/20-min power, 5K/10K run times, distance, climbing). You enable this yourself in Settings, and every such email carries a one-click unsubscribe link. These emails are sent only to your own address and are never shared with third parties.

Daily brief: optionally, we email you once a day at a time you choose with today's planned session, your Readiness score and the top coaching note. It is built by rule-based logic on our servers, with no AI provider. You enable this yourself in Settings, and every such email carries a one-click unsubscribe link.

Legal basis: Art. 6(1)(a) GDPR (consent). You can withdraw consent at any time with prospective effect.

11. Contacting us

If you email us at contact@tourk.it or privacy@tourk.it, we process the information you provide solely to handle your request.

If you use the support form when signed in, we keep your ticket (topic, subject, messages and attached files such as screenshots, GPX or FIT files) in your account. So that we can reproduce the problem, the app version, the platform, your plan, the page you were on and your browser's or app's identifier are stored with it automatically.

Legal basis: Art. 6(1)(b) GDPR (pre-contractual or contractual) or Art. 6(1)(f) GDPR (legitimate interest in responding).
Retention: until the request is resolved; thereafter subject to statutory retention obligations. Support tickets are deleted with your account at the latest.

12. Cookies and local storage

TourKit uses no tracking, analytics, or advertising cookies. No data is sent to analytics services (e.g. Google Analytics). The following cookies and local storage entries are used:

All cookies and storage entries listed are strictly necessary or fulfil a function you have specifically requested (§ 25(2) No. 2 TTDSG / TDDDG). No consent banner is therefore required.

13. Recipients and processors

We engage the following service providers as processors under Art. 28 GDPR or as independent controllers:

The currently available third-party services are listed in the Integrations area of the TourKit app. These providers act as independent controllers, not as processors on our behalf — see section 8.

No sale of personal data: we do not sell personal data or pass it on for advertising. The recipients are only those listed here; which of them receive Garmin data is set out in section 8.

14. International transfers

Every server TourKit runs on (website, app, database, email and engines) is in Germany (see section 13). Transfers to third countries outside the EEA occur only in the following case:

• USA — affected recipients include Anthropic (Coach Chat), Stripe group companies, any training/activity platforms you optionally enable (see section 8 and the Integrations area of the app), and Esri when you choose the satellite view (see section 6).
  The governing safeguard is the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR), which form part of our agreements with the relevant processors — this applies in particular to Anthropic PBC (Coach Chat). Where a recipient is additionally certified under the EU-U.S. Data Privacy Framework, the transfer also relies on Adequacy Decision (EU) 2023/1795.
  For Coach Chat and similar consent-based features we additionally obtain your explicit consent under Art. 49(1)(a) GDPR. In doing so we disclose the risks of a transfer to the United States — in particular that US authorities may under certain conditions access the data, and that remedies comparable to those available in the EU may not exist.

15. Retention

Unless stated otherwise in the sections above, we keep personal data only for as long as is necessary for the relevant purpose:

• Server logs: up to 14 days
• Coach Chat history and TourGuide history: each up to 14 days (automatic deletion)
• Garmin Edge: unconfirmed pairing codes 10 minutes; device records until removed, at the latest 30 days after 180 days unused; diagnostics 30 days
• Live tracking: positions and the link 24 hours after the ride ends (see section 21)
• Garmin Connect: Garmin's notifications until they are processed, then 30 days; all data received from Garmin until you disconnect, when it is deleted (see section 8)
• Account data: duration of the contractual relationship
• Payment-related data: up to 10 years (§ 147 AO)
• Newsletter subscriptions: until you unsubscribe
• Email enquiries: until the request is resolved, subject to statutory retention obligations

16. Your rights

You have the following rights with respect to personal data concerning you:

• Access (Art. 15 GDPR)
• Rectification of inaccurate data (Art. 16 GDPR)
• Erasure (Art. 17 GDPR)
• Restriction of processing (Art. 18 GDPR)
• Data portability (Art. 20 GDPR)
• Objection to processing based on legitimate interest (Art. 21 GDPR)

An informal email to privacy@tourk.it is enough to exercise these rights. We respond within one month (Art. 12(3) GDPR).

The following rights can be exercised directly from within your signed-in TourKit account — no email required:

• Rectification of your profile, training, and contact data in account settings
• Data export (Art. 20 GDPR) — download your data in a structured, machine-readable format (Settings → Privacy & Data → Download my data)
• Full account deletion (Art. 17 GDPR) — via the "Delete account" button in account settings; on confirmation, your personal data is removed from active databases immediately (backups age out within our host's retention window of up to two months)
• Disable Coach Chat, including deletion of the entire chat history; likewise turn TourGuide off, including deletion of its history (under Privacy & Data)
• Disconnect third-party services (Strava, Garmin, Intervals.icu, etc.) under Integrations, including deletion of stored tokens; for Garmin we also delete everything we received from Garmin (section 8)
• Unsubscribe from the newsletter

17. Withdrawing consent

Where processing is based on consent (in particular training / health data, Coach Chat, TourGuide, connected services such as Garmin, and the newsletter), you can withdraw consent at any time with prospective effect — no reason needed, no penalty. The lawfulness of processing carried out before withdrawal is unaffected.

You can withdraw consent directly in your account settings (turn Coach Chat or TourGuide off under Privacy & Data, disconnect Garmin and other services under Integrations, unsubscribe from the newsletter, delete your account) or by emailing privacy@tourk.it.

18. Right to lodge a complaint

You have the right to lodge a complaint with a data-protection supervisory authority, independent of any judicial remedy (Art. 77 GDPR). The authority competent for TourKit is:

Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18, 91522 Ansbach, Germany
Phone: +49 (0) 981 180093-0
Email: poststelle@lda.bayern.de
Web: www.lda.bayern.de

19. Minimum age

TourKit is intended for users aged 16 or older. Use by persons under 16 is not permitted. If we become aware that we have processed personal data of a person under 16, we will delete it without undue delay.

20. Data security

We apply technical and organisational measures (TOM) to protect your data, including:

• TLS encryption of all connections
• Application-level encryption of sensitive fields with AES-256-GCM — in particular health data (FTP, resting and maximum HR, weight, year of birth), contact data (email, display name), Coach Chat history, and credentials for connected third-party services; separate key management per data category
• Also stored encrypted (and additionally compressed): recorded activity files together with their GPS traces and sensor streams, the derived heat-map track data, and the geometry of the routes you save (track, elevation profile, and waypoints)
• Passwords stored only as a secure hash
• Session tokens as HttpOnly, Secure, and SameSite cookies
• In the mobile app: the session token is held in the operating system's secure key store (iOS Keychain / Android Keystore)
• CSRF protection for state-changing requests
• Role- and IP-based access controls on servers and databases
• Operation in physically secured Hetzner Online GmbH data centres in Germany (electronic access control with logging, CCTV)
• Routine software and security-patch updates

21. The apps TourKit: Maps, TourKit: Rides and TourKit on Garmin Edge

The sections above apply to the apps as well: you sign in with your TourKit account, and account, training, health, and route data are processed on the same servers and on the same legal bases as in the web app (see sections 4 to 6). The following applies in addition.

TourKit: Maps (iPhone and Android) — location and recording

To display the map, navigate and record rides, TourKit: Maps processes your location data (GPS position, timestamp, elevation, speed). At your request, recording can continue while the app is in the background or the screen is off, so that the recorded track remains complete. We also evaluate the device's motion sensors in order to detect stops automatically and reduce battery consumption. If you have paired sensors, their readings are recorded too. When you finish a ride it is uploaded to your TourKit account automatically; without a connection, as soon as the device is back online. On Android the app determines your location through the operating system's location services (Google Play services); their processing follows your device settings and Google's privacy notice.

If you choose, you download map, routing, search and POI data for an area or along a route to the device, to use it without a connection. For this the app sends the chosen map area or route course to our servers.

Live tracking (“Share live”) in TourKit: Maps

Only if you choose Share live while recording a ride does TourKit: Maps send your location to our servers as you ride: about every 20 seconds, the positions recorded since the last send (GPS position, time, elevation, speed; at most one per 10 seconds or 75 metres), with the ride's figures so far (distance, riding time, climbing) and, if you are following a route, that route and its title. We create a link for this, which you pass on yourself through your phone's share menu. We store the code in the link only as a fingerprint (hash), from which it cannot be recovered.

What the link shows. Anyone with the link sees, without an account, on a page at tourk.it: the route, the way ridden so far, your current position, the figures and the time of the last update, with your public name or, if you have not chosen one, your display name. You decide who gets the link; if it is forwarded, we cannot prevent that. So the page never shows a position inside your home zone while it is switched on (see section 6); while you are there, the page says only that the position is hidden, and shows a map of a wider area (about 80 × 55 kilometres) without your position in it. Without a home zone switched on, the page hides no position, not at the ride's start either. Search engines do not index the page, and the preview a messenger shows when the link is pasted contains no position. Anyone who opens the page is treated like any visitor to the site (see section 3).

Ending and deletion. Sharing ends when you finish the ride or choose Stop sharing, which you can do at any time; sharing a new ride ends the previous link. We store the positions encrypted and delete them, with the link, 24 hours after the ride ends, or 24 hours after the last position for a ride whose end never reaches us. After that the link leads nowhere. The ride itself is uploaded to your account as described above, independently of this.

Legal basis: Art. 6(1)(b) GDPR — you use this function at your request and decide yourself who receives the link.

TourKit: Rides (Mac, Windows, iPad, iPhone and Apple TV)

TourKit: Rides is the app for riding on an indoor trainer. It connects to your sensors and your smart trainer (see section 5, "Sensors"), records every ride second by second — power, heart rate, cadence, speed, distance and your position on the virtual road, not your real location — and uploads it to your TourKit account when you save it. During the ride the app saves the recording on the device at intervals; if a crash or quitting the app cuts the ride short, the app uploads it the next time it starts. A ride not yet uploaded goes only to the account it was recorded with. Riding with others is described in section 5, uploading to Strava in section 8. TourKit: Rides does not ask for your location, microphone or camera.

On Apple TV you sign in by QR code: you confirm the sign-in on tourk.it with your phone. For this the Apple TV sends its device name, so that you can recognise it when you confirm.

TourKit on Garmin Edge (Connect IQ)

TourKit on Garmin Edge loads your routes and workouts from your TourKit account onto a Garmin Edge bike computer. It reaches our server through the Garmin Connect app on your paired phone, which forwards the Edge's requests to us, so our server sees your phone's IP address (see section 3). Garmin is responsible for the Garmin Connect app and its own processing.

Pairing. To connect the Edge to your account, the app shows a short code that you confirm at tourk.it. For this it sends the device's name and model number (for example "Edge 840" and its Garmin part number) and the version of the app and of Garmin's Connect IQ software, so you can recognise the device when you confirm it and in your device list. We store these, encrypted where they identify the device, with the date it was paired and of its last request. The Edge then receives its own access token, of which we keep only a fingerprint (hash) that the token cannot be recovered from. When a new device is paired we email you its name, so you notice a pairing you did not make. Unconfirmed codes expire after 10 minutes.

What the Edge loads. Your routes, your favourites and public routes you choose, as courses with their summary (distance, climbing, surfaces, climbs), and workouts, whose targets are worked out from your FTP (see section 5). If you send a route to your Edge from the website, we note it on the device until the Edge collects it.

Your position. Only when you open Nearby (public routes near you) or Find nearby (water, cafés, bike shops and the like), the app reads the Edge's current position and sends it with that request. We use it to answer the request: to find routes and places near you and, if you pick one, to calculate a route there on our own engines (see section 6). We do not save it to your account. As part of the request it appears in our server logs, which are deleted within 14 days (see section 3).

Diagnostics. Only if you choose Settings → Send diagnostics, the app sends a list of its last 30 requests (the kind of request, its result code and the time, but no positions or content), with the model number and versions, linked to your account if the device is paired. We use it to solve connection problems and delete it after 30 days.

Removing a device. Under Settings → Privacy & Data at tourk.it you see your paired devices and can remove any of them, and its access stops at once. A device's record is deleted when you remove it, when you delete your account, or 30 days after its access lapses, which happens after 180 days without use. Courses and workouts already on the Edge stay in its own lists until you delete them there.

Legal basis: Art. 6(1)(b) GDPR for pairing, loading and the requests you make, and for diagnostics you send; Art. 6(1)(a) GDPR (consent, through the permission you grant when installing) for your position; Art. 6(1)(f) GDPR (our legitimate interest in your account's security) for the email on a new pairing. Where workout data are health data, Art. 9(2)(a) GDPR applies as well (see section 5).

Permissions

All permissions (location, motion sensors, Bluetooth) are requested solely through your device's own permission prompts and can be withdrawn at any time in your system settings. Without location access, map centring and ride recording in TourKit: Maps are unavailable, and without Bluetooth there are no sensors; everything else continues to work.

On Garmin Edge the app asks, when you install it, for access to your position, the connection to your phone and the Edge's course and workout storage; the Connect IQ Store shows these permissions before you install. You withdraw them by removing the app from the Edge.

Legal basis: Art. 6(1)(a) GDPR (consent, given via the operating system's permission prompt) and Art. 6(1)(b) GDPR for the recording and navigation you have requested. Where the recorded data constitute health data, Art. 9(2)(a) GDPR applies in addition (see section 5).

Data stored on your device

• The session token and cached account details (including your profile values such as FTP, weight and heart-rate figures) are held in the operating system's secure key store (Apple Keychain / Android Keystore). TourKit: Rides on Windows currently keeps them in your Windows user account's settings.
• In-progress and not-yet-uploaded ride recordings with their readings are stored locally until they are uploaded. TourKit: Maps keeps uploaded rides on the device for another seven days for display.
• The names and identifiers of paired sensors, your app settings, and in TourKit: Maps the offline maps you downloaded and a selected route.
• Signing out removes the token and cached account details from the device; rides not yet uploaded stay until you sign in again. Deleting your account in TourKit: Maps deletes the rides, routes, sensors, offline maps and settings the app stored on the device; map areas you viewed may remain in the map display's cache until you uninstall the app. Uninstalling the app deletes the locally stored data as well.
• On Garmin Edge: the access token, the lists you last opened (so they can be read without a connection), your app settings and the list of recent requests described above. Removing the app from the Edge deletes them.

Spoken navigation prompts are generated on the device. TourKit: Maps uses the microphone only when you tap the microphone in the TourGuide chat (section 7) to dictate a message (currently on iOS only). Recognition runs only on the device; if your language has no on-device recognition model, the app does not offer the microphone. No voice data is transmitted: the recognised text appears in the message box and is sent only when you send it, like a typed message. TourKit: Rides does not access the microphone.

No tracking, no analytics services

The apps contain no analytics, advertising, or crash-reporting libraries and no advertising or tracking identifiers; the statistics and diagnostics features of the Unity engine that TourKit: Rides is built with are switched off. No tracking of your behaviour across apps or devices takes place. As in the web app, TourKit: Maps obtains map tiles, route calculation, geocoding, and elevation data exclusively from TourKit's own engines (see sections 6 and 13), except for the satellite view (Esri, see section 6). TourKit: Rides loads no maps; the terrain and scenery are part of the app.

TourKit: Maps is distributed via the Apple App Store and Google Play; TourKit: Rides via Apple (App Store or TestFlight) for iPad, iPhone and Apple TV, and as a direct download for the Mac and Windows. We receive no personal usage data from the stores; Apple and Google only make crash reports available to us if you have agreed in your device settings to share them with app developers. If you take part in a test through TestFlight, Apple also gives us the feedback and screenshots you send there and information on installing and using the test version. Apple and Google are independently responsible for the data they collect in connection with the download and your store account; their own privacy notices apply.

TourKit on Garmin Edge contains no analytics or tracking either. It is distributed through Garmin's Connect IQ Store; Garmin is independently responsible for the data it collects in connection with the download and your Garmin account, under its own privacy notice.

22. Changes to this policy

We may update this policy to reflect changes in technical or legal circumstances or new features that require additional disclosure. The current version is always available on this page. Material changes will be notified to account holders by email in advance.

← Back to home  ·  Legal Notice  ·  Terms  ·  Withdrawal notice

Version history

• Version 15 · 24 October 2026: Garmin Connect through Garmin's official API: what TourKit receives from and sends to Garmin, what for, who processes it, no sale, deletion on disconnecting; an AI Transparency Statement; retention of Garmin's notifications.
• Version 14 · 24 October 2026: TourGuide has its own consent, separate from Coach Chat's, and receives no training or health data.
• Version 13 · 24 October 2026: TourGuide finds places in a town you name and reads the weather on your route: what that sends to Anthropic.
• Version 12 · 23 October 2026: TourGuide, Coach Chat's route planner: what it receives; dictation in TourKit: Maps, with recognition on the device only.
• Version 11 · 23 October 2026: The home zone can be switched off, and set in TourKit: Maps; in live tracking only the home zone hides your position, no longer the start.
• Version 10 · 23 October 2026: Live tracking in TourKit: Maps: what a shared link shows, what stays hidden, and deletion after 24 hours.
• Version 9 · 18 October 2026: TourKit on Garmin Edge (Connect IQ): pairing, position for Nearby and Find nearby, diagnostics and retention.
• Version 8 · 17 October 2026: Weather on route: MET Norway named as the exception in section 6.
• Version 7 · 15 October 2026: The apps TourKit: Maps and TourKit: Rides: riding together, sensors, the satellite view (Esri), shared routes, the heatmap, the daily brief, support, storage on the device and the stores.
• Version 6 · 7 October 2026: Hetzner as the only hosting processor; Penguin (United Kingdom) and the transfer there removed.
• Version 5 · 27 September 2026: Public rides in TourKit Rides under your public name.
• Version 4 · 23 August 2026: Coach Chat: trimmed tool results and the scope of route data.
• Version 3 · 26 July 2026: Coach Chat: a wider scope (fitness, readiness, durability, the next 21 days of the plan, records, the intensity split).
• Version 2 · 22 July 2026: The mobile app (iOS and Android): location and background recording, data stored on the device; encrypted activity files.
• Version 1 · 14 May 2026: The first version recorded. Earlier versions are not on record.