Privacy

A saved running route usually starts at your front door. That single fact shapes everything on this page, and it's why routes are treated as sensitive data rather than content.

What's stored

What	Why
Your username and a hashed password	To sign you in. Passwords are stored as bcrypt hashes and can't be read back, by us or anyone else.
Your email address, if you gave one	To verify it's really you and to send a password-reset link if you ever need one. It is never used to sign you in.
Your saved routes — names, descriptions, the coordinates, your hazard ratings and markers	So they're there next time. This is the sensitive one, and it's kept private to your account.
Places you keep in My places — a name and a position for each	So the loop generator can pass them again. Like routes, they're private to your account, never shared, and deleted with it.
Areas you paint in the loop generator — the parts of town you like, and any you mark to avoid	So your loops can go through them, or round them. Like routes, they're private to your account, never shared, and deleted with it.
Feedback you send, with the page you sent it from and your email if you chose to give one	So we can act on it, and reply if you asked us to.
A record of the emails we send you — the address, the subject, and whether it arrived	So a verification or reset link that silently fails to arrive can be found and fixed instead of leaving you stuck. The message itself is kept for 30 days and then deleted, because it contains a one-time link; the rest of the record has no such thing in it and is kept. We do not use open or click tracking, so there is no record of whether you opened anything.
Ordinary server logs	Kept briefly for security and debugging, then rotated away.

What isn't stored

• Nothing about shade. Canopy figures are recomputed each time you open a route, not saved onto it. That's mainly so old routes pick up better data, but it also means your route file is coordinates and your own notes, nothing more.
• No payment details. There's no checkout, so there's nothing to store.
• Not your location. If you let your browser share it, the map shows where you are as a dot and keeps it up to date while the page is open, and “Use my location” in the loop generator can start a loop there. Your location stays in your browser: it is never sent to us or saved with your routes.
• No advertising identifiers, no third-party analytics, no tracking pixels.

Who else is involved

Drawing a route means asking a few outside services for map data. They see the coordinates involved in the request — that's unavoidable for anything that draws a map — but they don't get your account, your name, or your saved routes. Separately, if you give us an email address, our email provider sees it and the message we send — nothing else about your account.

• Map tiles, search and routing — to draw the map, find the places you search for or pick, and follow the road network between your points.
• Elevation lookups — to build the climb profile, requested by our server rather than your browser. For England and everywhere outside the US it fetches whole map squares, so the source never sees your route; for a route in the US, the U.S. Geological Survey is sent the points along it, without your account or IP address.
• Canopy, crossing and sidewalk data — public datasets, requested by our server rather than your browser, and cached so the same area isn't fetched twice.
• Wind forecasts — when Wind is switched on, or when you generate a loop. Requested by our server rather than your browser, from MET Norway, which is sent only the centre of each roughly 5 km square your route touches: never the route itself, your account or your IP address.
• Email delivery — only if you gave us an address, and only to send you a verification or password-reset link.

Cookies

One session cookie, so the site knows you're signed in. It isn't used for tracking and there's nothing to consent to beyond it. Signing out clears it.

Your choices

• Delete any route at any time from the route library, and it's gone from the database.
• Delete your own account any time from your account page, which removes everything attached to it — or ask us to.
• Choose who can see a route from the route library — private to you, a link only someone you send it to can open, or public in the gallery, with the option to mask your starting point so the line's shape is visible without showing exactly where it begins. Switch back to private any time — the old link and gallery listing stop working the moment you do.
• Ask for a copy of what's stored about you. Routes export as GPX from the app already; for the rest, just ask.

Changes

If this page changes in a way that affects what's collected or who sees it, that'll be said plainly rather than slipped into a revision date.

Who to ask

RunMapApp is run by Drew Pearson. Any question about what is stored about you, a request for a copy of it, or a request to delete it, goes through the contact form and reaches a person rather than a queue.