Set it before you move.
Choose destinations, download territories, select a vehicle, and configure the interface while parked. If something needs attention during a journey, stop safely or ask a passenger.
- Mount the phone where it does not obstruct the road or vehicle controls.
- Follow local laws for mobile-device and navigation use.
- Never handle the phone or chase map interactions while moving.
No speed-based territory scoring.
Road Zone claims use verified distance, repeat passes, and distinct days. Speed, fastest times, risky manoeuvres, and public-road racing are outside the scoring model.
Use only what the feature needs.
Navigation and verified journeys require location data. Local progress can stay on the device. When cloud features are enabled, the server can derive aggregate Road Zone contributions from an eligible journey so standings do not need to expose exact route points or live location.
Location permission can be reviewed or revoked through device settings. Some navigation and verification features will stop working without it.
Your key. Your scopes. Your choice.
Connected assistants are optional. A named-account driver must enable the Connected Assistant Bridge and create a separate, scoped API key before an integration can connect. While enabled, the selected assistant may receive live route geometry, destination, precise location, saved places, navigation, journey, and bounded device state only within its granted scopes, and can request only approved app actions.
Key and command activity is audited. Switching the bridge off aborts bridge traffic and, when the device can reach Driftistan, requests immediate deletion of its live assistant snapshot and cancellation of pending commands. Whether or not that cleanup request arrives, the server automatically deletes precise live device state after two minutes without a device heartbeat. Keys can be rotated or revoked at any time. The transparent HUD never receives the API key. Third-party assistants are provided and controlled by their own providers, not Driftistan; review that provider's privacy terms before connecting it.
Short samples. Clear consent.
Navigation Improvement Sampling is off by default. If a driver explicitly enables it, Driftistan may record one private 60-second sample no more than once every 12 hours, only while a destination and road route are active and the app is visible. It never runs continuously in the background.
A sample can include precise GPS coordinates, route geometry, destination context, timestamps, speed and accuracy, accepted and displayed positions, available gyroscope and orientation readings, fused heading, marker/camera timing, app version, platform, and bounded device user-agent information. We use it to reproduce and improve GPS, heading, map-follow, rerouting, provider latency, and device compatibility.
A coarse regional cell is derived from sampled GPS so we can compare navigation performance worldwide; the upload IP is not retained as training data. Samples are private, are not used for advertising or public profiles, and remain until the driver deletes the capture/account or an administrator deletes them. Garage media is excluded from navigation training.
How we use your data.
Does installation start tracking? No. Sampling requires a separate in-app opt-in.
When can it record? Only during active navigation, after a two-minute delay, for up to 60 seconds, no more than once per 12 hours, while Driftistan is visible.
Who can see it? Only authenticated engineering administrators. It never appears in profiles, leaderboards, crews, Road Heat, or advertising.
How do I stop or delete it? Disable Navigation Improvement Sampling in Settings to stop future samples. Delete the capture/account or request administrator deletion for stored samples.
What does Spotify access? Android presents a broad notification/Now Playing permission. Driftistan does not read notification content; it queries only Spotify's active local media session to show track metadata and send supported playback commands. Optional PKCE library access can display playlists, saved and recently played tracks, search results, and queue information, and can send a selected playlist or track to Spotify. Tokens and Spotify metadata stay on that device until you disconnect; they are not uploaded, backed up, profiled, or used for training. Driftistan never receives Spotify audio or your Spotify password.
Look beyond the car.
Before sharing a garage image, check number plates, faces, home addresses, documents, reflections, and location clues. The watermark identifies the Driftistan garage upload; it does not prove legal vehicle ownership.
Private first. Portable by choice.
A named account and automatic backup are optional. Private backups may include progression, journey history, saved places, personal Road Zones, Garage records, and processed watermarked photos. Offline packs, raw diagnostics, live presence, and unprocessed photos are excluded.
Public driver profiles are off by default. When enabled, they expose only aggregate verified distance, journeys, active days, average smoothness, and coarse Road Zone standing. They never expose routes, destinations, saved places, exact territories, speed, fastest times, diagnostics, or live location.