Privacy Policy

Cycle Maps is an Android app, published under the same name. This page describes what information the app and this website handle and where it goes. Not every version of the app has every feature described here; for each feature, the page says what it uses in a version that has it. A version that handles your information in a way this page does not describe is not published until this page describes it. Last updated: 2026-11-18.

No account, no sign-in

The app has no accounts. On first launch it generates a random identifier that is stored only on your device. It is sent to the server only when you rename a track you uploaded, so that only you can rename it.

Location

The app asks for location permission to find tracks near you, show your position on the map and keep the map centred on you, and does not work without it. Apart from a search for tracks (below), the app does not send your position to the Cycle Maps server or to anyone else. It is kept only in rides you record, on your device, until you share them. The app uses your location while it is on screen. When it is not on screen, it uses your location only while a ride recording or route guidance that you started is running, and stops when you stop it. It never starts either by itself.

When you search for tracks, the app sends the centre of the map you are looking at and the search radius to the Cycle Maps server, which answers with tracks near that point. While the map is centred on you, that point is your position, so the point is rounded to about 100 metres before it is sent. Searches are not tied to your identifier. The server finds the tracks in its own copy of the cycling routes mapped in OpenStreetMap, and sends that point to no one else. The server writes request lines to its log, which includes that point rounded to about 100 metres; logs are not used for anything else and are deleted after 30 days. The app keeps the tracks your last search found, with that point as it was sent (rounded to about 100 metres) and the search radius, and the last track you looked at, on your device, so that it can lead you back to them the next time you open it. They are not sent anywhere and are not included in Android's backup. The app offers them for six months and deletes them the next time it is opened after that; it also deletes them when you close its offer to go back to them, and they go when you uninstall it.

When the app opens without a position fix, it opens the map on the country your phone names from its mobile network, its SIM card or its language. The country is worked out on your phone and not sent anywhere; the map then loads that country's tiles like any other view (see Map tiles below). Earlier versions of the app ask the server where to open the map instead; the server does not look up your IP address and answers with no position.

Riding with the app

Recording a ride, following a route and off-route alerts work from your position on your device. A ride you record is saved on your device and is not sent to the Cycle Maps server unless you choose to share it with other riders (below). It leaves your device only when you share it.

A ride is recorded only after you tap to start it, and only until you finish it. While it is recording or paused, a notification says so, if you allow the app's notifications, and lets you pause, resume or finish it. While it is paused, the recording does not use your location. The positions of a ride are kept in the app's private storage on your device. They are not sent to the Cycle Maps server unless you share the ride with other riders, never to the usage statistics or to anyone else, they are not included in Android's app backup, and they are deleted from your device when you uninstall the app.

Sharing a ride with other riders

After a ride, the app asks whether to share it with other riders; nothing is shared until you tap Share with riders, and closing the screen keeps the ride to yourself. A ride you share is collected for this one purpose: so riders who search near it can find the way you rode.

The app then sends the ride to the Cycle Maps server: its precise positions with the time of each and its height, and its name if you typed one. If you are offline, it waits on your device and is sent once you are online. The server cuts off the first and last 200 metres of the ride, so where it starts and ends, such as your home, is not shown, and keeps only the rest of its line with its heights, its length and climb, its two new ends, the day you rode it, and the name you typed, if you typed one. It does not keep the times or the file the app sent. Riders who search near it, and the route's page on this website, show that line, its distance and the day, the name you typed, and how many riders recorded the same way. When your ride is a new route, you can change its name after sharing it: the app sends the new name with the token below, and the server keeps it in place of the old one.

A shared ride is not linked to who you are: not to an account, a name, an email address, your identifier above or the advertising ID. The first time you share a ride, the server gives the app a random token, which the app keeps encrypted on your device and leaves out of Android's app backup; the server keeps only a scrambled form of it beside each ride you share, so that only your phone can take the ride back. You can stop sharing a ride at any time in My rides: the server deletes it and it no longer counts toward its route. Deleting a ride from your phone, or uninstalling the app, does not delete it from the server; stop sharing it first, or ask us at the address below.

Sharing

When you share a route or a ride, as a link or as a GPX file, the app hands it to the app you choose through Android's share menu, and it goes to whoever you send it to. A link to a route opens that route's page on this website.

Map tiles

The map's style and vector tiles are loaded from OpenFreeMap, which receives the standard web request for each one, including your IP address and which part of the map you are viewing. Maps you save for use without signal are downloaded from it the same way and kept on your device. The app sends it nothing else and uses no API key. Map data is © OpenStreetMap contributors, tiles © OpenMapTiles.

The map's contour lines and their heights are loaded the same way from Maptoolkit, which receives the standard web request for each tile, including your IP address and which part of the map you are viewing. The app sends it nothing else and uses no API key. Contour lines © Maptoolkit.

The signed cycle routes drawn on the map are loaded the same way from our own server, tiles.getcyclemap.com, which receives the standard web request for each part of the map, including your IP address and which part of the map you are viewing. We keep no log of these requests, and the app sends it nothing else.

Advertising

The app shows interstitial ads through Google AdMob. The AdMob SDK may collect device identifiers, including the Android advertising ID, and other information under Google's privacy policy. The app itself does not send ad activity or your position to anyone.

In the European Economic Area, the United Kingdom, Switzerland and other places where the law requires it, the app asks for your consent with Google's consent message before it requests any ad, and ads use your information for personalisation only if you agree. You can change your choice at any time in the app's Settings, under Privacy choices. Elsewhere, ads may be personalised without asking. Wherever you are, you can reset or delete the advertising ID in Android's settings.

Usage statistics

To learn which features are used, the app sends usage events to Mixpanel, an analytics service: that the app was opened and for how long, that it was updated, whether its map loaded, how many seconds it took and whether it was showing its note about location, how you answered a notice on the map and Android's question about location (whether you allowed precise or approximate location or refused, never where you are), that you searched for tracks, with the search radius, how many tracks came back and how many seconds the answer took, that you chose or shared a track, or added it to or removed it from your favourites, that the app asked Google Play to show its review request, that you opened the app from a link to a track, that the app offered to lead you back to the last track you looked at or to the tracks your last search found, and that you opened or closed that offer, with which of the two it was and how many days old it was, that you opened directions to a track's start, that you rode a track with the app, with whether you joined it and whether you reached its end, that you saved a track's map for use without signal or removed it, with how many map tiles and megabytes it took and how many seconds it took to save, that you finished recording a ride, with its moving time in minutes and, for a ride along a track, whether it rode all of it and whether it was your best time there, that you shared a ride with other riders, with whether it joined a route riders had recorded or became a new one, or stopped sharing it, and how you answered the question about screen recordings (below), or switched them in Settings. Once, when a newly installed app is first opened, it also sends the three campaign tags of the link that took you to the app's page on Google Play, which Google Play keeps for the installation: where the link was placed, what kind of place that is, and which campaign it belongs to (for an installation found in Google Play's own search, Google Play says so); nothing else Google Play keeps about the link. An event never carries your position, the point you searched around, a ride's line or distance, a track's name or your identifier on the Cycle Maps server. With each event Mixpanel receives a random identifier it creates for the installation; the device's manufacturer, brand and model; the Android version; the app's version and build number; the screen's size and density; the mobile carrier's name; and whether the device is on Wi-Fi, has NFC and telephony, and which kind of Bluetooth it has; and the version of Mixpanel's own code in the app. It also receives the standard web request, including your IP address and the app's user agent, and the app tells it not to work out your city or country from that address. The app does not send it crash reports. Mixpanel does not read the Android advertising ID. You can switch this off at any time in the app's Settings, under Usage statistics; nothing more is sent after that. If you switch it back on, Mixpanel creates a new identifier and is told that it was switched on.

Screen recordings

On Android 10 and newer, Microsoft Clarity records how you move through the app's screens, to help make the app better. In the European Economic Area, the United Kingdom and Switzerland, and on a phone that is on no mobile network, nothing is recorded unless you allow it: from the third day you open the app, the app asks once, when you go back to the map from a list or a track; closing the question is a no, and it is not asked again. Elsewhere it records unless you switch it off, or you switched Usage statistics off. The app tells the country from the mobile network the phone is on, on the phone; a choice you made stands wherever you are. When it records, Clarity receives the layout of each screen you open with every text on it hidden, where you tap and scroll, how long you stay, and the device's model, its Android version and screen size and the app's version, with a random identifier it keeps for the installation, and the standard web request, including your IP address, from which it works out an approximate location. Every map in the app, and the small drawing of each track in a list, is hidden from it, so it never receives the map, your position or the line of a track or a ride, and the app tells it to keep nothing for advertising. It sends what it recorded on Wi-Fi, also later if you were offline. You can switch it off or on at any time in the app's Settings, under Make the app better; recording stops at once.

Favourites and files

Tracks you mark as favourites are saved as files in the app's private storage on your device. They are included in Android's app backup if you have it enabled.

Earlier versions

Earlier versions of the app could publish recorded rides to a public map. Since October 2026 the server lists some of those rides again beside the routes from OpenStreetMap, those that make a ride for its own sake: riders who search near one see its line, its length and its name, if it had one, and so does its page on this website. They are not shown with who recorded them, or with the identifier of the app that sent them. To have one taken down, write to us at the address below.

Versions published before October 2026 also send each ad event, with the device's position, to the Cycle Maps server. The server does not accept or keep them.

Versions published before October 2026 send the centre of the map for a search without rounding it. The server rounds it to about 100 metres before it searches around it or writes it to its log.

This website

This website shows no advertising. To learn how many people visit it and what they read, every page uses Google Analytics and asks whether it may count your visits. Until you allow it, Google Analytics keeps nothing in your browser: for each page you open, and when you scroll to the end of it or follow a link to another site, it receives a message without any identifier, with the page's address and title, the page you came from, your browser's language, screen size and user agent, and your IP address, from which it works out an approximate location. If you allow it, Google Analytics also keeps a random identifier in a cookie, so that it can tell a returning visitor from a new one, and the page also loads Mixpanel, which keeps its own random identifier in your browser and receives each page you open, each tap on a link to Google Play or on a track page's button that opens the track in the app, each time the code that takes a phone to the app on Google Play, shown on a computer, comes into view, each GPX file of a route you download and each copy of the code to show a route's map, with the same kind of information; Mixpanel is told not to work out your city or country from your IP address. The page also loads Microsoft Clarity, which keeps its own random identifier in cookies on this website, and may keep one in a cookie of its own site, clarity.ms, and records how you use each page you open, so that we can see where the pages confuse people: what the page showed, where you scroll, tap, click and move the pointer, with the same kind of information about your browser and your IP address, from which it works out an approximate location; what you type in the page's search box is hidden from it, and it is told to keep nothing for advertising. None of them receives anything from the app, your position or anything you type. Your choice is kept in your browser; if you take back an Allow, the identifiers kept on this website are deleted from it, and Clarity is asked to erase its own. A link on this website to the app's page on Google Play carries the campaign tags of the link that brought you to this website, if it had any, or else says that it is this website and which kind of page it is on, so that the app, once installed, can tell where it came from; nothing is kept in your browser for it, and it is sent only if you follow the link. On a computer, the link beside the Google Play badge is also drawn as a QR code, in your browser, which sends nothing.

The page of a track, of a city and of a long-distance route draw a map whose tiles are loaded from OpenStreetMap, which receives the standard web request for each one, including your IP address and which part of the map you are viewing. The page of a long-distance route also shows a photo from Wikimedia Commons, which your browser loads from it with the same kind of standard web request. To build these pages the server reads its own copy of the routes mapped in OpenStreetMap; to name the places where a track starts and ends, it sends those two points to OpenStreetMap's Nominatim, and to draw a track's heights, it reads the tiles of the Copernicus elevation model around the track from Amazon's open-data service; neither receives anything about you. As with the app's requests, the server writes the address of each page asked for to its log, which is deleted after 30 days. The sites this website links to have their own privacy policies.

A long-distance route's page offers its route as GPX files to download, and the code that lets another website show the route's map in its own pages. Such a map, shown on another website, asks no question and keeps nothing in your browser; it loads its map tiles from OpenStreetMap as the route's page does. When it is shown, it tells this website's server which website shows it (that website's name, such as example.org, and nothing of its page) and which route, at most once a day, and keeps that answer in your browser for the day; the server passes that to Mixpanel as an event with the website's name as its identifier and no identifier of yours; Mixpanel receives the server's request, not your browser's, and is told not to work out any location from it.

Children

The app is not directed at children under 13 and does not knowingly collect personal information from them.

Changes

Changes to this policy are posted on this page with a new date.

Contact

Questions about this policy: support@getcyclemap.com.