Last updated: 31 August 2026
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.
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.
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. |
| 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 anonymous, aggregate 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. This telemetry carries no personal information — no name, no email, no address, no GPS position, no route details; you are counted only as a random, non-identifying token. 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, stored via Cloudflare Analytics Engine. 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.
Your location and sensor data are processed on your device and are never sent to our servers or stored by us. The app works without them: 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, using browser storage (localStorage, IndexedDB, Cache API):
You can erase all of it at any time by clearing this site's data in your browser or device settings.
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 | IP address, the coordinates you ask about |
| 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 |
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 subscription is cancelled first.
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.
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.
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. The only data kept in your browser is what the app needs to work — the items listed under "Data Stored on Your Device" — which is why the app does not ask for cookie consent. Our own anonymous, aggregate usage telemetry (described under "Information We Collect") uses no cookies and carries no personal information; you can disable it with motocamp_no_telemetry.
We do not carry out automated decision-making or profiling that produces legal or similarly significant effects.
The app is not directed at children and we do not knowingly process data from anyone under 16.
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.
Questions, requests or complaints: [email protected]