1. Who we are and what RunWars does
RunWars is a GPS running game for iOS, Android and the web. Outdoor runs are shown on a real-world map divided into hexagons. Eligible runs let players claim and defend territory, compete in battles and rankings, join teams and take part in social features. The mobile app records a route only when you start an activity and grant location permission. You may optionally import eligible workouts from services you connect. Location and health data are used for these game and activity features, not for medical diagnosis or advertising.
RunWars operates the app and website at runwars.app. For privacy requests, contact support@runwars.app.
2. Information we process
Account, sign-in and profile
We process your RunWars account identifier, email address, username, language, profile fields and settings. You may add a name or profile photo. Sign-in may use email and password or Google or Apple through Firebase Authentication. Firebase handles the sign-in credentials; RunWars receives the account information and authentication token needed to provide the service.
Runs, location and fitness information
For an activity recorded in the app, the device records GPS route points while tracking is active. Depending on device permissions and sensor availability, these can include latitude and longitude, time, altitude, speed and accuracy. We use them to calculate route, distance, duration, pace, elevation and map hexagons, validate eligible activities and operate game features. Location used for nearby or map features is processed when you use those features. The app does not need continuous background location outside an activity.
For an activity imported from a connected service, we process the workout data that service makes available and that RunWars needs to validate and display the activity, such as activity type, start/end time, duration, distance, summary metrics and, where available and authorized, GPS route points. We do not need unrelated health records such as sleep or nutrition for the running game.
Optional activity connections
You choose whether to connect Strava, Garmin, Suunto, Polar, COROS, Google Health, Apple Health or Android Health Connect where the connection is available on your device and in your app version. Cloud providers use their authorization flow; Apple Health and Health Connect use the device's health permissions. We process eligible running and walking workouts and route information to import activities into RunWars. Available data varies by provider and by the permissions you grant.
Garmin Connect: if you connect Garmin Connect and grant Activity Export, RunWars receives eligible activity details, including GPS route samples, activity type, time and metrics, plus the device model when supplied. We use these data to validate and display the activity and calculate RunWars game results. Garmin OAuth credentials are stored encrypted on our backend. You can disconnect Garmin in the app to stop future imports; this does not delete activities already imported into RunWars. You can delete imported activities or request account deletion using the controls described below. Garmin activity data and information derived from it are not used to train, test, evaluate, benchmark, improve or develop AI models or systems.
Google Health: the app requests only https://www.googleapis.com/auth/googlehealth.activity_and_fitness.readonly and https://www.googleapis.com/auth/googlehealth.location.readonly. The first is used to find and read eligible exercise sessions and their activity metrics. The second is used to retrieve the GPS route for an eligible session when one is available. Both are read-only; RunWars does not write health data to Google Health. We use the data to import a run, validate it and calculate its route and territory in RunWars. We do not sell Google Health data, use it for advertising, or use it to diagnose health conditions. The Google authorization code is sent to our backend; provider access and refresh tokens are encrypted in backend storage and used to retrieve or refresh the permitted workout data. Disconnect Google Health in the app to stop future access. Disconnecting does not itself delete activities already imported into RunWars; delete those activities or your account separately. Google Health data is handled only to provide or improve user-facing fitness features, consistent with the applicable Google Health API and Google user-data policies.
Provider connections are separate from Google or Apple sign-in to your RunWars account. Disconnecting a provider in RunWars stops future synchronization and removes its stored connection; it does not delete your account at that provider.
Social, team and user-submitted information
If you use social or team features, we process the information you submit or create: profile and team details, follows, reactions, comments, messages, invitations, challenges, shared content and participation records. We use this information to operate those features, keep teams and conversations working, prevent abuse and show relevant activity to other participants.
Notifications, app diagnostics and optional analytics
If you enable push notifications, we process a Firebase Cloud Messaging token and relevant app/device information to deliver notifications. You can disable notifications in the app or your device settings.
If analytics is enabled for your app version and you explicitly consent using the in-app Analytics control, Firebase Analytics may process app events and screens, device/app information, provider connection outcomes, whether you have an accepted activity, and timing metrics about when an accepted activity was first recorded or observed by the app. Analytics events may be associated with your internal RunWars account identifier to measure account-level journeys. Imported activities are only reported when you next open the app with analytics enabled. You can withdraw consent using that control; collection is then disabled and the analytics user association is cleared. We do not send raw GPS route points, exact activity dates or hexagon IDs to Firebase Analytics. Analytics is not used for ad targeting.
We use Sentry, when configured, to diagnose crashes, errors and performance issues. Diagnostic events may include technical details, app version and context needed to investigate a failure. Default personal-data collection is disabled, but after sign-in an event may be associated with your internal RunWars identifier and username for troubleshooting. Diagnostic processing is separate from optional analytics.
Payments and website preferences
If you buy a subscription or other paid feature, the relevant payment provider (such as Apple App Store, Google Play or Stripe, depending on the purchase flow) handles payment credentials. RunWars processes transaction, subscription, product and account references needed to verify purchases, manage access, billing support and refunds. We do not receive full card details handled by the payment provider.
The website uses essential browser storage to remember your language or cookie preference where applicable. The marketing site does not use tracking cookies. This statement does not describe third-party services' own websites or apps.
Information stored on your device
The app may keep session credentials in secure device storage, and cache your profile, activities, route points, sync status and pending actions for offline operation. This local copy remains under your device's storage controls and may require you to sign out, clear app data or uninstall the app to remove it.
3. How other people can see your information
RunWars uses activity summaries and affected hexagons in shared gameplay. Depending on the feature and your profile settings, other users may see your username, profile photo or public profile details, team and social activity, activity summaries, rankings, challenges and the hexagons your run affected. For Garmin-imported activities, the source attribution “Garmin [device model]” (or “Garmin” if the model is unavailable) appears with the activity data. Hexagons show approximate areas and can reveal general places where you run. We do not make your exact GPS track or exact activity start time visible to other users as part of the shared activity view. Information you choose to post in a team, conversation or other shared feature is visible to its intended participants.
4. Why we use information
- To create and secure accounts, authenticate users and provide the app and website.
- To record or import workouts, calculate activity metrics and routes, validate activities and run the map, territory, battle, team, ranking and social features.
- To synchronize activities, maintain connected provider access, and process provider notifications.
- To deliver notifications you enable, provide customer support, investigate errors, protect the service and prevent fraud or abuse.
- To measure app use through optional analytics only when enabled and consented to.
- To verify and manage purchases and subscriptions.
5. Legal grounds
Where data-protection law requires a legal basis, we process account and activity data to provide the features you request and perform our agreement with you; provider connections, device permissions and notifications on the basis of your choice or consent as applicable; and health data only with your specific permission/consent for the selected fitness features; optional analytics only when you consent; payment records to perform the purchase and meet legal obligations; and security, service reliability and fraud-prevention information for our legitimate interests, balanced against your rights.
6. Who receives information
We do not sell personal information. We share only what is needed with:
- Firebase / Google: account authentication, push delivery and, only when enabled and consented, Firebase Analytics. Google Health receives OAuth authorization requests; RunWars reads only the Google Health data described above.
- Connected activity services: Strava, Garmin, Suunto, Polar, COROS, Google Health, Apple Health or Health Connect, as applicable, to authorize and retrieve the activity data you request. For Garmin, RunWars uses Activity Export data for activity validation, display and game features, preserves Garmin attribution with the data, and does not use Garmin data for AI training or improvement. Their own privacy terms also apply.
- Sentry: error and performance diagnostics when configured.
- Payment providers: Apple, Google or Stripe, as applicable, to process or verify purchases and subscriptions.
- Hosting and infrastructure providers: providers that store and deliver the website, app backend, database and queued notifications on our behalf.
- Other RunWars users: only the profile, activity summaries, game state or content exposed by the social/team feature you use, as described above.
We may also disclose information where required by law, to protect users or the service, or as part of a corporate transaction with appropriate safeguards.
7. Retention and deletion
We keep account and service information while your account is active and as needed to provide the service, meet legal obligations, resolve disputes and protect the service. Raw, detailed GPS track points are automatically purged after 180 days; activity summaries, simplified routes, hexagon/game results and shared records may remain while your account is active. Some shared game history may remain in de-identified form after account deletion. Operational backups expire under the backup-retention process; deletion records may be reapplied if a backup is restored.
You can request account deletion in the app under Profile > Delete account, or use the account and data deletion instructions if you cannot access the app. Deletion removes or unlinks your account, profile, linked provider tokens, activities and associated personal records as described on that page. Certain shared, anonymized or legally required records may remain. Deleting RunWars does not delete your Google, Apple, Strava or other provider account, and you may need to revoke the connection with that provider separately. Logging out or uninstalling removes or limits local app data but does not by itself delete server data.
8. Your choices and rights
You can choose whether to grant location, health, notification and provider permissions; disconnect integrations; change profile information; control analytics consent; and delete your account. Depending on your location and applicable law, you may have rights to access, correct, erase, restrict or object to processing, and receive or transfer certain data. Contact support@runwars.app to exercise a right or ask a privacy question. You may also complain to your data-protection authority; in Spain, this is the Spanish Data Protection Agency (AEPD).
9. Security and international processing
We use technical and organizational safeguards appropriate to the information we handle. OAuth provider credentials are encrypted in backend storage and transmitted to our services over HTTPS. No internet service can guarantee absolute security. Our service providers may process information in countries outside your own; where required, appropriate transfer safeguards apply. Contact us for more information about a particular transfer.
10. Children
RunWars is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us so we can review and delete it where appropriate.
11. Changes and contact
We may update this policy when our service or legal requirements change. We will update the date above and provide additional notice for material changes where required. For privacy questions or requests, contact the RunWars privacy team at support@runwars.app.