Skip to content

Privacy Statement

Last updated: November 13, 2026

RUNCULTURE respects your privacy and processes as little personal data as possible. This statement explains what data we process, why, how long we keep it and which rights you have. This statement is part of our Terms and Conditions.

1. Who we are

RUNCULTURE (runculture.com) is the controller for the personal data processed through this website. For privacy questions you can reach us via the contact page on the website.

2. What data we process and why

Account — If you create an account we process your email address and the profile details you enter yourself (such as name, personal records and training preferences), to provide the service and store your settings.

Plans and training data — The data you enter to generate a plan (such as distance, goals and availability). If you create a plan without an account, you can optionally leave an email address to link the plan to an account later; that address is stored in a restricted way and deleted once the link is made.

Routes — The start locations and routes you enter or draw in the route editor. Your current location is only used if you grant permission in your browser, and is not stored unless you save the route.

Garmin Connect — If you connect your Garmin account, we process your Garmin user ID, the access keys for the connection, and the permissions you granted, and we send workouts from your plan and routes you choose to Garmin Connect. If you allowed Garmin to share your activities, we also receive your running activities from Garmin Connect™ by default (without a GPS track or location), including your heart rate; you can turn off both in the Garmin pop-up. See section 10.

Newsletter — Your email address, optionally your name, your language preference and the moment and source of sign-up. See section 4.

Contact forms — Name, email address and your message, so we can answer your question.

Runclubs — Contact details of the representative when claiming or managing a club page. If you sign up for a club event, we process your choice and optional message; the club manager sees these together with your name (first and optional last name, otherwise your username) and profile photo. If you are attending, members of that club see your first name (or your username if you have not set one), profile photo and the parts you are joining in the list of attendees (guests: first name only). Without an account we also process your name and email address for the confirmation, a reminder and withdrawing your sign-up. If you choose "Use my location" on the runclub overview, we use your location (rounded to about 1 km) once to find the nearest city with runclubs; we do not store it.

Security and technology — Your IP address is processed briefly for abuse prevention (rate limits and bot checks), but is not stored permanently. For share statistics we only use pseudonymized (hashed) values. Technical error reports are processed for debugging.

3. Legal bases

We process personal data based on:
• performance of the service — account, plans, routes, runclub management, contact handling, and the Garmin Connect integration if you turn it on yourself;
• consent — the newsletter for stand-alone sign-ups without an account, and the use of your location in the route editor;
• legitimate interest — the newsletter for account holders (existing customer relationship, see section 4), security, abuse prevention, error monitoring of the service, and visitor statistics to improve the site (see section 6).

4. Newsletter

  1. If you have an account (or create a plan with your email address), you receive our newsletter about RUNCULTURE and similar services of our own. This is stated at the moment you leave your email address, you can switch the newsletter off right at your first sign-in, and it is based on the existing customer relationship. If you sign up for the newsletter separately without an account, your sign-up is the consent. In both cases we record the moment and source of sign-up.
  2. You can unsubscribe at any time via the unsubscribe link in every newsletter or via your profile page, and unsubscribing is as easy as subscribing. After unsubscribing you no longer receive newsletters; that choice also remains in place if you sign in again later.
  3. We use a specialized email delivery service for sending (see section 5); your email address, name and language preference are shared with that service for this purpose.
  4. After unsubscribing we keep your address with the status "unsubscribed", so you are not emailed again without asking.

5. Processors and third parties

We only share personal data with service providers (processors) needed to provide the service, and have data processing agreements with them. These are the following categories:
• database and sign-in services — storage of accounts and entered data;
• hosting services — running the website;
• analytics services — visitor statistics to improve the site (see section 6);
• email delivery services — sending the newsletter and confirmation and contact email;
• security services — bot checks on forms and short-lived processing for rate limits;
• error monitoring — detecting technical errors;
• map and routing services — retrieving map imagery and route calculations; these requests are proxied through our own server.
For service providers outside the European Economic Area, appropriate safeguards apply, such as the European Commission's standard contractual clauses. An up-to-date overview of the processors we use is available on request via the contact page.

6. Cookies and local storage

  1. We use functional cookies for signing in (session).
  2. Preferences such as theme, units and language are stored locally in your browser.
  3. For visitor statistics we use Google Analytics by Google Ireland Limited. We've configured Google Analytics to be as privacy-friendly as possible: we have a data processing agreement with Google, data sharing with Google is turned off, we don't use advertising or remarketing features or Google signals, and we don't connect Google Analytics to other Google services. Google does not store IP addresses for visitors from the EU. We remove personal links, such as the link to cancel an RSVP, from the web address before sending. Google Analytics sets the cookies _ga and _ga_<id>, which expire after 13 months. Detailed data is kept for 2 months; after that, only aggregated numbers remain. Data may be processed in the United States; Google LLC is certified under the EU-U.S. Data Privacy Framework. If you'd rather not be counted, you can block these cookies in your browser; the site will keep working normally.
  4. We also count visits with Vercel Web Analytics. It sets no cookies and only counts visits as aggregated numbers.
  5. We do not use advertising cookies.

7. Retention periods

  1. Account — until you delete your account, which you can do yourself at any time via your profile page. Your profile data and newsletter subscription are deleted along with it.
  2. Newsletter — until you unsubscribe (after which only the unsubscribed status remains) or until your account is deleted.
  3. Anonymous plans — the optional email address for claiming is deleted once the plan is linked to an account.
  4. Contact messages — as long as needed to handle your question.
  5. Club event sign-ups — the name, email address and message of a sign-up without an account are deleted automatically 30 days after the event; sign-ups with an account are covered by your account.
  6. Garmin integration — connection data until you disconnect or delete your account; after that we delete your Garmin user ID, access keys, and permissions. We keep imported activities (and, while heart rate is on, heart rate data) for as long as your account exists, even after you disconnect or turn off importing, until you have them deleted or delete your account. If you turn off heart rate, we delete the stored heart rate data right away. A notification from Garmin waiting to be processed no longer contains any data once it is processed and is removed after 3 days (after 7 days if processing failed). See section 10.

8. Your rights

You have the right to access, rectification, erasure, restriction of processing, objection and data portability. You can delete your account (and the associated data) yourself via your profile page; for other requests, contact us via the contact page. If you disagree with how we handle your data, you can lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

9. Security

We take appropriate technical and organizational measures to protect your data, including encrypted connections (TLS), strict database access restrictions and separating personal data from publicly visible content.

10. Garmin Connect integration

  1. What we receive when you connect — If you connect your Garmin account (which you always do yourself, through Garmin's consent screen), we receive and store your Garmin user ID, the access keys for the connection (stored encrypted), and the permissions you granted to Garmin.
  2. Importing completed workouts — In the Garmin pop-up on RUNCULTURE, under "Import completed workouts," you choose Automatically (the default), Per workout, or Off. We receive your running activities through Garmin Connect™ only if you allowed Garmin to share activities on Garmin's consent screen. We discard activities from other sports (including obstacle runs and wheelchair activities) right away. For each run, we store: start time and date (with time zone offset), duration, distance, average speed and pace, elevation gain, calories, cadence, the name of your device, whether the activity was entered manually, lap splits (time and distance per lap), and which workout in your active plan the run is linked to. In addition, for each run we read the activity file (FIT file) once to get the effort score (1–10) and the feel you may have entered on your watch, the name of the workout your watch ran, and a list of which fields the file contains (without their values); we do not keep the file itself. We first store a notification from Garmin briefly (without GPS or location, heart rate only if it is on) so we can process it again if something goes wrong; once it is processed, none of its contents remain, and the notification is removed after 3 days (after 7 days if processing failed). We do not store a GPS track, route, or start location, and outside that queue we do not store the data as Garmin delivers it.
  3. Heart rate — Heart rate is health data (Art. 9 GDPR). By default, we store your average and maximum heart rate for your runs and your heart rate over the course of the workout (reduced to one reading every few seconds, with time and distance for each point). Only you can see this data. If you don't want this, turn off the "Also save my heart rate" switch in the Garmin pop-up. We then delete the stored heart rate data right away, including from notifications still waiting to be processed, and stop storing new heart rate data; anything Garmin still sends, we discard right away.
  4. What we send to Garmin — Workouts from your active plan, if you sync it to Garmin: name, description, steps (such as duration, distance, and pace), and the scheduled date. If you send a saved route to Garmin yourself, we send it as a course: name, short description, the route path (coordinates with elevation), distance, elevation gain, and drinking water points along the route. They appear in your Garmin Connect account and on your watch. Garmin then processes them under its own privacy policy.
  5. Why — To keep your training plan in Garmin Connect up to date (adding new workouts and updating workouts that changed or moved) and to put routes you choose on your watch. If you import completed workouts, we use them only to check off workouts with the distance and time you ran (automatically, or per workout after you confirm), compare planned and completed runs, show the run with its workout (with a heart rate chart if heart rate is on), suggest a suitable run as a test run (always only after you confirm), and count standalone runs as "extra" in your weekly total. We do not automatically adjust your plan based on what you ran.
  6. Legal basis — Connecting and sending workouts and routes to Garmin are part of performing the service, which you turn on yourself (see section 3). We receive completed workouts only if you allowed Garmin, on Garmin's consent screen, to share your activities with RUNCULTURE; you can set importing to Off in the Garmin pop-up. Heart rate is on by default; you can turn it off at any time, after which we delete the stored heart rate data right away (see item 3). Turning it off does not affect processing that took place before.
  7. Who processes the data — Apart from Garmin itself, only our processors: Vercel Inc. (hosting and servers), Supabase Inc. (database), and Functional Software Inc. (Sentry, technical error reports, without access keys). This also applies to imported activities and heart rate data. For parties outside the European Economic Area, the safeguards from section 5 apply.
  8. No sale, no AI — We do not sell Garmin data, including imported activities and heart rate data, or share it with third parties for their own purposes. We do not use it in AI systems or to train, test, or improve AI models.
  9. Retention and deletion — We keep connection data until you disconnect or delete your account. We keep imported activities (and, while heart rate is on, heart rate data) for as long as your account exists, even after you disconnect or turn off importing, until you have them deleted or delete your account. To have them deleted, you can delete your account (which also removes all your activities) or ask us via the contact page to delete your imported activities.
  10. Withdrawing consent — To stop importing completed workouts, set the choice in the Garmin pop-up to Off. To turn off heart rate, use the switch in the Garmin pop-up (see item 3). You can disconnect entirely at any time through your RUNCULTURE account or in Garmin Connect (Settings → Account Information → Connected Apps). We then stop syncing and importing right away, remove upcoming RUNCULTURE workouts from your Garmin calendar (when you disconnect through RUNCULTURE), and delete your Garmin user ID, access keys, and permissions. Imported activities are kept (see item 9) until you have them deleted or delete your account. Past workouts remain in Garmin Connect; you can delete them there yourself.
  11. Access and your other rights — To access, correct, delete, or export the Garmin data we hold about you, reach out via the contact page; see also section 8.

11. Changes

We may update this privacy statement, for example when the service changes. The date at the top indicates the latest change. For significant changes we will inform you via the website.

12. Contact

Questions about this privacy statement or about your data? Reach out via the contact page on the website. See also the Terms and Conditions.