MileBook Privacy Policy
This policy explains what data MileBook ("the app") handles, how it's used, and where it goes. MileBook is published by SundrySoft ("we", "us"). The app runs entirely on your Android device and is designed to keep your trip data local.
If you have questions, contact us at info@sundrysoft.com.
Summary
- Your trips, routes, vehicles, business locations, and notes are stored only on your device. We do not operate any servers and we do not receive a copy of your data.
- The app does not include analytics, crash reporting, advertising, or third-party trackers.
- The only data the app sends off your device is GPS coordinates from a finished trip, sent to Google Maps Platform to draw a clean route line on the map. This is optional and the app works without it.
- Subscription billing is handled entirely by Google Play. We never see your payment information.
- Uninstalling the app deletes all of your trip data.
1. Information stored on your device
MileBook stores the following data locally in the app's private storage. None of it is transmitted to us.
Trip records. For each trip detected: start and end timestamps, start and end coordinates, total distance, duration, vehicle, classification (Business / Personal / Commute / Unclassified), purpose, and any notes you add.
Trip GPS samples. Periodic location samples taken every ~2 seconds while a trip is being recorded — latitude, longitude, timestamp, speed, and accuracy. These are used to calculate distance and produce the route map for that trip.
Business locations. Places you save (such as a job site or home) as latitude/longitude points with a radius. Used to start/end trips automatically and to auto-classify trips.
Vehicles. Names, optional plate numbers, and any notes you enter for vehicles you track.
App preferences. Onboarding state, default geofence radius, and the last known parking location (used to re-arm trip detection after a reboot).
Cached route polylines. Compressed route shapes returned by Google Maps Platform (see Section 3) are cached locally to avoid re-requesting them.
2. Permissions and why they're needed
MileBook requests the following Android permissions:
- Location (Fine, Coarse, Background). Required to detect and record trips. Background location access is necessary because trips can begin while the app is closed; without it, the app cannot reliably auto-detect drives.
- Physical Activity (Activity Recognition). Used to detect when you start or stop driving, so the app knows when to begin and end a trip.
- Foreground Service / Foreground Service – Location. Required by Android to record a trip in the background. While a trip is being recorded, a notification is shown.
- Notifications. Required on Android 13+ to display the trip-in-progress notification.
- Receive Boot Completed. Used to re-arm trip detection after the device restarts. No data is collected at boot.
- Ignore Battery Optimizations (optional). If granted, prevents the system from killing the trip recorder mid-drive on battery-saver settings.
- Internet. Required to fetch route shapes from Google Maps Platform (see Section 3) and to communicate with Google Play Billing for subscriptions.
- Wake Lock. Keeps the CPU awake while a trip is being recorded so location samples are not dropped.
You can revoke any permission at any time in Android Settings. Revoking location or activity recognition will stop automatic trip detection.
3. Data sent off the device
The app makes one type of outbound network request, plus subscription checks:
a. Google Maps Platform — Directions API
When a trip finalizes (and optionally when you open a trip's detail view), the app sends the trip's GPS coordinates — start, end, and a small set of intermediate waypoints — to Google's Directions API to receive a road-snapped route shape. This is what produces the clean line you see on the trip map.
- What is sent: latitude/longitude pairs for that single trip; nothing else.
- What is received: an encoded polyline of the route. This is cached locally so the call does not repeat.
- Optional: if the call fails or is unavailable, the app falls back to a straight start-to-end line. Trip recording, distance, duration, and classification continue to work without it.
- Google's handling of the data: Google Maps Platform processes these requests under Google's own privacy policy and the Google Maps Platform Terms of Service. See https://policies.google.com/privacy and https://cloud.google.com/maps-platform/terms.
b. Google Play Services (location and activity recognition)
The app uses Google Play Services on your device to obtain GPS fixes and to be notified of driving-state transitions. These are on-device system services provided by Google. Google's handling of the data is governed by Google's privacy policy.
c. Google Play Billing (subscriptions only)
When you start a free trial or subscribe, the purchase is processed entirely by Google Play. We receive only an entitlement signal indicating whether your subscription is active. We never see, store, or transmit your name, address, email, or payment details. Google's handling of billing data is governed by Google's privacy policy.
What is not sent off the device
- We do not include any analytics, crash reporting, ad SDKs, or telemetry of any kind.
- We do not have any servers, accounts, or cloud sync. There is no "log in" because there is nothing to log into.
- We do not sell, rent, or share your data with anyone.
- We do not receive a copy of your trips, location history, vehicles, business locations, or notes.
4. Subscriptions and the free trial
MileBook offers a 14-day free trial followed by a paid subscription (monthly or annual). The subscription is sold and managed exclusively through Google Play. To cancel, manage, or refund a subscription, use the Subscriptions section of the Google Play Store. SundrySoft does not have access to your payment method or billing history.
When the trial expires without conversion to a paid subscription, the app enters a read-only state: your existing trip data remains intact and viewable, but new trip recording, edits, and exports require an active subscription.
5. Exporting and deleting your data
Exporting. You can export your trip log as a CSV file at any time from the Reports screen. The file is written to a location of your choice using the Android system file picker. The export does not pass through us or any third party.
Deleting. Because all of your data is on your device, you can delete it by:
- Removing individual trips, vehicles, or business locations inside the app.
- Clearing the app's data via Android Settings → Apps → MileBook → Storage → Clear data.
- Uninstalling the app, which removes all stored data.
We do not need to honor a deletion request because we do not hold any of your data.
6. Children
MileBook is not directed to children under 13 and we do not knowingly collect data from children. The app is intended for adults tracking vehicle mileage for personal or business purposes.
7. Security
Trip data is stored in the app's private Android storage area, which is protected by the operating system from access by other apps. Cached data on the device is only as secure as the device itself; we recommend keeping your device locked with a PIN, password, or biometric and keeping Android updated.
The single outbound network call (Section 3.a) uses HTTPS.
8. Changes to this policy
If we change this policy, the new version will be published in the app's repository and listed on the Play Store listing. Material changes will be highlighted with an updated "Last updated" date at the top of this document. Continued use of the app after changes take effect constitutes acceptance of the revised policy.
9. Contact
For questions about this policy or your data, email info@sundrysoft.com.
MileBook is operated by SundrySoft, a trade name of Davis Group Holdings, LLC.