How we handle app data.

What we collect

Location data. When you record a trip or use Live Convoy, the app processes precise location to determine your route, distance, and convoy position. Location can be used while the app is running, and in the background while you are actively recording or while Live Convoy is active. Location is also used to back up your route when you’re signed in.

Live Convoy sharing. When you join a convoy, your live position is shared with the other members of that convoy. Sharing stops when you leave the convoy or when the trip ends.

Community Help and SOS alerts. When SOS alerts are enabled, the app shares your location while it is open so we can notify you about requests within 5 km. We retain only your latest approximate area, eligible for alerts for 15 minutes and removed by scheduled cleanup after it expires. You can separately opt in to background SOS availability: iOS uses Always location permission; Android uses a location service with an ongoing notification. Both keep that area up to date while the app is in the background. This is optional; SOS remains useful without it. Stop background SOS or turn SOS alerts off to remove the retained area. SOS push notifications contain no coordinates. Nearby drivers see an approximate request area; the requester approves a helper before sharing a precise location.

Account identifiers. If you sign in, we store your user ID and your email address (including Apple relay addresses when applicable) to run your account.

Profile content. If you add it, we store profile content such as your handle, vehicle name, and club affiliation, including a club logo image.

Saved Places and GPX waypoints. If you save a place or import GPX waypoints, we store the name, note, and coordinates as your content.

Photos you add. Trip photos and other images you choose to upload are stored as part of your content.

Feedback you submit. If you send feedback in the app, we receive your selected category, message, optional reply email and screenshots, account ID, platform, app version and OS version. Screenshots are optional; review them for personal information before sending. We use this information to investigate problems and respond to suggestions. Feedback messages, support replies, ticket status and the information listed above are stored privately in Supabase. Screenshots are stored in private storage and accessed through temporary links. You can view your tickets and our support replies in the app; they are not part of your public profile. Feedback is also sent to our support mailbox through Resend. We email support replies only to the optional contact address you explicitly provide; we do not infer a reply address from your account. Ticket records, replies and screenshots are retained for 12 months after the last ticket activity and removed when you delete your account. Separate delivery metadata is kept for up to 30 days to prevent duplicate messages and abuse. Mailbox correspondence is retained as needed to handle your request.

Trip summary aggregates. We store trip summary aggregates such as distance, desert km, duration, and max pitch/roll/G. Pitch and roll are recorded but not surfaced. Peak G may appear on trip proof.

On-device motion processing. Device motion (including G-force) is processed on device to compute trip aggregates. Raw motion sensor streams are not treated as user content.

Notifications. We store your notification inbox, read and archive status, category preferences, and an installation identifier associated with your account. If you allow push notifications, we also store a delivery token for your device. These records let us deliver account updates and keep your inbox consistent across devices. Push alerts include the message title and summary, which may appear on your lock screen according to your device settings.

Product analytics. The iOS and Android apps use Amplitude Analytics to understand how they are used and to improve their features. The apps send events such as app opens, screen views, leaderboard use, public profile and vehicle views, and Share Card/template usage. Events may include your DuneTraq account user ID, an Amplitude device identifier, app version, device and operating-system information, and event timestamps. We do not send trip GPS coordinates or Share Card images to Amplitude as part of this analytics instrumentation. On iOS, analytics events may be associated with your account user ID. Android analytics uses a device identifier and does not attach your account user ID or trip identifiers to events.

How we use it

We use the data listed above to record trips, show your history and proof, and power Live Convoy coordination. If you sign in, we use your account identifiers to keep your account and saved data working across devices.

DuneTraq is built for off-road tracking and coordination. DuneTraq offers optional peer-to-peer help requests to nearby drivers; it is not an emergency service and does not alert authorities or emergency services.

Sharing and Share Cards. Share Cards are designed to share trip proof and highlights. We do not place exact GPS coordinates on Share Cards. Cards are designed to show regions and proof, not a coordinate pin. Review what you share and avoid posting sensitive locations.

Service providers and maps

We use Supabase for account authentication, database services and storage of uploaded content. Our Supabase project is hosted in the Mumbai region (India).

Push notifications are delivered through Apple Push Notification service on iOS and Google Firebase Cloud Messaging on Android. These services process the device delivery token and notification payload to deliver your alerts. We use them for app notifications, not targeted advertising.

Maps are provided by Mapbox. Its SDK processes location, usage and diagnostic information to operate and improve its mapping services. This includes map interactions and performance information. You can control Mapbox telemetry through the information and attribution control on the map. See Mapbox’s privacy policy.

We use Amplitude, Inc. for product analytics. Analytics data may be processed and stored outside the United Arab Emirates, subject to the provider’s applicable security and data-processing terms. We use the service only for product measurement and improvement, not for targeted advertising or the sale of personal data. See Amplitude’s privacy notice.

Retention

We keep app data for as long as needed to provide the service, and for legitimate purposes such as safety, security, and preventing abuse. You can delete your account in the app. After deletion, some records may be retained for a limited time where required for legal compliance or to protect the platform.

Sale and advertising

We do not sell personal data. We do not share app data with third parties for targeted advertising.

Your choices and controls

You can control location and notification permissions in your device settings. In the notification inbox settings, you can choose which categories may send push alerts. You can mark notifications as read or clear your inbox; clearing it archives the entries rather than deleting their delivery history. Within the app, you can manage your trips and your account, and you can delete your account using the in-app deletion flow.

You may ask us to stop associating analytics events with your account or to delete analytics data connected to your account by contacting support. We will verify the request before acting on it.

If you believe a profile should be reviewed, use the in-app profile report flow.

Contact

DuneTraq is operated by Florian Kall.

Questions or requests (including deletion requests) can be sent to support@dunetraq.app.

The WhatsApp channel is broadcast-only for product updates: WhatsApp channel.

If you request account deletion via support, we may ask for verification to protect your data.

UAE privacy note: If you are located in the UAE, we handle personal data in line with applicable requirements, including providing access, correction, and deletion options through the app and support contact above.

Updates

We may update this policy as the app evolves. Material changes will be reflected here.