In the app
App privacy notice
Last updated 19 November 2026 · Version 3
Draft. This page is being reviewed and isn't in force yet.
This notice is for everyone who uses the TrailVector app: trail leads, volunteers and association admins. For the website, see privacy and legal.
Who's responsible
Your association decides what's kept in its TrailVector and why, so it's responsible for your information there. TrailVector runs the app for your association, under a data processing agreement. For the few things we use for ourselves, we're responsible: feedback you send us, error reports, the log of requests to the app, and what each phone tells us about itself.
What the app holds
No accounts for trail leads. You open a forest with its access code. The app doesn't ask for your name or email address.
What you type in. Records can include names, such as who inspected a trail, who led a dig or who's first aider. Incident reports describe what happened and any injury and first aid; please leave out people's names and health details that aren't needed.
Photos and places. Photos are kept with where they were taken. The app uses your phone's location only when you ask it to, such as to mark a spot or to record a walk along a proposed trail, which saves the track. It never tracks you in the background.
Admins. Admins sign in with their email address, and the app records which admin added some things, such as key dates.
Training records. Admins can keep the dates of dig-leader courses and when first-aid certificates expire.
Feedback. If you send feedback, it includes your message, the page you were on, your browser and app version, and a screenshot if you choose to attach one. It goes to TrailVector, by email, to help us fix and improve the app.
Error reports. If something goes wrong in the app, it tells us by itself: the error, the screen it happened on, the app version and your browser, and the forest it was connected to. Never anything anyone typed.
Your phone. Each phone that syncs sends a random id it made for itself (not your name or number), its system and model, whether the app is installed, and how much it still has to send. Your association's admins see this, so a phone whose work hasn't arrived can be noticed before it's lost.
Why we use it
For your association's records, your association decides why and on what lawful basis. For the things we're responsible for, our lawful basis is our legitimate interests: keeping the app working, secure and getting better, and replying to feedback. We use them for nothing else. No decisions about you are made automatically: Ask Vector answers questions about the app, and decides nothing about anyone.
On your phone
So it works with no signal, the app keeps your forest's records, photos, drafts and the access code on your phone, and syncs them when there's a connection. Remove from this phone clears them. The app sets no cookies of its own; admins' sign-in uses one from Cloudflare.
Who else sees it
- Cloudflare hosts the app and its data for us, and keeps a log of requests to it (including your phone's IP address) for a few days, to find faults and keep it secure. If your association has Ask Vector, the questions typed into it are answered by Cloudflare's Workers AI; we don't keep the questions or answers, only how many each forest asked.
- Resend sends the app's emails: feedback you send us (without its screenshot), and, if your association's admins choose, an alert when an urgent issue or an incident is recorded, saying what was recorded but never who.
- Backblaze keeps an encrypted copy of the records and photos, made every night by a job that runs on GitHub, for 30 days, so they can be restored if something goes wrong.
- Map, place-search and weather services (OpenStreetMap, OpenTopoMap, Nominatim, Overpass, Open-Meteo) are contacted directly by your phone. They get its IP address and the places you look at, and nothing else.
- Calendars: if your association subscribes to its dig calendar, the calendar service (such as Google, Apple or Outlook) receives dig dates, places and meeting points.
Nobody gets your information for advertising, and we don't sell it.
Outside the UK. Cloudflare, Resend and GitHub are US companies, and Cloudflare's network is worldwide. Where your information goes outside the UK, it's protected as UK law requires, through the UK–US data bridge or the UK's International Data Transfer Addendum. Backblaze keeps the backup copies in its EU region.
How long it's kept
Your association decides how long to keep its records, and can delete them. Deleting a record, or taking a photo off one, deletes it from TrailVector's servers too; photos go within about a month, to give phones out of signal time to sync. When an association stops using TrailVector, we delete its data as the data processing agreement says.
What we're responsible for, we keep only as long as we need it:
- Feedback: deleted a year after it arrives, sooner if it's dealt with.
- Error reports: deleted when the error is fixed, or a year after it last happened.
- Request logs: a few days.
- Phone details: deleted 180 days after the phone last synced.
Your rights
You can ask to see the information about you, to have it corrected or deleted, to have its use restricted, to object to how it's used, and to get a copy to take elsewhere. Ask your association first, as it's responsible for its records; we'll help it. For feedback, error reports and the other things we're responsible for, email ppa.rotcevliart@olleh. If you're unhappy with how your information has been handled, you can complain to the Information Commissioner's Office (ico.org.uk, 0303 123 1113).