Privacy Policy — Bike Tracker

App: Bike Tracker (com.cooltime.bike_tracker) · Developer: Cooltime
Effective date: July 5, 2026 · Last updated: July 5, 2026

This Privacy Policy explains what data the Bike Tracker mobile app (the “App”) accesses, how it is used, and with whom it is shared. Bike Tracker automatically records your bicycle commutes and everyday rides using your device’s GPS. The App does not require an account or sign-in, and your ride records are stored only on your device.

Summary

Location is used to record your rides (route, distance, speed, elevation). It is stored locally on your device and is not uploaded to any server operated by us.
We use Google services (Firebase, AdMob) that collect limited diagnostics, usage analytics, and advertising identifiers to run analytics, crash reporting, ads, and push notifications.
No account, name, email, contacts, photos, or files are collected by the App.

1. Information we access and collect

Location data (precise and approximate, including in the background)

The App accesses your device location to provide its core feature: recording a bicycle ride. When you tap “Start ride,” a foreground service records your GPS route and distance for the duration of the ride, including while the screen is off or the app is in the background, so the route is captured without gaps. Location access runs only during a ride you start and stops when you end the ride.

Your route and ride data (distance, moving time, speed, elevation gain, estimated calories, timestamps) are saved only in local storage on your device. We operate no servers and do not receive, transmit, or store your location or ride history. Third-party services below may separately process approximate location as described.

App activity and diagnostics

Through Google Firebase we collect anonymous usage events (for example, when an ad is shown) and crash / diagnostic information (crash logs, device model, OS version, app version) to keep the App stable and understand aggregate usage.

Identifiers

Advertising ID — used by Google AdMob and Firebase Analytics for ads and analytics.
Firebase installation ID — used by Firebase for analytics, crash reporting and remote configuration.
Push token (FCM registration token) — used by Firebase Cloud Messaging to deliver notifications.

2. How we use the data

Data	Purpose
Location	Record ride route, distance, speed and elevation (core app functionality). Deliver relevant ads (Google AdMob may use approximate location).
App activity / diagnostics	Analytics and crash diagnostics to improve reliability and features.
Advertising ID / installation ID	Show and measure ads, analytics, remote configuration.
Push token	Send announcements and update notifications.

3. Third-party services

The App uses the following services, which process data under their own privacy policies:

Google Play services, Firebase Analytics, Firebase Crashlytics, Firebase Remote Config, and Firebase Cloud Messaging — Google Privacy Policy.
Google AdMob (advertising) — How Google uses information from sites or apps that use our services.
OpenStreetMap — map tiles are loaded from OpenStreetMap servers to display maps; tile requests reveal the approximate map area being viewed. OSMF Privacy Policy.
Google Play In-App Review — used to request app ratings; it does not share your review status with the App.

4. Data sharing

We do not sell your personal data. We do not share your location or ride history with any third party, because that data never leaves your device through us. The diagnostics, analytics, advertising and messaging data described above are processed by Google as our service provider in accordance with the policies linked in Section 3.

5. Data retention and deletion

Ride records are kept on your device until you delete them in the App or uninstall the App.
Uninstalling the App removes all locally stored ride data from your device.
Analytics and crash data held by Google are retained per Google’s retention policies.
To stop personalized ads, you can reset or delete your Advertising ID in your device settings.

6. Data security

Ride data is stored in the App’s private, app-scoped storage on your device. Network requests to third-party services use encrypted connections (HTTPS) where provided by those services.

7. Permissions we request

Location (precise, approximate, and background) — to record rides, including while the screen is off.
Notifications — to show the ongoing tracking notification, ride reminders, and push messages.
Foreground service — to keep recording your ride reliably while the app is in the background.
Network access — to load map tiles, ads, and app configuration.

You may revoke location or notification permission at any time in your device settings; some features (such as ride recording) will not work without location permission.

8. Children’s privacy

Bike Tracker is not directed to children under the age of 13 (or the minimum age required in your country), and we do not knowingly collect personal data from children.

9. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the “Last updated” date above. Continued use of the App after changes take effect constitutes acceptance of the updated policy.

10. Contact

If you have questions about this Privacy Policy or your data, contact us at:
enterfive@gmail.com