Your route is yours.
Here's how data works.

Information we collect

Depending on how you use Dash, we may receive:

• Account details including your email address, account identifier, display name, username and optional avatar. If you use Google or Apple sign-in, we receive the identity token and the profile information supplied by that provider, such as your name and email address. Apple may supply a private relay email address instead of your personal address.
• Activity and location data from a Dash session, including the route needed to record and check an outdoor loop, distance, duration, pace, and the territory result.
• Private setup answers such as activity preferences, usual activity area, age range, gender, discovery source, and an optional phone number. These answers stay off your public profile and can be reviewed, changed, or cleared in Settings → About you.
• Notification information such as device push tokens, notification preferences, and delivery or interaction records needed to provide optional alerts.
• Technical information such as device and installation identifiers, operating system, app version, IP/network information, errors, and usage or performance data needed to operate and improve the service. See Providers and SDKs below.
• Messages you send us when you contact support or submit in-app feedback, along with your account identifier, app/build details and the information needed to respond. Issue feedback can include diagnostic logs; feedback about a run also includes its run reference and diagnostic context. Review the diagnostics option where offered and avoid putting sensitive information into your message.

How we use information

We use information to provide the Dash experience: record and display an activity, check whether a loop is eligible for capture, place captured territory on the shared map, maintain activity history, protect the service from abuse, troubleshoot problems, review abuse reports, and respond to support requests.

We may also use aggregated or de-identified information to understand reliability and improve Dash. We do not use your raw route history to sell advertising.

Photos and sharing

If you choose an avatar, Dash asks for photo-library access and uploads the image you select to Supabase storage. Avatars are public: they can appear on profiles and rankings and can be viewed by anyone with the image link. Selecting an avatar does not upload your entire photo library. You can choose a different image through profile setup.

When you save a run sticker, Dash creates the image on your device and requests photo-saving permission where required. Sharing opens your device's share sheet; the app or person you choose receives the image and any information visible in it. Review the sticker before sharing. Saving a sticker does not itself publish it to Dash's public map.

Community reports, blocks and review records

These disclosures describe the community-safety release. When you report a profile in that release, Dash stores your account identifier, the reported account identifier, the selected reason, the report time, the profile revision and a snapshot of its username, display name and avatar link. The snapshot helps an authorized reviewer assess what was reported even if the profile later changes. A report snapshot stores the avatar link, not a separate copy of the image.

Dash also stores who you block and when, your accepted terms version and acceptance time, publication status/revision, and a moderation audit containing the reviewed account, revision, decision, reviewer note and review time. This information supports visibility controls, review, abuse handling and the record of your agreement.

Reports, snapshots and review notes are stored in Supabase for authorized moderation operations; ordinary users cannot browse them, including the reported account. Your in-app blocked-user list and acceptance/publication status are readable by your own account. Your report is associated with your account, so it is not an anonymous report to Dash. These moderation records and personal block relationships are not included in the public website snapshot or the separate Discord bug-report alert.

Blocking hides the two accounts from each other's signed-in app profile, ranking and territory views. It does not make your public website-map presence private, stop all gameplay/notifications, or delete images already shared or cached. Profiles are active by default, and ordinary identity edits do not wait for moderator approval. The community-safety flow records acceptance before you use that flow and publish identity changes; older app versions keep their existing signup and editing flow until the account enters it. Reporting does not automatically hide a profile. Explicit moderator holds or suspensions limit its in-app visibility and remain in effect after edits; an uploaded avatar can still be accessible to someone with its public image link. The website snapshot does not use individual block lists. It excludes profiles on explicit moderator holds or suspensions, including their owned territory and ranking entries, when the next snapshot is successfully published. Normal profiles stay visible by default; a report by itself does not remove them. The usual six-hour refresh schedule and publishing/cache delays apply.

There is no automatic age-based expiry configured for community reports or review records in this release. Unblocking removes your block relationship; deletion of either involved profile removes its block relationships and reports involving it. Terms-acceptance and publication-status records are removed with their profile, and review-audit records are removed with the reviewed profile. Resolving a report records its outcome time without automatically deleting the report. Contact support with access or deletion questions.

Providers, SDKs and diagnostics

Dash uses third-party services and their software to deliver these features. Data is processed for the feature you use and, where described below, service analytics and reliability:

• Supabase handles sign-in, account and activity storage, uploaded avatars, feedback and backend processing. Private account and activity information is associated with your account.
• Google and Apple sign-in verify the account you choose. The Google sign-in SDK declares processing of profile/contact information, including name, email and phone number where available, approximate location, account/device identifiers and other usage information for sign-in functionality and analytics. This is separate from Dash's optional private setup phone field; Dash does not read your address book. Apple sign-in supplies an account identifier and the name/email information Apple makes available.
• Mapbox supplies maps in the app and website. Map requests expose your IP/network information and the map area requested. The installed mobile Mapbox SDK also declares approximate/precise location, SDK identifiers, interactions, usage, performance and diagnostic data for map functionality and analytics. Its manifest describes this SDK collection as not linked to your identity; routes and territory that you separately save to Dash are linked to your account.
• Expo, Apple and Google process push tokens, device/installation information and notification delivery data to send alerts you allow. Notification permissions can be changed in device settings.
• Cloudflare hosts the website, waitlist and public map snapshots and processes request/security information needed to serve and protect them. App Store and Google Play also process information under their own store policies when distributing Dash.
• Discord receives internal operational alerts and feedback summaries, including the message and app context of a bug report. Full diagnostic attachments stay in Supabase. The separate waitlist alert is described below.

Dash keeps diagnostic logs locally to help investigate problems. Logs can be attached when you submit feedback. We also record account-linked setup progress and app-open events on the backend for product analytics. These local logs are separate from the provider/SDK processing described above.

The current app does not use this data for cross-company advertising tracking or sell activity routes for advertising. Provider processing still occurs for sign-in, maps, notifications, analytics and reliability. You can review Google's privacy policy, Apple's privacy policy and Mapbox's privacy policy for their practices.

iOS launch waitlist

If you join the iOS waitlist, we store your email address, the signup time, and the version of your launch-email consent in Cloudflare. We use that address to notify you about the iOS launch; joining does not create a Dash app account.

To leave the waitlist or request deletion, email support@dashtofit.com from the address you used to sign up. We retain the entry until the launch notification is complete or you ask us to remove it.

Routes and visibility

A route recorded during an activity is different from the territory produced when an eligible loop is completed. Your display name, username, avatar, territory totals, ranking and other game progress can be visible to other people through public profiles and rankings. The website explorer publicly shows profile names, captured territory and territory rankings without requiring a login. It does not publish your email address, private setup answers or raw activity route. Because a map area may still reveal something about a place, take care when choosing where to start or finish.

Dash may process location while a session is active, including in the background if you grant the relevant device permission. Dash also uses location to center the nearby map when you allow it. You can change location access in your device settings; turning it off can prevent route recording or loop verification.

Your choices

• Review or change location and notification permissions in your device settings.
• Contact us to ask a question about information associated with your account.
• Delete your account in Settings → Delete account, or use the Delete account page for assistance.
• Stop using Dash and uninstall the app. Uninstalling by itself does not send a deletion request.

Retention, security, and providers

We keep information for as long as it is needed to provide Dash, maintain the game map and account, resolve disputes, prevent abuse, meet legal obligations, or protect our rights. When information is no longer needed, we take reasonable steps to delete or de-identify it. Some copies may remain temporarily in backups.

Dash uses reasonable technical and organizational safeguards, including encrypted connections and access controls. No internet service can promise absolute security.

Setup progress events are retained for 90 days and do not include the values of your private setup answers. The public website map uses sanitized snapshots; deleted account territory and name labels are removed when a new snapshot is published, normally on the six-hour refresh schedule. A delayed or failed refresh can extend that delay. Uploaded avatars and private route-preview files are removed as part of in-app account deletion; previously downloaded or shared copies may remain with their recipients.

Service providers process information for the purposes described above under their applicable terms and privacy protections. Contact us with questions about provider processing or deletion. See Delete account for the in-app steps and support fallback.

Contact us

Questions, access requests, or privacy concerns can be sent to support@dashtofit.com. For account deletion, use the dedicated request page so your request is easy to identify.

This page describes the current Dash experience and may be updated as the product changes. Check the “Last updated” date above for the latest version.