DashFit is a running copilot. To analyse your sessions, the app reads your health data from Health Connect, Android's health service: exercise sessions, heart rate, heart rate variability (HRV), distance, speed, steps, active calories, sleep, VO2max and health history. This data is stored exclusively on your device, in the app's local storage (Room database and DataStore preferences). DashFit never asks for your name, address or phone number.
There is no DashFit server. The publisher operates no backend, no remote database and no online storage: your health data therefore passes through no server of ours, and we never have access to it. All computations (pace, kilometre splits, heart rate zones, freshness score) run directly on your device. The only data that leaves your phone goes to your own Google Calendar, as described below.
DashFit writes a summary of your runs into a calendar named "Running" that belongs to you, through the Google Calendar API and an OAuth 2.0 authorization that you grant yourself. This is the only data transmission the app performs.
The app requests ten Health Connect permissions, all of them read-only (READ): exercise sessions, heart rate, heart rate variability, distance, speed, steps, active calories, sleep, VO2max and health history (READ_HEALTH_DATA_HISTORY, which allows reading sessions recorded before the app was installed).
The Internet and network state permissions are used exclusively for Google authentication and for the calendar sync described above. They are used for nothing else: no telemetry, no advertising, no reporting of your data to any third party. Everything else in the app works offline.
The app may request the approximate location permission (ACCESS_COARSE_LOCATION) for a single purpose: showing the weather context of your runs. This permission is optional — the app works without it. Your position is not kept in any history, is never sent to the publisher, and is never written to your calendar.
The notifications permission is only used to inform you about the status of a background sync. No advertising or promotional notification is ever sent.
Unlike our other apps, DashFit requires signing in with a Google account: this is necessary to write your runs into your calendar. Sign-in goes through Android's Credential Manager and then an OAuth 2.0 authorization limited to the Google Calendar scope. The app receives a short-lived access token; it never sees your password and keeps no copy of it. No account is created with the publisher: we hold no customer records.
The app contains no advertising, no advertising tracking SDKs, no advertising identifier (Advertising ID), no analytics (Google Analytics, Firebase Analytics, Mixpanel, etc.), and no user behavior measurement tools. Your health data is never sold, rented or shared for commercial purposes — nor shared with anyone at all.
Your sessions, heart rate samples, kilometre splits, targets and settings are stored locally on your device by the app (native Android app written in Kotlin, local Room database, DataStore preferences). This data stays on your phone, apart from the run summary sent to your Google Calendar.
You stay in full control of your data. Uninstalling the app permanently deletes all the data it has stored on your device. You can also revoke the Health Connect permissions from your phone's settings, remove DashFit's access from your Google account security settings, and delete the events created in your "Running" calendar at any time directly from Google Calendar.
DashFit is intended for people aged 18 and over. The app is not directed at children and does not knowingly collect any data about them.
This policy may be updated if the app undergoes major changes. The last update date is shown at the top of this page.
Publisher: PIXELMORE. For any questions about this privacy policy: hugoferreirapro803@gmail.com