Privacy
Last updated: 06/11/2026
This explains which data RynkePoints processes, what for, who sees it, how long it is kept and what your rights are.
Who is responsible, and how to reach us
Responsible for the processing of data in RynkePoints is:
Sascha Steffen
For questions, help, a copy of your data or its deletion, write to support@rynke-points.eu.
What RynkePoints processes data for
RynkePoints is the training app of Team Rynkeby Europe. It reads the key figures of your activities from Strava, turns them into Rynke (training points) and badges, and shows them to you, the team and the organisers. There are no ads, no payments, no tracking and no analytics tools. Data is never sold or passed on, and never used for AI or machine learning.
Data from Strava
About you: your Strava athlete ID, your first name, the permissions you granted, and the access keys (tokens), stored encrypted.
For each ride: activity ID, title, sport type, start time and time zone, distance, moving and elapsed time, elevation gain, and whether it was entered manually, ridden on an indoor trainer, is private or was flagged by Strava.
For each run and each swim only the activity ID, start time, distance and whether it is private, for the running and swimming badges.
Only activities from the season start on are stored, and private (“Only You”) ones only if you granted the permission for them.
Never read or stored: GPS tracks, maps, routes, segments, photos, descriptions, heart rate, power, cadence, calories or other health data, your followers, and other athletes' data.
Strava reports new, changed and deleted activities by itself; RynkePoints doesn't keep asking. Once a day RynkePoints checks that you are still a member of the team's Strava club.
Data from the team, and what is worked out from it
The organisers can correct your Rynke with a reason and a date. Who changed what, and when, is stored too.
From all this RynkePoints works out your Rynke, your badges and which rides count, and why.
From your counting rides RynkePoints counts sessions, kilometres and elevation per season, month and week for the ranking without names, and your typical ride, which only you and the organisers see. The organisers see your sessions per season and per day with your first name.
Data needed to run the app
Cookies: “rp_session” keeps you signed in, until 180 days after your last visit; “rp_oauth_state” protects the sign-in with Strava for 10 minutes; “rp_lang” remembers a picked language for a year. There are no other cookies and no trackers.
Notifications are optional and per device. Only the address your device's or browser's push service gives it is stored. The notification itself is empty: what it shows, your device fetches straight from RynkePoints. The address is deleted when you turn notifications off, sign out on that device or leave.
Server logs hold only identifiers such as athlete and activity IDs and the kind of an error, never access keys or activity data. RynkePoints doesn't store IP addresses.
Who sees what
You see your own activities with their titles, your Rynke and your badges. Nobody else sees the titles.
Everyone else on the team sees your Rynke, overall and per week, without your name. Your kilometres and elevation, and on which days and at what hour you are active, count towards the team sums and team badges, without your name.
The organisers see your first name, your Rynke and where they come from, what you still need, whether you've reached your training goal, their corrections, and your kilometres outdoors and virtually and your elevation as totals per day, but no individual activities.
The administrators, who run the app for the team, see your first name, whether you're connected and since when, when your club membership was last checked and whether your import is still running, but no activities or Rynke.
None of it is public: every page with this data needs you to sign in with Strava.
Legal basis
Reading your Strava data and sharing your Rynke as described rest on your consent, given before you connect (Art. 6(1)(a) GDPR). Corrections, the necessary cookies and the logs rest on the legitimate interest in organising the team's training and running the app securely (Art. 6(1)(f) GDPR; for cookies § 25(2) TDDDG).
The block list rests on the team's legitimate interest in keeping out someone it has removed (Art. 6(1)(f) GDPR), not on consent. To ask for its erasure, write to the person responsible named above.
How long data is kept
Your data is kept while you are connected, and follows Strava: if you delete an activity on Strava, or make it private without having granted the permission for that, it disappears here too as soon as Strava reports it, usually within minutes. Activities from before the season start are deleted.
All data about you is deleted at once, and access on Strava is revoked where it still works, when you disconnect in the app, remove RynkePoints in your Strava settings, leave the team's Strava club (within 24 hours), or don't renew a broken connection within 7 days.
The one exception: if an administrator removes you, your Strava ID stays on the team's block list while the team runs the app, with no name, date or reason, so you can't connect again. Everything else is deleted.
After that the data stays in the database's automatic backups for at most 7 days, then it is gone. Cloudflare deletes server logs after at most 7 days.
At the end of every season we make a season album as a PDF for everyone on the team – from the data you see in the app and sums over the whole team. This happens on the computer of the person responsible, not at Cloudflare. Only you get your album, and it is deleted afterwards.
Who processes the data
RynkePoints runs on Cloudflare, Inc. as a processor: web server, work queue and database. To deliver the pages and protect them from attacks, Cloudflare necessarily processes your IP address. Cloudflare has data centres worldwide, including in the USA; for transfers there, Cloudflare is certified under the EU-US Data Privacy Framework, and the EU Standard Contractual Clauses apply.
The push services of the device and browser makers (such as Google, Apple, Mozilla, Microsoft) only receive empty notifications to your device's address.
Strava itself is responsible for the data in your Strava account. The Strava Privacy Policy applies, and takes precedence where it conflicts with this notice.
Strava may collect usage data about how RynkePoints uses the Strava API, and use it for any business purpose, such as improving the API and the Strava platform, providing support, or checking compliance with its terms.
Links to Strava
Links to Strava lead to pages run by Strava, which alone is responsible for their content. RynkePoints doesn't adopt that content as its own and has no influence on it. If we learn of unlawful content on a linked page, we remove the link.
Your rights
You have the right of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15 to 21 GDPR). You can withdraw your consent at any time, most simply by disconnecting in the app; what happened before stays lawful. You can also complain to a data protection supervisory authority, in particular where you live. For anything, reach us at support@rynke-points.eu.
Changes
If what RynkePoints reads, or who sees it, changes, we ask for your consent again before the app shows you anything.