Last updated: 21 October 2026 · iOS and Android
This is the same text you can read inside the app under Settings → Privacy Policy. The fuller Turkish version is at motoseyir-app.com/gizlilik/.
The app accesses your location to determine your starting point and to follow you along the route during navigation.
IF YOU START A RIDE RECORDING, location collection continues while the screen is off: the recording runs as a foreground service shown by a persistent notification, collecting a point roughly every 2 seconds and writing it TO YOUR DEVICE. This is so the middle of your ride is not lost when the phone goes into your pocket. When you stop the recording, collection stops too; the track is not sent to us while you record. When you start a tour made from a ride recording, an imported file or a trail shared with you, however, the track's points go to our servers to be matched to roads and are not stored (see Our servers, routing service). If you have turned on group riding, only your last location goes to the group riding service while recording (see Our servers).
When you are only planning a route, location is used only while the app is in the foreground. While navigation is running, location is also read with the screen off or while another app is open (on iPhone, also while another app is open on the car screen), so directions and voice prompts don't stop. On Android this works through a foreground service shown with a persistent notification: the notification shows the next turn, the remaining distance and the estimated arrival time (what appears on the lock screen depends on your phone's notification settings), and its “Finish” button ends navigation. Android does not ask for background location permission: the service starts when you tap Start, while the app is open. This location stays on your device and is no longer read once navigation ends. If group riding is on, your last location also goes to the group with the screen off while navigation is running.
Your location is processed on your device. For route calculation, the start, destination and via-point coordinates are sent first to Motoseyir servers in Türkiye and Greece, and to Stadia Maps (USA) elsewhere (and if our servers do not respond); no route request goes to Google on either platform. For rain warnings along the road, your location is sent to the MET Norway weather service. We do not store these requests — the request is served and it ends.
The rain radar works only in the US and Germany. If you turn on the radar on the map, the radar images for the area you are looking at come from NOAA in the US and from DWD in Germany (the two countries' official weather services); these requests carry the coordinates of that map area. While navigating with the radar on, the coordinates of a few points picked from your route are also sent to the same services to check whether rain lies on the road ahead. If you ask AI CoRider whether there is rain ahead, the same check is made even with the radar off on the map (for where you are, if you are not navigating). Nothing but coordinates is sent to these services, and we do not store these requests.
You can revoke the permission at any time (iOS: Settings → Motoseyir → Location. Android: Settings → Apps → Motoseyir → Permissions). In that case you choose the starting point manually.
When you search for a place, the text you type and your location (your device's location or your route's starting point) are sent first to Motoseyir servers: in Türkiye and Greece to the search service, and for place-name searches also to the place service (see Our servers). When our servers cannot find the place (mostly when you search for an address or a business), the search is done by Apple Maps on iPhone and by Stadia Maps (USA) on Android. On Android the Stadia search does not go directly from your phone but through a Motoseyir server: Stadia sees our server's address, not your IP address, and receives only the text you typed, the focus location and the app language; our server does not store the result. If a search returns nothing, the spelling correction suggested by our server is searched once more; the text you type is processed on our server for this and is not stored. AI CoRider's rated place search, and on Android abroad the category words our place service does not know (such as pharmacy, parking or charging), are sent to Foursquare through our server (see Third-party services). These searches are not linked to your identity.
On a place card, the address, phone number, website and opening hours — where available — come first from the place database on our server (when you open the card, the place's ID goes to our server); if our server does not respond or cannot find the place, they come from Apple Maps on iPhone. When you open the card of a place you picked from Stadia Maps in search, the place's Stadia ID is sent to Stadia Maps through a Motoseyir server. Ratings and Foursquare photos come only in Pro, when you open a place's card (see Third-party services › Foursquare).
Discover (places worth a stop around your route, on the tour screen) picks its source by tab. Passes and legendary roads are built into the app. On Android all tabs, and on iPhone the Beaches & coves, Restaurant, Café and Rest area tabs and, in Türkiye, the Campsites tab, come from the place database on Motoseyir servers (see Our servers, place service). On iPhone the other tabs (Fuel, Toilets, Viewpoints, Museum, Hotel, Groceries, Repair, Castle, Entertainment, Hiking, Sightseeing, All, and Campsites outside Türkiye) still come from Apple Maps for now. While Apple's result is shown for these tabs, the same circle query (location rounded the way the place service rounds it, to about 11 metres) is also sent to our place service for comparison; only numbers — the number of places in the two lists and the percentage they share — are sent to the error-tracking service (Sentry), never location, place names or IDs. Search along route, fuel and rest-stop searches and the rest stops near a stop come from the place database on both platforms; for searches the service has no equivalent for (such as a pharmacy or a free-text word) the older route is used (see Search queries). If the place service does not respond, Apple Maps is used on iPhone, the open data built into the app for Beaches & coves and Campsites in Türkiye, and the older server search for Fuel, Campsites, Viewpoints and Motorcycle repair in Türkiye and Greece (Android); where there is no fallback, a “Couldn't load the places” message appears instead of a list. If the place service is switched off remotely, Discover lists come from the older sources (including Foursquare on Android). When you tap a spot on the map on the tour screen to find the place's name, the coordinates of that point go to Apple Maps on iPhone and, through a Motoseyir server, to Stadia Maps on Android.
Photos on a place card are delivered to you through our server when you open the card, in this order: open-licensed photos built into the app or kept on our server, and Wikimedia Commons photos kept on our server (your IP address does not reach Wikimedia); on iPhone, the Apple Look Around image if there is one (below); an image search on the web using the place's name (see Third-party services › Brave Search; this search is not made for a place for which we already have at least three of our own or Commons photos); and finally, in Pro only, Foursquare photos. You can long-press a web photo and choose “Report this image” to remove it for everyone.
On the cards of urban venues (such as cafes, fuel stations and hotels), on iPhone, Apple Maps' Look Around street view is shown as a photo when it exists. The image comes to your iPhone directly from Apple (the place's location goes to Apple), is kept only in your device's cache and is not sent to our servers; if there is no coverage, nothing is shown. It is not used for natural places such as beaches, coves and passes. There is no Look Around on Android.
If you have entered your tank range in Settings, the app searches for fuel stations by itself: during navigation, the ones ahead on your route; and when you stop for more than two minutes during navigation or a ride recording, the ones near where you stopped, to tell whether you filled up. These searches send only the coordinates of the search point and the type searched for (fuel station): to Motoseyir servers (on iPhone, to Apple Maps if our server does not respond). With the tank range left empty, these searches are not made.
To prevent the trial period and the launch campaign from being claimed over and over by deleting and reinstalling the app, we derive a one-way hash (SHA-256) from a stable identifier of your device and send it to our server.
The source is Settings.Secure.ANDROID_ID on Android and, on iOS, a random identifier the app keeps in the Keychain. The raw identifier is never sent; only the hash is held on the server.
It is used for three things: the trial start date, the campaign order and — if you have turned on group riding — linking your group membership and current location to your device. It is not used for advertising, profiling or analytics.
If you installed the app after tapping an ad, Apple's SKAdNetwork system tells the ad network that the install took place — without sharing your identity, with a delay and in aggregate. This notice is sent by iOS, not by the app; Motoseyir sends no data about you to ad networks, and there is no ad-tracking SDK in the app.
When you use voice search, what you say is passed to the operating system's speech recognition service solely to turn the place you are looking for into text. Depending on your device, that service may perform the conversion on the device or send it to Apple/Google servers; the operating system decides. The audio is not sent TO US, is not stored by us, and it only runs when you press the microphone button.
When you use the group-ride intercom (only if you turn it on), your microphone stays open for the whole navigation and your voice is sent over the internet only to the members connected to the same group at that moment. Audio is NOT recorded or stored by us; our media server only relays it. The intercom stops when navigation ends; you can mute the microphone at any time with the switch on the group card or by tapping the intercom pill while riding.
When you use AI CoRider (only if you turn it on; a Pro feature), your microphone stays open from the moment you tap the button until the session ends; your voice is sent directly to a cloud AI voice service (a third-party provider) to generate the reply, and the reply comes back as speech. Audio is NOT recorded or stored by us; our server only sets up the connection, no audio passes through it. The following also go to the service as text: route information (the destination's name, remaining distance, next turn, your speed), your group friends' nicknames and relative distance, and the results of what you ask for (the names and distances of places found, weather and rain conditions; if you ask “where am I”, the name of the road, district and province you are in). For a request like “call Elif”, the name search in your contacts is done on your phone (contacts permission is optional and your contacts are not uploaded); if there is more than one match, the matching people's names also go to the service as text. Coordinates and phone numbers are never sent. A session lasts at most five minutes, closes by itself after a period of silence and when navigation ends, and can be closed any time with the button. AI CoRider never starts while the intercom is on: both use the same microphone.
In Chat mode a short summary of your earlier chats is sent to the service at the start of a session; transcripts are stored only on your phone and can be deleted in Settings.
The tours, stops and route drafts you save, your tour diary (notes and photos), your preferences, usage counters and subscription tier are kept only on your device and are not transmitted to us.
If you delete the app, this data is deleted too. Your photos are accessed only when you choose one to add to your journal, your Community profile or a mountain pass; your gallery is never scanned.
So that the free trial and the welcome offer can be given only once per device, the app stores the moment it first connected to our server and the moment the welcome offer started in the iOS Keychain. This information never leaves your phone and remains even if you delete the app.
On Android the same two moments (first connecting to the server and the start of the welcome offer) are kept in the app's own data and disappear when you delete the app. So that the welcome offer does not start over after a reinstall, the app asks the server when it first saw this device ID digest; the server already keeps that information for the trial record.
If the app closes unexpectedly or catches an error, a technical report is sent to the error monitoring service Sentry so that we can find the problem.
The report contains the type of error and where it occurred in the code, the app version, the operating system version, the device model and a technical trail of the last steps before the error. It does not contain your name, email, search queries or location: in the addresses of network requests, the part after the question mark — where coordinates appear — is removed before sending. Reports are not linked to your identity and are used only to fix the app.
The motoseyir-app.com/indir and /get pages that ads link to send anonymous step records to our server so that we can tell whether the hand-off to the App Store works: the page, the ad campaign tag, the step (page opened, redirected to the App Store, page left), time zone, iOS version, browser type and language. No cookies are used, no IP address is stored and there is no identifier that recognises you; records are deleted after 30 days.
The routing service calculates routes: the start, destination and via-point coordinates are sent, the route is calculated, the result is returned, and no record is kept. When it opens, the app also gets its settings from our server; this request carries only the hashed device ID and is not stored. When you start a tour that has a track — from a route file you imported (GPX, KML or GeoJSON), from one of your ride recordings or from a trail shared with you — the coordinates of points picked from the track are also sent, to tell whether the track follows roads and to give directions along it (at most 600 points for an imported file, up to about 1,500 for other tracks); these are not stored either.
The search service looks up places: the text you type and your location are processed only to produce the results, and no record is kept. The hashed device ID is used only in a one-minute counter to limit excessive requests; the server keeps only an hourly total of query types (place, address, business).
The place service queries the place database on our server for Discover, Search along route, fuel and rest-stop searches and place-name searches. What is sent: your location (rounded to about 11 metres), the category or tab, for Search along route points picked from your route about 100 metres apart, the text you type in a place-name search and — only to limit excessive requests — your hashed device ID and a hash of your IP address. The query is processed only to produce the result; location, search text, route and IP address are not written anywhere, and no request log is kept (the log keeps only the endpoint name and duration of a slow query). The rate-limit counter is held only in memory. The service does not reach the internet; the database contains no user data.
Offline maps (Pro subscribers only, iPhone only): when you download a tour's map, the tour's route line is sent to Motoseyir servers; when you download a region's map, the corner coordinates of the area you framed on the map are sent instead. The server prepares a map of that area. The route line and corner coordinates are not stored; the prepared map file is kept without knowing whose it is. The name you give a region stays on your phone and is not sent to the server. The file is held at Cloudflare (USA) and downloads to your phone from there; Cloudflare sees your IP address during the download. To prevent abuse, the number of new maps prepared that day is counted using non-reversible hashes of your device ID and your IP address; this count is kept only in memory and is deleted when the day ends. The downloaded map stays only on your phone and is not included in iCloud backups; you can delete it under Settings › Offline maps or with “Delete my data”.
Trip map video (only if you turn a tour or a ride into a video with the “Trip map” style): the video is made on your phone; your route, photos and location are not sent anywhere. Only the map itself is fetched from the internet: the pieces needed from the world map come from our map storage at Cloudflare (USA), and the terrain relief comes from Amazon Web Services' (USA) public map storage. Which pieces are requested shows the area in the video; your route itself is not sent. Motoseyir sends no device ID with these requests and keeps no request log; Cloudflare and Amazon see your IP address during the download.
The counter service manages trial and campaign entitlements: only the device identity hash is sent. No request log is kept; to prevent abuse there is only a one-hour counter, and what it holds is not your IP itself but an irreversible hash of it. The hash salt changes every time the service restarts, so no persistent identity is formed.
The group riding service (only if you turn it on): your group memberships and, WHILE A RIDE IS RUNNING, your last location are held here. No history is kept — only the last point is stored and overwritten. When the ride ends the location is deleted; if the app cannot send the delete request, the server deletes it itself after three minutes. Location is only sent WHILE a ride recording or navigation is running — also with the screen off.
People in the group see your route's name, how much of it you have completed, your current speed and heading, your last location and how many seconds ago it was updated. The nickname you enter when joining is held on the server — it is the only way other members can tell who is where. That name is YOUR choice, is visible only to people in the same group, and is deleted when the group is deleted.
Knowing the group code is not enough: only people who have JOINED the group can see members' locations, and whoever joins also appears in the list. There can be no silent watcher. A group goes to sleep after three hours of inactivity (it does not close — the same code works again the next day); if no member covers any distance for seven days, the group and its memberships are deleted.
Intercom service (only if you turn it on): for voice chat on group rides our server gives you a short-lived ticket to the group's voice room; audio is relayed through our own media server (LiveKit) only to the members in the room at that moment and is neither recorded nor stored. Only people who have joined the group can enter the room; the room closes when navigation ends.
AI CoRider service (only if you turn it on): our server gives you a short-lived ticket to open the session and negotiates the connection on your behalf; the AI service's access key stays on our server only and never reaches the phone. To count your daily session allowance, a hash of your device ID, the time the session opened and its length are kept — deleted after at most seven days. So that your Pro subscription's AI CoRider minutes and the minute packs you buy can be recognised, the store's proof of purchase (on iPhone Apple's signed transaction record, on Android the Google Play purchase token) is sent to our server together with your device ID hash and verified (on Android by asking Google Play); the server keeps only the device ID hash, the transaction ID, the product, the duration or expiry date and your minute balance — not the proof itself, nor your name, email or price. Your voice and the transcript never reach our server. If you use up the AI CoRider trial minutes, in addition, an irreversible hash of your IP address is kept for 24 hours to prevent the trial being abused from the same network with many new devices; the hash's salt changes every time the service restarts.
A ride recording sent to the group (only if you send it): the track, distance and duration of your recording are kept on our server for 14 days and can only be seen by people who joined the group. The part of the track within about 400 metres of its start and end points is not sent — the location of your home or parking spot does not reach the group. At most three recordings per sender are kept (a new one drops the oldest) and you can remove a recording from the group at any time.
The tour code service (only if you share a tour BY CODE): the tour itself — its name, its stops and the track if there is one — is kept on our server for 30 days and deleted when that expires. This is a route you planned, not a record of where you went. Who uses the code is NOT recorded: the server returns the tour for the code and neither knows nor stores who received it. Unless you share a code, none of your tours ever reach the server.
If you say “let's ride together” while sharing a tour, your group code is attached to the tour code; the person who receives it is ASKED whether they want to join the group and does not join silently. Until they join, nobody's location is shared.
Group route (only if you start a route while in a group): so that the group can open the same route with one tap, the route you start — its name, start, stops, line, turn instructions, distance and duration — is sent to our server. Only people who have joined the group can see it. It is deleted when the ride ends; if the app cannot send the delete request, the server deletes it itself after 12 hours.
Share my ride (only if you turn it on): anyone who has the link (including people the recipient forwards it to) sees, on a web page without the app, your latest location, the direction you're heading and when the location was taken and, if you're navigating, the name of your destination, the distance left and the estimated arrival time; the page's map comes from OpenStreetMap. The link closes on arrival, when you end navigation or the ride recording, or when you stop sharing; it also closes after 24 hours at the latest, or if no location arrives from your phone for three hours. Your location is still only kept while you ride.
Group alerts (only if you send one — I'm behind, Break, Hazard, Fuel): the alert is visible only to people who joined the group, for 10 minutes, and is then deleted. Your location at that moment is attached only if you show your location in that group.
Meeting point and roles (in group rides): if the group's leader marks a meeting point, its location, and its name and time if given, are stored on our server and visible only to people who joined the group; the point is deleted 30 minutes after its time (12 hours after it was set if it has no time), when the person who marked it leaves the group, or when the group is deleted. Who is the leader and who is the sweep is stored with the group. The “someone stopped / fell behind” alert is worked out on the leader's and the sweep's phones from positions the group already sees; nothing extra goes to our server, and members who don't show their location are left out.
Community (only if you join): the username and icon you choose, the tours you share (name, stops, route shape, your note), your likes and your comments are held on our server and are visible to EVERYONE using the app. Your visit times and your group code never enter the share; your diary notes and photos go only if you turn on "Share the diary too" while sharing, and then they become public. You can remove a post or a comment whenever you like, block a member and report inappropriate content; content reported by three different people is taken down automatically and we review it. If you share a recorded ride, the parts of the track within about 400 metres of its start and end are left out, so your home or parking spot does not end up in the feed.
If you choose the “Near me” sort in the Community feed, the last location known to your device is sent to our server to order posts by distance from you; it is only used for sorting and is not stored.
Instead of an icon you can upload your own PHOTO (optional). It appears next to your posts and comments, visible to everyone. We re-encode it on the server: it is downscaled and the LOCATION and device data inside the file (EXIF) is removed completely — the coordinates of a photo taken at home go nowhere. You can remove it at any time and go back to an icon; do not upload someone else's photo.
Pass photos (only if you add them): a photo you add to a pass on the Mountain passes page is stored on our server with your username and is visible to EVERYONE using the app on that pass's page. Before sending, the photo is shrunk on the phone to at most 1280 pixels; its location (GPS) and camera data (EXIF) are removed both on the phone and on the server. To link the photo to you, your device identifier digest, the upload time and your community region are also stored; they are never shown to anyone. Photos from new members are reviewed before they go live. You can remove your photo at any time and report an inappropriate one — a photo reported by three different people is taken down automatically and we take a look. The file of a rejected or removed photo is deleted from the server immediately; if you delete your community membership, all your pass photos are deleted too.
Community events (only if you create one): the event's title, description, start time and your time zone, the meeting point (its coordinates and place name), the number of spots and the attached route if there are any, the region tag (which region's list it appears in), its publication status and, if you cancel it, the time of cancellation are kept on our server. The meeting point is visible to EVERYONE who can see the event; pick a place anyone can find, not your home. Your current position becomes the meeting point only if you choose “My location”. The attached route is either a copy of your tour, cleaned as when sharing in Community (no visit times, journal or group code), or the code of a Community post. Your hashed device ID is also kept to link the event to you; it is never shown to anyone.
If you join an event, your hashed device ID and the time you joined are kept. Others see participants only by username and icon (or photo); participants' locations are neither kept nor shown. You can report an inappropriate event; reports go into the same moderation queue as posts. For events, blocking works both ways: the person you block doesn't see your events, and you don't see theirs. An event, its sign-ups and the reports about it are deleted 14 days after it starts; if you delete your Community membership, the events you organized and your sign-ups are deleted right away.
Badge leaderboard (only if you turn on “Show me on the leaderboard” on the Community › Badge leaderboard page; it is off by default): your username and icon and the following numbers are stored on our servers and shown on the leaderboard to app users in your region: your badge count, the number of different mountain passes you have crossed, the height of the highest pass you have crossed, the tier of your total-distance badge (0–4), your distance unit (km or miles), and the number of badges you earned and passes you crossed for the first time this month. The numbers are calculated on your phone: your location, routes, ride recordings and which passes or badges you earned are not sent to the server. To tie your entry to your device ID hash, that hash is stored too; it is shown to no one. The leaderboard is split by community region; members you have blocked and members who have blocked you do not appear on each other's leaderboard. When you turn the switch off, delete your community membership or use Settings › Delete my data, your entry is deleted from the server; an entry that is not updated is deleted automatically after 12 months at most. Because the numbers come from your phone, the server only performs a rough check.
Support chat (only if you write to us): the messages you send from Settings › "Something wrong, or an idea?", our replies, the app version and your phone's operating system are stored on our server; only the person who builds the app reads them and they are not shared with anyone. The conversation is tied to your hashed device ID and kept for at most one year. You can delete it at any time with the bin icon in the chat or with "Delete my data".
Notification service (only if you allow notifications): your notification address (the token issued by Apple on iPhone or by Google on Android), the app version, the language, your phone's time-zone offset, your permission status, your “likes and comments” preference and a hash of your device ID are kept on our server. Notifications about new versions and announcements are sent only between 09:00 and 23:00 your local time; notifications about likes, comments and replies to your Community posts are sent too, unless you turn them off. The text of a notification is produced on the server and delivered through Apple or Google (see Third-party services). When you turn notifications off in Settings the record is deactivated; “Delete my data” deletes the record from the server; a record that has not been renewed for more than 180 days is deleted.
Our servers hold no real name, email address, phone number, location HISTORY or payment information.
Google Maps SDK (Google) — on Android only, to display the map (including Watch in 3D and 3D video): map tiles come to your phone from Google; through the SDK, Google processes your IP address, request information such as the device model and operating system version, crash data and an anonymous SDK-specific identifier under its own privacy policy. Videos are made on your phone and are not sent anywhere. Motoseyir sends Google no place-search, place-card, Discover, routing or elevation requests; the Google Places, Routes and Elevation services are not used. The Google Maps SDK is not used on iPhone.
Google (other requests): (1) Connectivity check (iPhone only): to tell whether the internet is really working, the app sends an empty request to clients3.google.com (about every 5 minutes while connected, every 30 seconds while not); it carries no app data and Google sees only your IP address. On Android the operating system's own network check reports internet access and the app does not send this request. (2) Map links (both platforms): if you paste a Google Maps short link (maps.app.goo.gl) into the search box or share one from another app, the app opens that link at Google to learn its real address; Google sees your IP address and the link. (3) The “Maps” button on a place card and the “Walk” button on the arrival card open Apple Maps on iPhone and Google Maps on Android with the place's coordinates; what happens next is governed by that app's privacy policy.
Apple Maps (MapKit) — on iPhone: the map, place search, place cards and Discover. The search text and location go to Apple and are processed under Apple's privacy terms.
Stadia Maps (USA) — route calculation (outside Türkiye and Greece, and when our servers do not respond), speed limits during navigation and the elevation profile; on Android also place search, place cards and the name of a place you tap on the map. Route, speed-limit and elevation requests go directly from your phone; Stadia sees your IP address. On Android, place-search, place-card and place-name requests go through a Motoseyir server instead: for these Stadia sees our server's address, not your IP address; our server does not store the results, the access key stays on the server only, and to prevent abuse only the day's credit count is kept (with a hash of your device ID and a non-reversible hash of your IP); the counter is deleted when the day ends. What is sent: for routes, the start, destination and via-point coordinates, your route preferences (route mode, toll-road and avoid options) and the instruction language; for speed limits, when navigation starts and whenever the route is recalculated, the coordinates of points picked at regular intervals along the route line and the direction of travel at each point; for the elevation profile, the coordinates of up to 400 points picked from a track: when you import a route file without elevation (GPX, KML, GeoJSON or ITN), when you open a trail without elevation, and when you open one of your ride recordings (that recording's track); on Android, for place search (through our server), the text you typed, the focus location (or your route's starting point and the search radius) and the app language; for the suggestion you pick or the card you open, the place's Stadia ID; to find the name of a spot you tap on the map, that point's coordinates. Beyond these, the app sends Stadia no name, account or device-ID digest.
Foursquare (USA) — for two things. (1) Rated place search: in AI CoRider's rated place search (both platforms), when on Android abroad you search for a category our place service does not know (such as pharmacy, parking or charging), and in Discover lists if the place service is switched off remotely, the coordinates of the search centre, the word or type searched for, the search radius and the app language are sent to Foursquare through our server; your hashed device ID goes to our server, and Foursquare sees neither your device ID nor your IP address. (2) Ratings and photos: when you open a place's card in Pro, only the place's Foursquare ID is sent. Results are not cached on your phone; Foursquare photos are delivered to you through our server, are not written to disk on our server and are marked not to be cached — apart from the short-lived session memory of the image being displayed. Searches are not stored; to prevent abuse only the day's request count is kept (with a hash of your device ID and a non-reversible hash of your IP), and it is deleted when the day ends.
Apple Look Around — on iPhone, for urban venues (a café, petrol station or hotel, for example): if Apple Maps has a Look Around street-level image there, it is shown as a photo on the place card. The image comes to your iPhone directly from Apple (the place's location goes to Apple), is kept only in your device's cache and is never sent to our servers; if there is no coverage, nothing is shown. It is not used for nature spots such as beaches, coves or passes.
Brave Search (USA) — image search for the photos on place cards: when you open a place's card, the place name, its nearby locality (e.g. “Hamlet Beach Konyaaltı”) and the country code of the region are sent to Brave's image search through our server; your device ID, IP address and exact location are not sent to Brave. The images it finds are delivered to you through our server and kept on our server only temporarily, for at most 60 minutes, and then deleted (the same place is not searched again during that time; nothing is stored long-term); our server also downloads the image from third-party sites, so your IP address does not reach them. If you tap a photo's source chip, that site opens in your browser and its own terms apply. To prevent abuse we keep only that day's search count (as a hash of the device ID and an irreversible hash of the IP), deleted when the day ends. If you choose “Report this image”, its address is blacklisted for everyone; your device-ID hash is kept only to count reports from the same site. brave.com/search/api
Open place data — our place database is built from the open place data of OpenStreetMap contributors, Foursquare Open Source Places and Overture Maps Foundation. The app sends these sources no requests; no data about you goes to them.
Cloudflare (USA) — hosting of map files: when you download a tour's or region's map or make a trip map video, the map comes to your phone from Cloudflare; Cloudflare sees your IP address during the download. cloudflare.com/privacypolicy
Amazon Web Services (USA) — only for trip map videos: terrain relief tiles (public Mapzen/AWS Terrain Tiles data) come to your phone from Amazon's servers; the request carries only the tile's address, and Amazon sees your IP address during the download. aws.amazon.com/privacy
MET Norway (Yr.no) — weather forecast; only coordinates are sent.
NOAA (the US National Oceanic and Atmospheric Administration) and DWD (Deutscher Wetterdienst, Germany's national weather service) — rain radar, in the US and Germany only: with the radar on, the coordinates of the map area you are looking at; during navigation with the radar on, and when you ask AI CoRider about rain, the coordinates of points picked from your route or of where you are. Nothing but coordinates is sent. noaa.gov privacy · dwd.de data protection
The device's reverse-geocoding service (Apple on iPhone; on Android the phone's system service — on most phones Google's) — the coordinates of a point are sent to learn its name or address: a spot you tap or long-press on the map; where you are (first launch, a new tour, a meeting or gathering point, when you ask AI CoRider where you are); the stops of the tour generator and of an imported track; the start and end places shown in a video; and the start of a tour you share (for the country code). These requests do not pass through Motoseyir servers.
Cloud AI voice service (third-party provider) — voice conversation with AI CoRider; only if you turn it on, your voice and the reply pass through this service, subject to the provider's own terms. The provider's name is available on request.
Sentry — crash and error reports (see above).
Apple Push Notification service (APNs) and Google Firebase Cloud Messaging (FCM) — notifications are delivered from our server to your phone through these services; the text of the notification and your notification address (token) pass through them. The Android app includes the Firebase component; even if you do not allow notifications, it may contact Google and process information such as a Firebase installation ID (FID) that identifies the app installation, the app version, and the device model and operating system version, under Google's policy.
Apple App Store and Google Play — subscription and minute-pack purchases. We have no access to your payment details. On Android you enter a promo code on Google Play's “Redeem code” page; Play verifies the code and the app does not see it.
In Türkiye the free tier is always available and has no limit on the number of routes; other features come with a subscription. In other countries the app is used with a subscription. Any free trial is shown in the store's subscription offer and begins only when you start it.
The subscription renews automatically unless it is cancelled at least 24 hours before the end of the period. Management and cancellation happen in your store account — Apple ID settings on iOS, Google Play → Subscriptions on Android.
The app is not directed at children under 13 and does not knowingly collect data from them.
The app requires no account; all data on your device goes when you delete the app — except, on iPhone, three small records in the iOS Keychain: the random identifier your device ID hash is made from, the moment the app first connected to our server and the moment the welcome offer started. These stay on the phone even if you delete the app or use "Delete my data", and they never leave it; only the non-reversible hash of the identifier is sent to our server (see Device identifier digest). If you joined the Community, you end your membership with Community › My profile › "Delete membership": your username, posts, comments, likes and the photos you added to passes are deleted from the server immediately.
If you joined the badge leaderboard, your entry is deleted from the server immediately when you turn off “Show me on the leaderboard” or delete your community membership.
The following may remain on our server, tied to your device ID digest: your trial/campaign records; if you used group riding, your group membership and nickname; if you allowed notifications, your notification record; and your AI CoRider session, subscription and minute-pack records. You can leave the group from the app or end your membership with “Delete my data”; the moment you leave, nobody can see you. “Delete my data” also deletes your notification record from the server. If you want the other records deleted, write to the support address; we will delete them on request.
Do not handle your phone while riding. Set up your route before you set off and mount the phone in a proper holder.
You can write to us about questions, bug reports and subscriptions:
We usually reply within a few working days. In a bug report it helps a lot if you mention your device model, operating system version and the screen where you saw the problem.