For associations
Data processing agreement
Last updated 19 November 2026 · Version 3
Draft. This page is being reviewed and isn't in force yet.
This agreement is part of our terms of service. It covers the personal data your association puts into TrailVector. For that data, your association is the controller: you decide what goes in and why. TrailVector is the processor: we handle it only to run the app for you. It meets the requirements of Article 28 of the UK GDPR.
1. The processing
What we do: host, store, sync, back up and display the records your association keeps in TrailVector, and produce the exports and reports you ask for.
For how long: while the terms of service apply, and until the data is deleted under section 9.
About whom: your trail leads, volunteers, admins and landowners, and people involved in incidents.
What data:
- names typed into records, such as inspectors, dig leaders, first aiders and who looks after a trail
- admins' email addresses
- training records: names, course dates and first-aid certificate expiry dates
- landowner names and phone numbers
- photos, which can show people, and their locations
- locations and GPS tracks recorded on trails
- incident reports, which describe injuries and first aid
Health information. Incident reports can contain health information, which the law treats as special category data. The app asks leads to leave names out of incidents; you agree to tell your leads the same, and to have a lawful basis for any health information you do keep.
The app isn't designed for recording information about children. If your volunteers include under-18s, keep their details out of it.
2. Your instructions
We process the data only on your documented instructions, which are these terms and how you use the app, unless the law requires otherwise; if it does, we'll tell you first unless the law forbids it. We'll tell you if we think an instruction breaks data protection law.
3. Confidentiality
Only people who need to, to run and support the app, can get to your data, and they're bound to keep it confidential. We don't sell your data, use it for advertising, or use it to train AI models.
4. Security
We keep your data secure with measures suited to the risk, including:
- encryption of all traffic (HTTPS)
- a separate database for each association
- an access code for each forest, which your admins can change at any time
- admin sign-in by email through Cloudflare Access
- keeping our own access to the minimum
- exports your admins can take at any time
5. Sub-processors
You agree to us using these sub-processors:
- Cloudflare, Inc.: hosting, the database, photo storage, admin sign-in, answering Ask Vector questions (Workers AI, where the association has it), and request logs (including IP addresses), kept for a few days to find faults and keep the app secure. Its network is worldwide.
- Resend, Inc.: sends the app's emails: alerts to the addresses your admins choose when a lead records an urgent issue or an incident (what was recorded, never anyone's name), and to us the feedback and error reports people send from the app (screenshots stay in the app and aren't emailed).
- Backblaze, Inc. (B2): stores an encrypted copy of the database, records and photos in its EU region (Amsterdam), made every night and kept for 30 days, so it can be restored if something happens to the main one.
- GitHub, Inc.: runs the nightly backup. Each copy passes through its servers for a few minutes, where it's encrypted before it's sent to Backblaze, and isn't kept there.
We'll tell your admins at least 30 days before adding or replacing one, and you can object; if we can't resolve it, you can end the agreement and get a refund for the unused part of your paid period. We hold each sub-processor to data protection terms at least as strong as these, and we remain fully responsible to you for how they handle your data.
Some services are contacted directly by the phone or browser, not by us: map tiles (OpenStreetMap, OpenTopoMap), place search (Nominatim, Overpass) and weather and heights (Open-Meteo). They receive the device's IP address and the places looked at, and the app sends them no other personal data.
6. International transfers
Where data goes outside the UK, including to Cloudflare's, Resend's and GitHub's services in the US, we make sure it's protected as UK law requires, such as through the UK–US data bridge or the UK International Data Transfer Addendum.
7. Helping you
We'll help you answer people's requests to see, correct or delete their data, and with security, breach reporting, data protection impact assessments and any consultation with the Information Commissioner's Office before high-risk processing. If someone asks us directly, we'll pass the request to you. Most requests you can handle from the app: deleting a record, or taking a photo off one, deletes it from our servers too (photos within about a month, to give phones out of signal time to sync); for anything else, ask us.
8. Breaches
If we become aware of a breach affecting your data, we'll tell you without undue delay, and within 48 hours, with what we know and what we're doing, so you can meet your own duty to report it.
9. When the agreement ends
You have 30 days to export your data. After that we delete your association's database, including its photos, within a further 30 days, unless the law requires us to keep it, and confirm when it's done. The encrypted nightly backup copies are kept for 30 days, so the last of them is gone 30 days after that. Data on your leads' phones stays there until they remove the forest from the phone.
10. Information and audits
We'll give you the information you reasonably need to show we meet these terms, and allow reasonable audits, on reasonable notice, at most once a year unless there's been a breach.