Last updated: 9 November 2026
Motocamp is an off-grid camping and adventure mapping app. We are committed to protecting your privacy. This policy explains what data the app accesses, how it is used, and your rights. Using Motocamp requires an account: you sign up with your email address and a password. New accounts start a 14-day free trial; your card is taken up front by Stripe and nothing is charged until day 15, and if you cancel before then you pay nothing at all. Your saved data syncs to the cloud so it follows you across your devices.
Motocamp EU is a trip-planning and mapping app for motorcyclists, vans and overlanders in Europe and the UK. This policy explains what personal data we process, why, on what lawful basis, how long we keep it, who else it reaches, and the rights you have over it.
It is written to meet the EU General Data Protection Regulation (GDPR) and the UK GDPR. Where those laws use the word controller (the party that decides why and how your data is processed), that party is us.
You sign up with your email address and a password. Some older accounts sign in with a username instead; those are held as a synthetic internal address and have no real inbox. The following account data is stored on our behalf by Supabase (our authentication and database provider):
If you choose to sign in with Google instead of an email address and password, Google provides us your basic profile identifier for authentication only; we do not receive your Google password.
Payment for a subscription is processed by Stripe (on the web) or the Apple App Store / Google Play (in-app purchase). We store only your subscription status and, for web payments, a Stripe customer reference, never your card details.
We do not sell or share account data with anyone. You can delete your account and all associated cloud data at any time from the app (Account → Permanently delete my account) or by emailing [email protected].
Motocamp EU, operator of motocampeurope.com. For any privacy question, or to exercise any of the rights below, contact [email protected]. We answer data-subject requests within one month, as the GDPR requires. Our full legal and postal details are available on request from the same address.
Deleting your account erases it, along with your saved routes, favourites, home base, preferences and settings. Any Stripe subscription is cancelled first. A subscription billed by Google Play or the App Store has to be cancelled in that store. Any RevenueCat record that links a store purchase to your account is deleted too. If RevenueCat can't be reached at that moment, we keep only the account number it knows you by until it answers, then delete that as well.
We keep one record that a deletion happened. It holds the hour it happened, roughly how long the account had existed (a range such as "8 to 14 days", never an exact date), whether the account was on trial, paid, expired or complimentary, and the reason you picked, if you picked one, along with anything you chose to write in the box. It contains nothing that identifies you: no name, no email address, no username, no account number, no device or location data, and nothing that can be linked back to the account that has been erased. Answering is optional and you can delete your account without answering anything.
We keep it because it is the only way to know that something in the app is driving people away, and to fix it.
The app requests access to your device's GPS location to:
Your live position stays on your device unless a feature needs it to answer you. It leaves your device in these cases:
The app is account-gated and paid, so, unlike a purely local map, we do process personal data. Specifically:
| Data | Why | Lawful basis |
|---|---|---|
| Account: email address, hashed password, account status, recovery code hash, sign-in timestamps, and a name if you sign in with Google | To create your account, sign you in, confirm your sign-up, gate the app, let you reset your password or recover access, and send you service messages about your account and subscription. Some older accounts sign in with a username instead; those are held as a synthetic internal address with no real inbox. You can opt out of non-essential email at any time; we record that choice. | Contract (Art. 6(1)(b)): we cannot give you the service you signed up for without it. |
| Subscription: subscription state, plan, trial and renewal dates, and the customer/subscription identifiers Stripe gives us | To take payment and to know whether your access is active. | Contract (Art. 6(1)(b)); and legal obligation (Art. 6(1)(c)) for tax and accounting records. |
| Payment card details | Handled entirely by Stripe on Stripe's own pages. We never see, receive or store your card number. | Contract (Art. 6(1)(b)), processed by Stripe as its own controller for payment and fraud purposes. |
| Saved routes: the start, end and waypoints of routes you choose to save to your account | So your routes follow you between devices. | Contract (Art. 6(1)(b)). Routes you don't save never leave your device. |
| Where you came from: the campaign name on the link that first brought you to the app (which ad or post it was), when you arrived, and which version of our welcome page you were shown (also noted on your subscription with Stripe) | To tell which of our ads and posts, and which version of our welcome page, bring people who stay, and to stop paying for the ads that do not. | Legitimate interests (Art. 6(1)(f)): knowing which of our own ads and pages work. You may object; see your rights below. |
| Plan with AI: the messages you type into Plan with AI and the answers it gives | To find and fix faults in the planner. Kept for 60 days, then deleted. | Legitimate interests (Art. 6(1)(f)): making the planner work. You may object; see your rights below. |
| Star reviews: the stars and words you post about a place, with your display name | Shown to other campers with your display name. Your review may be shared with the place you reviewed. | Legitimate interests (Art. 6(1)(f)): helping other campers choose a place, and letting the place hear what campers say. You may object; see your rights below. |
| Terms: when you agreed to the Terms, kept with your account | To show you agreed before your first post. | Contract (Art. 6(1)(b)): the Terms are what you agree to when you post. |
| People you've hidden: who you've chosen to hide, kept with your account so it holds on every device. Nobody else can see this list. | To keep that person's posts off your screen. | Contract (Art. 6(1)(b)): you asked for it to be hidden. |
| Server and security logs: IP address, timestamp, request path, user agent, held by our hosting provider | To keep the service up, to block abuse, and to investigate incidents. | Legitimate interests (Art. 6(1)(f)): securing and operating the service. You may object; see your rights below. |
We run no third-party analytics, advertising, or cross-site tracking: no Google Analytics, no Meta pixel, no ad network, and no profiling. We do not sell or share your data with anyone for marketing. We do collect our own usage statistics to understand how the app is used and improve it: app opens, pages viewed, which named buttons are tapped, routes planned, offline map downloads, how long a visit lasts, whether you are on a phone, tablet or desktop, the country your connection comes from, and the site that linked you to us. Each record carries a random install number and, if you're signed in, a scrambled version of your account number, which we can match to your account to help you. It never includes your name, email address, street address, GPS position or route details. Location is recorded as a country only (for example “DE”), worked out at our network edge; we do not store your IP address or anything finer than the country. These records are stored via Cloudflare Analytics Engine and delete themselves within about three months. Our lawful basis is legitimate interests (Art. 6(1)(f)): knowing how the app is used; you may object, see your rights below. You can turn it off entirely by setting motocamp_no_telemetry to 1 in your browser's local storage, or by emailing us.
The app requests your device's GPS location to centre the map, show speed, heading, altitude and lean angle on the ride dashboard, measure distance to campsites and services, and run compass navigation. It may also read motion sensors (accelerometer, gyroscope, compass) for the dashboard.
Motion sensor data stays on your device. Your live position stays on your device unless a feature needs it to answer you. It leaves your device in these cases:
The app only uses your location if you allow it, and it works if you don't: you can deny the permission and use the map by hand. The home base address you choose to save is stored with your account so it follows you across devices (see "Data We Collect").
The app may access device motion sensors (accelerometer, gyroscope, compass) for the ride dashboard's lean angle and heading features. This sensor data is processed on-device only and is not stored or transmitted.
The app only uses your location if you allow it, and it works if you don't: you can deny the permission and use the map by hand.
One consequence worth stating plainly: when a map tile, a weather forecast, a search result or a route is fetched, the request necessarily tells that third-party service roughly where on the map you are looking. That is inherent to an online map. Download an offline area in advance and the map works with no requests at all.
The app stores the following locally on your device using browser storage (localStorage, IndexedDB, Cache API) and one cookie:
The app stores the following locally, using browser storage (localStorage, IndexedDB, Cache API) and one cookie:
You can clear all locally stored data at any time by clearing your browser's site data for this app.
You can erase all of it at any time by clearing this site's data in your browser or device settings.
The app makes requests from your browser to these third-party services:
These are the services the app and its backend actually use. Each of them may see your IP address, and, for the mapping services, the coordinates or search terms you request.
| Service | What it does | What it sees |
|---|---|---|
| Supabase: privacy | Account authentication and database (our processor) | Your email address, hashed password, subscription state, saved routes |
| Stripe: privacy | Subscription payments and billing portal | Your card and billing details, which it holds as its own controller. We receive only the identifiers and subscription status. |
| Cloudflare: privacy | Hosting, CDN and backend functions (our processor) | IP address and request logs |
| Stadia Maps: privacy | Map tiles | IP address, the tiles you request |
| OpenStreetMap / Overpass API: privacy | The underlying map data, and the live POI layers (fuel, water, huts, and the rest) | IP address, the map area you are querying |
| Open-Meteo: terms | Weather forecasts and elevation | The coordinates you ask about, sent through our server |
| RainViewer: privacy | Live rain-radar tiles | IP address, the tiles you request |
| Photon / Nominatim: privacy | Place search (geocoding) | IP address, what you type into the search box |
| BRouter / OSRM | Route calculation | IP address, the start, end and waypoints of a route you plan |
| RevenueCat: privacy | Keeps track of subscriptions bought in the Google Play or App Store app | Your account number and the purchase |
We have no control over how these providers handle data. Where one acts as our processor (Supabase, Cloudflare) it is bound by a data-processing agreement and may only act on our instructions. Where a provider stores data outside the EEA or the UK, that transfer is made under an approved transfer mechanism such as the Standard Contractual Clauses or the UK Addendum.
Deleting your account erases it, along with your saved routes, favourites, home base, preferences and settings. Any Stripe subscription is cancelled first. A subscription billed by Google Play or the App Store has to be cancelled in that store. Any RevenueCat record that links a store purchase to your account is deleted too. If RevenueCat can't be reached at that moment, we keep only the account number it knows you by until it answers, then delete that as well.
We keep one record that a deletion happened. It holds the hour it happened, roughly how long the account had existed (a range such as "8 to 14 days", never an exact date), whether the account was on trial, paid, expired or complimentary, and the reason you picked, if you picked one, along with anything you chose to write in the box. It contains nothing that identifies you: no name, no email address, no username, no account number, no device or location data, and nothing that can be linked back to the account that has been erased. Answering is optional and you can delete your account without answering anything.
We keep it because it is the only way to know that something in the app is driving people away, and to fix it. Our lawful basis is legitimate interest (Article 6(1)(f)): the record identifies nobody, and without it a fault that makes people leave is invisible to us.
These calls go to our own servers first, which then talk to the source and cache the answer so many riders share one upstream request:
/api/weather. Open-Meteo Terms/api/overpass/api/alerts/api/firmsCampground data from Recreation.gov, the Forest Service, BLM and OpenStreetMap, plus the OpenCelliD cell layer, is bundled with the app as static files. The app makes no runtime calls to Recreation.gov or OpenCelliD.
These services may log your IP address and the coordinates/queries you request. We have no control over their data practices. Please review their policies.
The app may also open outbound web links to Booking.com, Google Maps (for directions), and Australian national & state park agency websites for campsite/accommodation details; these open as ordinary web links.
These services may log your IP address and the coordinates/queries you request. We have no control over their data practices. Please review their policies.
Fuel prices: station prices come from our own server, which collects them from government fuel price feeds. Your device asks our server for the prices in the area it shows, never the feeds themselves. Victorian prices: © State of Victoria accessed via the Victorian Government Service Victoria Platform, used under the CC BY 4.0 licence and rounded to the cent. By using them you agree to follow the Service Victoria Terms and Acceptable Use policy and its Privacy Statement. Service Victoria does not endorse Motocamp.
The app may also open outbound web links to the NZ Department of Conservation (doc.govt.nz) and Booking.com for campsite/accommodation details; these open as ordinary web links.
These services may log your IP address and the coordinates/queries you request. We have no control over their data practices. Please review their policies.
Under the GDPR and UK GDPR you have the right to:
To exercise any of these, email [email protected] from the account you want to act on, or include enough detail for us to identify it. We will respond within one month and will not charge you for it.
You also have the right to complain to a supervisory authority: in the EU, the data-protection authority of the country you live or work in; in the UK, the Information Commissioner's Office. We would rather you came to us first, but that right is yours regardless.
We run a Meta Pixel (Facebook's advertising pixel) so we can measure which Facebook and Instagram ads led to a signup. It loads from Meta's servers, may set cookies or identifiers, and sends a page view plus a completed-signup event. We do not send your GPS position, saved routes, or account password. Meta's use of that data is under Meta's Privacy Policy. The same opt-out as our own telemetry turns the pixel off: set motocamp_no_telemetry to 1 in your browser's local storage, or email us.
We do not use Google Analytics or other ad networks. We do collect our own usage statistics to understand how the app is used and improve it: app opens, pages viewed, which named buttons are tapped, routes planned, offline map downloads, how long a visit lasts, whether you are on a phone, tablet or desktop, the country your connection comes from, and the site that linked you to us. Each record carries a random install number and, if you're signed in, a scrambled version of your account number, which we can match to your account to help you. It never includes your name, email address, street address, GPS position or route details. Location is recorded as a country only (for example "US"), worked out at our network edge; we do not store your IP address or anything finer than the country. These records delete themselves within about three months. It is stored via Cloudflare Analytics Engine. You can turn it off the same way as the pixel. If you sign in, Supabase stores an authentication token in your browser solely to keep you signed in.
Traffic to the app is encrypted in transit (HTTPS). Passwords are stored only as hashes. We cannot read yours. Access to the production database is restricted to the operator. If a breach ever puts your rights at risk, we will notify the supervisory authority within 72 hours and tell you directly where the law requires it.
We use no cookies for advertising or cross-site tracking, and no third-party analytics cookies. We set one cookie of our own, and only while we compare versions of our welcome page: the welcome page version, listed under "Data Stored on Your Device" with everything else the app keeps in your browser. Our own usage statistics (described under "Data We Process") use no cookies; you can turn them off with motocamp_no_telemetry.
We do not carry out automated decision-making or profiling that produces legal or similarly significant effects.
So we can see where the app goes wrong and put it right quickly, the Motocamp website and Android app may record a replay of how you use them: the screens you see, where you tap and scroll, and any code that fails. The map is never recorded, because it shows where you are. Anything you type is hidden before it leaves your device, including your email address. If you are signed in, a recording is linked to your account number, never your email, so we can match it to something you tell us about. We make no recordings in Europe, the UK or Switzerland (we judge this from your device's time zone), and none in the iPhone app. Outside Europe, the iPhone app sends us only failure reports (which code failed and where), cleaned the same way. We use PostHog to store recordings and failure reports, on its servers in Frankfurt, Germany. PostHog processes them only for us, never for advertising. Requests go through our own servers, so PostHog does not receive your IP address. Page addresses are cut back to the page itself before anything is sent. PostHog keeps a random visitor number in your browser's local storage, not in a cookie. We keep recordings for 30 days. You can turn recordings and failure reports off by setting motocamp_no_telemetry to 1 in your browser's local storage, or by emailing us.
The app is not directed at children under 13 and does not knowingly collect data from children.
You may request access to, correction of, or deletion of your account data (username, saved routes, favourites, home base, preferences, usage and subscription status) at any time, from the app (Account → Delete account) or by emailing [email protected]. Deletion removes your account and all associated cloud data.
To delete your account and all associated data: open the app, go to Account → Delete account, and confirm. If you signed in with Google or Facebook and cannot reach the app, email [email protected] from the address on the account, or with the name on it, and we will delete it for you. Deletion is permanent and removes your profile, saved routes, favourites, home base and subscription record.
The app is not directed at children under 13 and does not knowingly collect data from children.
Motocamp AUS handles personal information in accordance with the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs). You may request access to, correction of, or deletion of your account data (username, saved routes, favourites, home base, preferences, usage and subscription status) at any time, from the app (Account → Permanently delete my account) or by emailing [email protected]. Deletion removes your account and all associated cloud data. If you are not satisfied with how we handle a privacy concern, you have the right to complain to the Office of the Australian Information Commissioner (oaic.gov.au). Riders in other jurisdictions retain their own rights of access, correction and erasure under the EU/UK GDPR and the California Consumer Privacy Act (CCPA).
The app is not directed at children under 13 and does not knowingly collect data from children.
You may request access to, correction of, or deletion of your account data (username, saved routes, favourites, home base, preferences, usage and subscription status) at any time, from the app (Account → Permanently delete my account) or by emailing [email protected]. Deletion removes your account and all associated cloud data. Under the New Zealand Privacy Act 2020 you also have the right to complain to the Office of the Privacy Commissioner (privacy.org.nz).
The app is not directed at children and we do not knowingly process data from anyone under 16.
We may update this policy from time to time. The "last updated" date at the top will reflect any changes.
We may update this policy. The "last updated" date at the top will change, and we will tell you in the app if the change is material.
For questions about this privacy policy, contact us at: [email protected]
Questions, requests or complaints: [email protected]