Privacy Policy
Last updated 2026-11-20
In short
- We keep what you need for your account, your rides, your routes and your training plan, and nothing for advertising. We don't sell your data.
- Heart rate and Garmin health data are used only if you allow it, and you can withdraw that at any time in Settings → Your data.
- Strava and Garmin Connect™ only get or send data if you connect them.
- Analytics run only if you click “Accept” in the cookie banner.
- Download everything in your account, or delete your account, at any time in Settings → Your data. Deleting is immediate.
- An account nobody has used for about two years is deleted, after a warning email.
Who is responsible
MB "MR Labs", company code 308157519, Ateities g. 31-17, LT-30121 Ignalina, Lithuania, is the controller of your personal data. We don't have a data protection officer. For anything about your data, write to support@blockride.cc.
What we collect and why
Each item says what we use, why, the legal basis under the GDPR and how long we keep it. The sections further down give the details.
To run your account and the game (contract, Article 6(1)(b)):
- Account: your email address, your password (stored by Firebase Authentication only as a hash), your name and profile picture if you sign in with Google, when the account was made, when you last signed in, and which version of these terms and this policy you agreed to. Kept while you have an account.
- Signed-in devices: for each device you sign in on, a short name such as "Chrome on Mac", when you signed in, when it was last used and when it was signed out, so you can see where you're signed in and sign a device out. Kept 14 days after the device was last used.
- Rides: what you save after a ride (see Your rides), and the game progress worked out from them. Kept until you delete the ride or your account.
- Routes: the routes in My routes, and a copy of a route you saved a ride on (see Your rides).
- Settings: the game's settings, kept with your account (see Settings).
- Training: your training profile, plan, activities, “how did it feel” answers and coach reviews, for Supporters (see Training).
- Nickname and POP UP Rides: your nickname and the group rides you host or join (see Nickname and POP UP Rides).
- Sign-in codes: codes you make to sign in on an iPad or iPhone (see Sign-in codes).
- Connected apps: what we need to work with Strava and Garmin Connect™ when you connect them (see Strava and Garmin Connect).
- Account emails: your email address, to send the emails listed under Emails we send.
With your explicit consent (Article 9(2)(a), and Article 6(1)(a)):
- Health data: heart rate and the Garmin daily health data you choose to share (see Health data).
With your consent (Article 6(1)(a)):
- Website analytics: only if you click “Accept” (see Website analytics). Detailed visit data is kept 2 months, data linking visits from the same browser 14 months.
For our legitimate interests (Article 6(1)(f)): keeping the service secure and working, and giving you the world you asked for.
- Security and server logs: sign-in events, IP address, browser details, your account ID and what was asked of our server, and whether each request passed our security check. Used for security and troubleshooting. Kept up to 30 days.
- Protection against abuse: reCAPTCHA through Firebase App Check (see Protection against abuse).
- Rate limits: counters of how often an email address, an IP address or an account asked for emails, sign-in codes or account changes, so nobody can flood the service. Email addresses and IP addresses are stored only as a hash, not in plain text, and these counters are deleted within a day. Daily counts of the issue reports and FIT files you sent are kept with your account.
- Map and weather: a simplified line along your route, used for one request and not stored (see Your rides).
- Issue reports: reports you send from the game, if you were invited to send them (see Issue reports). Kept 180 days.
- Deleted accounts: a daily count of how many accounts were deleted, with nothing about who.
What you must give us: an email address, because there is no account without one. Everything else is optional: health data, Strava, Garmin, issue reports and a nickname (needed only for POP UP Rides). Without them, the features that need them don't work, and everything else does.
Your rides
A GPX file you choose for a ride is read in your browser, and the world is built from it there. The file is uploaded to our servers only in these cases:
- You are a Supporter and add it to My routes. We keep a cleaned copy in your account (the route's points, heights, surface tags and name) until you delete the route.
- You host a POP UP Ride on it. The cleaned copy is given to the riders who join and our copy for the ride is deleted after 7 days. Riders who joined can save the route to their own My routes and keep it.
- You are a Supporter and save a ride you did on it. We keep the cleaned copy for 90 days so you can add the route to My routes, then delete it. Deleting the ride deletes it straight away.
Times, heart rate, power and device details in the file are removed before anything is stored. Your routes are private to your account; nobody else can see or ride them unless you host a POP UP Ride on one (contract).
To build the world with real towns, water and terrain, the game sends a simplified line along your route (one point every 400 m or more) to our server. The server uses it only to work out which map squares, about 6 km across, the route passes through, looks up public map data for those squares and cuts it back to the route. The line isn't stored or linked to your account; it's used for that request and then discarded (legitimate interest: building the world you asked for). The game keeps the map data it gets in your browser, so the same route loads faster next time.
With Real weather on (the default; you can choose Calm in the game's settings instead), the game also sends that line to our server to get the current weather along the route. The server works out which weather squares (0.1°, about 10 km across) the route passes and the squares around them, and gets the forecast for each square's centre from MET Norway (see Weather data below). The line isn't stored or linked to your account; it's used for that request and then discarded (legitimate interest: riding in the weather you asked for).
When you finish or stop a ride in the browser version and choose to save it, we store it in your account: the route name, start time, the weather it was ridden in (wind, rain and temperature, or Calm), where the power came from (trainer or power meter, with the names the game showed for them, and whether anything set the resistance), and one sample per second of position on the route, elevation, distance, speed, power, cadence and, if you allow health data, heart rate. We use it to show your ride history, let you download it and send it to apps you connect (contract). From your rides we also work out your game progress (XP, level, badges, segment records and the "ghost" of your best ride on each route), which only you can see. You can delete any ride at any time in your account.
Health data
Heart rate, and anything worked out from it, is health data, and so is the daily data you share from Garmin Connect™. The GDPR protects it more strictly, so we use it only with your explicit consent (Article 9(2)(a)). This covers:
- heart rate from a heart-rate sensor, saved with your rides;
- from activities you import (Strava, Garmin or a FIT file): average and highest heart rate, used to work out training load when there's no power, and the highest heart rate seen, kept as one number on your training profile;
- your heart rate at a steady effort, worked out from each ride and kept with your training data and challenge profile, used to size challenges;
- Garmin daily data: resting heart rate, heart rate variability (HRV), sleep score, stress, Body Battery™ and weight, and the plan changes made from them.
Where we ask: in the game when a heart-rate sensor connects, on the account page before you connect Garmin, and at any time under Settings → Your data. We record your answer and when you gave it.
If you say no, or don't answer: rides are saved without heart rate, imported activities count by their power or their time only, challenges don't adapt to your heart rate, and Garmin Connect can't be connected. Everything else works as before.
Riders from before we asked: if you had not answered, heart rate keeps being saved and used as before, and a Garmin connection made before keeps working, until 1 December 2026. From that day, no answer counts as no. Connecting Garmin always needs a yes.
How we use it: only to show your rides, work out training load and adapt your challenges and training plan. It is shown only to you. It is never used for AI features, including the AI coach, never used for advertising, and never sold or shared with anyone, except that a ride you send to Strava carries its heart rate. Plan-change emails say what changed in your plan, not the health values behind it.
Withdrawing: go to Settings → Your data and press Withdraw. Withdrawing doesn't affect what happened before. When you withdraw:
- Garmin Connect is disconnected, and everything BlockRide got from Garmin is deleted (see Garmin Connect). Your plan stops changing from health data, and the record of the changes it made is deleted.
- Heart rate from imported activities is deleted, and their training load is worked out from time instead. The highest heart rate on your training profile is deleted.
- Your typical heart rate for challenges is deleted, and new rides are saved without heart rate.
- Your saved rides keep their heart rate unless you tick Also remove heart rate from my saved rides; then it is removed from every saved ride.
- Rides already on Strava are not changed; delete or edit them on Strava.
Settings
The game's settings are stored in your account, so they follow you to any browser, and the game also keeps a copy in your browser. They are: rider weight, trainer difficulty, weather (Real or Calm), graphics and style, virtual shifting, the battery tile, coach messages and plan-change emails, your coach, the names and models of the Bluetooth devices you used (never their Bluetooth IDs), and the last spin-down calibration of your trainer with its firmware. We use them to run the game the way you set it (contract). They are kept while you have an account.
Nickname and POP UP Rides
To ride with others you choose a nickname in Settings. It's unique, and you can change it once every 30 days. We keep it with your account.
In a POP UP Ride (for Supporters), the other riders in the same ride see your nickname, your rider's look (jersey, helmet, bike, skin, face and figure), whether you are the host, whether your world has loaded and your trainer is connected, and while riding your position on the route, your speed and your finish time. The nickname of a ride's host, the ride's name, its distance, climbing, the country it starts in and how many riders have joined are shown in the list of open rides to every player who can see that list. Positions pass through our live server and are kept in memory only, never stored or logged. When your connection drops mid-ride, we note how far you had got, so you can rejoin.
The ride's record (who joined, finish times and the host's nickname) is deleted about 7 days after the ride (within a day after that), and the route file after 7 days. We use this to run the group ride you joined (contract).
Training
If you are a Supporter, we work out a training profile from the power in your saved rides: your threshold power, battery (W′) and peak power, with the best efforts they came from and how they changed over time. From each session in your account we work out its training load, and from those your fitness, fatigue and form. If you make a training plan, we store your answers (goal, event date, focus, hours and riding days) and the plan made from them. You can leave any session out of your plan, and set a starting point for your fitness. We use all of this only to size your workouts and run your plan, and only you can see it (contract). Ending a plan deletes the plan; deleting a ride removes it from your load. The rest is kept while you have an account.
After a ride the game asks how did it feel. Your answer is saved with the ride and used to make your next sessions and challenges easier or harder. Every rider also has a challenge profile: how hard your Catch, Drop and Hold challenges should be, how they went, your best times and your record against the game's computer riders. Only you can see it, and it's kept while you have an account.
As a Supporter you can also add a session from a FIT file (exported from a watch or bike computer) on the Activities page. The file is read on our server to work out the session's training load from its power or, if you allow health data, its heart rate, and then discarded: we keep the session's name (the file name), sport, start time, duration and load, never the file, its GPS track or its samples (contract).
Automated decisions. Your training plan is adapted automatically: from your rides and how they felt, and, if you allow health data, from your heart rate and Garmin daily data. This is profiling, but it has no legal or similarly significant effect on you: it only changes the workouts suggested to you. You can end the plan, leave any session out of it, change a week yourself, or withdraw health data consent at any time.
AI coach (Supporters). To write a short summary of a ride in your coach's voice, BlockRide sends the ride's numbers (the workout, load, battery and your "how did it feel" answer) to Google's Gemini models on Vertex AI, processed in the EU. Nothing that identifies you, such as your name, email or location, is sent, and no heart rate or other health data. Google processes it only to write the reply and does not use it to train its models. Activities imported from Strava or Garmin are never sent: their summaries are written by rules on our server. Summaries are stored with the ride on your account and deleted with it.
Strava
If you connect Strava, we store the access tokens Strava gives us, your Strava athlete ID and the IDs of the activities we upload. We don't store your Strava name, photo or anything else from your Strava profile. Each saved ride is then uploaded to your Strava account as a Virtual Ride, including the route map and the data above, and Strava handles it under its own privacy policy. Unless you also allow reading (below), we only upload and don't read your other Strava activities. Disconnect Strava in your account at any time, or revoke BlockRide in your Strava settings: we then delete the tokens, the Strava activity IDs and everything we imported from Strava straight away (your rides stay in your BlockRide account). Rides already uploaded stay on Strava until you delete them there.
If you are a Supporter and allow Training plan imports in Connected apps, Strava asks you to let BlockRide read your activities. We then read each activity you record on Strava (and the last 6 weeks of them when you allow it): its name, sport, start time, duration, whether it was indoors, average and maximum heart rate, and for rides with a power meter its power, second by second. We use them to work out the training load of each session and add it to your training plan, so the plan counts what you do away from BlockRide (contract). We keep the activity's name, sport, start, duration and the load worked out from it. If you allow health data, we also use its heart rate to estimate load when there's no power, and keep the highest heart rate seen as one number on your training profile; without it we don't use or keep heart rate. We don't keep the power or heart-rate samples, GPS tracks or anything else from Strava. This is shown only to you and never shared with anyone or used for AI features. Choose which sports count in Connected apps; turning a sport off deletes its imported activities, and disconnecting Strava deletes all of them.
Garmin Connect
If you are a Supporter and connect Garmin Connect™, Garmin asks you which data to share with BlockRide, and you can change that in your Garmin Connect account at any time. Connecting needs your consent to health data first (see Health data). We store the access tokens Garmin gives us, your Garmin user ID and which data you agreed to share. We don't store your Garmin name, photo or anything else from your Garmin profile.
- Activities: each activity you record on a Garmin device is sent to us as its file. We read it on our server to work out the session's training load from its power or heart rate and add it to your training plan, and then discard the file. As with Strava imports, we keep the activity's name, sport, start time, duration, the load worked out from it and the Garmin device name, and the highest heart rate seen as one number on your training profile; we don't keep the power or heart-rate samples or GPS tracks. When the same session also reaches us from BlockRide, a FIT file or Strava, we keep it once.
- Daily health data: for each day, your resting heart rate, overnight heart rate variability (HRV), sleep score, average stress level, Body Battery™ values and weight. We compare them with your own average of the previous 4 weeks to make planned workouts easier when your body shows strain or harder when it has room, and use your weight for watts-per-kg targets: a new weigh-in updates the rider weight in your settings. We keep each day's values for 60 days, then delete them.
- Plan changes: when your health data changes your plan, we tell you what changed and why in the game and, unless you turn Plan change emails off in Settings → Rider, by email, in your coach's voice. These messages come from fixed templates, not AI. The notice in the game quotes the values behind the change and is deleted after 60 days, like the data it comes from; the email says only what changed. Your plan also keeps a record of its health-based changes, with the values behind them, for the same 60 days, or until the plan ends, you disconnect Garmin or you withdraw consent.
We use this data only to run your training plan, with your consent. It is shown only to you, never sold or shared with anyone for their own use, and never sent to AI services, including the AI coach, or used to train or test AI models. These plan changes are training advice, not medical advice. Garmin handles your data on its side under its own privacy notice.
Disconnect Garmin in Connected apps at any time, or remove BlockRide in your Garmin Connect account: we then delete the tokens, your Garmin user ID, your daily health data, the plan-change notices and the activities imported from Garmin straight away. The rider weight in your settings stays as it was. Turning off a type of data in Garmin Connect stops it reaching us.
Sign-in codes
On an iPad or iPhone you can sign in with a one-time code made on your account page. We store the code only as a hash, with when it was made and used and the browser details of the devices that made and used it; the code works for 10 minutes and its record is deleted within a day after that. Each time a code is used we email you, and we keep the last 5 code sign-ins (when, and the kind of device, such as "Bluefy on iPad") so you can check them on your account page. We use this to keep your account secure (contract and legitimate interest).
Issue reports
Accounts we invite to help test BlockRide can send an issue report from the game. A report holds what you write, a screenshot of the game, the place on the route with about 1 km of the route around it, the ride's values at that moment (time, power, speed, cadence, climbing, rider weight and difficulty, and heart rate only if health data is allowed), the game world and weather there, your browser, screen and graphics details, the names, makers, models and firmware of your trainer, power meter and other Bluetooth devices, recent Bluetooth errors, and your email address and account ID. We use it to find and fix the problem (legitimate interest), and delete it 180 days after you sent it.
Emails we send
We send account emails through Brevo: confirming your email address, resetting your password, changing your email address, a code sign-in on another device, a plan change from your health data, asking about health data consent, your account being deleted, and a warning before an unused account is deleted. When you change your email address, Firebase (Google) sends the old address a link to undo it. We don't send marketing emails.
Protection against abuse (reCAPTCHA)
To stop automated sign-ups, password guessing and scripts that misuse our server, the sign-in and account pages and the browser version of the game use Google reCAPTCHA through Firebase App Check. It checks in the background that requests come from a real browser on blockride.cc; you won't be asked to solve a puzzle.
- reCAPTCHA collects technical data about your device and browser (such as browser and screen details, IP address and how the page is used) and sends it to Google, which returns a score. We see only that score and whether the check passed, not the data behind it.
- The legal basis is our legitimate interest in keeping accounts and the service secure (GDPR Article 6(1)(f)). Because it's needed for security, it runs without asking for consent.
- Google processes this data as our processor under the Google Cloud terms. Google may transfer it to the USA; Google LLC is certified under the EU-U.S. Data Privacy Framework. See Google's privacy policy and terms of service.
- If a browser extension or privacy setting blocks reCAPTCHA, signing in and saving rides may stop working; allow it for blockride.cc to continue.
Website analytics (only with your consent)
If you click “Accept” in the cookie banner, we use Google Analytics 4 to understand how people use this website: which pages are visited, how visitors arrived (for example from a search engine or a link), whether a visit led to creating an account (and whether by email or Google), and general device, browser, language and approximate location (country or city) details. We use it to improve the website and decide what to build next. The legal basis is your consent (GDPR Article 6(1)(a), and Article 61 of the Lithuanian Law on Electronic Communications for the cookies).
- Nothing is loaded from Google and no analytics cookies are set until you click “Accept”. If you click “Reject”, or don't answer, Google Analytics stays off.
- Google Analytics 4 doesn't log or store IP addresses; they are used only briefly to estimate location. We don't use Google Signals, advertising features or user-ID tracking, and we don't send your name, email, account ID or ride data to Google Analytics. When you delete your account, we count that as one event with no details about you.
- The data is processed by Google Ireland Ltd as our processor. Google may transfer it to the USA; Google LLC is certified under the EU-U.S. Data Privacy Framework.
- Google deletes the detailed data about each visit after 2 months, and the data that links visits from the same browser after 14 months. Our reports keep only totals, with nothing about who you are.
- You can withdraw your consent at any time: open cookie settings (also linked at the bottom of every page) and click “Reject”. We then stop analytics and delete the analytics cookies from your browser.
Separately from Google Analytics, when you open a BlockRide link from a ride on Strava (blockride.cc/strava), our server adds one to a daily count of clicks before taking you to the home page. Only the date and the total are kept: no IP address, cookie, device details or anything else that could identify you.
Cookies and similar storage
Essential (always on, no consent needed because the site and game can't work as you ask without them):
__session: keeps you signed in to the browser version. It expires after 14 days.- Firebase Authentication stores your sign-in state in your browser's storage, and
br.signedIn(local storage) remembers that you're signed in, so the pages show the right links. - reCAPTCHA stores a small amount of data in your browser (for example the
_GRECAPTCHAentry) for its security check, and Firebase App Check keeps the resulting short-lived token (valid for a day) in your browser's storage. br.consent(local storage): remembers whether you accepted or rejected analytics, so we don't ask on every page.br.cooldown.*(local storage): how long to wait before you can ask for another email or code, after too many tries.br.hcBanner(session storage) andtr-hours-keep:*(local storage): that you closed the health data notice for this visit, or chose Keep on a suggestion to change your plan's hours.- The game, in local storage:
blockride.settingsandblockride.settingsPending(your settings, and whether a change still has to reach your account),blockride.supporter(whether you are a Supporter),blockride.seen(which new features you have seen),blockride.lastRidden(the featured route you rode last),blockride.powerGap(how your power meter and trainer compared on your last ride with both) andblockride.btLevel.*(which way of pairing each kind of Bluetooth device worked). In IndexedDB,blockride: the ride you are riding, and one whose save failed, so it can continue after a crash or be saved later; it stays on your device and is deleted once the ride is saved, when you discard it, or after 7 days. In session storage,blockride.liveAs: a random ID for the browser tab. - The game also keeps the map data of routes you rode in your browser's cache storage (
blockride-map-v4), so they load faster next time.
Deleting your account clears the site's local storage in that browser, except your analytics choice.
Analytics (only if you click “Accept”):
_gaand_ga_C807EV2LHH: set by Google Analytics to tell visits apart and count returning visitors. They expire after 13 months.
We don't use advertising cookies.
Map data
Towns, lakes, rivers and coastline come from OpenStreetMap (© OpenStreetMap contributors, Open Database Licence). We keep our own copy of that data on our servers, so no outside service is asked about your route's area.
Terrain heights come from the public terrain tiles in the AWS Open Data programme. Your browser never contacts AWS: our server does, and AWS receives only the coordinates of the terrain tiles being looked up. It doesn't receive your IP address, account, route or rides.
- Amazon Web Services (AWS Open Data terrain tiles): terrain heights for map tiles.
We keep the terrain tiles we fetch (they contain no personal data) so the next route through the same area loads faster, and delete them 30 days after they were last used.
Weather data
Weather comes from the Locationforecast service of MET Norway (the Norwegian Meteorological Institute), under the CC BY 4.0 licence. Your browser never contacts MET Norway: our server does, and MET Norway receives only the centres of the weather squares being looked up. It doesn't receive your IP address, account, route or rides.
- MET Norway (Norwegian Meteorological Institute, api.met.no): the current weather forecast for weather squares along a route.
We keep each square's forecast (it contains no personal data) for up to an hour, so riders in the same area share it.
Who receives your data
Processors handle data for us, only on our instructions:
- Google Cloud / Firebase (Google Ireland Ltd): hosting, database, file storage, our server functions and the POP UP Rides live server. Our server functions and the POP UP Rides live server run in Belgium (the europe-west1 region). The database and file storage are in the United States. Firebase Authentication (sign-in) and reCAPTCHA / App Check (security checks) may process your sign-in and device data in the United States and other countries where Google operates. Google transfers data to the United States under the Google Cloud data processing terms with the European Commission's standard contractual clauses, and Google LLC is certified under the EU-U.S. Data Privacy Framework.
- Brevo (Sendinblue SAS, France): sends our emails, including sign-in emails and training plan change emails, which may say that your health data changed your plan.
- Google Vertex AI (Google Ireland Ltd), Supporters only: writes ride summaries from a ride's numbers, in the EU, as described under Training.
- Google Analytics (Google Ireland Ltd), only if you accept analytics cookies: website usage statistics, including sign-ups, as described above.
Apps you choose to connect are separate companies. Data goes to them or comes from them only because you asked, and they handle it under their own privacy policies:
- Strava, Inc. (USA), only if you connect it: receives the rides you save and, if you allow reading, sends us your activities, as described above.
- Garmin Ltd and its subsidiaries, only if you connect it: sends us the Garmin data you choose to share, as described above.
Other riders in a POP UP Ride see your nickname, look, position, speed and finish time, and every player who can see the list of open rides sees the nickname of a ride's host (see Nickname and POP UP Rides).
AWS and MET Norway receive no personal data (see Map data and Weather data). Where a provider processes data outside the EEA, it does so under the European Commission's standard contractual clauses or an adequacy decision.
How long we keep it
- Account data, settings, nickname, progress, training data and My routes: while you have an account, or until you delete a route or end a plan.
- Rides: until you delete the ride or your account. The copy of the route a ride was ridden on: 90 days.
- POP UP Rides: the ride's record and route file, about 7 days.
- Garmin daily health data and the plan-change notices that quote it: 60 days, or until you disconnect Garmin or withdraw consent. Strava and Garmin tokens and imported activities: until you disconnect, or turn a sport off.
- Issue reports: 180 days.
- Sign-in codes: the code works for 10 minutes, and its record is deleted within a day; the last 5 code sign-ins while you have an account.
- Download my data file: 24 hours.
- Server logs: up to 30 days.
- Analytics: visit data 2 months; data linking visits from the same browser 14 months.
- Logs of the emails we sent (at Brevo, our email provider): 1 month.
- Terrain tiles and weather (no personal data): 30 days after last use, and up to an hour.
- Unused accounts: an account nobody has signed in to for 23 months gets a warning email. If it's still unused 30 days later, it is deleted as if you had pressed Delete account. Signing in once keeps it.
When you delete your account, everything above is deleted straight away. What remains: a daily count of deleted accounts with nothing about who, server logs until they expire (up to 30 days), emails we already sent, and rides already uploaded to Strava, which stay there until you delete them. In a POP UP Ride still running, your finish time stays, under the name "deleted", until the ride's record is deleted. We don't keep backups of the database, so deleted data isn't held in a backup.
Your rights
- See and take your data (access and portability): Settings → Your data → Download my data gives you one JSON file with everything in your account: rides with every second of data, routes, training, health data, progress, settings, connected apps (never passwords or tokens), sign-in codes and issue reports. A new file can be made once every 24 hours. You can also download each ride as a
.fitor.tcxfile and each route in My routes as a.gpxfile. - Delete (erasure): Settings → Your data → Delete account deletes your account and everything in it straight away and for good: rides, routes, training, health data, progress, your nickname and Supporter status. Strava and Garmin are disconnected. You can also delete single rides and routes at any time.
- Correct (rectification): change your email address, nickname and weight in your account and settings. For anything else, email us.
- Withdraw consent: health data in Settings → Your data, analytics in cookie settings. Withdrawing doesn't affect what happened before.
- Object or restrict: you can object to what we do for our legitimate interests, or ask us to restrict how we use your data, by email.
Email support@blockride.cc for any of these, and we'll reply within one month. You can also complain to the State Data Protection Inspectorate of Lithuania (vdai.lrv.lt) or the authority where you live.
Age
BlockRide is for people aged 16 or older. We don't knowingly keep data about anyone younger; if you think we do, email us and we'll delete it.
Changes to this policy
The date at the top says when this policy last changed. We email you before a significant change takes effect.