Version 3 · Oct 20, 2026
Who is responsible
The data controller is BikeCoders (bikecoders.life), based in the Netherlands, which stewards the Cycling Commons today. As set out in our governance, the Commons is committed to spinning out to an independent Dutch foundation; the controller will transfer accordingly, and this page will be updated.
Questions about your data: info@cyclingcommons.org (or use the form at Contact). You also have the right to lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens.
We have not appointed a Data Protection Officer (DPO), and the law does not require one of us: we are a small operation, we do not monitor people on a large scale, and special-category data is not part of what we do (GDPR Art. 37). Data protection questions and requests go to the same address as everything else, info@cyclingcommons.org (or use the form at Contact). If that ever changes and we do appoint one, this page will name them.
What we collect
We ask for the minimum needed to run an open, accountable map. We never ask for your real name.
When you create an account
- Your email address, to sign you in, secure the account, and send essential service messages.
- A password. We never store the password itself, only a scrambled form of it that cannot be turned back into the password. When you sign in, we scramble what you type in the same way and compare the two.
- A display name you choose. It can be a pseudonym, and we never ask for your real name. Your profile is off by default: while it is off, what you contribute shows your pseudonym, for example rider#k3x9q2mf, instead of your display name. It is the same on everything you add, so others can see that one person made it, but not who you are; together, those contributions can show roughly where you ride. Turn your profile on and your display name becomes public, together with a profile page that shows things such as your country, your contribution counts and the routes you proposed.
- If you enable two-factor authentication (2FA), we store the TOTP secret encrypted at rest, and your backup codes only as hashes.
- An optional base location and riding radius, if you set one. We do not store the point you pick: we store a random point up to about 2.5 km from it, so the stored point says no more than roughly which town. We also keep the place name you chose with it, and the regions and countries your radius reaches. It tailors only what you yourself see: your map view, and defaults such as the region the best-of page and the ballot open on. It is never shown to other riders and never part of the Commons dataset.
- Your time zone, so the times we show read in your own: the one you choose in your settings, or, while that is set to automatic, the zone your browser reports (for example Europe/Amsterdam). It is a zone name, not a location.
- Your settings. What you choose in your settings, such as your language, your units, and the bike types and riding styles that decide what the map shows you first. We also keep the date you confirmed you are 16 or older, and the date you last signed in, which the 24-month rule under How long we keep it counts from.
When you contribute
- Everything you write into the Commons. If you typed it and sent it, we have it: for example a place, a vote or a message to a curator. Each one is linked to the account that sent it, so that a curator can write back to you. Messages to curators and reports stay between you and the curators: they never appear on the map or in the dataset.
- Any photos you upload. A photo can carry hidden data (EXIF), such as where it was taken: we strip that out and re-encode the file, so what we publish carries none of it. We then write one thing back in: a stamp saying the picture is licensed CC BY-SA 4.0, and a link to its page on Cycling Commons. Your name is never written into the file. The link is how somebody reusing the photo finds who to credit, and that page names you only while your profile is public; otherwise it credits an anonymous rider.
- Traffic summaries and tags from Scout, only if you send them from Scout's ride review. A traffic summary, from a ride with a rear radar, holds per road you rode what you and the radar measured, such as the distance and the cars that passed you, with only a rough time: a part of the day, never the hour or the date. It holds no GPS track, nothing near where your ride starts or ends, and nothing that names you or links your rides together. Summaries only ever count as anonymous totals per road, mixed with other rides. A tag you set during the ride becomes an ordinary contribution, with its spot, what you write, any photos and the date; a tag for a stretch of road also sends that stretch of your ride. Both are optional, per ride. If Scout ever sends a new kind of data, this notice changes first.
- "I rode this" marks. When you mark a route as ridden, we keep the mark with the bike type you chose and the date. On the route, only the number of riders who marked it shows.
- Roadmap votes, follows and proposals. When you vote for an item on the roadmap or a proposal, or follow one, we keep that mark with the date. The page shows only how many riders voted, never who; what you follow is seen by nobody but you. A follow means we tell you, in your messages and by email, when the item moves, ships or leaves the roadmap; click Follow again to stop. When you send a proposal, we keep what you wrote, the language you wrote it in, the picture you add and our answer, linked to your account. Until we read it, only you and the curators see it. If we open it for votes, its title and text show on the Proposals tab, and later perhaps on the roadmap, without your name; the picture only if you allowed that when sending and we choose to show it.
- Rides you plan. On the map you can plan a ride for the bike you ride: a start, a few stops and an end, routed over roads by our own routing engine. The stops reach our server only to be routed, and we keep no copy of the ride: it stays in your browser, and in the GPX file you download if you want to keep it. A GPX file you open is read in your browser; its track reaches our server only to put the ride on the same roads, and is not kept. Nobody else sees it.
- Map presets. On the map you can save the switches you want on, under a name, and mark one as the preset the map opens with. We keep the name and the switches, linked to your account. Only you see them.
- How safe a road felt. On the map you can mark a road you rode as safe or unsafe. A mark holds that road, the part of the day, whether it was a workday or a weekend or public holiday, the quarter of the year, and safe or unsafe: never the hour or the date, and nothing that names you. You can mark several roads with one answer: they arrive together, then each road waits on its own. Your account limits how often you can mark, and is not stored with the mark. Marks wait until enough riders have marked the same road for the same time; then only curators see whether it felt safe, mixed or unsafe.
- Bug reports. When you report a bug, we keep what you wrote, the screenshots you add, technical details that help us find the fault, such as the address of the page you were on and your browser, and your email address if you want an answer. If you are signed in, the report is linked to your account. A curator may publish a bug on our known-issues page and as an issue on GitHub, with a title and text the curator writes; only that title and text go there, never your email address, the page address, your screenshots or anything else from your report.
- Curator applications and country requests. If you apply to curate, we keep what you fill in, such as the area you ask for, what you write about yourself and your OpenStreetMap username if you give one, which you do not have to. Our server looks it up on OpenStreetMap to see whether it exists and how many edits it has. Later it can also let us send what you add to the Commons back to OpenStreetMap in your name; we will ask your permission before we ever do. If you ask us to open a country, we keep what you fill in, such as the country, your note and whether you would curate there.
- Optional profile details you choose, such as your country, your bike types and your riding styles. They show on your public profile only while it is on. Profiles are opt-in and off by default.
Automatically, when you use the site
- Technical data: IP address, browser type, and timestamps in our server logs, kept to operate and secure the service.
- Use counters and coded addresses. To stop one visitor from using up a tool for everybody, or from flooding a form, we count requests. Signed in, we count against your account. Without an account, most counters, such as the one on the ride check, count against a code made from your IP address, which cannot be turned back into the address. A few count against the address itself, such as the ones on the report form, the public API and downloads of the bulk export. The same kind of code is kept with some things you send us, such as a report or a contact message, so that we can spot a flood. That code is still personal data, so everything on this page applies to it.
- Error reports. When something breaks on our server, it writes an error report: what went wrong, the page, the moment and what the request sent, with passwords and other secrets hidden. We leave out what you send in forms with personal content, such as signing in, your account and your messages. An error report never holds your IP address. The reports stay on our own machines in the EU, with everything else we run (see The companies that handle data for us).
No ride tracking. The Commons is a map of places, not of people. We do not track where you ride and never see your live location. We hold a line you rode only when you send it on purpose, such as a route you propose or the stretch of a ride a Scout tag covers. A traffic summary from Scout's ride review is not a GPS trace, but it does say which roads you rode and in which part of the day, an "I rode this" mark says you rode that route, and a mark of how safe a road felt names that road (see When you contribute). The ride check reads a ride file you give it on our server, to find places along it, and keeps nothing of it.
Locate me on the map reads your position in your own browser, only when you tap it, and sends it nowhere: no request to us or anyone else carries it. The map then loads the map images for that area, as it does whenever you move the map.
Why we use it (legal bases)
- To provide your account and the service: performance of a contract (GDPR Art. 6(1)(b)).
- Showing your name. A public profile, and being credited by name on what you contributed, rests on your consent (GDPR Art. 6(1)(a)). Withdraw it any time in settings and your name comes off those pages. On our side that happens at once. A copy of a page that somebody else saved is beyond our reach.
- Publishing what you contribute. A photo or an edit you give to the Commons is published under the licence you agreed to when you sent it, which is part of our agreement with you (GDPR Art. 6(1)(b)). That licence is irrevocable by its own terms, so withdrawing consent takes your name off the page but does not un-publish the contribution itself. One exception matters: if a photo shows you, that is your personal data, and a copyright licence does not sign away data-protection rights. Every photo page carries a link to ask for it to come down. A photo you had no right to license was never validly licensed: tell us through the same link and it comes down too.
- Telling you what is new. Only if you asked for it, for example with the setting in your account: that choice is your consent (GDPR Art. 6(1)(a)), and you can withdraw it at any time. In your settings you choose how often, for example big news only. Every message also carries a one-click unsubscribe that needs no sign-in. News about the Commons only, never advertising, and the mailing list is never shared or sold.
- Security, abuse prevention, and aggregate analytics: our legitimate interests in keeping the Commons honest and working (GDPR Art. 6(1)(f)).
- Meeting legal obligations: where the law requires it (GDPR Art. 6(1)(c)). That includes the statement of reasons we owe you when we restrict something you added or your account (Digital Services Act Art. 17), and informing the police or a judicial authority of a threat to somebody's life or safety (Digital Services Act Art. 18).
Cookies & analytics
We keep this light. We set two cookies, both of them strictly necessary, and both listed in full below. For usage statistics we run self-hosted analytics on our own infrastructure: it receives the page you open and technical details such as the referrer, your screen size and your browser type, and it receives your IP address, which is personal data, but does not store it. The address is used only to work out an approximate location (country, region and city) and to derive a one-way session identifier, and is then discarded. No analytics cookies are set, no visitor is given a persistent identifier or tied to an account, and there is no cross-site or cross-device tracking. Analytics data stays on our own infrastructure and is never shared with, or sold to, third parties.
The cookies we set
| Name |
What it does |
How long it lasts |
PHPSESSID |
Keeps you signed in, and carries the token that protects the forms you use while signed in against cross-site request forgery (CSRF), an attack in which another website makes your browser submit a form here as you. It is set when you sign in, or when you use a form that has to remember something between pages, such as resetting your password. Reading the map and the rest of the site, the contact page included, sets no cookie at all. It holds a random identifier and nothing else: no name, no email address, no record of what you looked at. |
Until you close your browser |
REMEMBERME |
Signs you back in on your next visit without asking for your password. Set only if you tick Remember me when you sign in, and removed when you sign out. We do not recommend it on a computer that other people use. |
7 days |
That is the whole list. We set no advertising cookie, no analytics cookie and no cross-site tracking cookie, on any page. Both cookies above are strictly necessary to deliver something you asked for, so the law needs no consent for them, and that is why there is no cookie banner here. If we ever added something that did need one, we would ask you first rather than assume.
Your browser also keeps a few things for this site on your own device. In its local storage: your display and map preferences, such as the theme, the area you last looked at, your filters and the size of a panel, and a home area if you set one without an account. A bug report you have not sent yet is kept as a draft, with its screenshots, in the browser's own database (IndexedDB). While you edit, some work in progress sits in session storage, which the browser clears when you close the tab. A ride you are planning on the map, with its undo and redo steps, is kept in local storage, and the roads drawn for it in the browser's own database, seven days after your last change, so closing the tab loses nothing and the ride opens again without being routed again; after that your browser forgets it, and signing out removes it at once. None of this is a cookie. It all stays in your browser: we never read it from there, and a draft reaches us only when you send it. Clearing your browser data removes it. Other websites cannot read it: a browser keeps each site's storage apart. Two things can still read it. Anybody who uses the same browser on the same computer, and any script that runs on this site, such as a browser extension you installed. A home area says roughly where you live, so on a shared computer you may prefer not to set one.
Who we share it with
First, what is not in these lists. We run as much of this ourselves as we can, on our own machines, such as the map data, the route planning, the photo storage and even the error reports. Two services we used to call out to, for routing and for elevation, now run on our own machines too, so what you ask them no longer reaches an outside company. It is slower to build that way and it costs more, but it is why your browser talks to only a handful of outside services, each listed below, instead of twenty, and why the tables below are as short as they are: every name in them is one we could not reasonably run ourselves.
- The services that run our infrastructure, and the few we ask for a check. Hosting, backups, email, the map services your browser fetches directly, and the checks our server makes. Each one is named below, with what it does and what it can see.
- OpenStreetMap: contributions you choose to give back become part of the open map under the ODbL. That is public, open data, not personal data about you.
- The police or a judicial authority, when the law requires it. If something posted on the Commons suggests a crime that threatens somebody's life or safety, we must inform the competent law-enforcement or judicial authority of the country concerned, or of the Netherlands when that is not clear (Digital Services Act Art. 18). We give them what they need to act, such as what the curator saw, where it appeared, and the account details we hold for whoever posted it, for example the display name and email address. The material itself goes only if they ask for it. The legal basis is our legal obligation (GDPR Art. 6(1)(c)).
- No one else. We don't sell personal data and we don't run third-party ad tracking.
The companies that handle data for us
The companies below hold or handle your data on our instructions. They are our processors: they may only do what we tell them to, under a written contract, and they may not use your data for anything of their own.
| Who |
Where |
What they do for us |
What they can see |
| Hetzner Online GmbH |
European Economic Area |
Runs the machines: the website, the database, the storage that holds uploaded photos, and the error reports. |
In principle everything we store, because it sits on their hardware: your email address, your contributions, your photos, the server logs and the error reports. Passwords and two-factor secrets are unreadable even there (see How we protect it). |
| Scaleway SAS |
European Economic Area |
Delivers the mail the site sends you, and stores the nightly backups. |
Your email address and the contents of the messages the site sends you. The backups are encrypted on our own servers before they are sent, so their contents cannot be read at the other end. |
| Proton AG |
Switzerland (covered by an EU adequacy decision) |
Holds the project mailbox, the address printed on this page, and the replies we write back. |
Your email address and whatever you chose to write to us, for as long as the conversation is kept. |
Services your browser contacts directly
The map is assembled in your browser, so a few pieces are fetched straight from the people who publish them rather than passing through us. We never hand them your account, your display name or your email address. They do see the network address your request comes from, because every request on the internet carries one. Nothing in this list loads until you open a page that uses it.
| Service |
What it is for |
What it receives |
| OpenFreeMap |
The base map: the roads, water and place names under everything else. |
Your IP address, and which map squares you asked for. |
| Esri |
The satellite view, only once you switch to it. |
Your IP address, and which image squares you asked for. Esri is in the United States. |
| Mapillary |
Street-level photos, only once you open the street view. |
Your IP address, and which photos you opened. Mapillary is run by Meta Platforms Ireland Limited, in Ireland, and the image files themselves come from Meta's content network, which is worldwide. |
| Photon |
Place search, wherever you look up a place by name, such as the map search or the base location field in your settings. |
Your IP address, what you type into a place search, and the language of the page. From the map search, also the region or country the search is limited to, or, for an area round your home area, a box round its middle rounded to about 10 km. From the ride planner's start search, also the middle of the map, rounded to about 10 km. Photon is run by komoot, in Germany. |
Two of these can reach outside the European Economic Area (EEA): Esri is in the United States, and Mapillary's image files come from Meta's worldwide network. If you never open the satellite view or the street view, your browser contacts neither. See International transfers below.
Services our server asks
When you apply to curate, our server looks up the username you gave on OpenStreetMap, if you gave one, to see whether it exists and how many edits it has. Our server asks this itself, so OpenStreetMap sees our server's address, never yours, and the username is already public there.
When you plan a ride on the map and set a day for it, our server asks Open-Meteo for that day's forecast at one point near the middle of your ride, rounded to about 10 km. Open-Meteo sees our server's address, that rounded point and the date, and nothing about you. We keep the answer for three hours and nothing else.
International transfers
Your account, your contributions, your photos and our backups stay in the European Economic Area (EEA). A handful of outside services can see something from outside it, each one named above. Proton, in Switzerland, holds our mailbox, so it sees the email you write to us. The EU has decided that Swiss law protects personal data as well as EU law does (an adequacy decision), so no extra contract is needed for that. Esri, in the United States, serves the satellite view. Only when you switch that view on does your browser ask Esri for the images, and Esri then sees your IP address and which images you asked for. We send Esri nothing ourselves. The street-level photos from Mapillary come through Meta's worldwide network, which can serve them from outside the EEA; it sees the same as Esri does, and only once you open the street view.
How long we keep it
- Account data. Until you delete your account, and then it is gone. Deletion is immediate: you ask, we email you a code, you confirm, and the account is removed from the live database in that moment. The email address, the password hash, the two-factor secret and the backup codes go with it. A message you sent us or a report you filed while signed in keeps the address it came from for its own period, set out below, so we can still answer you. There is no waiting period and nothing is held back in case you change your mind. Our nightly backups still hold the old record until they rotate out, which takes at most 90 days; those backups are encrypted and are opened only to recover from a disaster. An account nobody has signed into for 24 months is deleted in the same way. We email you first, more than once, each time with the date it will close. Signing in once is enough to keep it. After that deletion too, our backups hold the old record until they rotate out, at most 90 days. If an administrator removes your account for a breach of our terms, we read your email address just before the deletion and use it once, right after, to send you the statement of reasons. It is then gone, as with any deletion. If that email does not go out, we keep the address with the statement until we send it again or decide not to, and then delete both.
- Unconfirmed accounts. An account whose email address is not confirmed within 7 days is deleted, without a warning email. The address may belong to someone who never signed up, and the only email we could send would go to them.
- Server logs. Kept for at most 90 days, then deleted automatically. Some entries record a full IP address, for security and abuse handling. Those are deleted within the same 90 days. Error reports are deleted within 90 days too.
- Use counters and coded addresses. A counter expires on its own, at the latest two days after your last use. The counter for downloads of the bulk export is the exception: it lives only in our web server's memory, is never written anywhere, and is cleared when a later download needs its place or the server restarts. A coded address kept with something you send us stays as long as that does: with a report, as long as the report; with a contact message, until the message is deleted, within 24 months of the conversation ending.
- Contributions. Facts you give back to the open map persist as part of the Commons (with provenance), even after you leave; they are not personal data about you. Your confirmations, your "I rode this" marks (except on a route you proposed yourself, where they never counted and are deleted) and the history of your edits also stay when you leave, without any link to your account.
- Traffic summaries. A line waits, encrypted, until its road has enough rides, then joins the totals per road and is deleted. The totals persist as part of the Commons. They hold no rider, so nothing in them is deleted with your account.
- Marks of how safe a road felt. A mark waits, encrypted, until its road has enough marks for the same time, then joins the counts per road and is deleted. The counts persist as part of the Commons. They hold no rider, so nothing in them is deleted with your account.
- Messages about your contributions. The messages between you and the curators about what you contributed are kept as long as your account exists, and deleted with it. So are the statements of reasons we send you when a decision restricts something you added, your contributions that were turned down or that you withdrew before a curator decided on them, and your curator applications. A request to open a country stays only as an anonymous count, without your note or your offer to curate. What a curator approved stays on the map, without your name. A contribution held for a legal case is kept, with its messages, while the hold lasts. Each statement of reasons is also emailed to you; one about your account goes by email only.
- Suspensions. If an administrator suspends your account, we keep on it when the suspension started and when it ends, the ground, the facts as we sent them to you, and which administrator decided. That stays until a later suspension replaces it or the account is deleted. If that administrator's account is deleted, the link to them is cleared. Your data export holds all of it except who decided. Our admin log records the account, the ground and the end date, never the facts or your address.
- Licence consents. When you licence something to the Commons, such as a photo or a translation, we record that you agreed, the exact wording you agreed to, and when. We keep that record indefinitely, and it survives closing your account: it is our evidence that the licence was granted, which we may need to establish or defend a legal claim (GDPR Art. 17(3)(e)). It holds a reference to your account and nothing else about you. When you delete your account, we remove that reference, and the record stays linked only to what you licensed.
- Email and contact-form messages you send us. We keep a conversation while the matter is open, and delete it within 24 months of it ending. That covers you coming back to us about the same thing a year later, and it covers us if a complaint about how we handled it arrives late. Threads that are part of a legal matter, such as a copyright claim or a takedown, are kept until that matter is finished.
- Bug reports. A bug report stays, as part of the record of what was broken and how it was fixed. If you were signed in, it is linked to your account until you delete the account; then it stays without that link. The email address you gave for our answer is kept while the bug is open, and deleted 24 months after we tell you the outcome, the same period as for email you send us.
- Roadmap votes, follows and proposals. A vote or a follow stays until you take it back, until the item or proposal leaves the roadmap, or until you delete your account. A promoted proposal hands its votes and follows to its roadmap item. A proposal that is waiting or that we declined is deleted with your account, picture and all. A proposal open for votes or on the roadmap stays, without the link to your account.
- Map presets. A preset stays until you delete it in Settings or delete your account. It is in your data export.
- Reports about content. When you report something on the site, including a photo that shows you, we keep the address you leave for our answer until we have decided on your report: acted on it, found nothing wrong, or closed it because it no longer applies. We delete the address 90 days after that decision. The report itself stays, as the record of what we were told and what we did about it. If the reported photo is held for a legal case, we keep the address until that hold is lifted. This also holds when you delete your account after reporting: we still tell you the outcome.
- Reports to the authorities. When we inform an authority about something posted here, we record when, which authority, its reference, and which administrator recorded it. The record stays with the photo or submission for as long as that exists, and the material is kept until the authority says it may go. A line in our admin log, with the reference and the authority but nothing of the material, is kept with no end date. If the administrator's account is deleted, the link to them is cleared and the record stays.
- The mailing list. Your address stays on it until you take it off, from your settings or from the link in any message. We keep the record that you agreed, and to what wording, the same way we keep a photo licence consent: it is the evidence that we were allowed to write to you.
How we protect it
The law asks us to take measures that fit the risk (GDPR Art. 32). In plain words:
- Your password is never stored. We keep only a one-way scramble of it, so nobody here can read your password and a stolen database does not hand anyone yours either.
- Two-factor secrets and backup codes are encrypted where they sit, with the key held outside the database. Somebody who steals only the database still cannot produce a working code.
- Everything travels encrypted, between you and us and again when a backup leaves our servers. Browsers are told to refuse an unencrypted connection to us at all.
- Only the people who need your data can reach it, and every curator and administrator has to use two-factor sign-in. Repeated failed sign-ins are slowed down and then locked out.
That is the short version. The exact measures, and the reasoning behind each one, are in our public source code, which is the point of building it in the open: you do not have to take a security paragraph on trust.
No system is perfect and we will not pretend ours is. There is no certification behind that paragraph and no penetration test: what there is, is a small system that keeps as little as it can, and code anyone can check.
If data ever leaks
If personal data is lost, exposed, or reached by somebody who should not have it, and that is likely to put people's rights at risk, we report it to the Autoriteit Persoonsgegevens within 72 hours of finding out (GDPR Art. 33). If the risk to you personally is high, we also contact you directly and without delay (GDPR Art. 34), in plain language: what happened, which of your data was involved, what we have done about it, and what you should do. We keep an internal record of every breach, including the ones we are not obliged to report, so the pattern stays visible to us even when no single one is reportable.
Your rights
Under the GDPR you have the following rights:
- Access (GDPR Art. 15): request a copy of the personal data we hold about you.
- Rectification (GDPR Art. 16): correct anything inaccurate, or complete anything missing.
- Erasure (GDPR Art. 17): delete your account at any time from your account settings. Your personal data goes with it and does not come back, such as your account details, your messages and your votes. Some things stay for a while longer: our encrypted backups hold the old record until they rotate out, at most 90 days, and a contribution held for a legal case is kept while the hold lasts. Some things deliberately stay, without any link to your account, such as the contributions you gave to the open map, the history of edits and the record that you granted a licence. Your approved photos stay too, credited to an anonymous rider, unless your profile is public and you choose to keep your name on them when you leave. How long we keep it above says more about each kind.
- Data portability (GDPR Art. 20): download what we hold about you as a single ZIP file from your account settings. How often you can do that is limited, only to stop abuse. Among other things it holds your account details, your contributions, your messages and statements of reasons, your licence consents, and your photos as files. It leaves out what somebody else wrote when they reported one of your photos, because those words are theirs. While a curator is still looking at such a report, or while a photo is held for the authorities, it also leaves out the reason; the decision tells you.
- Restriction and objection (GDPR Arts. 18–21): restrict or object to certain processing.
- Withdraw consent at any time, for example by turning off your public profile or the news emails. From that moment we stop doing what you consented to. What we did with your consent before then stays lawful (GDPR Art. 7(3)).
- Not a user? These rights don't depend on having an account. If you are recognisable in a photo on our map, every photo page carries a "this photo shows me" link. Report it there, no account and no ID required, and a curator answers within one month at the latest.
To exercise any of these, email info@cyclingcommons.org (or use the form at Contact). We answer within one month at the latest, and normally much sooner. The law allows up to three months for a request that is genuinely complicated, but only if we tell you inside the first month that we are taking longer, and why. If you are unhappy with our answer, you can complain to the Autoriteit Persoonsgegevens.
Children
The Commons isn't intended for children under 16. We don't knowingly collect personal data from anyone under that age; if you believe a child has given us data, contact us and we'll delete it.
Automated decisions
We don't make decisions about you by solely automated means, and we don't profile you for advertising.
Changes to this policy
If we change how we handle data, we add a new version here, with its date and what changed, and show signed-in riders a notice until they have read it. A significant change, such as a new purpose, a new recipient or a new country, is also emailed to every account at least 30 days before it applies, so you can read it and close your account first if you do not agree. Your account records the version of each page you last saw.
Version 3 · Oct 20, 2026
- Clarified: a message you sent us or a report you filed while signed in keeps your address for its own period, also after you delete your account, so we can still answer you and tell you the outcome of a report.
- New: you can vote for and follow items on the roadmap, and send proposals for it. After we read one, it can be shown and voted on without your name. See what we keep and for how long.
- New: you can plan a ride on the map. It stays in your browser and in the GPX you download; we keep no copy. See what your browser keeps.
- New: a planned ride can show the forecast for its day. Our server asks Open-Meteo for it with a point rounded to about 10 km and nothing about you. See the services our server asks.
- New: you can keep map presets, the switches you want on under a name. Only you see them. See what we keep and for how long.
- New: on the map you can mark how safe a road felt: the road, a part of the day, the day type, the quarter and safe or unsafe. A mark is not stored with your account. See what we collect and how long we keep it.
Version 2 · Oct 9, 2026
- New: from Scout's ride review you can send a traffic summary of a ride with a radar: per road, the distance, the cars and the part of the day. A summary holds no GPS track. See what we collect and how long we keep it.
- New: we store your time zone, the one you choose in your settings or the one your browser reports, to show times in it.
- Corrected: with your profile off, your contributions show your fixed pseudonym, not no name at all.
- Changed: your base location is stored as a random point up to about 2.5 km from the point you pick, instead of a point rounded to about 1 km.
- Easier to read. It says that both things you can send from Scout, traffic summaries and tags, are your choice for every ride. It explains in plain words how we keep your password, why we count how often a tool is used without an account, and what the map stores in your own browser. For each service outside the EEA it says what that service sees. Every GDPR article it names links to the law itself.
- Added: error reports from our server, what they hold, and that they stay on our own machines.
- Added: how we tell you about changes. A significant change is emailed to you at least 30 days before it applies; a smaller one gets a new version here.
- Added: what a Scout tag sends; what we keep from bug reports, curator applications and "I rode this" marks; your other settings; where we keep coded IP addresses, and for how long; and what happens to each kind of data when you delete your account.
- Added: the statements of reasons we send when a decision restricts something you added: kept with your messages as long as your account, part of your data export, and emailed to you.
- Added: what we keep when an administrator suspends an account, for how long, and what your data export holds of it; and that a removal for a breach uses your email address once, to send you the reasons.
- Added: when the law requires us to inform the police or a judicial authority of a threat to somebody's life or safety, what we give them, on which legal basis, and how long we keep the record.
Version 1 · Oct 4, 2026
- The first numbered version. Earlier wording is in the revision history linked below.
View the revision history on GitHub.