YOUR INFORMATION
Privacy, in
plain language.
Updated September 8, 2026 · Operated by RaSstudios LLC
MileMarX is preparing for public launch. This policy covers this website and the limited beta service, including earlier app builds under the previous name. The website previews some controls that are not yet deployed. Where behavior differs, we explain it below rather than treating planned protections as already available.
The website
This site has no advertising, analytics scripts, tracking pixels, sign-up form or payment checkout. It does not request your GPS location. Images and styles are served from our host. 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.
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 the current limited beta, sharing can remain enabled for future runs, and a legacy anonymous-public option can expose progress without a displayed name. Omitting a name does not make a precise location anonymous. Review your sharing settings and only share invitation codes with people you trust. Someone who receives a code can forward it. Live positions stop being shown after approximately 15 minutes without an update; hiding a stale point is not the same as deleting stored records.
The next release is designed to remove the public runner directory, authenticate ownership with a private device credential and add bounded Meet Up sharing after finishing. Those protections require the matching app and service update. Until that release is deployed, do not assume the previewed controls are active in an older beta.
Voices, cheers and AI providers
Optional AI voice features send alert text or cheer messages to ElevenLabs to generate speech. Text may include a chosen name, running progress and course context; don't include sensitive personal details. Generated audio and cheer messages may be stored or cached for delivery. The next release adds explicit AI consent controls and Anthropic filtering for custom cheers; filtering is not currently available on the production service.
Provider processing is governed by their policies: ElevenLabs and Anthropic. Declining future processing doesn't undo information already sent. Use built-in iPhone voices instead of AI features if you do not want that text sent to a voice provider. For concerns about an existing message or audio clip, contact us.
Other information the app uses
- Sharing and notifications: invitation codes, device push tokens, followed codes, optional names and run status enable following and start notifications.
- Feedback and correspondence: course reports, wait-time reports, feature/race requests and any optional email or other information you submit.
- History transfers: if you choose to transfer run history, a package that can include routes and run details is stored temporarily on our server. It is encrypted in transit, not end-to-end encrypted. Anyone holding its transfer code and PIN may restore it while valid. Transfers have a 30-minute access window; expiry is distinct from physical cleanup.
- Purchases: Apple processes payment. The app and service use purchase/entitlement information and transaction events, not payment-card details.
- Apple Health: optional workout and route saving takes place on your device. The app does not read your Health history. This is separate from app-generated location and fitness data you choose to share or transfer.
- Directions: where available, choosing directions opens Apple Maps with a last-shared destination. Apple handles navigation; the destination isn't a continuously moving route.
- Diagnostics: earlier beta features and hosting operations may record device/app information, request paths, IP addresses and operational errors for troubleshooting and security.
Retention and your choices
Keep location, Health and notification permissions under your control in iOS Settings. Turn off sharing in the app when you no longer need it. Local run history remains until you delete it; Apple Health and Apple purchase records are separate.
The current beta does not yet have the upcoming release's uniform automated retention and in-app server-data deletion controls. Stored sharing history, cheers/audio, requests, diagnostic records and backups can remain after their user-visible access window ends. Contact us to request access, correction or removal. We may need enough information to verify your request, but never your Apple password or private device credential. Necessary purchase, security or abuse-investigation records may need to be retained. We do not promise an unverified deletion schedule for infrastructure logs or backups.
The upcoming release includes code revocation, Report and Block, and Delete this device's server data in Settings → Privacy. It also introduces bounded sharing sessions and scheduled cleanup. These are planned controls, not a substitute for contacting us about records in the current beta.
Children and contact
MileMarX is not directed at children under 13 and we do not knowingly collect their personal information. 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.