← Home

Privacy Policy

Last updated: 2026-11-17

The short version

  • Before you choose, we count page views, page exits and how fast pages load, and we keep a running total of how far visitors get and which campaign brought them — that total is counted on our own server, not by a third party. No analytics cookie or identifier is stored on your device until you choose.
  • Say "Decline" and we stop measuring you, immediately.
  • On this website, accepting never links your activity to an account. In the app, it does.
  • You can ask us to show you what we hold, to correct it, or to delete it.
  • Eight outside services touch your data, and every one of them is listed below.

What we collect

Two kinds of things: what you give us, and what we see while you use Trail Draw.

  • What you give us: your email address, so we can create your account and send you a sign-in code; the routes, checkpoints and registration codes you create; and anything you send us, such as a support ticket or feedback.
  • When you join an event: your name, and your signature on that event's waiver — kept with the text of the waiver you agreed to, the date, and the event.
  • What we see while you use the app: your browser type and operating system; which pages you visit, which features you use and how long you spend; and analytics events that tell us how far people get through a signup.
  • When you check in at a checkpoint: the photo you take (if any), the location your device reports at that moment, and the time. For a location-only (GPS) checkpoint we record three location readings taken a few seconds apart, with the accuracy your device reports for each. The organizer of that event sees whether you were inside the checkpoint area, how far away and how accurate your best reading was, and any photo you added — not the individual readings. Location is only read while you are checking in, never in the background.
  • One thing to know about support tickets: a ticket we email to us also carries your IP address, your browser's user-agent string, and the organizer's email address for that event. That is what lets us find the problem. It goes into our support inbox, into our support-ticket database, and it is relayed by our email providers along the way.

Payments

We do not handle participant registration fees or in-app purchases such as extra hands or redraws. Those are paid directly between the organizer and the participant, and we never touch that money. We do process payments for organizer plans through Stripe, and we never store your full card details.

What we do with it

We do not sell your personal information to anyone, and we do not use it for advertising.

  • To run Trail Draw: score events, publish leaderboards and results, and keep the app working.
  • To keep other people out of your event: sign you in, and check who is allowed to see what.
  • To send you what you actually need: sign-in codes, and event updates.
  • To make it better: see which pages confuse people and which errors they hit.
  • To meet our legal obligations.

Cookies and what we measure

This is the part most privacy policies bury, so here it is up front.

What we keep on your device

Some of this has to be stored locally for the site to work at all:

  • Your sign-in session, so you stay logged in.
  • Your choice about analytics, so we do not ask you again on every visit.
  • A short queue of analytics events, if you are offline when the site tries to send them. It is sent when you are back online, and only if you have accepted.

Before you choose

  • We count page views, page exits and page performance, and we keep a running total on our own servers of how far visitors get through the site and which campaign they came from — no cookie, no identifier, and no third party for that count. There are no session recordings and no form values, no cookies, no saved identifier, and nothing attached to your account.
  • Your browser holds a few values for the length of your visit — the campaign details from the link you arrived on, and a cache of today's homepage headline. None of them is a cookie, none identifies you, and all of them disappear when you close the tab.
  • We keep a running count of how far visitors get through the site and which campaign they came from. That is a total on our servers, not a record of you.
  • Your IP address is used to rate-limit automated requests, and our web server keeps it in its ordinary access logs, the same way any site records who visited. Our hosting and analytics providers see it too, because they are the ones serving and measuring the site. Our analytics provider also turns that address into a location — country, region, city and postal code — and stores it with the visit. That derived location is the one part of a visit that is not anonymous.

If you accept

  • PostHog starts recording clicks, feature usage, and how far you get through a signup, using cookies and local storage. It also records a session replay with form fields masked, and it ties that activity to one identity for this visit. PostHog only creates a profile for people we can identify, so activity that is not tied to an account does not become a person in our analytics.
  • Grafana Faro starts recording how the site is performing: the page you are on, your browser and operating system, your full browser user-agent string, how fast the page loaded, errors your browser reported, and the addresses of the requests the page made. We remove the query string and fragment from those addresses, along with sign-in codes and tokens. Faro labels your visit with a random identifier kept in your browser's session storage, which is gone when the session ends. Faro does not record which links or buttons you click.
  • Sentry starts recording errors: stack traces, and the browser and device they happened on. We strip credentials and sensitive fields out before anything is sent.
  • On the app, accepting also links your activity to your account. On this website, it stays separate.

If you decline

All measurement stops, immediately. Faro is not even loaded. Nothing captured before you declined is delivered afterwards or linked to a later visit.

Changing your mind later

Your choice is stored on your device, so it survives closing the tab. You can change it by clearing cookies and site data in your browser settings — the banner will ask again next time, and until you answer, the pre-consent count described above keeps running.

How we store and protect it

  • Your data travels to us over an encrypted connection, and it is stored on our own servers.
  • You sign in with a code we email you. You can also set a password on your profile if you would rather not wait for an email.
  • We do the ordinary things to protect it: access controls, encrypted connections, and backups. No system is perfectly safe, and we will not pretend otherwise.

How long we keep it

  • Your account and the events you create: while your account is open, and for as long as we need those events to run an event you are part of.
  • Finished events: the results and leaderboards behind them are meant to be public, and we keep them. The participant records behind them are kept too, because an organizer may need to settle a dispute months later.
  • Location-only (GPS) check-ins: the individual location readings, any location data stored inside a photo, and any photo you added are deleted 90 days after the game ends. We keep the result — whether you were inside the area, how far from the checkpoint your best reading was, and its accuracy — with the rest of the event record.
  • Your account, on request: ask us to delete it and its data at any time. We aim to answer within 30 days. We take it off the live site straight away — the copies sitting in our backups fade away on their own within about a month.

Who else sees it

Eight services outside Trail Draw handle data on our behalf. Each has its own privacy policy, and each is here for one job:

  • Oracle Cloud — runs our servers, and holds the backups of our database.
  • Cloudflare — sits in front of the site, and handles our DNS, our file storage and our email. It sees every visitor's IP address.
  • Mailgun — sends our email. That means it sees your email address, your sign-in codes, and anything you send us through a form.
  • PostHog — our product analytics. Your analytics data lives in PostHog's cloud service in the United States; we send it through our own domain so that blockers are less likely to stop it.
  • Sentry — error monitoring.
  • Grafana Cloud — stores the performance and browser-error data Faro collects.
  • OpenStreetMap Nominatim — turns the addresses you type into coordinates.
  • Stripe — processes payments, if you buy an organizer plan.

Your rights

Depending on where you live, the law may give you rights over your data: to see what we hold, to correct it, to delete it, to stop us using it, to take a copy of it somewhere else, or to object to our using it at all. In the EU and UK that is the GDPR; in California that is the CCPA. To use any of these, contact us at the address below.

Children

Trail Draw is not meant for children under 13, and we do not knowingly collect information from them. If you think we have, contact us and ask us to delete it.

If this page changes

We will change this page when Trail Draw changes in a way that affects your data. We would like to tell you when that happens, but we have not built the machinery to do that yet, so please check back when something seems different.

Contact us

Questions about your data, a request, or something you would rather not put in a ticket: the contact form at https://traildraw.com/contact. You can also email [email protected] — it reaches the same inbox as every other address at traildraw.com.