← DashTrack Pro
DashTrack Pro

Privacy Policy

Effective date: October 12, 2026
Last updated: November 6, 2026

DashTrack Pro is a shift, earnings, mileage, and tax-estimate tracker for independent delivery drivers. This policy describes information practices in supported versions, including expense-vault and smart delivery planner features introduced in 1.4.0 and optional active-shift GPS estimates in supported Android GPS-capable builds (1.5.0 and later). It also covers optional Google Play subscriptions prepared for the Android 1.11.0 production release. The advertising section applies to Android sample-only builds (1.6.2 and later), not 1.6.1 or older ad-free builds. Features depend on the installed version and operating system; publishing this policy does not confirm that a production release is already available. Older builds without GPS support do not request location permission.

Information you enter in the app

DashTrack Pro lets you choose to enter and store information about your work, including:

The app calculates summaries and tax-export information from the records you enter. On supported Android builds, optional GPS distance estimates can also update the active shift's live vehicle-cost and profit estimates as described below; GPS coordinates are not part of your financial records or exports.

How your information is stored and used

Your shift records and preferences are stored in a database on your device. The app uses them only to provide its tracking, calculation, insight, backup, and tax-export features. Optional Android GPS tracking keeps a separate, small app-private summary, described below; it does not create a DashTrack cloud account.

The app does not send your shift records or odometer photos to DashTrack Pro servers. Builds before 1.6.5 do not offer sign-in accounts. Optional email/password accounts are described below for account-enabled Android builds (1.6.5 and later); they do not provide cloud synchronization or paid subscriptions. A manually logged subscription expense is just a record, not a purchase. Android 1.6.1 and older builds do not request or display advertisements. Android 1.6.2 and later sample-only builds include optional sample-banner testing, described below; it does not enable live, revenue-generating ads. Third-party SDK data practices are separate from your local work records.

Optional sign-in accounts (account-enabled Android 1.6.5 and later)

This section applies only when accounts are enabled in your installed build. Earlier builds and builds with accounts disabled do not offer this account service. Account availability is not an announcement of a public app release. Core tracking remains available without an account.

If you choose Connect account service in Driver settings, DashTrack connects to Google Firebase Authentication. You can create an email/password account, sign in, request verification or password-reset emails, sign out, or delete your sign-in account. These online requests require internet access. After connection, Firebase may maintain and refresh the login session while its SDK is active.

Firebase processes the email address and authentication credentials you provide, a generated account identifier, and service/security information such as IP addresses and user-agent information for authentication, account management and abuse prevention. These are not delivery-platform credentials. DashTrack does not request access to your DoorDash, Uber Eats, Grubhub or Instacart accounts. This account feature does not initialize Firebase Analytics or send work records to Firebase.

Passwords are sent to Firebase over HTTPS. DashTrack does not store your raw password in its device database, saved settings, exports, logs or backups. Authentication tokens used to remember the login session are kept in encrypted native device storage. That session storage is excluded from DashTrack JSON backups and from this feature's Android cloud-backup/device-transfer rules. Removing app cache can require signing in again. This does not add encryption to the separate work-record database or exported backups, and no system is completely secure.

Signing in does not upload or synchronize shifts, mileage, GPS coordinates, receipts, notes, earnings, plans or settings. Work records are shared by this app installation, not separated into private driver profiles. Signing out or switching accounts does not hide, switch or delete them; another person using this installation can still view them. Continue saving private JSON backups outside the app if needed. Account creation does not buy or unlock premium, start a trial, enable live ads or activate billing.

While parked with no active shift, open Driver settings → Account → Delete account to delete the sign-in account. The app requires your current password and a confirmation. This removes the Firebase login account, not the device-only work records or previously exported copies. You can delete records separately in DashTrack or clear local app data in device settings; export anything you need first.

You can also request account deletion without reinstalling or opening the app through our Account deletion page. We verify account ownership before completing a manual request. Never send a password, recovery link or verification code. Support messages are handled by our email provider as described below. DashTrack support cannot remotely access or erase your device-only records.

Google's Firebase documentation describes authentication processing in the United States, service/security retention, and removal from live and backup systems following deletion. Deleting a login account does not mean every Google log or backup disappears immediately. See Firebase Privacy and Security for current processing and retention information.

Authorized app-review access

Supported versions of the prepared Android 1.11.0 release can give a designated Google Play review account free access to premium tools. This is separate from a purchase, trial or paid subscription. Ordinary account creation or an email address alone does not grant it; an administrator must authorize the account through a Firebase Authentication custom claim.

After explicitly connecting the account service and signing in, choosing Driver settings → Account → Review access → Check review access refreshes that account's Firebase ID token online and checks its account identifier and review role. Opening this panel does not itself connect Firebase or make the review check. This check does not send work records to Firebase, attach your Firebase identity to RevenueCat, or start payment processing.

The app keeps the review authorization only in memory, tied to the current sign-in session, for no more than one hour. Reopening the app or expiry can require another explicit online check. Signing out, changing the sign-in session, or a failed fresh authorization check removes this access. An administrator's role removal is recognized on the next fresh check or when the existing authorization expires; it is not an immediate remote logout. Deleting the Firebase account removes its review role. None of these actions cancels a separate Google Play subscription or deletes local work records.

Google Play subscriptions and RevenueCat

Version scope: Optional Google Play subscriptions and RevenueCat connections are prepared for the Android 1.11.0 production release. Designated free beta builds keep paid subscriptions and RevenueCat connections disabled. Availability depends on the installed build and its release status; this notice does not confirm that the production release is already available. Reading this policy, creating a sign-in account or using a free beta preview does not start a subscription or a charge.

In a billing-enabled version, choosing Connect subscription status, Restore existing purchases or Load Google Play plans connects RevenueCat to verify Google Play premium access. Before your first explicit connection, opening the app or displaying the Remember billing connection checkbox does not initialize or call RevenueCat. When no choice has been saved, the checkbox starts on. Leaving it on saves permission to reconnect after a successful explicit action. A saved off choice stays off when you connect, restore or load plans manually; you must turn it on yourself to remember a connection again. Turning it on yourself also permits a connection now, when the app is in a safe foreground state.

With a saved on choice, DashTrack can reconnect and refresh subscription status after you reopen the app in a safe foreground state, including read-only status refresh during an active shift. Plan loading, checkout and restore remain blocked during an active shift. This choice stores only an on/off value in encrypted Android device storage. It is not a premium entitlement or a stored customer, transaction or work record. It is not uploaded to Firebase or included in DashTrack manual/cloud backups or Android cloud backup/device transfer. Premium access still requires store verification.

Turning Remember billing connection off stops DashTrack's own automatic reconnection and status checks. It does not cancel a Google Play subscription, delete RevenueCat records or shut down an already configured RevenueCat SDK. You can still request a connection, refresh, restore or plans manually. The SDK can perform its own lifecycle requests while active, so turning this choice off is not a promise that all SDK network traffic stops.

RevenueCat processes a randomly generated app-user identifier, purchase tokens and subscription/transaction information, and technical device/app information. These records support access verification, restoration, subscription operations and related purchase analytics. Requests use encrypted HTTPS. Connection is not limited to a single request or one app session when the remembered choice is on.

Google Play handles payment details; DashTrack does not receive your payment card number. This integration does not send shift earnings, work logs, GPS routes, receipt photos or Firebase email/account ID as RevenueCat subscriber attributes. RevenueCat's subscriber identity is separate from the optional Firebase email sign-in account. Core tracking can be used without connecting billing. Optional SDK diagnostics, automatic device-identifier collection and automatic in-app messages are disabled; this does not eliminate the service's required identifier and transaction processing.

RevenueCat retains customer and transaction information to operate and support subscriptions, subject to its applicable service, security and legal retention requirements. To request deletion of DashTrack's RevenueCat customer records, contact dashtrackpro@gmail.com; support must verify ownership and locate the correct subscriber record. Firebase account deletion does not automatically identify or delete that separate record. Google may retain purchase information under its own requirements. A later connection, purchase or restore may create customer records again. See RevenueCat's privacy information and our subscription-data deletion instructions.

Uninstalling DashTrack, deleting local records or deleting a Firebase/RevenueCat account does not cancel a Google Play subscription. Manage or cancel in Google Play. See the subscription terms for pricing, renewal, restoration and refund information.

Premium access, beta previews and demo benchmarks

Designated free beta builds can include a premium-feature preview and a local testing switch without billing or automatic trial charges. That preview is not a purchased subscription and is not transferred as an entitlement through backups. The prepared Android 1.11.0 production release does not include the free beta-preview switch: paid premium access requires verified Google Play subscription status. Core tracking and access to existing saved records remain available without a subscription. Turning off a beta preview or losing premium access does not delete saved work records.

Community benchmarks are clearly labeled synthetic demonstration data, not real nearby drivers. The region and app-combination choices select a local demo; they do not access your location or request regional records from a server. Personal comparison metrics are calculated on your device, and the app does not upload them or create a public profile. Peak-pay plans are local notes, not delivery-app bookings or calendar events. Historical estimates and deduction worksheets are not promises of earnings or tax savings.

Optional test advertising (Android sample-only builds)

Android 1.6.2 and later sample-only builds include Google's Mobile Ads and User Messaging Platform (UMP) SDKs. This section does not apply to older builds without the ad-serving SDK. Only Google's sample banner is used: it is labeled as a test advertisement and earns no revenue. There are no full-screen, pop-up or rewarded ads. In designated free beta builds, premium preview may start on by default; turn it off to test free mode. In free mode, choose Load test ad in Insights while parked. The app does not automatically request a banner on launch or navigation. It suppresses banners during active shifts, background use, open forms, the keyboard and busy operations.

Google documents SDK processing of IP addresses (which can imply a general location), device/account identifiers, app/ad interactions and diagnostics for advertising, analytics and fraud prevention. The Android 1.6.2 test configuration removes the advertising-ID permission to prevent Android advertising-ID collection; this does not eliminate app set ID or all other identifiers. Google states its SDK data is encrypted in transit. Sample or non-personalized ads do not mean zero data processing. See Google's Mobile Ads data disclosure.

DashTrack does not provide shift records, earnings, odometer readings, delivery zones, notes, photos, receipts or precise GPS coordinates as ad-targeting parameters. Network-derived general location is separate from active-shift GPS tracking. Core records remain on your device unless you explicitly export or share them. Premium mode prevents new banner requests, but does not remove the native SDK, guarantee zero SDK startup processing, erase earlier Google data, or prevent a privacy-options request you explicitly make.

Before the app initializes ads or loads a banner, it asks UMP for current privacy information and displays a consent form when required. If UMP does not permit ad requests, the banner is not loaded. You can use Ad privacy options in Insights when Google requires that option, including after returning to premium mode; finish any active shift and close forms first. Non-personalized ads may still require consent. Ad or consent failures do not block manual tracking, saved records or exports. Google and applicable regional privacy messages control the choices offered; a test banner is not proof that every region's consent setup is complete.

Google's services have their own retention practices and controls. Local deletion does not delete information already held by Google. See Google's Privacy Policy, Google's ad controls and your device's advertising-ID settings. Contact DashTrack support below for questions about this integration.

Optional active-shift GPS estimates (Android)

On supported Android GPS-capable builds (1.5.0 and later), you can explicitly enable GPS mileage estimates during an active shift. Before requesting location permission, DashTrack explains this feature in the app. It uses precise device location to estimate distance and update live fuel-cost and net-profit estimates. Tracking can continue in the background while you use another app or the screen is off through an Android location foreground service, with an ongoing tracking notification and Pause/Stop controls. Manual mileage entry remains available if you decline or stop tracking.

The supported Android build requests approximate and precise location permissions together and requires precise location, device location services, and enabled tracking notifications to start or resume. On Android 13 and later, this includes the notification runtime permission. The build declares the permissions for a location-type foreground service; it does not request Android's separate always-allow background-location permission. This does not mean location use stops whenever DashTrack is minimized: a service you explicitly started may continue as described above.

DashTrack processes successive location fixes on your device using Android's native location APIs, without adding a location advertising SDK or account. Only the recent coordinates needed to compare fixes are held transiently in memory, and they are cleared when the GPS segment is paused or stopped. DashTrack does not save a route history, place coordinates in backups or tax exports, or upload GPS positions to DashTrack servers. It does not sell GPS positions or use them for advertising, peer rankings, live delivery-platform demand, or real-time delivery-app offers. Device location providers and operating-system services have their own settings and privacy practices. Existing SDK diagnostics are described separately below.

A small app-private summary stores the shift identity, saved mileage baselines, estimated distance, tracking state and session controls, timestamps, and fix/gap counters. It is not a route record and contains no coordinates. DashTrack does not add separate encryption to this summary. It is excluded from DashTrack JSON backups, and the app's Android backup rules exclude its preference file from cloud backup and device-to-device transfer. Other app records remain subject to the app's existing export and device-backup behavior.

GPS starts or resumes only through your explicit action in the visible app during an active shift; restoring records, receiving reminders, rebooting, or reopening the app does not start or resume it. Reviewing the end of a shift pauses GPS, and completing or deleting an active shift stops it. If you cancel the end review and continue driving, you must explicitly resume GPS. Removing the app task, stopping its process, or rebooting may interrupt tracking; the app does not silently restart the service. Permission changes or disabled tracking notifications can pause tracking.

Stopping GPS retains its single local summary for mileage review. After the shift is successfully saved as complete or deleted, the app attempts to clear that summary; if clearing fails, it reports that the stopped summary remains. When the app reconciles its records, it attempts to stop and clear a summary that does not belong to the current active shift, and reports reconciliation failures. Explicitly enabling a new GPS segment replaces a stopped summary and may carry forward the previous live distance estimate as a baseline. It does not grant consent for a different shift. Clearing app data or deleting the app removes the device-local summary.

Signal quality, tunnels, permission changes, battery settings, and operating-system interruptions can cause missing or inaccurate estimates. DashTrack filters unsuitable fixes and flags gaps rather than guessing the missing distance. GPS mileage is an estimate, not an actual odometer reading, proof of deductible business travel, or a measure of fuel burned while idling. When finishing a GPS-tracked shift, enter the actual ending odometer and review business miles, excluding personal and commuting travel. GPS estimates do not automatically replace confirmed odometer readings, tax records, or earnings.

Odometer photos and text recognition

When you choose Scan odometer photo, the app requests camera permission and opens the camera. It processes the photo on your device to suggest an editable mileage reading. You must confirm the reading; the scan does not automatically save a shift. Photos are kept temporarily in the app cache, may remain until the operating system clears the cache, and are not included in backups or tax exports. DashTrack does not upload these photos.

Android uses Google's bundled ML Kit text-recognition SDK. Google documents collection of device/app information, per-installation identifiers, and performance, configuration, input/output size, event and error metrics for diagnostics and usage analytics. This SDK telemetry is distinct from your locally processed photo and shift records. See Google's ML Kit data disclosure. iOS uses Apple's on-device Vision framework. Camera scanning is optional; manual mileage entry remains available.

Optional expense receipts and recurring templates

You can attach one JPEG, PNG or PDF receipt to an itemized expense, using the camera or the system file picker. DashTrack reads only the file you select, not your other files. The attachment is stored in the app's local database and included in JSON backups, but not embedded in tax CSVs; CSVs contain only the receipt filename. Each attachment is limited to 2 MiB and combined receipt storage, including its JSON encoding, is limited to 6 MiB. DashTrack does not upload attachments or run receipt OCR. Existing photo/PDF bytes may contain embedded metadata. Keep originals separately.

You may explicitly view or share a receipt using the system sharing interface. This creates a temporary app-cache copy which may remain until a later receipt action clears copies older than 24 hours, or the operating system clears cache. Chosen recipients' privacy practices apply. Removing an attachment and saving the expense removes it from the local record, not from earlier backups, shared copies or your original file. The app does not add encryption to its database, receipt attachments or JSON backups.

Recurring templates contain an amount, category, notes, app tags, optional business-use percentage, label, cadence and due date. They are local checklists, not bank connections, automatic charges, notifications or proof of payment. Only an expense you explicitly confirm as paid contributes to reports. Removing a template does not remove paid expenses.

Smart delivery planning and optional plan reminders

The smart planner compares your own completed shifts by delivery zone, weekday, two-hour local-time window and exact delivery-app combination. Its 30-, 90- or 180-day history controls are separate from dashboard filters. Estimates subtract the vehicle costs saved with each shift, before taxes and other expenses; shift totals are allocated evenly across time. The app requires several comparable workdays rather than inventing results for missing history. This planner does not fetch live demand, app promotions, peer results or GPS locations.

Saved delivery plans use the same local plan records as manually entered peak-pay plans and are included in JSON backups. Saving a plan does not request notification permission, book a shift, create a calendar event or start earnings tracking. If you explicitly enable a reminder, the app requests notification permission and keeps a device-local reminder snapshot with the plan ID, zone, delivery-app label and times. Reminder notifications may show the zone and app label on your lock screen, depending on device settings. The intended reminder time is 15 minutes before the plan, but battery, notification and operating-system settings may delay or suppress it. Android workers skip reminders once the planned start has passed. On iOS, the app clears stale requests when it next checks reminder state; the operating system may still defer presentation while the app is closed.

Plan reminders do not use remote push, GPS, exact alarms or a foreground tracking service. Device-local reminder consent and pending notification state are not included in DashTrack JSON backups and are not enabled automatically on restore. You can turn off existing plan reminders even when premium testing is off. Removing a plan cancels its reminder; it does not delete shift history. Android/iOS operating-system backup and notification settings are separate from DashTrack JSON exports.

Optional recorded-activity reminders

Reminders are off by default. If you enable them and allow notifications, the app keeps a small local active-shift snapshot to check how long it has been since you recorded an increase in earnings or odometer mileage. These reminders use local notifications, not remote push or GPS, and do not independently start location collection. The app suppresses recorded-progress reminders while an optional GPS session is starting or tracking; they are not a separate GPS movement or physical-idling detector. Android background scheduling is inexact and can be delayed by battery settings. Ending a shift or disabling reminders cancels pending reminders. Restoring driver settings does not automatically enable reminders.

Exports and sharing

You can choose to export a JSON backup or a CSV tax export. When you choose an export, DashTrack Pro creates the selected file temporarily in its app cache on your device and opens your device's system sharing interface. The temporary copy may remain until the app or operating system clears that cache. The app sends the file only to the app, person, service, or destination that you select.

Once you share an export, the recipient's privacy practices apply. Please review the contents before sharing because an export may include the shift and preference information described above.

Restoring a backup

You can choose a DashTrack JSON backup through your device's system file picker. The picker copies the selected file into the app cache so DashTrack can validate it and show a preview. That temporary copy may remain until the operating system clears the cache. The app reads only the backup you select; it does not scan your files or upload the backup to DashTrack servers.

Restoring adds missing shift, subscription-expense, itemized-expense, recurring-template and peak-pay-plan records to your device without overwriting existing records. Expense receipts remain attached to their restored expense. Applying a restore pauses any existing active GPS session before records are merged; the restore does not grant location consent, enable GPS, or automatically resume it. You must explicitly resume an eligible session in the visible app. You can separately choose whether to restore driver settings; reminders remain off until you explicitly enable them again. Backups are not encrypted by DashTrack and may contain earnings, mileage, zones, delivery counts, notes, receipt files, expense records and scheduled windows, but not GPS coordinates or the native GPS tracking summary. Files over 10 MiB are refused rather than truncated. Keep them in a private destination you trust. Manual backup and restore is not automatic cloud synchronization.

Information we receive when you contact support

You do not need to provide your name, email address, or contact details for core guest tracking. An email address is needed only if you choose to use the optional sign-in account service or contact support. If you contact support at dashtrackpro@gmail.com, we may receive the information you include in your message, such as your email address, name, device details, and description of the issue. We use that information only to respond to and help resolve your request. Messages are handled by our email provider and retained only as long as reasonably needed for support, recordkeeping, or legal obligations.

Other information and external links

Only supported Android GPS builds access precise location after explicit active-shift opt-in, as described above. The app does not access contacts, microphone or health data. Camera access is optional and used for odometer scans or receipt photos. DashTrack does not sell your work records or use them for behavioral ad targeting. Do not interpret this as a claim that third-party SDKs collect nothing: ML Kit diagnostics and the planned Android 1.6.2 advertising SDK's identifier, network and other processing are described above. Exports use temporary app-local files and your device's sharing interface. Restore reads only the backup file you explicitly select; DashTrack does not scan your other personal files.

The app includes a link to the Internal Revenue Service mileage-rate webpage. If you open that link, the IRS website and your browser are governed by their own terms and privacy practices.

Your choices and deletion

You can edit or delete individual shift and manual expense records, remove saved peak-pay plans while testing is enabled, decline camera or location permission, and disable reminders. GPS tracking is optional: you can pause or stop it in the app or through its available notification controls, and revoke location or notification permission in Android settings. Manual mileage entry remains available. For all locally stored app data, you can delete the app or clear its application data through device settings. Export a backup first if you want to keep your records.

Because your records are stored locally in this beta, DashTrack Pro cannot retrieve, correct, or delete records from your device for you. Device backups, shared exports, and support emails may be subject to the settings and policies of your device, backup provider, email provider, or chosen sharing destination.

Security

We design DashTrack Pro so that the current beta keeps work records on your device rather than in a DashTrack Pro cloud account. You are responsible for using device protections, such as a screen lock and current operating-system updates, and for choosing where to share exported files. No method of electronic storage or transmission is completely secure.

Children

DashTrack Pro is not directed to children under 13, and we do not knowingly collect personal information from children through the app. If you believe a child has sent us personal information through support, contact us so we can address the request.

Changes to this policy

If DashTrack Pro changes its account service or adds cloud sync, live advertising, new subscription data practices, new permissions, or other material data practices, we will update this policy before or when those practices take effect and revise the dates above. The optional Android 1.6.2 sample-banner test is not authorization for live ads or a paid subscription.

Contact us

For privacy questions, support, or requests about information you sent to us by email, contact:

DashTrack Pro Support
dashtrackpro@gmail.com