RunRoute policy
RunRoute Privacy Policy
Version 1.1 Effective 24 October 2026 Version history
What changed in version 1.1
Covers the app and the website (runroute.duodev.in). Adds optional accounts (email/password, Google Sign-In) and cloud sync of sessions, GPS routes, achievement progress and health profile; Firebase Analytics, Google Play update checks and technical data; a website section on essential cookies and third-party content; account deletion in the app, on the website and via emailed link (immediate, backups removed within 30 days); the Digital Personal Data Protection Act, 2023; not directed at children under 13.
On this page
1. Scope #
RunRoute is published by Duo Dev Technologies ("we", "us", "our"). Support contact: support@duodev.in.
2. Information We Process #
1. Location Data:
- Precise location while using the app in the foreground.
- Background location during an active tracking session (when permitted by you) to keep route, distance, and pace accurate while the app is minimised or the screen is off.
- Location is collected only while a tracking session is active or while you use map and route features.
2. Activity Data:
- Session history, recorded GPS route points, start and end coordinates, distance, duration, pace, speed, calories, and related activity metrics.
- Achievement progress calculated from your activities.
3. Health and Fitness Profile (optional, entered by you):
- Display name, age or birth date, gender, height, weight, step length, activity preferences, units, and goals. These are used to estimate calories and personalise goals.
4. Account Data (only if you create an account or sign in):
- Name and email address.
- If you register with email: a password, which is stored on our servers only in hashed form.
- If you sign in with Google: your Google account name, email address, Google account identifier, and profile picture, provided by Google with your permission.
5. Settings and Preferences:
- App preferences such as theme, units, notification choices, and retention settings.
6. Photos (optional):
- If you choose a background image when sharing an activity, the image you pick is used on your device only to create the share image. It is not uploaded to our servers.
7. Diagnostic and Usage Data (app):
- Crash diagnostics through Firebase Crashlytics (crash stack traces, device model, OS version, and app version).
- App usage analytics through Google Analytics for Firebase (for example, app launches and screens viewed, together with device and app information and an app-instance identifier).
8. Technical Data (website and servers):
- IP address, browser or device type, and request details, processed when the app or your browser connects to our servers.
- For website sign-in sessions, your IP address and browser type are stored with the session while you are signed in.
3. How We Use Information #
1. Track activities and show route, history, and statistics insights in the app and on the website.
2. Generate and save routes.
3. Estimate calories and track your goals and achievements.
4. Back up and sync your sessions and profile across devices when you are signed in.
5. Keep your account secure, prevent abuse (for example, by rate-limiting requests), and verify account deletion requests.
6. Improve stability, troubleshoot crashes, and understand which app features are used.
7. Apply your chosen settings, reminders, and retention preferences.
8. Tell you when a new version of the app is available.
We do not use your location or activity data for advertising.
4. Storage and Data Architecture #
2. Signed-in users: your activity sessions (including recorded GPS route points), achievement progress, and health and fitness profile are also stored on RunRoute servers operated by us, so they can be backed up, synced, and shown on the website. Your account data is stored there as well.
3. Data is sent between the app, the website, and our servers over encrypted connections (HTTPS).
4. Saved route plans, notifications, and app settings remain on your device and are not synced.
5. Our server database is backed up daily. Each backup is kept for no longer than 30 days.
5. RunRoute Website #
2. Cookies: the website uses only cookies needed for it to work:
- A session cookie that keeps you signed in.
- A security token cookie that protects forms against cross-site request forgery.
- A "remember me" cookie, only if you choose to stay signed in.
- A timezone cookie that stores your browser's timezone so dates and daily statistics are shown in your local time.
3. The website does not use advertising or analytics cookies.
4. To display pages, your browser loads some content directly from third-party providers, including Google Fonts, OpenFreeMap (map tiles), public content delivery networks (cdnjs and the Tailwind CSS CDN), an embedded Google Map on the contact page, and a QR code image service on the registration confirmation page. These providers receive your IP address and browser information when your browser requests that content.
6. Third-Party Services #
1. Google Maps Platform: to display maps and generate routes in the app. Map and route requests include the locations needed for the request.
2. Google Sign-In: only if you choose to sign in with Google.
3. Firebase Crashlytics: crash reporting in the app.
4. Google Analytics for Firebase: app usage analytics.
5. Google Play: to check whether a newer app version is available.
6. OpenFreeMap: map tiles shown on the website.
These providers process data under their own privacy policies, including Google's Privacy Policy: https://policies.google.com/privacy.
7. Data Sharing #
2. We do not share your location or activity history with third parties for advertising purposes.
3. Data is shared with the service providers listed in Sections 5 and 6 only as needed to provide their function.
4. Content you choose to share (for example, an activity share image) is shared by you, through the app you choose.
8. Retention and Deletion #
2. Your account: you can permanently delete your account at any time:
- In the app: Profile > Delete Account.
- On the website while signed in: Profile Settings > Delete Account.
- On the web without the app or a password: https://runroute.duodev.in/account/delete (we email you a confirmation link).
3. Deleting your account permanently deletes your account data, synced sessions, achievement progress, synced profile, and all sign-in sessions and tokens from our servers. Deleting from the app also erases RunRoute data on that device.
4. Server data is deleted immediately when the deletion is confirmed. Residual copies in backups are removed within 30 days.
5. We keep a minimal record that a deletion took place (an irreversible code that cannot be traced back to your name or email, how the deletion was requested, and when). It contains no personal data.
6. Crash and analytics data held by Firebase is retained according to Firebase retention settings and is not linked to your RunRoute account.
7. You can request assistance via support@duodev.in.
See the RunRoute Data Deletion Policy for full details: https://legal.duodev.in/products/runroute/data-deletion-policy.
9. Children and Age Considerations #
10. Your Choices #
1. Grant or deny location, background location, and notification permissions.
2. Use the RunRoute app in Guest Mode without creating an account.
3. Stop activity tracking at any time.
4. Adjust retention settings.
5. Clear local data in the app.
6. Delete your account and server data at any time.
11. Legal Framework #
12. Policy Updates #
13. Contact #
Version history
| Version | Effective | Changes | Accept again |
|---|---|---|---|
| 1.1 (this page) In force | 24 October 2026 | Covers the app and the website (runroute.duodev.in). Adds optional accounts (email/password, Google Sign-In) and cloud sync of sessions, GPS routes, achievement progress and health profile; Firebase Analytics, Google Play update checks and technical data; a website section on essential cookies and third-party content; account deletion in the app, on the website and via emailed link (immediate, backups removed within 30 days); the Digital Personal Data Protection Act, 2023; not directed at children under 13. | Yes |
| 1.0 | 14 April 2026 | First published version. | — |
Questions about this policy? Contact us.