Privacy policy

MotoNomad app (Android and iPhone) · effective 24 October 2026 · version 18. The Polish version is the primary one.

1. Who is responsible

The data controller is the developer of MotoNomad. Contact for all data matters: hello@motonomad.app.

2. Data on your phone

The data below is stored in the app's private storage on your device. We do not send it to our server or anyone else — the exception is cloud backup in Pro, when it is on: then a copy of part of it is also on our server (section 6a):

• rides: GPS track (coordinates, altitude, speed, heading, accuracy, time), distance, moving time, elevation gain and an approximate lean angle from the phone's sensors;
• garage: motorcycles with name, make, model, tank data, odometer and an optional cover photo (a copy stored inside the app);
• refuels, trips, stages, expenses, saved places and notes (text and voice recordings);
• settings, your "Home" address and recent destinations;
• route ideas from the AI assistant: the description you typed and the chosen places with reasons, so the same question does not go to the server twice. Clear them in Settings → AI assistant;
• motorcycle display: the hotspot name and password copied from the motorcycle screen, the handlebar button setup and the TFT screen settings;
• diagnostic log: technical entries about how the app runs. It leaves the phone only if you share it yourself from Settings, e.g. by e-mail to us. The same goes for the “Report a connection problem” report of the motorcycle display: we prepare a file with your phone model, app version, technical data of the motorcycle dash without serial numbers and the connection entries from the log, and you send it yourself from your e-mail.

This data is deleted when you delete it in the app or uninstall the app. Android system backup (on your Google account, if you have it turned on) includes rides, trips, refuels, notes, cover photos and settings, so they are not lost when you change phones. It does not include your sign-in session or the diagnostic log. Google creates and stores the backup; we cannot see it. On iPhone, app data is included in iCloud backup or a computer backup if you have it turned on — Apple creates and stores it; we cannot see it.

3. Data sent to external services

Each request contains only what the service needs to answer. Every provider also sees your device's IP address, as with any internet connection.

Motorcycle display (TFT). If you connect the phone to the colour display of a motorcycle (EasyConn module, e.g. Benelli TRK 702), the app sends the picture of its screens — map, maneuver, time to destination, weather and stations — directly to the motorcycle over your phone hotspot Wi-Fi, on the local network (in the experimental mode the phone joins the motorcycle Wi-Fi or connects to it over Wi-Fi Direct; the internet then stays on mobile data). The picture does not go through the internet or our server and is not stored anywhere. From the motorcycle the app receives only the technical data needed to connect (the module model and software version and its identification number); the model and version go to the diagnostic log on the phone. Handlebar buttons arrive over Bluetooth as ordinary media keys. The QR code on the motorcycle screen is read by the Google Play services scanner on the phone: the app receives only the decoded text (network name and password), not the camera image. Bluetooth (Bluetooth LE, without pairing) is used solely to set the motorcycle clock: the phone sends the module the current date and time and nothing else; nothing leaves the phone and the motorcycle over Bluetooth.

Motorcycle display on iPhone. The iPhone joins the motorcycle’s Wi-Fi network (the display’s “Apple” mode), which you choose yourself in the phone’s Settings, and finds the motorcycle there with Bonjour — that is why iOS asks for local network access. The picture travels the same way, on the local network, without the internet or our server. On iPhone there is no QR code scanner and no clock setting over Bluetooth; handlebar buttons arrive as system media commands.

4. Location, including in the background

• During a ride, also with the screen off, while the app records the ride or guides you. A persistent notification ("MotoNomad nagrywa jazdę") with a stop button is shown the whole time.
• In the background with the app closed, only if you enable automatic ride recording in Settings. The app then detects motion (activity recognition) and starts recording. This is off by default.

Recorded coordinates are stored on the phone. Only individual points needed for the route, weather and stations are sent to the services in section 3.

On iPhone background location works while the app records a ride, guides you or sends the picture to the motorcycle display — iOS shows the blue location indicator in the status bar. Automatic recording (requires “Always” location and Motion & Fitness access) detects motion only while the system has not closed the app. The “audio in background” mode is used only for voice prompts with the screen off, and background refresh only for the morning weather for a trip stage.

5. Permissions

• Precise and approximate location: map, ride recording, guidance, weather and stations ahead.
• Background location: only with automatic recording enabled.
• Activity recognition: detecting that you started riding.
• Notifications: the ongoing-ride notification and the morning weather for a trip stage.
• Microphone (optional): only for voice notes, when you start recording yourself. The recording stays on the phone in the app's private storage; deleting the note deletes the file. Transcribing the recording to text after recording is done by on-device speech recognition, without sending anything. Only when the phone cannot do that and you tap “Transcribe” on the note yourself, the app passes the recording to the system speech recognition service (usually Google), which may send it to its servers and returns only the text; the recording never reaches our server. You can turn off transcription after recording in Settings → Logbook.
• Foreground service (location) and start after reboot: uninterrupted recording and restoring automatic start.
• Notification access (optional): only to show the title of the song playing during a ride. It is read on the phone and never sent anywhere.
• Internet and network state: the requests in section 3 and the "no network" notice.
• Foreground service (connected device), Wi-Fi multicast and Wi-Fi state, access to devices on the local network, changing Wi-Fi and network state, nearby Wi-Fi devices (without location): only for the motorcycle display — finding the motorcycle on the phone hotspot network, joining the motorcycle Wi-Fi or its Wi-Fi Direct group and sending it the picture continuously while the phone screen is off. A "Motorcycle display" notification with a "Disconnect" button is shown for the whole connection.

On iPhone the same features ask for iOS permissions: location (while using and “Always”), Motion & Fitness, notifications, microphone and speech recognition (voice notes only) and local network (motorcycle display only). You can revoke each in iPhone Settings → MotoNomad.

Motion sensors (accelerometer, gyroscope) are used for the approximate lean angle and only while recording. The motorcycle cover photo is chosen with the system photo picker; the app has no access to the rest of your gallery.

6. Account (optional)

No feature requires an account. On first start with internet, the app creates an anonymous identifier with the Supabase sign-in service so that an account can later be attached without losing data. The identifier itself contains no data about you. On our server only two things are linked to it: the Pro status (whether it is active, until when and which plan — from RevenueCat notifications or from a Pro code you enter in the app, e.g. a code for store reviewers; we also keep the number of code attempts per day so it cannot be guessed — deleted after 60 days) and the daily count of AI assistant requests. Both serve only to let the server know how many requests a day you are entitled to.

If you sign in with Google, Supabase receives your Google ID, e-mail address and account name from Google. If on iPhone you choose “Sign in with Apple”, Supabase receives an identifier and e-mail address from Apple — your real one or, if you choose “Hide My Email”, an Apple relay address; we do not ask for your name. If you use an e-mail code, Supabase receives your e-mail address and the one-time code is sent through the mail provider Resend.

Without Pro or without signing in, rides and other data are not synchronised to the account; they stay on the phone. Cloud backup in Pro is described in section 6a.

Signing out does not delete data from the phone; the app asks whether to delete it. The cloud backup stays on the server. See Account deletion.

6a. Cloud backup (Pro)

Cloud backup is a Pro feature that works only after signing in (Google, Apple or an e-mail code) — not on an anonymous account. Signed in with Pro it is on; you can turn it off in the app: Settings → Account and app → Cloud backup. It keeps your data on every phone you sign in on, so it is not lost when you change phones.

What goes to the server: rides with their GPS track (coordinates, altitude, speed, heading, accuracy, time, approximate lean angle), motorcycles with their cover photo, trips with stages, points, routes (including from imported GPX files) and expenses, refuels, saved places, text notes and voice recordings, as well as your “Home” address, recent search destinations and the monthly goal. The Home address, if you set it, is in the backup with everything else — there is no separate switch. Not included: recorder, ride screen, motorcycle display (TFT) and other phone settings, the diagnostic log, stored AI assistant answers and the sign-in session.

Where and who can access it: on our server at Supabase in the eu-west-1 (Ireland) region — the same project as the account. The data is linked to your account and only your account can see it: access rules in the database check the owner on every row and every file. Connections are encrypted (HTTPS). We do not share this data with anyone and use it only for backing up and syncing your phones.

When: entries (rides, trips, expenses, notes and so on) go when the app starts, when the network comes back, a few seconds after a change and after a ride ends — also over mobile data; during a ride the backup waits. Files (tracks, photos, recordings) go over Wi-Fi only outside the EU, and with the “Files over Wi-Fi only” switch — over Wi-Fi only everywhere.

How long: until you delete the item in the app or delete the account. A deleted entry stays on the server marked as deleted for at most 90 days, so that the deletion reaches your other phones; a file whose entry no longer exists (e.g. the photo of a deleted motorcycle) is deleted within 30 days. Turning backup off, signing out or Pro expiring does not delete data from the server — after Pro expires, new changes stay on the phone and the backup still comes to your phones as long as the account exists. You delete it by deleting the account: the app first deletes your files from the server, then the account with all entries; if a file cannot be deleted right away, the server deletes it by itself within 30 days.

6b. Sharing a trip plan by link

When you tap “Share” and “Create link” in a trip’s details, the app sends a snapshot of the plan to our server at Supabase (eu-west-1, Ireland) and you get a link motonomad.app/w/… with a random, unguessable token. It also works on the anonymous account, without Pro and without cloud backup. Anyone with the link can see the plan on motonomad.app or in the app — without an account.

What the snapshot contains: the trip name, dates, stages (day, date, name, km, countries) and the stage routes. What it does not contain: notes, addresses, names of overnight places (only the town, which our MapTiler geocoder derives from the overnight point — the “Overnight stops” switch, on by default), costs (the “Cost per person” switch, off by default — then a single amount: the sum of the trip expenses), rides, GPS tracks or your account. The route is cut 2 km from your “Home” address (if you have not set it — 2 km from the start and end of the trip) and 500 m at the end of each day, so nobody can see where you live or sleep. The phone also draws the link preview image (route, name, numbers) into a public file on the same server — Facebook, Messenger and other messengers show it.

When and for how long: the snapshot updates by itself a few seconds after you change the trip, when there is a network. We count page openings (without preview bots); we do not record who opened the link. Link pages are not indexed by search engines. The link works until you turn it off (“Turn off link”), delete the trip or your account; a turned-off link only shows “The author turned off this link”, and the image is deleted right away. Every link page has “Report content” (e-mail hello@motonomad.app); we may turn off a reported link.

6c. Trip story by link and day photos

In the same place (“Share” → “Story”) you can create a second, separate link: a story of what you actually rode. You can turn it on once the trip has at least one finished ride. The story snapshot goes to the same server (Supabase, Ireland) and contains: the ridden GPS track of rides linked to the trip (simplified, cut 2 km from “Home” and from the start of the first day — and, once the trip has ended, from the end of the last day — and 500 m at the start and end of every day, i.e. at overnight stops), for each day the km, moving time and countries, the highest point, the trip plan as in section 6b (recipients can copy the plan — never your track), and — only if you choose so — day posts you approved yourself (after your edits; an unapproved post never leaves the phone), day photos and the cost per person. The story never contains notes or the area around “Home”.

Day photos: you add up to 3 per day from your gallery in “Day post” or next to a day of the story. The app keeps a copy on the phone scaled down to 1600 px and without EXIF metadata (no GPS position, date or camera model). Only photos of days shown in the story with “Day photos” switched on go to the server — into the link’s public folder; anyone with the link can see them.

When and how long: with “Add the next days” on, today reaches the link only from 8 pm phone time or the next day — never live, so nobody can see where you are. You turn the story off with one tap (“Turn off link”): the snapshot stops being available, and we delete the photos and the preview image right away. A photo removed from a day or switched off in the story disappears from the server with the next update. When you delete your account, the app first deletes from the server the photos and images of links created on this phone. “Report content” is on the story page too.

6d. Position for loved ones

While riding (☰ menu → “Position for loved ones”) you can create a link motonomad.app/p/… where your loved ones see on a map where you are — no account and no app needed. It works with the anonymous account, for free. In Settings → Recorder you can turn on “On every trip stage”: a ride within a trip then shares your position by itself under one link for the whole trip.

What the phone sends: your GPS position about every minute while riding and every 5 minutes when stopped, a “moving / stopped” flag and the time, and with “Destination and expected arrival” on (default) also the destination name, arrival time and km to go from guidance; plus the day number and trip name and the phone’s time zone (so the arrival time is yours). Never: your speed, positions closer than 2 km to your “Home” address (riding home ends sending earlier), notes or rides outside the sharing time. Without a network only the newest position waits.

Who and how long: anyone with the link sees the page: the latest position and the track of the last 2 hours. A ride link works until the ride ends and at most 24 h more as “ride finished”, a trip link — up to 24 h after the last ride; “Stop now” turns it off at once. We delete positions older than 24 h from the server (Supabase, Ireland) automatically every half hour. We count page openings, not who opened them. The page is not indexed and has “Report content”. The map on the page is drawn by MapTiler (the recipient’s browser downloads the image with the position and 2-hour track).

6e. “Ridden” and collections

After a trip planned from a MotoNomad idea the app asks once “How was it?”. When you tap “Send”, our server (Supabase, Ireland) receives with your account (also anonymous): the idea ID, the trip ID, the date and the ready-made tags you chose for the days (e.g. “recommended”, “roadworks”) — no text, route or position. Others see in the idea details only the total number of rides in 12 months, the date of the last one and tag counts — only once at least 3 people have ridden the idea, never who. Entries are deleted with your account.

Collections (countries, regions and passes in the Logbook) are counted by the phone from your rides and from data packages bundled with the app — nothing goes to a server. The collection image only leaves the phone if you share it yourself.

6f. Crew — a shared trip

With Pro you can invite up to 8 people to a trip with a link motonomad.app/e/… (valid 7 days). Joining requires signing in (Google, Apple or e-mail code) — the crew has to know who is who. An invitee without the app sees on the invitation page the trip name, dates, days and km, the members’ names and bikes, and the invitation code.

What goes to our server (Supabase, Ireland) and to crew members: the name, bike name and colour you enter yourself; the trip plan (stages, points, lodgings, names), expenses marked “whole crew” or “selected” (amount, currency, who paid, for whom) and notes you mark “for the crew”; attendance days and number of shares; settlement state (“I paid”, “confirmed”). What never goes: rides and GPS tracks, “just me” expenses, private notes, your Home address, recent destinations, refuels outside the trip budget.

On the ride: during a recorded ride of a stage of the shared trip your phone sends the other members your GPS position about every 15 s (every minute in saving mode), a “stopped” marker, the “all OK” answer, your motorcycle’s fuel range rounded to 10 km (so the crew sees who has the least and the nearest station) and signals (“refuelling”, “10-min stop”, “I have a problem”). Positions travel over a live channel through our server and are not stored — neither by us nor by the members; the phones compute the “falling behind” and “stopped” alerts from them. Without a recorded ride nothing is sent.

Who and for how long: trip data is visible only to crew members; the organiser can remove a member, anyone can leave the crew — they then stop receiving changes and keep what they have as a copy. We keep trip data until the organiser deletes the trip (90-day tombstone as in cloud backup) or the account is deleted; invitations expire after 7 days, inactive crews are cleaned up 180 days after the trip ends. Abuse reports: the “Report” link on the invitation page (e-mail to us).

7. Legal basis and retention

• Requests to the services in section 3 and account handling serve the features you ask for (Art. 6(1)(b) GDPR).
• The AI assistant runs only after you tap “Find” or “Polish”; route ideas can be switched off in Settings → AI assistant (Art. 6(1)(b) GDPR).
• Background location, activity recognition and notification access require your consent in Android, which you can withdraw in the phone settings at any time (Art. 6(1)(a) GDPR).
• Cloud backup (section 6a) is a service you request by enabling Pro and signing in (Art. 6(1)(b) GDPR). It is kept until you delete the item in the app or the account; deleted entries for at most 90 days, files without an entry for at most 30 days.
• Data on the phone is kept until you delete it or uninstall the app. Account data is kept until the account is deleted; we delete it within 30 days of a request. The daily AI request count is deleted after 60 days and stored assistant answers (without the account identifier) after 90 days; the Pro status and the counter are deleted together with the account.
• A trip plan link (section 6b) is a service you request by creating the link (Art. 6(1)(b) GDPR). We keep the snapshot until you turn off the link, delete the trip or your account.
• A trip story (section 6c) is a service you request by creating the story link (Art. 6(1)(b) GDPR). We keep the snapshot and photos until you turn off the link, delete the trip or your account; a photo removed from the story is deleted with the next link update.
• Position for loved ones (section 6d) is a service you request by creating the link or turning on “On every trip stage” (Art. 6(1)(b) GDPR). We keep positions for at most 24 h.
$1
• Crew (section 6f) is a service you request by creating a crew or joining from an invitation (Art. 6(1)(b) GDPR). We keep shared trip data until the trip or the account is deleted; ride positions are not stored at all.
• Providers in section 3 may keep server logs (e.g. IP address) for a short time under their own policies.

Some providers may process data outside the European Economic Area under GDPR transfer mechanisms such as standard contractual clauses.

8. Your rights

You have the right to access, rectify, erase, restrict, port and object to the processing of your data, and to withdraw consent. You can export rides yourself as GPX files. We will provide the cloud backup (section 6a) on request by e-mail. For account matters write to hello@motonomad.app. You may lodge a complaint with the Polish data protection authority (UODO) or your local authority.

9. Children

The app is intended for adult motorcyclists and is not directed at children under 16.

10. Security

Connections to external services are encrypted (HTTPS). Data on the phone is kept in the app's private storage, inaccessible to other apps.

11. Changes

If the app starts processing data differently, we will update this policy and its date, and announce significant changes in the app. Version 5 (28 September 2026) adds the AI assistant — “Route ideas” and “Polish with AI” in notes (Mistral AI via our server), the place package on the phone, and the Pro status and AI counter on the server. Version 6 (28 September 2026) adds “Day post” — a post from the rides, notes and stops of one day, where place names, numbers and the notes of that day go to Mistral AI, never the GPS position or track. Version 7 (29 September 2026): places for “Route ideas” are picked by our own server in Poland from the shape of the planned route instead of a package on the phone and Overpass; the place package leaves the app, and the day post no longer receives passed places from the map. Version 8 (5 October 2026) adds the motorcycle display: a picture sent to the motorcycle display on the local hotspot network, without the internet and without our server, with the QR code from the motorcycle screen and an experimental mode over the motorcycle Wi-Fi, and setting the motorcycle clock over Bluetooth. Version 9 (7 October 2026) adds transcribing voice notes to text: after recording only on the phone, and through the system speech recognition service (usually Google) only when you tap “Transcribe” yourself. Version 10 (10 October 2026) covers the iPhone app: iOS system services, App Store payment, “Sign in with Apple”, iCloud backup and the motorcycle display over the motorcycle’s Wi-Fi with local network permission. Version 11 (21 October 2026) adds cloud backup in Pro after signing in (section 6a): rides with GPS tracks, motorcycles with photos, trips, expenses, refuels, places, notes with recordings, the Home address and recent destinations on our server at Supabase (Ireland), with retention periods for deleted entries and files. Version 12 (22 October 2026): weather from our own server weather.motonomad.app (OVH, Poland) instead of the public Open-Meteo — the same data, requests are not stored. Version 13 (23 October 2026) adds sharing a trip plan by link (section 6b): a plan snapshot without notes, addresses and the area around Home on our server at Supabase, a plan page on motonomad.app that is not indexed, and a link preview image. Version 14 (23 October 2026) adds a trip story by link (section 6c): the ridden track after the privacy cut, approved day posts and day photos without EXIF, added in the evening. Version 15 (23 October 2026) adds position for loved ones (section 6d): your position every minute during a ride under a link, without speed or the area around Home, deleted after 24 h. Version 16 (23 October 2026) adds “Ridden” (section 6e): day tags after a trip from an idea, shown to others in aggregate from 3 rides; collections counted on the phone only. Version 17 (23 October 2026) adds Crew (section 6f): a shared trip for up to 8 people after signing in — the plan, shared expenses and “for the crew” notes on our server for crew members, ride position over a live channel without storage. Version 18 (24 October 2026): the crew ride position also carries the fuel range rounded to 10 km, without storage; the signals are now “refuelling”, “10-min stop” and “I have a problem”.