RunXRoam Privacy Policy
1. Who is responsible
Pixel Nomads operates RunXRoam and is the personal information controller for information handled through the app. Contact our privacy team through our contact form.
This policy covers our web and mobile services. Features and controls may vary by platform and installed app version. It explains our processing under applicable privacy law, including the Philippine Data Privacy Act of 2012. External services have their own policies.
2. Information we handle
- Accounts: email address, account identifier, sign-in provider, verification status, and account authentication information. Google or Apple sign-in, where available, supplies the identity details you authorize. Authentication is handled through Firebase Authentication.
- Profiles: display name, biography, profile photo, location, country, team, preferred activities, appearance settings, featured badges, and privacy preferences. Date of birth is requested when saving profile information and is used for age-related features. Its visibility is separate from age-group display.
- Activities: activity type, title, dates and start time, elapsed, timer and moving time where available, distance, elevation, calories where supplied, source, import identifiers, notes, audience and route data. Records come from manual entry, supported GPX, TCX, FIT or CSV files, native GPS recording and health workouts you review and import. Strava-export files can be imported without connecting a Strava account. A chosen file may contain more data than the activity summary saves. Original account-saved GPX files are retained as described below. We calculate progress, pace, records, streaks, goals and achievements from saved records.
- Equipment: gear names and details, activity assignments, starting mileage, calculated use, targets and reminders. Earlier imported equipment may remain; the current app no longer fetches gear from the Strava API.
- Race planning and spending: private race notes and reflections, planning choices, budget items, amounts, currencies, paid-entry information and recorded spending totals. When you create a shared plan, we store a separate copy of selected budget information, event details, member names and identifiers, viewer/editor roles and edit history metadata.
- Events and clubs: saved participation choices, selected distances, linked completion activities, event submissions, club memberships and roles, group events, club photos, meetup schedules and locations, pace groups, RSVP choices, and race or virtual-challenge tracking. Browsing and filtering use the location, preferences, or search input relevant to the feature.
- Community: shared activities and achievements, event ratings and reviews, follows and follow requests, reactions, comments, reports, blocks, and in-app notification preferences and read status.
- Merchant listings: store names, descriptions, official links, locations, showcase and product photos, product details and supplied starting prices. For assigned store managers, we also store account identifiers and management assignments.
- Rankings: submitted race results, distances and finish times, evidence links, review decisions, ranking preferences, age groups, calculated performance information, and optional ITRA profile links and retrieved public runner statistics.
- Developer support through Google Play: optional one-time support product, account identifier, random purchase-account key, purchase token and its hash, Google order identifier, purchase and refund status, confirmation timestamps, supporter points, tier and badge choices. Where Google supplies a verified amount, we also store the charged amount, currency and a private support-total summary. Pending or test transactions are distinguished from confirmed support. Google handles checkout and your payment credentials; RunXRoam does not receive your card details, Google password, PIN or one-time code. Earlier support recognition may be retained separately and is not relabelled as a verified Google Play payment.
- Training plans: private plan settings, scheduled workouts, training notes, completion choices and links to your recorded activities.
- Optional health features: steps, distance, workout time, dates, time zone, originating app/provider and workout identifiers, connection and permission choices, optional step goals, workout links and import-removal preferences. Supported sources include Android Health Connect (including data Samsung Health shares into it), Apple Health on supported iOS builds, and authorized Polar Flow workouts. Native device reads, optional daily-summary cloud storage and reviewed workout imports are separate actions.
- Optional Insights usage statistics: only after you opt in, event types such as opening a card or explanation, fixed module identifiers, ready/insufficient counts, access state, app/platform and engine versions, timestamps and random session/event identifiers. These statistics exclude your name, email, account ID, activity text, route coordinates and exact performance values. Authentication and the device queue are still account-scoped; we do not describe the system as anonymous.
- GPS recording and saved routes: precise coordinates, sample timestamps, accuracy and available altitude, recording/pause/gap events, selected sport and goal, calculated metrics, device recording files and pending uploads. Account-saved GPX routes include the original file, filename, title, size, content hash, track summary, optional location and synchronization metadata. An original GPX may include timestamps, waypoints and extensions that are absent from its simplified preview.
- Ask RunXRoam and AI planning: messages and bounded conversation context, training goals and dates, recent training volume/results, experience, available days and session limits, restriction choices and notes you supply, and an explicitly selected saved workout or generated draft. Conversations with the assistant are saved to your account so you can reopen them: the messages you and the assistant exchanged, related in-app links suggested by the assistant, a title taken from your first message, and timestamps. We also keep consent/adult-confirmation records, usage and request/recovery metadata, structured setup facts and private generated results. Do not include names, contact details, home locations, passwords or medical records in AI text.
- Optional activity recaps: cadence and delivery preferences, timezone, closed-period activity totals and sport breakdowns, comparison with the previous equivalent period, saved summary text and its origin, calculation/provider metadata and delivery status.
- Private messages: conversation members, text, selected pictures, sender and timestamps, message status, last-message previews, unread counts, mute/block choices and report evidence. Reports include the selected message and up to ten preceding messages, report reasons, optional notes and review decisions.
- Apple developer support, where offered: product and transaction identifiers, a random purchase-account token, signed transaction verification, store environment, purchase/revocation state, timestamps, supporter credit and available price/currency. Apple handles checkout; we do not receive your card or Apple Account payment credentials.
- Service operation and support: the messages and attachments you send, consent document versions and acceptance times, and request, error, security and operational records. Hosting and infrastructure providers receive connection information such as IP addresses when handling requests.
3. Location, files and health access
Location and recording
Nearby discovery, course-position and forecast actions request location when you choose them. You can deny permission and use supported search or manual alternatives. Native Android and iOS builds can also record a workout after you choose Record, grant permission and start the session. Recording captures precise GPS positions and times, including available accuracy and altitude, and stores session data on the phone. A GPS readiness check uses your position before Start without saving a workout track.
A user-started recording can continue when you navigate away, lock the screen or put the app in the background, using Android’s foreground location service/notification or the iOS location background mode/indicator. These builds request while-in-use location rather than Android background-location or iOS Always authorization. Leaving the recording screen does not pause it. Use Pause, Finish or Discard to stop capture. OS restrictions, force-stop, reboot, poor GPS or lost service can interrupt recording; a recovered session may contain a gap. This is workout recording you initiate, not general-purpose continuous tracking.
Recording data is saved locally first. Saving an activity queues its record and route chunks for your account; offline or failed uploads can retry on reconnect or a later app session. Discarding a recording is different from deleting an already saved activity. Do not assume that turning off permission or uninstalling deletes a cloud copy. Routes and activity times can reveal home, school and daily routines.
Files, maps, photos and calendars
Selected files supply activities or routes; selected photos supply profile, community or permitted listing media. Account-saved GPX import keeps the original on the device and queues an upload to your private account, up to 20 MB per file. Existing device-only routes can be backed up when you choose that action. Remove offline download removes that device’s copy; Delete from account removes the account route and queues related file cleanup. A disconnected device or an externally exported copy may retain data until it reconnects or you remove it.
Map and place requests can include the displayed area, location or search text. Offline map downloads store tiles and course/region data on the device. A weather request sends a representative point rounded to approximately one kilometre and the relevant dates to the weather provider, rather than your whole route; direct requests expose your IP address. External directions pass the destination to your chosen maps app.
System file/photo pickers, sharing and download permissions vary by platform. Calendar access is used when you choose to add an event; the feature does not upload your existing device calendar. The private RunXRoam training calendar is separate from your phone’s calendar. Where offered, a device widget displays a locally saved progress snapshot; consider who can see your home screen.
Optional health connections
Supported native builds read steps, distance and exercise/workout records from Android Health Connect or Apple Health with your requested type selections and system authorization. Samsung Health/Galaxy Watch information reaches RunXRoam only when it is shared into Health Connect; RunXRoam does not require your Samsung password or a direct Samsung cloud connection. Apple read authorization may not reveal whether an empty result means denied access or no data. Missing data is not treated as a measured zero.
Native health reads run in the foreground on Sync now or when opening Health on an existing connection. They do not request health write access, background health collection, health-route access or heart-rate streams. Device-only reading is separate from optional daily-summary uploads: these uploads are off until you explicitly enable cloud storage, and one primary installation supplies summaries. Recent workout candidates require your review before an import or link; imported copies start private. These features do not feed advertising or verified rankings. A saved activity you later include in a recap is processed as explained in the AI section.
Polar Flow is a separate optional browser-authorized cloud connection, available where configured. The backend holds Polar identifiers and access credentials, retrieves eligible recent workout summaries when you ask, and lets you review/import or link a workout. It does not import Polar GPS routes or continuous heart-rate streams. Provider history limits apply; connecting does not promise a complete backfill.
Pause or disconnect to stop future sync, and revoke native permission in Health Connect or Apple Health settings. Use the offered keep/remove controls or Delete imported health data for saved copies. Disconnecting does not automatically erase imported activities or the provider’s own records. Polar disconnection disables new reads first and attempts provider deregistration; if that fails, a disabled credential can remain for retry. Native integration availability depends on the installed binary, device and OS; a web page update alone cannot add a missing native module.
4. Why we use information
We use account and profile data to provide access and personalize your profile; activity data to organize your history and calculate progress; event and club information to manage your selections and memberships; and shared content to provide community features. Gear information supports usage calculations and reminders. Race planning data supports personal preparation, spending summaries and the shared plans you choose to create. Reviews and merchant content support event feedback and store discovery. Results and evidence support ranking calculations and review. Support records enable supporter recognition. Correspondence and operational information help us answer requests, investigate problems, moderate abuse and protect the service.
For ordinary personal information, the applicable basis depends on the purpose: providing the service you request, complying with law, your consent, or legitimate interests such as service security after considering your rights. For sensitive information, including age and health-related information, an applicable sensitive-information ground is required; ordinary legitimate interests alone are insufficient. Where consent is the basis, it must be specific and may be withdrawn by using the relevant control or contacting us. Accepting the Terms is not blanket consent to unrelated processing.
Notification preferences control in-app notices. Optional digest delivery by push or email is attempted only when the relevant channel is enabled for the release and you select it. Native push requires device permission and a push token; email digests use a verified email address and a configured delivery provider. Browser and device capabilities differ. A queued email is not a confirmation of delivery.
Statistics, achievements and rankings are informational calculations, can contain errors, and are not medical assessments. We do not use your activity information to make decisions about employment, credit or insurance.
Training records support your private planning calendar. Health data supports the private progress and explicit import features you choose. Supporter Insights calculates explanations on your device from your activity history; it does not send your history to an external AI service. Separate, optional usage statistics help us understand feature reliability and usefulness. You can switch Insights usage collection off in Settings → Privacy; collection stops and unsent events are discarded. Changing this choice does not automatically erase already-uploaded records.
RunXRoam is a convenient directory for finding events, registration pages, stores and gear links. It never collects, holds or processes payments on behalf of listed events, organizers or stores. Event entry and store purchases use the organizer’s or seller’s official channels. Personal budgets, shared plans and paid-status notes are records supplied by users, not transactions or proof of payment. Optional platform-store developer support is a separate transaction for maintaining RunXRoam.
Optional AI assistance and recaps
Ask RunXRoam and AI training planning use OpenAI to answer supported questions about the app and about running, trail running, hiking, walking, cycling, triathlon basics, training and related outdoor activity, and to generate a draft from information you confirm. Some fixed app-help answers are supplied without a model request. AI features require the separate in-app consent and adult confirmation, and may be disabled or limited by release configuration. Accepting this policy alone does not enable AI or authorize unrelated data use.
For model requests we send the bounded messages/context and structured training facts needed for the action. Explaining an explicitly selected workout can include its title, date, target, effort and notes; a selected draft can also be supplied. The adapter does not add your account identifier, email, profile name, full activity library or GPS route. Free text you type, or notes in a selected workout, can still contain identifying or sensitive information; avoid including it. AI drafting does not automatically write your calendar: review the preview and confirm Add to calendar.
Weekly, monthly and yearly activity recaps are independent, off-by-default choices in notification settings. When enabled for a release, we aggregate saved activities in the closed period, save a report and attempt the selected notifications. When AI consent, adult confirmation and service controls allow a model request, OpenAI receives period dates, activity counts, active days, distance/time totals, sport totals and the previous-period comparison. It does not receive activity titles, notes, names, identifiers or route coordinates for this recap request. Totals can reflect health-imported workouts that you saved in your library. Recaps use the existing AI authorization record; there is no separate recap-specific provider-consent record in the reviewed implementation. Review this disclosure before enabling recaps. Turn the cadence off to stop future scheduled reports. If AI is unavailable or the authorization/capacity check fails, the report uses a labelled factual template; a template label after a provider error does not mean no provider request occurred.
OpenAI requests use the API with response storage disabled (store:false). This is not zero provider retention: provider security/abuse-monitoring and applicable contractual retention may still apply. We do not use these AI requests to train our own models; OpenAI states API data is not used for model training by default. No health-connection data is used for advertising, sold to data brokers or supplied for unrelated marketing. Local supporter Insights calculations are distinct from these optional external AI requests.
5. Visibility and sharing
Core profiles are discoverable by signed-in members. Activity audiences are “Everyone,” “Connections,” and “Only me.” The current default for new profiles is Connections; in the social system this means approved followers. Badge visibility defaults to Everyone, and achievement posting defaults to asking first. Existing accounts and individual activities may have different saved settings. Review each audience before sharing.
Date of birth is hidden by default and has a separate visibility setting. An age group may still appear in relevant ranking features. ITRA links have their own visibility setting. Hiding a link does not make the underlying ITRA public record or shared cache private. Ranking leaderboard participation and activity privacy are separate controls.
Community content, club membership and event attendance can be visible to the audience of the relevant feature. Administrators can access information needed for support, moderation, submission review and service administration. A hidden field in a screen is not necessarily a private record; contact us with questions about particular data or to request restricted processing.
Private planning and shared plans: personal budgets, spending entries, race reflections and equipment records are kept in your account rather than published to the social feed. Creating a shared budget makes a separate plan accessible to the specific members you invite from mutual connections; it does not publish your original private budget. Members can see plan contents and member information. Viewers can read, editors can change the plan, and the owner can change roles or remove access. Shared plans have no public-link sharing. Review the copied information before inviting someone.
Routes and exports: recorded tracks and account-saved GPX routes are stored under your private account. Sending a route to another user, publishing an activity or exporting a GPX, image or screen recording is a separate sharing choice. An original GPX can contain more detail than the simplified map, including timestamps and waypoints. Share templates can reveal routes and activity details. Check start/finish points and the audience first. In-app privacy changes cannot recall downloaded files, pictures, recordings or copies held by others.
Reviews, meetups and stores: event reviews and ratings are intended for other users to read. Club session information, RSVP choices and uploaded club photos are visible within the relevant club feature. Merchant descriptions, photos, product details and supplied prices are displayed to people viewing the store. Do not put private information in these submissions.
Changing an audience cannot remove screenshots, downloaded share images or copies already held outside RunXRoam. External registration links take you to the organizer or registration service, which handles information you provide under its own terms. Selecting Interested, Going or Completed in RunXRoam does not itself register you with an organizer.
Private messages are not end-to-end encrypted. The service stores message text and pictures. Ordinary conversation access is restricted to its members; a conversation can be started between mutual followers, and blocking stops new messages. Unfollowing alone does not close an existing conversation. When a member reports a conversation/message, authorized administrators gain access to that reported conversation and its evidence for safety review, including the conversation beyond the copied report excerpt. Resolving a report does not automatically remove that administrative-access marker. Do not send passwords, payment credentials or sensitive medical records in chat. Notification previews may reveal message content on a recipient’s device.
6. Connected services and recipients
- Google Firebase and Google Cloud: account authentication, database storage and synchronization, uploaded profile, club and merchant media, backend processing and operational logging. See Firebase privacy information and Google's Privacy Policy.
- Strava: the current app uses user-supplied Strava-export files instead of new Strava API connections, automatic activity syncing or route/gear fetching. A retirement path attempts to revoke and remove old stored credentials; older API imports and associated data may remain until reviewed or removed. We do not claim that historical cleanup or provider-side revocation has completed for every account. You can remove RunXRoam access in Strava’s connected-app settings and ask us about legacy data. File imports and data retained by Strava remain subject to your rights and Strava’s policy.
- Google Maps Platform and external maps apps: map display, place searches, location lookup, nearby trip suggestions and directions. Requests can include the location or search input used by the feature. Google Maps use is also subject to Google Maps terms and Google's privacy policy.
- ITRA and Apify: optional runner matching and retrieval of public ITRA statistics. The runner name and optional nationality used for a search are sent through Apify. A confirmed runner identifier and retrieved public statistics are cached. This does not require your ITRA password. See Apify's Privacy Policy and ITRA.
- Google Cloud Vision: event-source text extraction and, in iOS releases offering pre-upload image moderation, safety classification of the image submitted for checking. A selected image can be sent to Google Cloud for this check. Automated moderation is not a guarantee that every harmful item will be detected.
- Google Play Billing: processes optional developer-support checkout in supported Android releases. A random account key links a purchase to the signed-in account without sending its email or RunXRoam user ID as that key. Our backend sends purchase tokens to Google to verify purchases, reconcile pending states, and handle refunds or reversals. Google provides purchase/order status and available amount/currency details. Google applies its own payment, order-history and privacy practices. See Google’s Privacy Policy and Google Play Terms.
- Merchants and external stores: opening a store website, social page or directions sends the relevant request to that provider. Information you submit there, including inquiries, orders and payment information, is handled under that provider’s terms and privacy policy. RunXRoam’s store showcase does not provide an in-app checkout.
- Apple, Google, GitHub and external sites: optional sign-in providers, platform services, and hosting or delivery of our public legal pages receive the requests needed to provide their services. Opening a link or loading content directly from another provider can expose your IP address and request information to that provider.
- OpenAI: optional assistant, training-draft and recap processing described above. Our backend sends the necessary bounded input and receives output plus operational usage/response metadata. See OpenAI’s API privacy information.
- Apple Health / HealthKit and Polar Flow: optional read/import sources with the scope and controls above. Polar receives authorization, workout-fetch and deregistration requests; native Apple health reads occur on the device before any optional RunXRoam upload. See Apple’s privacy policy and Polar’s privacy notice.
- Apple App Store: where supported iOS developer-support purchases are enabled, Apple processes checkout and signed transaction verification/status. A random app-account token binds the purchase; our backend verifies transaction identity, environment and reversals. Apple keeps its own payment records under its policies. This is App Store in-app purchasing, not event or store checkout.
- OpenFreeMap / OpenStreetMap and Open-Meteo: map tiles/styles and weather data where those features are enabled. Requests disclose IP/network information and the requested map area or rounded weather point/date to the provider. Downloads can persist locally; retain the supplied map attribution. See OpenFreeMap, OpenStreetMap Foundation privacy and Open-Meteo’s terms.
- Contact form / Netlify: contacting Pixel Nomads through the website submits your name, reply email, topic and message to Netlify Forms and our company inbox so we can respond. See the website Privacy Policy. Never submit passwords, full payment credentials or a complete health file with a general inquiry.
We may disclose relevant information when required by law or necessary and lawful to address abuse, protect people, or establish or defend legal claims. We do not sell personal information. A new unrelated use or new data-sharing purpose requires an updated disclosure and any consent required by law.
Notification delivery: where enabled and selected, Expo’s push service and the device platform deliver push notifications, and the configured email service processes the address and digest content needed for email delivery. Operational delivery status may be saved. No delivery provider is required to browse listings.
Following an event, registration or store link sends your browser request to that destination, which may receive your IP address and referral information. Details you enter there, including registration, shipping and payment details, go to that provider under its own policies, rather than through a RunXRoam checkout. RunXRoam and Pixel Nomads are independent of the listed events and stores; a listing is not an affiliation, sponsorship or endorsement.
7. Storage, security and retention
Account-linked information is stored in cloud systems. Device or browser storage also supports sessions, preferences and caches. Infrastructure providers may process information outside your country. We remain responsible for information under our control and use access controls and provider arrangements to protect it. No service can guarantee absolute security; legally required breach notifications will be provided.
We retain profiles, activity history (including imported routes), equipment, planning records and associated settings while needed to provide your account and requested features, or until you delete them or request erasure. Connection tokens are needed while a connection remains active. Community content is kept while needed for its publication and related interactions. Support, security and payment-related records may need retention to resolve an open request, investigate an incident, meet a legal recordkeeping obligation, or handle a claim. We assess those purposes when you request deletion and explain any specific exception rather than treating it as permission to keep everything indefinitely.
Deletion from active systems may not immediately remove restricted infrastructure logs or provider recovery copies. We do not promise a fixed backup-expiry period here because retention depends on the relevant provider and configured service. Ask us for the retention details applicable to your request. Retained copies must not be used to restore a deleted public profile or resume unrelated processing.
Health summaries, imported workout records and training plans remain in your account until removed through the relevant controls or account deletion; health day records are not automatically pruned. Optional Insights usage events are marked to expire after 90 days. Expiry processing may take additional time, and operational logs have separate provider retention. Because those uploaded usage events contain no account identifier, deleting an account may not identify every prior event for individual removal; contact us about a privacy request.
Unused support-purchase intents are scheduled for removal after 14 days. On account deletion we remove account-linked purchase intents, raw purchase tokens, private receipts, support totals and account bindings. A restricted minimum purchase record remains for up to 400 days before scheduled removal to prevent a consumed purchase from being credited again and support order/refund obligations. It retains the token hash, Google order identifier, product, catalog/points information, test/state flags and necessary timestamps, but no RunXRoam user ID, account key, intent ID or raw purchase token. This record is not treated as anonymous. Google keeps its own payment records under its policies.
New feature records and their retention
Local recording sessions, tracks, route originals, offline maps and pending uploads remain on the device until saved, discarded, removed or cleared by the applicable account/device action. Synced activities and original GPX files remain in your account until you delete them or the account. GPX deletion records prevent another device from recreating a deleted route; file deletion can retry and an orphan-cleanup job is a backstop. Old device-only routes backed up from a simplified copy may lack the original timestamps/extensions. Exported files and another person’s saved copies require separate removal.
Ask RunXRoam conversations are saved to your account so you can reopen them. A conversation expires 30 days after its last message; each new message restarts that period. The app stops listing expired conversations, and a daily cleanup job is scheduled to delete them; processing or a backlog can delay removal from storage. Saved conversations are accessible only to their signed-in owner through the app and its client access rules, not to other members or app administrators. This does not prevent authorized operational or legally required access to database records, restricted logs or recovery copies, which are subject to the safeguards and retention limits described in this policy. You can delete a conversation at any time from Your conversations, and the supported account-deletion workflow also removes saved conversations. When you continue a conversation, recent messages that fit the request size limit are sent to OpenAI as context for your next message. Separately, private generated answers/drafts and structured intake facts are recoverable for seven days. Expired content becomes unreadable through recovery, and scheduled purge normally follows within the next day. Minimal request/session authorization metadata is retained for 40 days. Usage counters, consent records and saved calendar workouts have separate account lifetimes; deleting an unsaved draft does not reset usage. Saved recap reports retain their frozen statistics, summaries, origin/provider and delivery metadata in your account; switching off a cadence stops future reports but does not erase earlier ones. Request removal or delete the account for those records.
Direct-message text and pictures remain for the conversation until removed through supported controls or account cleanup. A removed message becomes an empty marker. Account deletion removes that account’s message content/pictures and closes its conversations; the other participant’s own messages remain. Copied report text, conversation/member references and moderation evidence can remain for safety review and lawful claims. The reviewed code has no automatic expiry for those reports or their access markers. A proposed 90-day picture-storage rule requires separate infrastructure configuration, so this policy does not promise automatic deletion at 90 days. Contact us for review or erasure of retained evidence; we will assess and explain any lawful limitation.
Apple purchase records are separate from the Google Play 400-day rule. In the reviewed iOS implementation, account deletion removes linked intents, private supporter records and rate counters, and replaces each linked Apple purchase record with a restricted transaction-derived hash key, account-deleted state and timestamp. It removes the user ID, transaction details and app-account token from that record. No automatic expiry for these replay-prevention markers is implemented; request review of retention through our contact form. Apple’s independently held records follow Apple’s practices.
8. Account deletion and privacy requests
Use Profile → Settings → Account → Manage data & account → Delete Account in the current app. Older versions may place Delete Account directly in Settings. Review the owned-group preview, follow the typed confirmation and choose Permanently Delete Account. “Clear all data” is a separate operation and does not itself delete the sign-in account. You may need to confirm a recent sign-in.
You can also submit full-account, specific-data or remaining-data requests on our Account & Data Deletion page, without installing or signing in to RunXRoam.
The supported server workflow checks owned groups before deletion, prevents new background work for the account, removes account-owned data and files, verifies cleanup, and deletes the authentication account last. It covers the account tree (including saved activities, GPX routes, health records, training calendar, private AI recovery data and saved AI conversations), profile media, follows, eligible community contributions, feedback, owned/shared references and supported connection credentials. Your direct-message content and pictures are removed while other people's messages and restricted safety evidence may remain. Source health records on your phone or provider are not deleted by removing an imported RunXRoam copy.
If a group you own has other members and no other administrator, deletion is blocked before cleanup. Promote another administrator or resolve/close the group, then retry. Where another administrator exists, supported ownership transfer allows the group to continue. A sole-member group can be closed.
A failed step can leave earlier data removed while the sign-in account still exists. The workflow does not roll changes back. A lost response means the outcome may be unknown; retry the supported check or contact us rather than assuming everything was restored. Maintenance verifies late writes after completion where the service is operating.
Limited information remains for defined purposes. The deletion marker is retained until cleanup is verified, then for 30 days after verification. Google Play purchase records are reduced to restricted, pseudonymous anti-reuse/refund records, without the account ID, account key or raw token, and scheduled for removal after 400 days. A hashed token or order reference is not treated as anonymous. Audit records may be de-identified; retired usernames stay reserved without an account owner; public catalog content, shared public statistics, safety evidence and independent provider records can follow their own applicable retention. See the deletion page for details and a further-review request.
We aim to respond to a verified and understood website request within 30 days, subject to applicable legal deadlines and any explained limitation. Uninstalling, signing out or deleting local files is not account deletion. Deletion does not refund a purchase, cancel a registration/order or erase records held independently by stores, organizers, health providers, Google or Apple.
9. Younger users and families
RunXRoam is for athletes of all ages, including younger athletes with appropriate parent or legal-guardian involvement. If you are under 18, ask your parent or guardian to read these documents with you, supervise your use and approve sharing and payments. Where applicable law requires verified parental authorization before collecting a child's information, do not submit that information until the required authorization has been arranged with us. Contact us before creating an account if this applies to your child.
The current app does not provide a verified parental-consent workflow or a dedicated child account with separate privacy defaults. A standard legal-agreement checkbox does not verify parental permission. Families should use private activity settings, keep birthdays hidden, avoid identifying home or school details, and review club and event audiences. These choices do not replace our legal obligations.
A parent or guardian can contact us to request information about a child's account, correction, restricted processing or deletion, subject to appropriate verification and the child's applicable rights. Report suspected unauthorized collection or unsafe contact so we can investigate and take appropriate action.
The optional AI assistant and AI training planner require a separate confirmation that you are 18 or older; they are not offered as a child coaching service. Do not bypass this confirmation. Parents and guardians should also review messaging audiences, picture sharing, location recordings and notification previews.
10. Changes and contact
We update this page and its version when our practices change. Material changes will be brought to your attention through appropriate service notices; we seek additional consent where required. You may contact Pixel Nomads about any part of this policy at the email and address below.