Privacy policy
Last updated November 19, 2026
RunnerOutpost gives a running group one private map for its runs. This page explains what personal data we handle, why, who else handles it, and what you can do about it. Questions: contact@runneroutpost.com.
Who we are
RunnerOutpost (runneroutpost.com) is the service described on this page, and we are responsible for the personal data it handles. You can reach us at contact@runneroutpost.com. The operator's legal name and address are given in the terms of use on our parent site, TrailStation.
What we collect
It depends on how you use RunnerOutpost.
- Everyone who signs in (owners and members, free or Pro): your email address, used to sign you in with a link, with no password. We also keep an identifier for your account, which we store only as a hash.
- Members of a group: the first name and colour you choose, which groups you are in, and which runs you said you are coming to.
- People who post a run: the title, time, pace, effort and note, a meeting point rounded to about 25 m, and a route with its time and elevation removed.
- If you set a Home pin: that one point, visible only to you. It is used only to show other people an area instead of the exact spot for runs that start within 500 m of it. You can move or remove it at any time.
- Owners who pay for Pro: the plan, its status and its dates, and the payment provider's references. We never see a card number.
- Anyone opening the app or the website: your IP address reaches our servers and our service providers, as with any web request. We never write invite tokens, session tokens or email addresses to logs.
- Visitors to our landing page (runneroutpost.com and nothing else) and to our blog (blog.runneroutpost.com): our own Matomo server counts visits without cookies and with your IP address shortened.
- Email list subscribers: your email address, after you confirm.
We do not collect your live location, your contacts or your health data, and we do not track your runs. We do not use advertising trackers, and we do not sell personal data.
Why we use it
We use personal data to run the service you asked for, which is needed to provide it (GDPR Article 6(1)(b)):
- to sign you in with an email link and keep your groups;
- to show a group's runs on its private map and tell the group who is coming;
- to take payment for Pro and send a receipt;
- to email you notices about your group (a report, a payment, a deletion), and to answer messages sent to us.
We also rely on our legitimate interests (Article 6(1)(f)): letting a running group meet, keeping the service secure and free of abuse (rate limiting, error reports with personal details removed), answering reports, and knowing which pages of our landing page and blog help people. You can object to this at any time (see Your rights). We keep payment and tax records because the law requires it (Article 6(1)(c)). Where the law asks for your consent, we ask for it, and you can withdraw it at any time.
You do not have to give us any of this, but without an email address we cannot sign you in, and without a first name a group has nothing to show for you.
If you join our email list, we send it because you asked and confirmed (Article 6(1)(a)), and you can withdraw that at any time by unsubscribing.
Who sees what
Only people with a group's invite link can see the group, its runs and its first names. Members see first names only. The group owner and its admins can see and remove runs and members, and can close or replace the link.
Public runs are switched off. If they are turned on, an owner can mark a run public, and anyone can then see its title, time, note and meeting point on the map. Public runs never show member names.
Who handles data for us
We use these services to run RunnerOutpost. Most of them act only on our instructions and for the purpose given. Stripe, Google Play and Apple also use payment data for their own fraud prevention and legal duties, as their own controllers, and OpenFreeMap receives a request from your browser directly.
- Supabase: the database, accounts and the sign-in emails. Hosted in the EU.
- Vercel: hosting and delivery of the site, which handles request data such as your IP address while a request is served. Hosted in Dublin.
- Stripe, Google Play and Apple: payments for Pro. On the website you enter your card on Stripe's page; in the Android and iPhone apps you pay the store (Google or Apple). We keep only a reference to the payment, never card details.
- Resend: email we send because of something you did or asked for, such as a sign-in link, a receipt or a notice about your group. EU.
- OpenFreeMap and OpenStreetMap: map tiles and place search. The map tiles receive the viewer's IP address and the area on screen; the words you type in the place search go from our server, not from your phone.
- Sentry: error reports with personal details removed and invite links redacted. EU.
- Matomo, on our own analytics server (analytics.yellowtentacle.com): counts visits to the landing page and the blog without cookies, with IP addresses shortened and no data passed to anyone else. Google Analytics: only if you say yes on the landing page or the blog. It counts visits to those pages and receives the page name and your browser and device details.
- Our own server: it hosts the blog at blog.runneroutpost.com. Its access log records visitors' IP addresses and is kept for a short time to run and secure the site.
- Brevo, a French email service: our email list for the blog and the landing page, after you confirm.
Some of these providers may process data outside the European Economic Area. Where they do, the transfer relies on the safeguard the law requires, such as the EU-US Data Privacy Framework or standard contractual clauses, and you can ask us for a copy of the safeguard in use. We keep an up-to-date list of these services and review it before adding another.
How long we keep it
A group, its runs, routes, answers and first names stay until the owner deletes the group or the account. An owner's deletion takes the group, its runs and answers with it. A member can leave a group, or delete their account, at any time, and what they gave goes with it.
When something is deleted we remove it from our database too, apart from short-lived backups held by our database provider, which expire on their own. Place searches are cached for 30 days. Payment records are kept by Stripe, the stores and us for as long as tax and accounting rules require.
Email list subscribers stay on our list until they unsubscribe. Write to us and we will delete the address.
Your rights
Depending on where you live, you can ask us to:
- show you the personal data we hold about you;
- correct it or delete it;
- give you a copy you can reuse;
- stop or limit how we use it, or object to a particular use.
Write to contact@runneroutpost.com and we will reply within one month. You also have the right to complain to your local data protection authority. Anyone can leave a group, and delete their account with everything it holds, from the app or at runneroutpost.com/delete-account.
Children
Private groups can include younger runners when an adult runs the group; group owners are adults. Public runs are for people 18 and over. We do not knowingly collect more from a child than the first name and colour a group needs. If you believe a child has an account that should not exist, write to us and we will act on it quickly.
Cookies and local storage
We use only what the service needs: a sign-in cookie, kept fresh while you use the app, and small settings in your browser. There are no advertising trackers and no advertising cookies. The app, the map and your groups use no analytics. Our own Matomo analytics on the landing page and the blog sets no cookies and stores nothing in your browser; it also stops counting you if your browser sends Do Not Track. Google Analytics counts visits there only after you say yes; it then sets cookies (named _ga and _ga_…) so it can count visits, Google signals and ad personalisation are off, and you can change your answer from the link at the bottom of the page, which removes them. If you say no, no Google script is loaded.
The Android and iOS apps
The Android and iOS apps show the same website inside the app, so everything on this page applies to them. Purchases in the apps go through Google Play or Apple under their own terms; we receive a signed record of the purchase, the plan and its dates, never a card number. The apps do not read your contacts or location, and send no data to us beyond what the website does. Reminder notifications are switched off for now; if they come back we will say so here and ask your permission first. Google Play and Apple's App Store, which distribute the apps, have their own privacy policies for the store. To request that your account and data be deleted, use the delete-account option in the app or at runneroutpost.com/delete-account, or write to contact@runneroutpost.com.
Security
Data travels over an encrypted connection and is stored in the EU. An invite link is a long random address, and we keep tokens only as hashes. We never write invite tokens, session tokens or email addresses to logs, and error reports never carry a name, an invite link or a request body. No service is perfectly secure. If a breach puts your rights at risk, we will tell the data protection authority and, where the law requires it, you.
Changes
If we change this policy in a way that matters, we will update the date at the top and say so in the app.
Contact
Questions, requests or complaints about your data: contact@runneroutpost.com.