Privacy
No accounts, no adverts, no tracking profiles. Here is the small list of what the beta handles.
Who is responsible for your data
GravelRights is operated by Hedley Stirk, trading as GravelRights (sole trader). Postal contact: 34 Rayner Drive, Brighouse, HD6 2DG. [email protected].
Privacy enquiries: [email protected].
What we store
- Issue reports you send us — the category, your message, and only the technical context you attach: map coordinate, corridor reference, release version, and ride setup where relevant. No accounts, no names, no device identifiers.
- Postcode searches — forwarded one-way to a lookup provider to turn a postcode into coordinates; we do not build profiles from them.
- Technical faults — an error category, a one-way hash of its message, the map release if known, and a broad page category. The message itself, stack trace, page URL, search text, ride stops, IP address and browser details are not included. These limited records help us spot broken features; they do not identify a device.
What we do not store
- Your IP address is used transiently to rate-limit abuse and is never written into feedback records.
- GravelRights does not add browser or device fingerprints to reports.
Why we use it
We rely on legitimate interests to investigate problem reports and technical faults, provide the postcode lookup you requested and protect the service against abuse. We aim to collect only what those tasks require. Please do not put personal or sensitive details in a report. Named place searches use the local place list; postcode searches are sent through our service to postcodes.io.
Service providers
Cloudflare hosts the website, protects connections and stores private feedback and limited fault records in D1. Cloudflare processes connection information such as IP addresses under its own service terms. Postcodes.io receives the postcode you search for. We do not sell reports or publish them as community comments.
Cloudflare may process information outside the UK. Its data processing agreement describes its international transfer safeguards. We review the applicable hosting and transfer arrangements before public launch.
The riding map uses Mapbox for its background map. Your browser connects directly to Mapbox for map tiles, labels and the usage requests needed to operate the map. Mapbox receives connection information, including your IP address, the map area requested and limited browser/session information under its product privacy policy. Mapbox may process this information outside the UK. We disable optional map performance reporting; our route calculations remain in your browser and do not use Mapbox's Directions API.
Browser preferences and cookies
Your last map view is saved in your own browser so you can return to it. You can remove it by clearing site storage. We do not use advertising cookies or tracking profiles. Planned rides remain in your browser unless you share a link; anyone you share it with can see the stops in that link. GravelRights analytics are not enabled; Mapbox handles its own essential map usage records as described above.
How long reports are kept
Issue reports are working data for fixing the map. They are kept for 12 calendar months, then automatically deleted by the next hourly maintenance run (normally within one hour). You can ask for earlier deletion of anything you submitted via the contact page.
Technical fault records are removed after 30 days during hourly maintenance. Temporary service-wide abuse counters expire after their minute or day window; they contain no rider identifiers.
What we do not do
- No accounts and no passwords to lose.
- No advertising and no sale of data.
- Your planned rides stay in your browser unless you choose to share a link.
Contact
Questions about your data: use the contact page.
Your rights
You can ask for access to personal information we hold about you, correction, deletion or restriction, and object to processing based on legitimate interests. These rights depend on the circumstances; we normally respond within one month. Include the report reference if you have one so we can locate a report without collecting extra identifying information.
You can also complain to the Information Commissioner's Office, the UK data protection regulator.