Skip to content
DustRide

Privacy policy

Last changed: 1 November 2026

DustRide is an app for group motorcycle rides. It shows the route on a map and where everyone in the ride is. This page explains what personal data DustRide processes, why, on what legal basis, who receives it, how long it is kept, and what you can do about it. It covers the Android and iOS apps and this website, app.dustride.pl.

DustRide shows no ads and contains no advertising or analytics tools. It does not track you across other apps or websites, and your data is never sold or shared with anyone for money. To find and fix faults, the apps and this website send crash and error reports to Sentry, as described under "What we process". The one other third-party library that may send diagnostic data is described under "Libraries in the app".

In short

  • You create an account with an email address and a password. You can give the name the group sees you by straight away or later.
  • Your position is seen only by the riders in the ride you join and, from a browser, by that ride's organizers and DustRide's administrator, and only during the ride.
  • We do not store positions, alerts or messages on our servers.
  • You can delete your account in the app at any time; you can ask by email for the rest of your data to be deleted.
  • For anything about your data, write to admin@dustride.pl.

Who is responsible for your data

The controller of your personal data is Adventure Zbigniew Tarnawski (NIP 7681534840, ul. Berberysów 21, 40-750 Katowice) ("we", "us"). For everything on this page, including the rights described under "Your rights", write to admin@dustride.pl. We have not appointed a data protection officer, as the law does not require us to.

What we process, why, on what basis and for how long

The legal bases are those of Article 6(1) GDPR: (b), performance of a contract, meaning providing the service you sign up for; (c), a legal obligation; and (f), our legitimate interest, which we always name.

  • Your account and signing in. Email address, password as an irreversible hash, the name the group sees (if you give one), role, the dates the account was created and last signed in to, sign-in sessions. Basis: (b). Kept: until the account is deleted.
  • Sharing your position in a ride. Precise position, heading, speed, time, the name the group sees, and a random identifier of this installation of the app. Basis: (b). Kept: not stored on our servers.
  • Alerts and messages in a ride. The kind of alert or the message text, name, position and time, installation identifier. Basis: (b). Kept: not stored on our servers; on riders' phones, alerts stay for the next 20 rides.
  • Rides and routes. Code, name, start and expiry times, who created and organizes the ride, the route file (GPX) with its file name, the route's geometry and its waypoint names. Basis: (b). Kept: until the organizer's account is deleted, then as described under "Deleting your account".
  • Your ride history. Which rides were joined, when first and last, and in what role. Basis: (b). Kept: until the account is deleted, then as described under "Deleting your account".
  • Settings that travel with your account. Map and display settings, language, the name the group sees. Basis: (b). Kept: until the account is deleted (the name goes at once, the other settings as described under "Deleting your account").
  • Record of accepting the terms. Account identifier, version of the terms, date, and where they were accepted (the app or this website). Basis: (f), our interest in being able to show what was agreed and in establishing, pursuing and defending claims. Kept: 6 years from the end of the year in which the account was deleted.
  • Showing the map. The IP address of the phone or browser and which part of the map is being fetched. Basis: (b). Kept: not by us; by MapTiler under its own rules.
  • A route shared from Google Maps. The route's points, stop names or addresses, Google place identifiers, vehicle type, the app's identifier, IP address. Basis: (b). Kept: not by us; by Google under its own rules.
  • Signing in on this website. Session identifier, IP address and browser identifier (user agent), time zone and language. Basis: (b), keeping you signed in, and (f), our interest in protecting accounts from unauthorised access. Kept: until you sign out, and at most 30 days without use or 90 days from signing in.
  • Account emails. Email address and content: the code confirming your address, password reset codes, invitations, notices of changes to the terms or this policy. Basis: (b); notices of changes: (c). Kept: our mail provider keeps its sending log for 45 days.
  • Complaints, data requests, content reports and appeals. Email address, content and attachments; for a reported message, also the sender's name and identifier, the ride code and the message itself; our decision. Basis: (c), our obligations under the rules on complaints, the GDPR and the DSA, and (f), our interest in protecting DustRide and its users from abuse and in defending claims. Kept: 6 years from the end of the year in which the matter was closed.
  • Other correspondence (questions, help). Email address, content and attachments. Basis: (f), our interest in answering you. Kept: 24 months from the last message.
  • Server logs. IP address, request and time. Basis: (f), our interest in running the service securely and finding faults. Kept: at most 90 days.
  • Crash and error reports. From the app: what went wrong and where in the code, the app version, the phone's model and system version, the app's state at that moment (free memory and storage, battery level, orientation, language and time zone), the steps leading up to it (the app moving to the foreground or background, screens opened, connectivity and system events, but never the addresses the app fetched), a random identifier of the installation (not of your account), and when app sessions start and end, to count how many end in a crash. From this website: what went wrong and where in the code, and the address of the page requested; passwords, tokens, email addresses and positions are removed. No report contains your position, name, email address or account identifier, and the IP address is not stored. Basis: (f), our interest in finding and fixing faults. Kept: 30 days; Sentry deletes its backups after 90 days.
  • Database backups. The data in the database as it was on the day of the backup. Basis: (f), our interest in being able to restore the service after a failure. Kept: no longer than 90 days.

Below we describe these in more detail.

Your account

To use DustRide, you create an account with an email address and a password. Our sign-in provider stores the password only in a form from which it cannot be recovered; nobody at DustRide can read it. Your role (participant, organizer or administrator) decides whether you can create rides.

The name the group sees. You can give it when you create the account or later in the app's settings; it does not have to be your real name. Other riders, the organizer and the administrator see it next to your position. Until you give one, the app on Android uses the name given to the phone in its settings, and on an iPhone a generic name. This website shows the same name.

Your location

DustRide asks for access to the phone's precise location. It uses it:

  • to show your position on the map and on the loaded route, which happens only on your phone;
  • during a ride, to send your position, heading and speed to the other riders in that ride, so they can see where you are.

Who sees your position. The riders in the same ride, in the app, and organizers who are riders in that ride and DustRide's administrator, who can follow the ride on this website without riding in it. The administrator does so only for support, finding and fixing faults, and running the service.

In the background. During a ride your position is also sent while the app is in the background or the screen is off, because that is how a phone is used on a motorcycle. On Android a persistent notification shows while this happens, from which you can leave the ride; on iOS the system shows its location indicator. Leaving the ride or signing out stops the sharing. DustRide never asks for "Allow all the time" location access on Android or "Always" on iOS. Outside a ride your position does not leave your phone.

How often, and what exactly. The phone sends your position after moving about 10 metres, no more often than every 2 seconds (every 5 seconds in battery saver mode), and about every 20 seconds while stopped. Sent with the position: the name the group sees, the time and a random identifier of this installation of the app (not your account identifier).

Not stored. Positions are passed to the other riders live through our real-time service and are not stored on our servers. Other riders' phones keep your last position only in memory, until the ride ends.

Alerts and messages

Alerts (for example about a breakdown, a fall or running out of fuel) and short messages reach the other riders in the ride live, or only its organizers if you choose so, together with your name and position at that moment. They are not stored on our servers.

  • Choosing "organizer only" sends an alert or a message only to the phones of the ride's organizers and, on this website, to its organizers and the administrator; our server does not let other riders receive it. If no organizer is in the ride, or you are the organizer, it goes to everyone. If the organizers' phones have an older version of the app, it reaches every phone in the ride as before, and only the organizers' phones show it.
  • The app stores alerts with a position on riders' phones as points on the map (name, kind, place, time) and keeps them for the next 20 rides. Messages disappear when you leave the ride.
  • The app automatically masks the worst swear words in messages, using a fixed list of words. This happens on the phone; it is not a decision about you or your account.
  • You can block whoever sent a message. The list of blocked riders is stored only on your phone.

Rides and routes

When an organizer creates a ride, we store its code, name, start and expiry times, who created and organizes it, and the route file (GPX) the organizer uploads and the riders' phones download. The file is stored and passed on unchanged, with what it contains: its file name, waypoint names and sometimes its author and timestamps from the device that recorded it. From the file we also store the route's geometry and waypoint names, to show them on this website.

When you join a ride, we record that you did, and when you first and last joined, so that your list of rides travels with your account to another phone. Membership also decides who can reach the ride, its route and the riders' positions.

The map

The map is fetched from MapTiler. Like any request on the internet, this gives MapTiler the IP address of the phone or browser and which part of the map is being fetched. The app fetches the map along the ride's route in advance, so that it works without signal too. The app never sends your position itself to MapTiler.

Routes shared from Google Maps

An organizer can share a route from Google Maps into DustRide. The app then connects directly to Google: it opens the shared link and sends the route's points (coordinates, place identifiers, or stop names and addresses), the vehicle type and the app's identifier to the Google Routes service, to work out the way between the points. Google also receives the phone's IP address. Nothing is sent to Google unless you share a route this way. Google (Google Ireland Limited) processes this data as a separate controller; see Google's privacy policy.

This website

Organizers and the administrator sign in on this website. It stores in your browser:

  • A session cookie (for every visitor): protects forms and remembers where to return after signing in; until the browser is closed.
  • A sign-in cookie (once signed in): keeps you signed in; until you sign out, and at most 30 days without use or 90 days from signing in.
  • An entry in the browser's storage on the live ride page: a random identifier of the browser in the ride; until you clear the site's data. The key that connects the page to the ride, valid for 10 minutes and for that one ride only, is kept only in the page's memory and never stored.

All of them are needed for the website to work and none is used for tracking, so we do not ask for consent to them. The public pages (terms, privacy policy, help, sign-in) load nothing from other services. Pages with a map fetch it from MapTiler.

For each sign-in we keep a session with the browser's IP address and its identifier (user agent). The session is deleted when you sign out, change your password or delete your account, and expires after 30 days without use and at the latest 90 days after signing in. For each account we also keep the website's time zone and language.

Emails

We send emails only about accounts: codes confirming your address and resetting your password, invitations from the administrator to organizers, and notices of changes to the terms or this policy. We send no marketing.

Writing to us

When you write to us (with a question, a complaint, a request about your data or account, or a content report), we process your email address, the message and any attachments to deal with it. A message report, which the app can prepare for you, also contains the name and identifier of the rider who sent the message, the ride code and the message itself. We use them only to deal with the report.

On your phone

The app stores on the phone: your sign-in session, settings, recent rides, the loaded route, the trail of your ride, distances ridden, alerts from the last 20 rides, the list of riders you have blocked, a random installation identifier and the map downloaded for use without signal. None of this is sent to our servers beyond what is described above.

  • Signing out and deleting your account remove your session, the list of recent rides and your account settings from the phone. The rest stays on the phone until the app is uninstalled.
  • On Android the app's data is left out of backups and of transfers to a new phone. On iOS it may be included in your device's backup (iCloud or a computer), which you control.
  • Uninstalling the app removes all of it.

The camera is used only to read a ride's QR code. The image is read on the phone and is never stored or sent anywhere. On Android a notification shows that the ride is sharing your location; an alert from another rider makes the phone vibrate and sound.

Libraries in the app

On Android, QR codes are read by Google's ML Kit library. The camera image is analysed only on the phone. The library itself may send Google diagnostic data about how it works (device and app information, performance metrics and error codes), as described in Google's information about the data ML Kit collects. This does not include the camera image, your position or your account data.

Do you have to give us your data?

An email address and a password are needed to make the agreement and create an account; without them DustRide cannot be used. The name the group sees is optional and does not have to be your real name. Location access is needed for the app to show where you are and share it with the group; without it the app only partly works. Camera access is needed only to read a ride's QR code.

Where your data comes from

Almost all of it comes from you or arises as you use DustRide. The exception: if a DustRide's administrator invited you to be an organizer, we received your email address from them.

Automated decisions

We do not take automated decisions about you and do not profile you. What an account can do depends on the role the administrator gives it. Masking swear words in messages works from a fixed list of words and is not a decision about anyone.

Who receives your data

  • The other riders in the same ride see your name, your live position and the alerts and messages you send to everyone.
  • Organizers. An organizer who is a rider in a ride can follow it on this website, seeing the names, positions, alerts and messages of every rider in it. Organizers who use DustRide in their business (a riding school, for example) are separate controllers of the data they see, and are themselves responsible for their customers' data kept outside DustRide.
  • DustRide's administrator, that is us, through a single administrator account, sees the email addresses, names, roles, sign-up dates and ride counts of all accounts, the list of all rides with their routes, and any ride live. We can invite accounts, change their details and roles, and delete them. We have no access to passwords. We use this access only for support, finding and fixing faults, and running the service; the basis is (f), our interest in helping users and keeping DustRide working.
  • Service providers who process data on our behalf, under data processing agreements:
    • Codelens Paweł Krysiak (Poland): builds and runs the apps, this website and their infrastructure; Poland. It engages the providers listed below, other than cyber_Folks, as its sub-processors, with our consent.
    • Supabase Pte. Ltd. (Singapore), with support from Supabase, Inc. (USA): database, sign-in, route file storage and live relay. The database and files are stored in Frankfurt (Germany). The live relay runs on Supabase's worldwide network: positions, alerts and messages normally pass through the servers nearest the riders, and what a rider's phone shares about them in the ride (name, the current alert and the latest message) is copied, in memory only, to its servers in other countries too.
    • DigitalOcean, LLC (USA): this website's server and its logs; Frankfurt (Germany).
    • AC PM, LLC (Postmark, an ActiveCampaign company, USA): sending emails; USA.
    • Functional Software, Inc. (Sentry, USA): crash and error reports from the apps and this website; Frankfurt (Germany), in Sentry's EU data region.
    • cyber_Folks S.A. (Poland): our mailbox and domain; European Union.
    • OVH Sp. z o.o. (Poland): the former address admin@trailbee.app, where reports from versions of the app released under the name TrailBee still arrive; European Union.
  • MapTiler AG (Switzerland) provides the map, and also processes IP addresses and requests under its own rules.
  • Google Ireland Limited works out the way for routes shared from Google Maps and, on Android, provides the ML Kit library; it processes that data as a separate controller.
  • Public authorities, when the law requires it.

App stores (Google Play, the App Store) know that the app was downloaded and process that under their own rules; we pass them no data from DustRide.

Transfers outside the European Economic Area

Some of our providers process data outside the European Economic Area.

  • Supabase contracts through its company in Singapore, and its US company Supabase, Inc. provides support, so data stored in Frankfurt may be accessed from Singapore, the US and other countries where its support staff work, and live data passes through its servers in other countries as described above. These transfers rely on the standard contractual clauses adopted by the European Commission (Implementing Decision (EU) 2021/914), which are part of the agreement with Supabase.
  • DigitalOcean may access this website's data from the US, and Postmark processes the email address and the message being sent on servers in the US. Both are certified under the EU-US Data Privacy Framework (DigitalOcean, LLC, and ActiveCampaign, LLC, whose certification covers AC PM, LLC), so these transfers rely on Commission Implementing Decision (EU) 2023/1795. Their agreements also contain the standard contractual clauses.
  • Sentry keeps crash and error reports in Frankfurt, but Functional Software, Inc. may access them from the US. It is certified under the EU-US Data Privacy Framework, so this transfer relies on Commission Implementing Decision (EU) 2023/1795; the agreement with Sentry also contains the standard contractual clauses, which apply if the Framework no longer does.
  • MapTiler is based in Switzerland, which the European Commission has found to provide an adequate level of protection (Decision 2000/518/EC).
  • Google Ireland Limited receives the data for routes shared from Google Maps and ML Kit's diagnostic data as a separate controller, under Google's own privacy policy.

You can get a copy of the clauses as they apply to us by writing to admin@dustride.pl. Certifications can be checked at dataprivacyframework.gov.

How long we keep data

The list under "What we process" gives the period for each kind of data. In short: we keep account data until the account is deleted, we do not store positions, alerts or messages at all, and what remains after an account is deleted, the record of accepting the terms and formal matters are kept for at most 6 years.

Deleting your account

In the app, open the menu, choose "Your account" and tap "Delete my account". The first tap asks you to confirm; the second deletes the account. Without the app: see app.dustride.pl/delete-account. When the account is deleted:

  • straight away we delete your email address, name, password, sign-in sessions and the name the group sees; the account can no longer be used, and the rides you created disappear for every rider in them;
  • the rest of the account's data (settings other than the name, your ride history, and the rides you created with their names and route files, hidden from everyone) is kept pseudonymised: without your email address or name, but tied to a single internal identifier. We treat it as your personal data. You can have it deleted at any time by writing to admin@dustride.pl from the address the account used; we delete it within a month. Without a request, we delete it at the latest 6 years after the end of the year in which the account was deleted; then only the code of each ride you created remains, with no link to you, so that it is never reused. We keep it so that ride codes are never repeated, other riders' data stays consistent and reports of abuse can still be dealt with (point (f));
  • for 6 years from the end of the year in which the account was deleted, we keep the record of which version of the terms was accepted and when, to be able to show what was agreed in case of a dispute;
  • database backups expire within 90 days, and the email sending log after 45 days;
  • correspondence with us is kept for the periods given above.

What other riders have on their phones (alerts with your name from recent rides) disappears for them after the next 20 rides or when they uninstall the app. You can later create a new account with the same email address.

Your rights

Under the GDPR you have the right to:

  • access your data and get a copy of it;
  • rectify it: change the name the group sees in the app's settings and your password on the sign-in screen, and write to us about anything else;
  • erase it: by deleting your account or by writing to us;
  • restrict its processing;
  • port the data you gave us: we send it in a commonly used, machine-readable format (JSON).

Write to admin@dustride.pl from the address your account uses. If you write from another address, we will ask you to confirm from the account's address. We answer without undue delay and within a month at the latest. If your account has been deleted, give your former email address and roughly when it was deleted, so that we can find what we still hold. We do not process your data on the basis of consent.

Your right to object

Where we process your data on the basis of our legitimate interest (server logs, error reports, backups, the record of accepting the terms, data kept after an account is deleted, correspondence, session security, the administrator's access), you may object at any time, on grounds relating to your particular situation, by writing to admin@dustride.pl. We will then stop processing that data unless we can show compelling legitimate grounds that override your interests, rights and freedoms, or that we need it to establish, pursue or defend legal claims.

Complaining to a supervisory authority

You can lodge a complaint with the President of the Personal Data Protection Office (UODO, ul. Stanisława Moniuszki 1A, 00-014 Warsaw, Poland, uodo.gov.pl) or with the supervisory authority of the EU country where you live, work or where the infringement took place.

Age

DustRide may be used only by adults. We do not knowingly create accounts for people under 18; if we learn of such an account, we will delete it.

Security

  • Everything the apps, this website and our servers send is encrypted in transit (HTTPS).
  • A ride, its route and its riders' positions can be reached only by signed-in riders in that ride and, through the live page, by organizers who are riders in it and by the administrator; the live page gets a key from our server that is valid for 10 minutes and for that one ride only. Settings, history and the record of accepting the terms can be reached only by the account's owner.
  • Passwords are stored only as irreversible hashes.
  • Administrative access is ours alone, through a single account.
  • No system is completely secure. If a personal data breach is likely to put you at high risk, we will tell you.

Earlier versions of the app

Versions of the app before 1.1 had no accounts. Each installation signed in with a random identifier containing no email address, password or name. Those versions no longer work. The identifiers from those versions and the rides and routes created with them cannot be reached by anyone but us; we will delete them by the end of 2032 at the latest.

Changes to this policy

When the way DustRide processes personal data changes, we will update this page and the date at the top, and tell account holders about significant changes by email before they take effect. Earlier versions are available on request.