Support

A drive was missed

This is the failure that matters most, so it is worth diagnosing properly rather than guessing.

First, check the permission. Open iOS Settings > Milelog > Location. It needs to say Always. "While Using the App" is not enough: the app is not open while you are driving, so it will only ever catch drives you happen to start from inside the app. iOS also occasionally asks you to reconfirm "Always" weeks later, and a tap on the wrong button quietly downgrades it.

Then check Precise Location is on in the same screen. Without it, iOS hands the app a rough neighbourhood position, which is not enough to measure a route.

Then open Milelog > Settings > Detection. It shows the live state of the detection engine. If it says NOT STARTED, the engine failed to attach, and that is worth emailing us about with the date and time.

Add the drive by hand in the meantime. Trips tab, the + button. A trip you entered yourself is a perfectly good record; what matters for an audit is that it was written down close to when it happened, not that a computer wrote it.

The mileage does not match my other app

It probably will not match exactly, and the reason is worth understanding.

Some trackers report the distance of the road route between your two endpoints, which they get by sending your route to a server to be matched against a road map. Milelog measures the path your phone actually travelled, on your phone, because sending your routes to a server is the one thing this app promises never to do.

Milelog also discards movement it cannot vouch for: a stationary phone still emits GPS fixes that wander by several metres, and summing those raw would add distance you never drove. Inflating a deduction is the error that causes real trouble, so where the two approaches disagree, Milelog errs low rather than high.

If the difference is large rather than a few percent, that is worth reporting.

The location name is wrong

Reverse geocoding gives the nearest street address, which for a car park or a large site can be a road you never set foot on. The fix is to name the place once:

Open the trip, tap Name this place under either endpoint, and give it a name you would recognise. Every trip that starts or ends there, past and future, uses that name from then on.

Milelog also watches for this. Once you have been somewhere three times without naming it, it appears under Settings > Places as a suggestion, with the number of visits. It will never name a place for you, because that name can end up on a tax document and it should be your word rather than a guess.

Battery

GPS runs only while you are driving, and is off between drives. To see this rather than take our word for it, open Settings > Detection, which reports how many minutes of GPS the app has used today.

If iOS Battery settings show Milelog using a lot of power, check whether the detection engine is stuck in DRIVING on that same screen, and tell us if it is.

Deleting your data

One trip: open it and tap Delete trip.

All of it: delete the app. Milelog keeps no server copy and we hold nothing of yours, so uninstalling removes it permanently and there is no request to send us.

Export first if you might need the records: Reports tab, then Export, which produces a CSV or PDF you can send wherever you like.

Getting your log out

Reports tab > Export. CSV opens in any spreadsheet, and the PDF is formatted to be handed to an accountant as-is. Both include every trip in the year you selected, with the date, endpoints, distance, category, purpose and the rate applied.