YOUR INFORMATION

Privacy, in
plain language.

Updated November 2026 · Operated by RaSstudios LLC

What's new in version 1.95

Runners can share a temporary live web link that works in any browser; friends can send recorded or scheduled cheers; we ask an age range (never a birthday) before someone shares a web link or sends a cheer from a browser; and the server now deletes its copy of a cheer 24 hours after it reaches the runner's phone. Sharing changes still require private device credentials, and there is no public runner directory: the only shared map of runners is an opt-in crowd map inside sponsored races.

The website

This site has no advertising, analytics scripts, tracking pixels, sign-up form or payment checkout. Pages don't request your GPS location; on a live runner page, “Use my location” asks your browser only if you tap it, and the result stays in your browser to estimate when the runner reaches you. Images, styles and the live-page map are served from our host; the map is drawn from our own course data with no third-party map service. Microsoft Azure may process IP addresses, request paths, timestamps and security/error information to deliver and protect the site. We do not sell personal data. Contact links open your email application; information you send is handled as correspondence.

First-party service activity

We keep a private server-side activity log of website and app API requests to understand service usage and troubleshoot problems. Records include the request time, page or generalized API endpoint, source IP address, HTTP method, response status and duration, and a broad browser/client and device-type label derived from the reported User-Agent. We do not use this log to derive your location, build a device fingerprint, identify you across other apps or websites, or advertise to you. There are no analytics cookies or third-party tracking pixels.

Activity records exclude request bodies, query strings, private credentials, friend codes, names, messages and GPS coordinates. Access is restricted to authorized administrators. The log retains up to seven days or the newest 100,000 requests, whichever is smaller; older records are regularly removed while the service runs. Downtime can delay physical cleanup. Activity logs are not linked to your app's private device credential and are separate from in-app device-data deletion. Contact privacy@milemarx.com about privacy requests. API traffic may be background communication rather than an app opening.

Live web links

A runner with Pro who is 18 or older can create a live web link. Anyone with the link can see the runner's chosen name, race, live position on the course, distance, elapsed time, pace, projected finish and the trail run so far, and can send a cheer. Links are 22 random characters, are never listed or indexed, and stop working 60 minutes after the runner stops sharing (or at the end of the day if the run never starts). A runner can stop or replace a link at any time. In Free Run, the first and last 400 meters of the route and any live position near the start are hidden. Meet Up and spectator locations are never shown on a web link. Wrong, expired and revoked links look the same, and repeated wrong guesses from one IP address are blocked for an hour.

To show runners how many people are watching, each open page sends a random identifier made in that browser tab. It is kept only in server memory for about a minute and is not linked to anything else. Visits are also covered by the access log described above. The runner sees only a count.

Browsers that send a cheer use two functional cookies, not tracking cookies: one remembers whether the age question allowed cheers in this browser, and one holds a random sender ID so a runner can report and block unwanted messages from that browser. Clearing cookies removes them.

Location and running data

The app uses precise GPS location on your phone for progress and course cues during an active race, practice or Free Run, including in the background when permitted. If sharing is enabled, our Azure service in the United States receives position, progress, pace, timing, estimated finish, an optional name or bib and sharing identifiers. Course runs can use a course-snapped position; Free Run uses actual GPS. In a race whose organizer sponsors MileMarX, a runner may opt in to the crowd map, which shows their first name and live course position to other MileMarX users viewing that race.

In the updated app, spectator sharing defaults on, respects a saved off choice, and starts when you open the app in spectator mode. It sends actual GPS and your optional display name, not runner pace or timing. When you add a runner's or friend's code while sharing your spot, that person can see your shared spot too, without entering your code; removing their code stops it. It continues while you use other apps or lock your phone. Turn it off to stop local GPS immediately. Force-quitting also stops GPS, but iOS may not deliver a final server stop; the last position expires within two minutes. A background relaunch does not restore spectator sharing. Spectator and run sessions have a 12-hour safety limit. Finishing a shared run enters Meet Up for up to one hour; End Sharing stops it sooner.

Only share invitation codes with people you trust: anyone holding a code can view its active shared position and forward the code. A missing display name does not make precise location anonymous. A separate private device credential controls changes; the server stores its hash and a random installation identifier, not the credential itself. A viewer code cannot authorize changes to another person's sharing. Server clearing requires connectivity, and stale visibility is different from physical record cleanup.

Voices, cheers and speech processing

The app asks for optional permission before personalized text goes to ElevenLabs to make speech. Custom cheers are private, one-way spectator-to-runner messages: their text goes to ElevenLabs for speech, not to a separate AI moderation service. They are not posted to a public feed. Anyone with a forwarded invitation code may be able to send a cheer; keep codes within your trusted circle. Text may include a chosen name, running progress and course context; don't include sensitive personal details. Custom voice messages require the runner's eligible paid access, sender permission and an available voice service. Before sending a typed cheer, the sender can preview it; an unsent preview is deleted within an hour. Recorded cheers are the sender's own voice, up to 15 seconds, and are not sent to any AI service. Preset cheers remain an alternative. Senders appear to runners as a short alias, not a name. A runner can choose to have cheers play aloud, wait until after the run, or be turned off, and followers see that choice.

Preset, custom and recorded cheers, including their text and audio, are kept on MileMarX servers for 24 hours after they reach the runner's phone. A cheer that never reaches the phone is deleted 24 hours after it was sent once the runner's sharing has ended, and no cheer is kept on our servers longer than 7 days. The runner's phone keeps the cheers it receives, including their audio, so they can be replayed and saved later; they stay on that phone until the runner deletes them or deletes this device's sharing data. In the app, a runner can play, save, delete, or report and block a cheer, and lift blocks. While on our servers, cheers are available to the receiving runner's app and to authorized MileMarX staff, who may review them for support, safety and abuse prevention. After that they are automatically deleted and can no longer be accessed through MileMarX. Copies can remain in our hosting provider's automatic system backups for up to 30 days until those backups expire; we do not restore cheers from backups. Personalized live voice requests are not added to the public audio cache. Fixed non-personal course and preset audio can be cached. Speech processing follows the ElevenLabs privacy policy. Withdrawing permission stops new personalized requests, not earlier processing. Built-in iPhone voices and preset cheers remain alternatives. Earlier app versions may still describe a separate AI safety-check provider; that provider is no longer used for custom cheers after this service update.

Other information the app uses

Retention and your choices

Keep location, Health and notification permissions under your control in iOS Settings. Turn off sharing when you no longer need it. The updated service runs cleanup at startup and approximately every minute. Position history is automatically deleted after 24 hours. If we're investigating a specific problem, such as a tracking error or service outage, we may keep the records needed for that investigation for up to 30 days, limited to authorized MileMarX staff, and delete them when the investigation ends. After a runner finishes, their shared position, finish stats and trail stay visible to people following them until that automatic deletion. Other records follow the same cleanup: history transfers after 30 minutes, cheers and private audio 24 hours after delivery to the runner's phone (at most 7 days), live web links when they expire, push registrations after 30 days without refresh, and inactive device identities, shares and requests after 90 days. The app also sends voice-cue timing so we can make cues more accurate: which race and cue played, when it was triggered and when it was heard, the course mile and distance from the cue, and the app version, with no GPS coordinates or name. Voice-cue timing records are deleted after seven days. Downtime can delay physical cleanup.

Settings → Privacy in the updated app offers Report and Block and Delete this device's server data. Deletion revokes owned codes and removes owned sharing, cheers, registrations, transfers, feedback and requests. Local run history and Apple Health records are separate. Blocking applies to a sender installation, not every possible device. Unresolved abuse reports are retained for investigation; resolved reports are removed once older than 90 days. A received-cheer inbox may remain on the phone.

Infrastructure logs and restricted-access backups are separate from in-app deletion. A private service backup was created for the September migration; backups are not used to keep deleted locations publicly accessible. We do not promise an unverified deletion schedule for infrastructure copies. Contact us for access, correction or removal, including older records. We may need information to verify a request, but never your Apple password or private device credential. Necessary purchase, security or abuse evidence may need to be retained.

Children, the age question and contact

MileMarX is not directed at children under 13 and we do not knowingly collect their personal information. To follow the U.S. Children's Online Privacy Protection Act (COPPA), we ask for an age range, never a birthday. In the app, MileMarX asks Apple for your age range the first time you share or send a cheer; the range stays on your phone, and our server is told only whether a web link is allowed. Under 13, the app doesn't allow location sharing, web links, or typed or recorded cheers; 13 to 17 can share with friends by code but not by web link. On the website, the first cheer from a browser asks which age range you're in; we don't store the answer, and the browser only remembers whether cheers are allowed. Under 13 can watch but not send cheers. Send privacy requests to privacy@milemarx.com, or contact the owner at bobby@milemarx.com. We will update this policy when the matching release and its actual data-handling practices change.