Effective: November 2, 2026. Developer/publisher: AntnyGamer.
Road Conquest collects precise location data to record driven roads and reveal visited places, including in the background when automatic tracking is enabled and the app is closed or not in use. It also uses location to display your live map position. Local driving history, explored places, points and cosmetics are stored on your device unless you export them. Optional cloud account and forum data are handled separately as described below.
Road matching for new roads sends bounded GPS coordinate batches, timestamps and accuracy through Road Conquest's Cloudflare map proxy to Geoapify, or to LocationIQ when Geoapify is unavailable or its allowance is exhausted. See LocationIQ's privacy policy. Repeat drives on previously saved roads may be recognized on-device without a network request. The map proxy processes matching coordinates transiently and does not retain GPS traces. It stores daily request totals, daily keyed client-address fingerprints and random matching-attempt identifiers to enforce separate free allowances and avoid counting unsent work. Those daily records are deleted when a later day's requests are processed. Short provider-availability records contain no coordinates or raw client addresses. Expired records are pruned during later activity. OpenFreeMap and Esri provide map display data. Geoapify supplies backup street-map tiles. Map providers receive requests for areas you view. While the map is visible or the tracking foreground service remains active in the background, bounded discovery workers may send saved coordinates to Android's system geocoder for place names and to U.S. Census TIGERweb to verify the exact municipality visited. Outside the U.S., place names may be sent to the configured OpenStreetMap boundary service. Country and region overlays can fall back to public geoBoundaries datasets, selected by country code without sending GPS coordinates to geoBoundaries. Enabling place overlays downloads and locally caches public boundaries for discovered places.
Optional Firebase Crashlytics reporting is off by default and enabled only after you enable Share crash reports in Settings. When enabled, Google receives crash stack traces, app/device and operating-system information, diagnostic events and installation identifiers. Road Conquest does not attach saved routes, GPS history, usernames, passwords or session tokens, and does not include Google Analytics. Turning reporting off stops automatic reports and requests deletion of unsent reports on the device. See Firebase privacy information for Google's handling of reports already sent.
Friend-request notifications and weekly challenge reminders are on by default unless you have already turned them off in Settings. Occasional friend forum-post notifications are also on by default unless previously disabled and can be controlled independently. At most one friend-post alert is attempted per recipient in seven days. Only roughly one in four approved new posts is considered, and blocked accounts are excluded. Both server push types require sign-in and Android notification permission. Weekly reminders work locally. When at least one server-delivered friend notification category is enabled and these requirements are met, the app initializes Firebase Cloud Messaging and shares a Firebase Installation ID with Google and the Road Conquest account service. The server encrypts the token and binds it to the current login session. Logout, account deletion or disabling both server push categories removes that session's registration. Logout preserves your saved notification choice. Device registrations expire after 30 days without refresh. Google receives only a generic friend-request or friend-post event and a random device binding, without usernames, passwords, Road Conquest session tokens or GPS. The phone checks the current setting, permission and account binding before showing a notification. Firebase may process device, app and installation information to deliver messages. Notifications do not enable crash reports. Weekly challenge reminders are scheduled locally without Firebase or a cloud account. You can turn all three notification categories off independently in Settings.
The app downloads public provider availability switches from Cloudflare. These switches contain no personal data and cannot change road-verification rules or service URLs. UptimeRobot checks public service health endpoints and alerts the developer to outages. These monitoring requests contain no player account or driving data.
Optional Road Conquest accounts send your username and password over HTTPS for signup/login. Passwords are salted and scrypt-hashed on the server and are not stored in plaintext. Android stores an encrypted session token. If you explicitly enable verified scoring, live non-mock GPS evidence and Google Play Integrity evidence are sent to the Road Conquest account service to verify visits to the app's exploration cells and award leaderboard credit. Ordinary local driving history is not uploaded for leaderboard scoring.
Road Conquest uses Google AdMob for banner ads on the Garage, Achievements, Leaderboards, and Settings screens, and optional rewarded ads in the Garage. The Google Mobile Ads SDK can collect and share IP addresses (which may estimate general location), device or account identifiers such as the advertising ID and app-set ID, app and ad interactions, and diagnostics for advertising, analytics, and fraud prevention. Google encrypts these transmissions in transit. Road Conquest does not pass recorded routes, GPS coordinates, or Road Conquest account credentials to its ad requests.
Where required, Google's User Messaging Platform presents privacy choices before ads can load. You can reopen applicable choices using Ad privacy choices on these screens. The driving map has no ads. Rewarded ads are voluntary: the Garage shows the point reward before playback, and a completed ad earns local points only after the ad SDK confirms the reward. See Google's Privacy Policy for Google's data practices.
Community posts, GIF links, reactions and usernames are public, including when your leaderboard profile is hidden. Posting requires an account and agreement to the community rules. Private driving history is not automatically shared. Text and a preview containing all GIF frames are sent to OpenAI for automated moderation. GIFs load directly from Giphy or Tenor. Those services receive media requests. Automation can make mistakes. Reports and appeals can be reviewed by project moderators.
The forum stores posts, reactions, reports, blocked-account choices, rules acceptance, a posting cooldown and moderation penalties until account deletion. Removed or deleted posts have their text and GIF link erased immediately. A submission fingerprint and moderation categories remain to prevent duplicate penalties. Moderator actions and penalties affect forum participation only.
Forum Plus is an optional, one-time Google Play purchase tied to your Road Conquest account. The server verifies and acknowledges the purchase with Google, storing a keyed account identifier, a purchase-token fingerprint, an encrypted token and entitlement state. Authenticated Google notifications update refunded purchases. Notification IDs expire after 30 days during subsequent notification activity. Deleting the account deletes these records and its Forum Plus access. The optional Buy Me a Coffee support link opens an external site and grants no app benefits.
Competitive accounts count only server-verified exploration cells. Private visited-cell identifiers and weekly cell counts are stored until account deletion. These identifiers describe coarse geographic areas. Older totals and imported or local progress cannot enter hardened rankings. For anti-cheating continuity, the account service keeps one latest accepted GPS fix encrypted with an account-bound server key, plus its timestamp and keyed fingerprint. It is replaced by the next accepted batch and removed with account deletion. Full GPS traces are processed transiently for verification rather than stored in the ranking database.
The Export progress control offers two choices. Secure backups are encrypted and authenticated with AES-256-GCM and saved to a user-chosen .rcbackup file. The app requests a per-account encryption key over HTTPS, requiring an active Road Conquest session; only the key is delivered, not the backup contents or GPS history. The same account and network connection are required to restore; deleting the account or losing a configured backup master key version prevents recovery. The keyring is separate from the account password pepper and must be kept through rotations. A separate password-free readable ZIP contains CSV tables and metadata, including precise GPS history, for external inspection or analysis. It is not encrypted and cannot be imported or restored into Road Conquest. Exported files remain where the user saves them and are not automatically sent to cloud storage. Retired Play-signed ZIP and passphrase-encrypted backup files are no longer supported. Local pre-restore recovery ZIPs use an installation-bound authentication key. Treat readable exports as sensitive and share them only intentionally. Restored history, including delayed road matching and place discovery, cannot earn new weekly challenge credit or change global or friend verified rankings. Previously earned local rewards remain part of restored history. Importing an authenticated backup validates and replaces local progress without uploading that history for verified scores. Before replacement, the app keeps one private recovery ZIP on this phone. Delete all data and uninstalling remove this recovery copy. Google Play VIP ownership and account credentials are not imported. Weekly local challenges award local points. Accepted friends can compare newly verified exploration cells each week. Friendships require consent, may be removed by either person, and are deleted with the account. Hiding a profile hides it from friend rankings as well as public leaderboards. Weekly verified totals remain with the account until account deletion.
Local app data remains on your device until you use Delete all data, uninstall the app, or otherwise clear app storage. Delete all data requires typing the exact in-app confirmation phrase and removes local Road Conquest data while keeping the cloud account and leaderboard scores. It does not require account sign-in or network access. Exported files are controlled by you and must be deleted separately. Delete account requires the current account password and removes the cloud account, forum data and Forum Plus access, sessions, leaderboard scores, visited-cell and legacy verified-road records, live runs, and verification receipts while leaving saved device history in place. Some short-lived anti-abuse and verification records expire automatically.
Network account traffic uses HTTPS. You can use Road Conquest without an account, hide yourself from leaderboards, leave verified-drive sharing off, use manual tracking, export your data, delete only your cloud account, or delete all local Road Conquest data while keeping your account.
For privacy questions, use the Road Conquest project's GitHub Issues page. Do not post passwords, precise location history, session tokens, or other sensitive information in a public issue.
Delete a Road Conquest account