Support & privacy
What we collect: nothing.
Dirtstorm MX has no accounts, no advertising, no analytics SDK, no crash-reporting service, and no third-party data collection. The game runs offline and the runtime contains no outbound network path at all.
What lives on your device
| Data | Stored | Purpose | Your control |
|---|---|---|---|
| Career progress (credits, bikes, upgrades, records, sponsors) | Local save file on device | Offline progression | Delete app data — there is no account to manage |
| Time-trial best ghosts | Local save file, per layout | Best-line replay | Capped retention; delete app data |
| Audio levels, LOW FLASH, MOTION, bike and event selection | Device preferences | Remember your setup | In-game toggles |
Nothing leaves the device. The app requests no runtime permissions — no storage, contacts, location, microphone, camera, notifications, advertising ID, or account access.
Accessibility
Playable your way
Full control remapping, mirrored and assisted control profiles, tilt steering, scalable UI, and colour-safe cues that never rely on hue alone.
Comfort options
LOW FLASH for photosensitivity, MOTION reduction for camera and particle intensity, and caption support for rider callouts and race audio.
Honest assistance
Assists and cheats are labelled in-game and separated from competitive results, so an assisted run never masquerades as an unassisted record.
Reporting a problem
Playtest builds are covered by a short written protocol: what device you used, what you expected, what happened, and whether it repeats with the same inputs. That last part matters more than anything else, because it is what turns a bug report into a fix.
Send reports to [email protected] with your device model and the build you were running.
This page summarises the shipped data behaviour of Dirtstorm MX. It will be updated if that behaviour ever changes, and any change would be announced here first.