Privacy policy · Version 1.2 · October 23, 2026. Published by Ayhem Benabdennour.
DODGE US stores your chosen callsign, emoji, local identifier, blocked challenge/contributor IDs, saved challenges, movement recordings, preferences, course medals, daily records, city career statistics, unfinished runs, duel invitations/replies and personal bests on your device. The app does not require a separate DODGE US account. We do not operate a gameplay server or receive your names or recordings automatically. Version 1.2 can show a Google AdMob banner in History, subject to your privacy choices and ad availability. Advertising data use is described below. It does not request access to your contacts, location, microphone or photo library.
For the separate earlier rooftop friend mode, Apple’s Game Center handles match invitations and turn delivery. City Duels use manually shared files, as described below. The game submits the match data needed to continue play, including callsigns, emoji, movement recordings and scores, to Game Center. Other participants in a match can receive that data. Game Center requires an Apple Game Center account and a network connection. Apple processes Game Center data under its own privacy policy and account settings. We do not operate the Game Center service or receive those turns on our own server. Solo play and saved local arenas do not require Game Center.
New Supporter purchases are paused in version 1.2. Ads may appear in History for players without an existing Supporter entitlement. All gameplay remains free. People who bought Supporter earlier can restore that purchase in Settings using the Apple Account that made it. Apple processes payments and refunds; the app checks existing entitlements through StoreKit. We do not receive payment-card details.
Version 1.2 enables the History banner only when regional choices permit ad requests and iOS tracking authorization is granted. New Supporter purchases remain paused; existing ad-free entitlements can still be restored. Ads may be unavailable after a privacy choice, while offline, when Google has no suitable ad, or while consent information cannot be updated.
History can display a small Google AdMob banner for players who have not purchased Supporter. Availability depends on your privacy choices, network connection and ad availability. Ads do not appear during gameplay. Google’s advertising and consent services may process IP addresses (including approximate location derived from IP), app- or developer-bounded device identifiers, ads viewed and ad interactions, app interactions, crash reports, performance information and other diagnostics for ad delivery, fraud prevention, analytics and measurement. Approximate location, identifiers and interaction information may be associated with your device. Performance, crash and other diagnostic information is declared unlinked by the bundled SDK. The consent service uses approximate location, product interaction and performance information to provide consent and privacy-choice functionality. After regional choices allow ad requests, iOS may ask for permission to track across apps and websites. We do not start the Google advertising SDK or request a banner unless that permission is granted. If it is denied, restricted, unresolved or later revoked, gameplay continues without a banner. When permitted, we request non-personalized ads and disable publisher personalization and the optional publisher first-party identifier. Non-personalized ads can still use mobile identifiers for frequency capping and aggregate reporting. Regional consent messages are shown where required; available advertising privacy choices can be reopened in the app’s Settings. Solo routes do not require ads. If regional consent or iOS tracking authorization cannot be established, no ad is requested; a regional privacy form may need a choice before History resumes. Google and eligible advertising partners process advertising data under their own privacy policies and retention practices. The consent form provides partner details where applicable. See Google’s privacy policy and how Google uses information from apps. We do not send your chosen name, emoji or movement recordings to AdMob.
A challenge file or link contains curated contributor callsigns, emoji, local identifiers and movement recordings. Anyone who receives it can open or forward it. Callsigns are not verified identities. Older saved files can contain legacy names. City Duel invitations and replies are immutable .dodgecity files containing the course recipe, hazards, chosen identity, route recording and score needed to reproduce the challenge. You choose when and where to share each file; the app does not automatically deliver replies or notify a friend. Anyone with a copy may forward it. Older .dodge files and challenge links remain supported in their earlier modes. Game Center remains a separate option for earlier rooftop friend turns. The messaging or storage service you choose processes your shared content under its own policies.
You can prepare a report for an earlier Classic challenge or an advertisement from within the app. For an unwanted City Duel, use your messaging service to block the sender or contact support. A report is only sent if you send the prepared email or message. Challenge reports include local challenge/contributor identifiers, your selected reason and information you choose to add. We use reports and your reply address for support and safety review, not marketing. Reports are retained only as needed to resolve the issue and prevent repeated abuse; contact us to request deletion, subject to legal retention obligations. Blocks are stored on your device and can be undone in Settings. Local IDs are not verified, so also block unwanted senders in your messaging service.
The website host may process ordinary request data such as IP addresses, browser information and access times. This page is hosted using Cloudflare Pages. See Cloudflare’s privacy policy for information about the hosting provider. Movement data in a link fragment is processed locally by the browser and app rather than included in the ordinary HTTP request to this website.
You can remove earlier saved arenas from the Classic archive. You can delete individual saved new routes from History after any queued friend turn is resolved. Other new route history stays on your device until you remove it or uninstall the app. Removing the app removes its local app data, subject to any device backups you maintain. Deleting a local copy cannot delete copies already shared with other people.
Contact ayhembaappstore@gmail.com with privacy questions. If you choose to email us, we use the information you send to answer your request. Please share only what is needed for support. We do not add you to a marketing list.