Privacy notice
What the app and this website do with information about you, and why. In short: as much as possible stays on your phone, nothing is sold or used for adverts, and you can see, take or delete what I hold.
The short version
- Maps, routing, place search, plate covering and insurance-certificate reading happen on your phone.
- The server I run holds your account, your friends and groups, what you choose to share, and the records the shared features need.
- Your position leaves the phone only when you use a feature that needs it: a Convoy or Meet-up you've joined, a shared car, a sign-in to the log, the weather on a route, or a report.
- No adverts, no analytics, no trackers, no selling. This website sets no cookies.
- Who's responsible
- What stays on your phone
- What the server holds, and why
- This website
- Other services the app uses
- Who else sees your data
- How long it's kept
- Your rights
- Keeping it safe
- Changes
1. Who's responsible
The data controller is Alex, the individual who makes The Scenic Route. Contact: . My full name and a postal address are available on request. There's no data protection officer: it's me.
This notice covers the app, the server it connects to, and this website. It's written for the beta, which is private and limited to my friends and family.
2. What stays on your phone
These are worked out on your phone and never sent to me:
- maps, routing, place search, Preview, Roundtrip planning and the speed-limit, camera, blackspot and sign warnings;
- your drives as you drive them. Recordings are saved on the phone until you share them;
- finding and covering number plates in photos, and reading insurance certificates (the certificate never leaves the phone);
- your driver profile for cover checks (age, years licensed, points, clubs);
- contacts you look up to fill in a car owner's name. The app reads your contacts only when you tap that search, and only after you've allowed it;
- notes on your reviews, your places that you haven't shared, your settings;
- crash reports, unless you choose to send one.
All of this is deleted if you uninstall the app. Export it first if you want to keep it.
3. What the server holds, and why
The app's server runs on hardware I own and manage. The UK GDPR lets me use your data only with a lawful reason. For each kind of data, the reason is given below.
| What | What for | Lawful reason |
|---|---|---|
| Your account: name, email address (and a one-way hash of it), password hash, @username, profile picture and public note, the invite code you joined with | Signing you in, letting friends find you, sending sign-in codes | Needed to provide the app to you (contract) |
| Sign-in records: time, IP address and device name for each sign-in and sign-out | Spotting and stopping misuse of your account | Legitimate interests (security) |
| Friends, groups and cohort membership, with join dates | Groups, chats, sharing and members-only packs | Contract |
| Messages, photos, videos and files in chats | Delivering them. They're end-to-end encrypted, so the server stores them in a form it can't read in normal use (see section 9) | Contract |
| Live position, name and voice in a Convoy, Meet-up or radio channel | Showing the group where everyone is, and relaying push to talk. Positions are passed on live and not kept after the session. Voice is never recorded. | Contract |
| Driver log receipts: when each driving stint started and ended, the car's registration, the driver's name as you entered it, the place, and the distance | A server-stamped record of who was driving, for you to rely on later | Contract. For other drivers you name: legitimate interests (yours and theirs, in an accurate record) |
| Shared cars: the car's details, photos, crib sheet, gripes and conditions; drivers' requests and approvals; agreements to conditions; damage and fault reports with photos; and each drive made in the car (times, start and end, distance and the GPS track) | Lending and borrowing cars, and giving the owner a copy of each drive, as the driver is told before agreeing | Contract |
| Route ratings (one per route per account), and route problem reports | Showing what drivers think of a route, and fixing bad routes | Contract / legitimate interests (improving the app) |
| Route packs you register: an ID, its name, you as owner, and who else may edit or share it | Enforcing who can edit or pass on a pack | Contract |
| Vehicle registrations you look up | Fetching make, model, tax and MOT from DVLA and DVSA. Answers are cached for up to 12 hours. | Contract |
| Beta status: your access and end date | Ending the beta, or one tester's access, reliably | Contract |
I don't use your data for profiling or for any automated decision that affects you, and I never sell it or use it for advertising.
4. Feedback, surveys and this website
- Joining: the beta is by private invitation. This website doesn't collect applications.
- Feedback, sent from the app or from this website: your report, any screenshots or logs you attach, and optionally your phone model and app build. It's stored on the app's server and linked to your account, so I know which tester sent it and can follow up if you've said I can. On the website, the 6-digit code from the app is what links it, so you don't give your name or email there. I use it only to fix and improve the app. Lawful reason: legitimate interests (improving the app), and our beta agreement. An app log can hold technical details of what the app was doing, such as places it was routing to. Look through a screenshot or log before you send it.
- Feedback codes: each lasts an hour and is then deleted. To stop codes being guessed, the server counts wrong codes by IP address for an hour, in memory only.
- Surveys: none yet. Each survey will say what it asks and why before you answer.
- The site sets no cookies, runs no analytics and loads nothing that tracks you. Fonts come from Google Fonts, which receives your IP address in order to send them.
5. Other services the app uses
A few things can't be done on the phone, so the app or server uses outside services. Each gets only what it needs:
| Service | What it gets | Where |
|---|---|---|
| Cloudflare: hosts this website and carries the app's and this website's connections to the server | Your IP address and the traffic passing through it, encrypted on the way. Nothing from the website's forms is stored there. | Global network, US company |
| Resend: sends sign-in and account emails | Your email address and the email's content | US |
| Open-Meteo: weather forecasts | The places and times along your route (not who you are) | Switzerland |
| openrouteservice: online routing, used only if the offline routing data isn't installed | The start, end and via points of that route | Germany |
| GitHub: where the maps and data packs are downloaded from | Your IP address when you download a pack | US |
| DVLA and DVSA: vehicle, tax and MOT details | The registration you looked up, sent by my server, not your phone | UK |
Where data goes outside the UK, it goes to countries the UK treats as having adequate protection, or under the UK's approved safeguards: the UK Extension to the EU–US Data Privacy Framework, or the UK's International Data Transfer Addendum.
6. Who else sees your data
- People you choose: the friends, groups and session members you share routes, places, messages, photos or your position with, and car owners whose cars you drive.
- Other app users can see your @username, profile picture and public note, and can find you by @username to send a friend request.
- Nobody else, unless the law requires it, for example a valid request from the police or a court. I'd tell you unless the law forbids it.
7. How long it's kept
- Your account and everything on the server linked to it: until you delete your account. When the beta ends, beta accounts and their server data are deleted within 90 days, unless you've asked to move your account to the release version.
- Deleting your account (Settings › Account & data) removes your account and its server data straight away. Server backups are replaced on a rolling basis, and deleted data drops out of them within 90 days. Two exceptions: what you've already sent to other people (messages, shared routes and places, copies of drives in a friend's car) stays with them, and if your account was banned, a one-way hash of your email is kept to stop a new account being made with it.
- Sign-in records: 12 months.
- Feedback and its attachments: until 12 months after the beta ends, or until you delete your account if that's sooner.
- Convoy and Meet-up positions: not kept after the session. Voice: never recorded.
- Vehicle lookups: cached for up to 12 hours.
8. Your rights
You can ask to:
- get a copy of the data I hold about you (much of it is also in Export everything in the app);
- have something corrected;
- have your data deleted (or do it yourself in the app);
- restrict how I use it, or object to my using it for legitimate interests;
- receive it in a format you can take elsewhere.
Email . I'll reply within one month and won't charge you. If you're not happy with how I've handled your data, please tell me. You also have the right to complain to the Information Commissioner's Office: ico.org.uk/make-a-complaint, 0303 123 1113.
9. Keeping it safe
- Everything between the app and the server is encrypted in transit (TLS). Passwords are stored as strong one-way hashes (Argon2). Sign-in tokens are stored hashed. The server's disks are encrypted.
- Chats are end-to-end encrypted, so the server stores messages it can't read. One thing to be aware of: your messaging account's sign-in is managed by my server, so in principle the server could sign a new device into it. I don't do that. A new device can't read your earlier messages without your message backup key.
- Convoy, Meet-up and push-to-talk are encrypted on the way to and from the server, but they aren't end-to-end encrypted. The server relays them live and doesn't keep them.
- No system is perfectly secure. If I learn of a breach that puts you at risk, I'll tell you promptly, and the ICO where the law requires it.
10. Changes
If this notice changes in a way that matters, I'll tell you in the app and by email before the change takes effect. The version and date are at the top of the page.