Your data, your mileage.

Last updated: August 30, 2026. MileSpend is designed to keep core mileage information on your device.

What MileSpend stores locally

The app stores trips, route points, vehicle parking anchors, places, classifications, receipts, and reports in its local app database and files. This data is not sent to MileSpend’s servers for the core mileage experience.

Optional beta diagnostics

Beta testers may consent to pseudonymous operational diagnostics. These can include app/build version, device class, OS version, tracking lifecycle events, crash signatures, performance timings, battery/thermal/memory indicators, POI/classification outcomes, and tester corrections. Diagnostics are intended to improve reliability and do not include raw routes, receipt contents, personal labels, or exact coordinates in the normal telemetry payload.

Connected services

The beta diagnostic service uses Supabase for authenticated ingestion and storage, and Vercel hosts this website. The public website uses privacy-respecting Vercel analytics for anonymous page and install-CTA measurements. The website does not receive mobile trip data.

Receipts and permissions

Receipt images and OCR results remain local unless you explicitly submit a diagnostic attachment through the app’s problem-report flow. Location, Bluetooth, motion, camera, calendar, photo, and notification access is requested only for the corresponding feature.

Retention and choices

You can decline beta diagnostics without losing core app functionality. You can remove local app data by deleting it from the device or using the app’s available data controls. Contact support for beta diagnostic deletion requests.

Contact

Questions about this policy: privacy@milespend.app.