RaceGoat

Legal

Privacy Policy

Last updated November 10, 2026

This policy explains what RaceGoat (operated by Dead Reckoning Labs Inc) collects when you register for a race, why we collect it, and who we share it with. We do not sell your personal information.

What we collect

  • Registration details: name, email, phone, birthdate, division, mailing address, shirt size, and answers to race questions (such as dietary needs).
  • Emergency contact and, for a runner under 18, the parent or guardian’s name, relationship, phone and signature.
  • Your signed waiver, with the date, time, IP address and browser used to sign it.
  • Payment details, handled by Stripe. We receive the card brand and last four digits, never the full number.
  • Basic technical data (IP address, browser, pages visited) to keep the site secure and working.

How we use it

To register you, process payment and sales tax, send your confirmation and race communications, give the organizer what it needs to run the event safely, publish entrant lists and results, prevent fraud, and support you when you contact us.

Who we share it with

  • The race organizer, who receives your registration, emergency contact and waiver to run the event.
  • Payment and tax processors (Stripe) to charge your card and calculate tax.
  • Service providers that host the site, send email and texts, and monitor errors, only to do that work for us.
  • Google Analytics, which counts visits to RaceGoat’s public pages for us. It never sees the address of an account, receipt, claim, waiver or other private page (those show up only as “private”), page addresses are sent without anything after the path, the page you came from is trimmed the same way, and it does not load if your browser sends a Global Privacy Control signal.
  • Our athlete profile service, which links your results across races and years so your race history stays yours.
  • Ad platforms the race organizer connects (Meta, Google). When an organizer adds their own Google tag, that race’s pages and your receipt load it, unless your browser sends a Global Privacy Control signal. Meta’s code never loads in your browser: when an organizer connects Meta, we send Meta from our server a scrambled (hashed) copy of your email, name, gender, date of birth, city, state, ZIP and country, an anonymous id for your entry, the ad click id from the link you arrived on and your browser’s user agent, with the order total, so the organizer can measure their ads. Never your phone number, never anyone under 18, and never if your browser sends a Global Privacy Control signal.
  • The organizer’s email platform (Mailchimp, Klaviyo or ActiveCampaign), only if you tick the box at checkout to get that organizer’s news: your name, email and the race and distance you entered. Unsubscribe from their emails at any time.
  • Travel partners on race pages (Stay22 for lodging, Discover Cars for rental cars). A race page may show their map or search box in a frame that their own site serves. Inside that frame they set their own cookies and run their own analytics (Stay22 uses Hotjar, Mixpanel and Google Tag Manager; Discover Cars uses Google Tag Manager), and they see your device’s address and the race page you came from. We do not send them your name, email or registration. If you book through one of them, their own privacy policy applies and RaceGoat or the race organizer may earn a commission.
  • Authorities, when the law requires it.

None of the above includes mobile phone numbers or text-messaging opt-in data and consent: these are never shared with or sold to third parties or affiliates for marketing or promotional purposes.

What is public

Entrant lists show your name, city and state, division and age group. Results show your name, placing and performance, and your runner profile collects your results across races. Your email, phone, birthdate, street address and emergency contact are never public. Search engines such as Google may list entrant lists, results and runner profiles. Entrant lists leave out runners under 18, and runner profiles are only offered to search engines for runners we know are 18 or older; race results are public the way the sport has always published them. You can turn on Hide me from search under Privacy in your account. To ask about hiding your profile, contact us.

Children

A runner under 18 must be registered by a parent or legal guardian, who provides the child’s information and signs on their behalf. We do not knowingly collect information directly from children under 13. A parent can review or delete their child’s information by contacting us.

Text messages

If you opt in to RaceGoat text messages (registration confirmations, race-day alerts and event logistics), we use your mobile number only to send those messages. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the categories of sharing in this policy exclude text-messaging originator opt-in data and consent; this information will not be shared with or sold to any third parties. Message frequency varies; message and data rates may apply. Reply STOP to opt out or HELP for help. Details: racegoat.com/sms.

The RaceGoat app

The app on iPhone and Android uses your location while it is open to show where you are on the course map and how far it is to the next aid station; that position stays on your phone. Location leaves your phone only when you turn on one of the features below, and each one is off until you do.

Crew tracker (runners). From the day before your race you can turn on a crew link for your own entry (adults only) and text it to your crew. While it is on, the app sends your position up to once a minute, with the mile you are at and the aid stations you last passed and are heading to. Anyone you give the link to can see your latest position, mile and an estimated time to the next aid station; no account is needed to open it, and the page is never indexed by search engines. We keep only your latest position, never a trail. Turning the tracker off stops the link and deletes that position at once; otherwise the link stops showing a position 6 hours after your distance’s time limit and the position is deleted shortly after. While it is on, Android shows an ongoing notification.

Message race staff (runners). If you send your location from the app’s race command screen, it is added to your message thread with that race’s staff and kept with those messages.

Share my location (race staff and volunteers). Staff and volunteers working a race can turn this on so the race team sees sweepers and course marshals on the map, even with the app in the background: on iPhone it asks for background location (“Always”), and on Android it keeps an ongoing notification showing while it is on. We keep only your latest position, accuracy and battery level for that race, shown only to that race’s staff; it is deleted when you turn sharing off, and automatically 12 hours after the last update.

Truck mode (drop bag crews). A drop bag crew signed in to a station can turn on Truck mode while driving bags between stations. While it is on, the phone sends the truck’s position to Drop Bags (dropbags.io), the drop bag service the race uses, with an ongoing notification on Android. The race’s operations team sees the truck on their map; a runner whose bag is on the truck sees only the nearest station and how long ago the truck was seen, never its position. The truck’s route is kept with that race’s drop bag records.

If you allow notifications, we use your device’s push token (Apple Push Notification service on iPhone, Firebase Cloud Messaging on Android) only to send race alerts and reminders. You can delete your account in the app from your profile.

Cookies

We use cookies to keep you signed in and to hold your spot during checkout. When you arrive through a race’s shared link, we set an anonymous visitor ID (kept one year) and a note of which link you used (kept 30 days) so the organizer can see which of their links bring in registrations. When you arrive from an ad or a campaign link, we keep a note of that campaign (kept 30 days) for the same reason. Google Analytics sets its own cookies to count visits to our public pages (not when your browser sends Global Privacy Control). RaceGoat does not use cookies for advertising. If a race’s organizer has connected their own Meta or Google account, those companies set their own cookies on that race’s pages and checkout to measure the organizer’s ads, under their own privacy policies.

Keeping and deleting your data

We keep registration records, including signed waivers and payment records, as long as needed for the event, for your race history, and for tax and legal requirements. You can ask us to access, correct or delete your information; some records (like payments and waivers) we are required to keep.

Security

See our Security page for how we protect your data.

Changes

We will post any update here with a new date, and email you about material changes.

Questions? Contact us.