1. Who are we?
In this cookie policy, "we", "us" and "TrainerLink" mean Olympus Performance, trading as TrainerLink, the provider of this platform.
You can find our full business details on the Business details. More information about how we process personal data is in our Privacy statement.
3. Why do we use cookies?
We use cookies and similar technologies to keep TrainerLink safe, working well and easy to use. This includes sign-in, security, bookings, payments, language settings and remembering your cookie preferences.
With your consent, we may also use statistics and marketing cookies to improve the platform, measure performance and measure advertising campaigns or conversions. These categories are off by default.
Where needed, we use privacy-limited telemetry for error monitoring. It helps us investigate errors, abuse signals and security problems, not build marketing profiles. Product analytics and performance measurement load only after analytics consent. The public entry analytics below is always consent-based.
Public entry analytics (statistics/analytics)
This local browser technology helps us understand which public page families visitors view and evaluate public SEO work. The category is statistics/analytics. It stays off until you give analytics consent; analytics consent is the legal basis for this processing (GDPR Article 6(1)(a)).
After analytics consent, TrainerLink may locally record the first suitable public page observed afterwards in your browser. This is not necessarily the first page visited before consent and does not prove that your visit came from organic search results. Current suitable pages include the homepage, the clean trainer discovery page, clean personal trainer city pages and existing public trainer profiles. Trainer discovery and city pages with query, search or filter parameters are excluded.
This uses localStorage key trainerlink.analytics.organicEntry.v1. The record contains only entry_path (a normalized public route template, for example /personal-trainers/[city] or /personal-trainers/profiel/[profile]; placeholders represent the city, trainer number and slug; the exact city and query string are not stored), entry_family (the public page family), entry_locale (the language/locale) and entry_captured_at (capture time). The first touch remains unchanged until the record expires. The context can be used for up to 90 days. After that, an expired record is no longer usable and is removed at the next local storage access. If the browser stays closed, background removal is not guaranteed.
The four safe fields may be added to selected existing analytics events through the current PostHog EU analytics pipeline, where PostHog EU acts as analytics processor/recipient. No new event family or provider is introduced. We do not use this for profiling, session replay, heatmaps or automated decision-making.
For this context we do not send URL query strings, search or filter text, full referrer URLs, names, email addresses, account or trainer IDs, exact addresses, GPS locations, health data, booking, chat or payment content, uploads or free text.
If you withdraw analytics consent through the current Cookie settings, that consent flow immediately attempts to remove this browser record and stops future analytics and enrichment. We do not promise automatic retroactive deletion of provider events already sent. Your privacy rights, such as access, deletion and objection, apply separately. The platform remains usable when you refuse or withdraw analytics; only non-essential measurement and enrichment stop.
4. What types of cookies do we use?
Necessary cookies
These cookies and similar technologies are needed for TrainerLink to work safely, including sign-in, session management, security, bookings, payments and storing your cookie preferences.
Preference cookies
These cookies remember practical choices such as language, theme, city or the last selected account mode. We use them only where consent is required and you have given it.
Statistics cookies
These cookies help us understand how TrainerLink is used and where we can improve the platform. We use them only with your consent.
Marketing cookies
These cookies may be used for advertising measurement, conversions and relevant marketing. We use them only with your consent.
5. Cookie overview
The current Cookiebot cookie declaration appears below. It updates automatically based on the cookies and similar technologies Cookiebot detects on TrainerLink. For each cookie or similar technology it shows, among other things, the provider, purpose, category and retention period.
6. Giving, changing or withdrawing consent
Necessary cookies do not require consent. We ask for consent before using statistics and marketing cookies. Consent is always required for public entry analytics. You can change or withdraw your consent at any time.
7. Rejecting or blocking cookies
You can reject non-essential cookies through the cookie banner or cookie settings. You can also block or delete cookies through your browser settings. TrainerLink may work less well or not at all if you block necessary cookies.
8. What data can be processed through cookies?
Cookies and similar technologies may process your cookie preferences, session data, technical browser and device data, IP address, page views, click behaviour, referring pages and conversion or campaign data. The exact data depends on the cookie or technology and is shown where possible in the Cookiebot declaration.
At launch, TrainerLink does not use heatmaps, session recordings, PostHog autocapture or PostHog session replay. We do not allow payment card data, IBANs, login data, chat messages, health data, private addresses, exact GPS locations, uploads or raw free text to be collected through analytics or replay tools.
9. Which third parties may use cookies or similar technologies?
We work with providers that help keep the platform safe, working well and relevant. These include hosting and security, login and account functions, booking and payment functions, analytics and error monitoring, consent management and advertising or marketing services.
For cookies and similar technologies, this may include Supabase for first-party analytics and consent auditing, Sentry for error monitoring, PostHog EU for product analytics after analytics consent, Vercel Speed Insights after analytics consent, Cookiebot for consent management and Google Tag Manager for consent-controlled tags. Sentry is for error and security monitoring; PostHog and Vercel Speed Insights are analytics/performance tools and must not load without analytics consent.
Not every provider places cookies or similar technologies, and the cookies used may change. We therefore show the current overview through the Cookiebot declaration on this page. It lists, among other things, the provider, purpose, category and retention period for each cookie or similar technology.
10. Retention periods
Cookies and similar technologies are not used or kept longer than needed for the purpose for which they were placed, unless a longer period is legally required. The current retention period for each cookie is in the Cookiebot declaration.
11. Transfers outside the EEA
Some providers may process data outside the European Economic Area. Where this happens, we use appropriate safeguards such as an adequacy decision, Standard Contractual Clauses, the EU-US Data Privacy Framework or other measures permitted by the GDPR.
12. Your privacy rights
If cookies or similar technologies process personal data, you may have rights such as access, correction, deletion, restriction, data portability, objection and withdrawal of consent. More information is in our Privacy statement.
13. Changes
We may change this cookie policy when our services, cookies or legal obligations change. The latest version is always on this page.
14. Contact
For questions about this cookie policy or privacy, contact us at support@trainerlink.nl.