FAQ
Answers about tracking, review, privacy, export, and tax boundaries.
MileLedger is meant to make work-driving records easier to understand, not to blur what the app does, where data lives, or when a professional advisor should still help.
Does MileLedger store trips on the server?
No. The product is designed around a local-first record model, so trips and notes stay on-device unless the user explicitly exports or shares them.
Who is the product for?
The first audience is self-employed service professionals who drive to customers, job sites, estimates, and supply runs. Other work-driving patterns may still fit when trip review and export matter.
Can the app separate business, personal, and commute?
Yes. The review workflow is built around that distinction, with category suggestions, saved places, and business-purpose entry all supporting a cleaner record.
Is MileLedger trying to replace tax advice?
No. MileLedger exists to improve record quality and export readiness. Tax treatment and filing decisions still belong to the user or their advisor.
What makes Pro worth paying for?
Pro is meant to reduce cleanup later: more trip history, stronger export coverage, saved places, reusable work context, and accountant-ready summaries.
What happens if someone declines location permission?
The product should still remain manually usable. Permission is earned progressively, not used as a hostage gate for the rest of the experience.