Donate using PayPal

Privacy policy / site policy

Last updated: September 2020

These terms apply to use of our website or third-party use via our API.

If you have any questions on use of personal data, please do not hesitate to contact us via the feedback facility.

About our site

CycleStreets enables you to plan cycle routes, contribute photos of transport infrastructure, and view/contribute transport-related data for cycling advocacy purposes.

We aim at all times to operate a privacy-aware site that protects your rights.

This website is operated by CycleStreets Ltd, a not-for-profit social enterprise (company no. 06948959) working to increase cycling (and active travel more generally), based in Cambridge. You can read more about us at:

Data processing

Data is solely processed on servers in the UK.

No intrusive user tracking cookie technologies such as Google Analytics, third party cookies, or browser canvas fingerprinting are in use.

The server logs have standard default logging enabled for the purposes only of generating generalised usage analytics (using a locally-installed log analyser) and for site security. These are checked manually only retrospectively in the event of a security issue requiring investigation. Log files are anonymised after 6 months by stripping out IP addresses. Log data is not shared with any third party.

All our services use HTTPS, which ensures that, where a username and password are entered in order to save/retrieve account details, these are sent encrypted to the server.

User accounts

A user account is not required to plan journeys using the site or view other resources.

Some parts of the site invite you to submit crowdsourced data, e.g. the Photomap. These require an account to be created, for the purposes of ensuring material is correctly credited and preventing abuse.

An account requires your e-mail address and a display name. The display name is used to credit your submissions, but your e-mail is not shown.

Passwords are stored hashed using a standard strong encryption mechanism.

If an account is requested to be deleted, this is fully deleted rather than deactivated.

Journey planning

The location points (start, finish, any waypoints) of your journey are initially sent our system in order that a route can be planned. We receive no indication whether this relates to your current physical location.

No location tracking data is sent to our servers while following a route.

Journey itineraries can be retrieved at any time by entering the route number in apps which support this. Viewing of itineraries are segregated by application (API key), i.e. a route planned in one app/website is not viewable from a different published app/website. Implementations using our API v2 can disable itinerary storage.

No personal data is ever displayed in route listings.

If you have a user account and plan a route while signed in, the route is stored in your user account.

We retain waypoint data so as to create an aggregated origin-destination dataset that may be used to improve the future performance of the planner, or for research / transport planning purposes (e.g. network accessibility analysis, determining cycling rates in different areas, or modelling the safety effect of hypothetically removing one-way street restrictions). Any such uses are not connected to user IDs (nor IP addresses).

We will not intentionally make available any publicly-accessible index of journeys planned.

CycleStreets apps that request access to the user's address book have this functionality purely so that the user can do 'route to contact' on demand. Apps do not, and are unable to, upload any such data to the CycleStreets server. This can be independently verified by viewing the source code of our apps, and the APIs do not support such upload.

User photo/other submissions

While it is not our intention to moderate postings or prevent dissenting views, overtly anti-cycling postings will be subject to removal, as they will be considered off-topic.

Postings that are defamatory or abusive will also be subject to removal. Any such postings can be reported via the feedback facility.

We welcome your feedback, especially to report bugs or give us route feedback.

My comments relate to: *

Your comments: *
URL of page: *
How did you find out about CycleStreets?:
Your name:
Our ref: Please leave blank - anti-spam measure

* Items marked with an asterisk [*] are required fields and must be fully completed.