TRAILBOARD.
🇬🇧 EN
📋 Plain language, no jargon

Terms of Use and Privacy

What Trailboard collects, why, which services can interact with the data, and what stays strictly private.

🔒

Strava: strictly personal use

Each connected Strava account can display only transient copies of its own authorized activities. Trailboard does not aggregate them across athletes, use them for rankings, analytics, product improvement, or artificial-intelligence features, or disclose them to a third party.

🏃

Connection, cache, revocation, and Strava limits

If you connect Strava, Trailboard uses OAuth, the official API, and your personal application's webhooks to read the activities you authorize and display them only in your space. Each copy is a transient cache deleted no later than seven days after retrieval, regardless of the activity date; a deleted or unavailable activity is removed sooner. You can disconnect Strava from Account or from Strava. The connection, copies, and derived personal data are then deleted, with written confirmation. Each member provides encrypted credentials for their own Strava application. Trailboard respects each application's quotas and is not affiliated with, sponsored by, or endorsed by Strava.

📡

Usage Data collected by Strava

Strava may monitor and collect API Usage Data and use it, among other purposes, to improve its services, provide support, and verify compliance with its rules. Strava's privacy policy applies to this processing.

🧭

Controller and purpose

Trailboard is software for trail and ultra-trail race preparation. Data is used to run your account, prepare your races, display your dashboards, plans, calendar, favorites, voluntary challenges, and nutrition modules. For any data-related request, you can use the Contact page.

©

Intellectual property of the guides

Original texts, teaching methods, diagrams, tables, and illustrations published in Trailboard guides are protected editorial content. Reading, sharing a link, and brief quotations are permitted when Trailboard, the guide title, and the source page are credited. Any substantial reproduction, adaptation, republication, structured extraction, or commercial use requires prior permission, subject to applicable legal exceptions. Trailboard claims no rights over cited scientific publications, trademarks, or third-party content.

🥣

Nutrition: information, not medical advice

Nutrition only provides informational and organizational guidance for preparing trail and ultra-trail races. Trailboard is not a doctor, nutritionist, dietitian, or medical service. Your nutrition profile, products, plans, and reviews remain private: no private nutrition data will ever be transmitted to a third party.

🤝

Your consent, asked at every step

Nothing is ever shared without a deliberate action on your part. Connecting Strava or Google goes through Strava's or Google's own authorization screen, before any data reaches Trailboard — and you can decline right there without ever landing on the site. From then on, every action that links you to someone else stays an explicit click: sending a friend request ("Devenir ami"), accepting or declining one, joining a challenge ("S'inscrire à ce défi"), or deleting your account (its own dedicated confirmation, detailed below). None of these ever happen automatically just from browsing the site.

📈

Audience measurement: anonymous, no cookies

Trailboard uses self-hosted Plausible to measure page views and understand general site usage. It sets no cookies, creates no persistent visitor identifier, does no fingerprinting, and does not track people across websites. The IP address is used only for the technical calculation of aggregated statistics and is not retained as identifiable data. In this setup, no consent banner is required, but you can still opt out of these stats below.

🍪

Cookies and local storage

Trailboard only uses cookies that are necessary for the service, mainly the login session and selected language. Some local settings may be stored in your browser, such as Plausible opt-out, a display preference, or a pending action. These items support site functionality and are not advertising trackers.

Why there is no GDPR pop-up

Trailboard does not show a generic GDPR pop-up because the site does not place any tracker requiring consent before browsing: no advertising, no retargeting, no cross-site tracking, no marketing SDK, and no third-party analytics with a persistent identifier. GDPR information is therefore provided here, on a publicly accessible page, and the consents that are needed are requested at the exact moment of the relevant action: Strava or Google sign-in, acceptance of the nutrition terms, friend request, challenge registration, or account deletion.

🛠️

Technical Direction

  • 🇫🇷 Server hosted in France.
  • 🧩 Preference for recognized open-source development tools.
  • 📈 Cookieless audience measurement with no cross-site tracking.
  • 🔐 Clear separation between personal data, sports data, nutrition, and social features.
  • 🗑️ Account and associated data deletion from the interface.
🌍

External services used

Some external services are called only when a feature requires them: Strava for login and activities if you connect it, Google for Google sign-in and some map or route features, YouTube for embedded video playback, IGN/cartes.gouv.fr for GPX maps, and email infrastructure for required messages. Trailboard does not sell your data and does not transmit your private nutrition data to these services.

👥

Member directory & friends: identity only

The directory uses only the profile you enter directly in Trailboard; identity received from Strava is never copied into it. Activities and Strava data never appear there. An account created with Strava remains hidden until the user takes an explicit action.

🏆

Challenges: the one exception, and why

Challenges let you compare results across several athletes — the only feature on Trailboard that does. It's only possible because no data from a Strava activity ever enters a challenge, at any point: no reading your activities, no automatic syncing, no pre-filling from a workout. A challenge result is only ever what a participant types in by hand (a race name, plus a number: kilometers, elevation, or time) — never a value read from your Strava account. Joining a challenge or logging a result stays, like everywhere else on the site, a voluntary and explicit action.

🗄️

Retention period

Data entered directly in Trailboard is kept while your account exists or while necessary for the requested service. Strava copies follow a separate rule: a transient cache for no more than seven days from each retrieval. Sessions, technical data, and security logs are limited to the time needed for operation and security.

🧰

Your rights

You can request access, rectification, erasure, restriction, objection, or portability of your data via the Contact page. When an action already exists in the interface, it remains the fastest path: make your profile invisible, reset your nutrition profile, or delete your account.

🗑️

Your data, deletable at any time

From "My account", "Delete my account" immediately and permanently erases everything tied to you: activities, connections, goals, challenges, favorites, videos, calendar, events, documents, nutrition data, and associated plans. No intentional delayed deletion, no copy used elsewhere.

🔑

Strava and Google, two independent sign-ins

You can use manual features with a Google account only, without connecting Strava. After signing in with Google, you may enter the Client ID and Client Secret of your own application; the secret is encrypted server-side and never displayed again.

⚖️

Third-party warranties and liability

To the extent permitted by law, third-party services are provided without warranties, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement. Those third-party providers, including Strava, are not liable for consequential, special, punitive, or indirect damages connected with the use of Trailboard.

Chargement…