MileWorks Privacy Policy

Effective date: November 2, 2026

Last updated: November 2, 2026

MileWorks is a fuel, EV-charging and mileage log for iPhone and Android, made by MileWorks LLC ("we", "us"). This policy explains what the app keeps, what it sends, to whom, and why.

The short version

Your log stays on your phone. MileWorks has no accounts and no server that holds your data. We can't see your vehicles, fill-ups, charging, maintenance, expenses, trips, receipts or photos. Your phone's own backup (iCloud or Google's) may copy it to your account, as described below.
No ads, no tracking, no selling. The app has no advertising or analytics tools, doesn't use your phone's advertising ID, and has no crash-reporting tool besides what the update service receives: which updates failed to start and, after the app crashed while starting, a short error message (row 8).
A few lookups go out, only when they're needed, and each one gets only what it needs to answer: your vehicle's model (fueleconomy.gov), its VIN if you look it up by VIN (NHTSA), its model again for safety recalls (NHTSA), a location to find the gas station (OpenStreetMap) and a location or address for the street address or map position (your phone's own maps service, Apple's or Google's), currencies and dates (exchange rates), if you turn it on, where you filled up rounded to about 10 km and the days you drove from each (past temperatures, NASA), the parts of the map in view when you open the Passbook's map to drag and zoom or Drop a pin's map (its streets, OpenFreeMap), and the app's update check (Expo). Some of them carry a precise location or your VIN; none carry your name or your log. On Android, Google's ML Kit, which reads photo text and VIN barcodes on your phone, sends Google its own diagnostics (row 9), never the photo or what's in it.

What the app keeps on your phone

Everything you log is stored in the app's own storage on your phone:

your vehicles (year, make, model, nickname, color, official EPA ratings or the targets you type, tank size, starting odometer, its VIN and where you bought it if you add them, a loan, lease, purchase price or value if you add them, tire sets and tread readings, the unit its odometer reads in if it has its own, and the safety recalls found for its model with the ones you've marked seen or done);
rental cars (MileWorks Plus): the company if you give it, whether it came full and when it's due back, and its pickup and return (each one's date, time and odometer, and the place you picked it up in; an address and map position only when you add them);
borrowed cars (MileWorks Plus): the same, with whose car it is if you say (for example "Mom's car", as you type it), and what you agreed to pay its owner (a flat amount, a share of their insurance, a rate per mile or km, and the currency); what you paid them is logged as an expense;
condition photos of a rental or borrowed car, taken at pickup and at return, kept with those entries;
documents and renewals you add for a vehicle (insurance, registration, inspection, a driver's license, a warranty, the title and the like: their names, numbers such as a policy, plate or license number, who issued them, their dates and notes, with photos or scans of them);
fill-ups and charging sessions (date, time, odometer, amount, price, cost, currency, fuel grade, station or network, address, map position and time zone, notes);
maintenance visits, expenses, refunds, odometer readings and trips (including where and why a trip went, and any reimbursement, and, only when you add it, where a reading, trip, visit or expense was logged: its address and map position), and gig work pay (the platform, pay and tips, hours, distance and notes);
border crossings: each one's date, time and odometer, and always the place you crossed into (the country, and its state or province if you choose one); its address and map position only when you add them;
a trip being recorded (MileWorks Pro): its GPS track, until you save or discard it;
automatic tracking (MileWorks Pro + Automatic tracking, Android): the drives it found in the last 90 days (each one's start and end time, distance, start and end addresses and map positions, the borders and state lines it crossed and how far into the drive, the odometer if you add it, its car and how you sorted it), the tracking library's own record of your locations for the last 3 days, from which the drives are worked out, and each drive's path (a point about every 200 m with its time), kept until you delete its trip; none of these is copied to Google's cloud backup. A drive you sort becomes a trip in your log, with its addresses, crossings, speeds, miles in each place and odometers, which the phone's own backup copies with the rest of your log;
tires (MileWorks Plus): each set's spec as its sidewall prints it, the door placard's sizes and pressures, tread readings, and photos of a sidewall you keep with a set;
damage and condition photos (MileWorks Plus): what was damaged and how, when it was repaired, and the photos;
an accident or incident you log: what happened, when and where, the answers to the guide's steps, the police report number, the claim, the photos, and the other drivers' and witnesses' details as you type them (names, phones, insurers, policy and plate numbers, a driver's license number); kept on your phone like everything else, and in a report only when you share it yourself (a backup carries the details, not the photos);
photos of your odometer and receipts, and receipts or documents you attach;
in Mexico, the facturas (CFDI) you attach, their XML and PDF files, and what the app reads from the XML on the phone (the seller's name and RFC, your RFC and the use (uso CFDI), the amounts and taxes, how it was paid, its lines and its UUID); a backup carries what was read, not the files;
your settings (region, and your home region if you add one, units, currency, home electricity rate, business mileage rate, reminders, display choices), a cache of exchange rates the app has looked up and, if you use the weather lookup, a cache of past daily temperatures by rounded place and date;
if you turn on the automatic backup, a daily copy of your log as a CSV file;
copies of the files you export or share (CSV, PDF and images), in the phone's cache, until the phone clears it or you erase everything.

This data is protected by your phone's lock screen and the encryption your phone provides. The app doesn't add encryption of its own, so anyone who can unlock your phone can open it.

Your phone's own backup. If iCloud Backup (iPhone) or Google's backup (Android) is on, your phone may include MileWorks's data in its backup to your Apple or Google account, under their terms. On Android, photos, attached documents and the map's cache are left out of Google's backup because of its size limit.

What the app sends, to whom, and why

The app connects to the internet only for the lookups below. Each request also carries your IP address, as every internet connection does. None of them include your name or your log. Some carry something that could point to you: a precise location (rows 4 and 5, which can be your home, for example a trip that starts there or a receipt photographed there), your VIN (row 2), or the random update ID that goes to Expo (row 8).

When	What is sent	Sent to	Why
1. You pick a vehicle from the EPA list	The model year, make, model and engine option you choose	fueleconomy.gov (U.S. Department of Energy and EPA)	To show the lists and fetch the official ratings
2. You add a vehicle by its VIN	The 17-character vehicle identification number	NHTSA's vPIC service (U.S. Department of Transportation)	To read the year, make and model from the VIN
3. Once a week, for each vehicle you still own with a year, make and model (when the app is open), if your region is in the United States, Canada or Mexico, or you haven't chosen one	The model year, make and model	NHTSA's recalls service (api.nhtsa.gov, U.S. Department of Transportation)	To show the safety recalls for that model
4. You tap Use my current location on a fill-up or charging session, or add a photo to a new fill-up that has no station yet	The map position: where you are, or where the photo was taken	OpenStreetMap's Overpass service (overpass-api.de) and your phone's address lookup (Apple's on iPhone, Google's on Android)	To find the nearest gas station and the street address
5. You tap Place them on the map in the Passbook, or Stop on a trip you're recording (MileWorks Pro); or you add a place to an odometer reading, trip, maintenance visit, expense, rental pickup or the purchase of a car: Use where I am, coordinates you type, a pin you drop, or a photo's own location (an odometer reading's or a purchase's photo, new or picked from your photos, or an invoice's on a new entry), used only when you choose it	The addresses of fill-ups and public charging that have no map position yet; for a recorded trip, the map positions where it started and ended; for a place you add, the map position: where you are, the coordinates or pin, or where the photo was taken (not to OpenStreetMap: no station is looked up for these)	Your phone's address lookup (Apple's or Google's)	To put those stops on the Passbook's map, to name where the trip went from and to, and to give the place you add its street address
6. An amount is in a currency other than yours, or than the one you show money in (your home region's, with Home and away in MileWorks Plus)	The currency codes and the dates	Frankfurter (api.frankfurter.dev), which publishes the European Central Bank's daily reference rates. For a currency the European Central Bank doesn't publish (such as the Fijian dollar or the Tongan paʻanga), the free currency-api instead (fawazahmed0's, through jsDelivr at cdn.jsdelivr.net, or its copy on Cloudflare at currency-api.pages.dev), which gets a date and your currency's code. A currency fixed by law to one the European Central Bank publishes (such as the CFP franc to the euro) converts at its fixed rate over that one's, so only that one's rate is asked for	To convert the amount at that day's rate
7. You tap Look up the weather in Stats → Fuel economy (MileWorks Plus), and after that whenever that card needs a day it hasn't looked up yet, until you tap Stop looking up the weather or erase everything	The map positions of your fill-ups rounded to 0.1° (a grid of about 10 km or 6 miles), each with the days you drove from it (every day of a tank goes under the nearest fill-up's place), as date ranges: a day-by-day record of the area you drove in. Not the fill-ups themselves, their addresses, amounts or anything else from your log	NASA's POWER project (power.larc.nasa.gov, NASA Langley Research Center, United States)	To show your fuel economy by the outside temperature. Each place and day is looked up once; the temperatures are kept on your phone
8. The app opens, or you tap Check for updates	A random ID the update library creates the first time the app opens (new with each install, though an iPhone restored from a backup brings the old one back), the app version, the platform (iPhone or Android), the update you have, and the IDs of recent updates that failed to start on your phone. After the app crashed while starting, the next check also carries a short technical error message (up to 1,024 characters): on iPhone for any crash in its first seconds, on Android only when the update itself couldn't start	Expo's update service (650 Industries, Inc., "Expo")	To download app updates, and to tell which updates fail to start. Expo also uses the random ID to count how many installs have each update
9. You read numbers from a photo, scan with the camera, or scan a VIN's barcode, on Android	Not the photo, the camera's picture or what's read in them. Google's ML Kit, which reads the text and barcodes on your phone, sends Google technical information about that feature (by Google's ML Kit data disclosure: the phone's maker, model and Android version, the app's name and version, the image's format and size, and speed and error figures), encrypted on the way and not shared with others	Google	Google's diagnostics for ML Kit
10. You buy, restore or renew Plus or Pro (once paid plans launch)	See Purchases below	Apple or Google, and RevenueCat	To unlock and restore what you bought
11. You open the Passbook's map to drag and zoom (MileWorks Plus, app 1.0.7 and later), or tap Drop a pin for a place (any level, app 1.0.7 and later), and while you move around it; Driving now's map while a drive or a recorded trip is on screen (it follows the car), and a drive's route map	Requests for the parts of the map in view (its tiles, style, fonts and symbols), which show the area and zoom you're looking at: after Where you are, the area around you; on Driving now, the area around the car as you drive; on a route map, the area of the route. Not your stops, your location itself or anything from your log	OpenFreeMap (tiles.openfreemap.org, Hyperknot Software Kft., Hungary, through Cloudflare's network), which serves OpenStreetMap's map data	To draw the streets under your stops, which the app draws on your phone, or under the pin you place (the spot you choose then goes only to your phone's own maps service, for its address). Nothing is sent until you open one of these maps (Driving now opens by itself on Android when you come back to the app mid-drive). The map library keeps the parts already seen in a cache on your phone (about 10 MB at most, the oldest replaced as it fills; Erase everything empties it, and uninstalling deletes it). On Android it isn't copied to Google's backup

With automatic tracking on (MileWorks Pro + Automatic tracking, Android), a few minutes after each drive ends: the map positions where it started and ended, and for a drive across a border or a state line a few spots along the way, go to your phone's address lookup (Apple's or Google's), to name where it went and the place it crossed into. Nothing else about the drive is sent, and the tracking library itself sends nothing.

Never sent: your photos and receipts, what the camera sees while you scan, and what's read from them (photo reading and barcode scanning happen on the phone: Apple's Vision and the camera on iPhone, Google's ML Kit on Android), your fill-ups, charging, maintenance, expenses or trips (beyond a recorded trip's start and end and the spot of a place you add, in row 5, and the rounded places and days of row 7, when you turn it on), the track of a trip you record, your settings, and your files. The average fuel and electricity prices (from the U.S. Energy Information Administration) and the average fuel prices of Canada (from Statistics Canada), the EU's member states (from the European Commission's Weekly Oil Bulletin), the United Kingdom (from the government's weekly road fuel prices), Norway (from Statistics Norway), New Zealand (from the Ministry of Business, Innovation and Employment) and Western Australia (from FuelWatch) are built into the app and arrive with its updates; the app never contacts any of them. The Passbook's overview maps and the time zones are worked out on the phone; the map to drag and zoom fetches only its streets (row 11).

These services answer the request and may keep ordinary server logs under their own terms. We don't receive those logs and can't link them to you. Where a company works for us (Expo, and RevenueCat once purchases launch), it processes the data on our behalf under terms that require it to protect it.

Sharing you choose

Some features hand your data to an app or place you pick. What happens next is up to that app's terms:

Exports and reports (CSV and PDF) and Share the latest backup open your phone's share sheet.
Automatic backup on Android can also save to a folder you choose (for example, a cloud-storage app's folder). On iPhone, the backup copies are visible in the Files app (On My iPhone → MileWorks); the app's own data, your photos and documents aren't shown there.

These files are ordinary, unencrypted files containing your log, including addresses, trips, border crossings (each with the place you crossed into and when), rental cars (the company, where and when you picked each up and returned it), borrowed cars (also whose car it is and what you agreed to pay its owner), gig pay and your documents' details (such as policy, plate or license numbers; the backup carries no photos or scans, condition photos included). Keep them somewhere private.

Permissions

MileWorks asks for each permission only when you use the feature that needs it, and works without any of them. You can turn them off at any time in your phone's settings.

Location ("While using the app" only, never "Always"): to find the gas station and address for a fill-up or charging session (when you tap Use my current location, or take a photo for a new fill-up that has no station yet and the photo carries no position of its own), to add where an odometer reading, trip, maintenance visit or expense was logged, or where a car was bought or picked up, when you choose to (Use where I am, or a new one's photo taken with the camera that carries no position of its own), to look up the street address of a spot you add (coordinates typed, a pin, a photo's own location) and to place stops on the Passbook's map, both on Android only (its address lookup requires it; an iPhone's doesn't, so it isn't asked there), to show where you are on the Passbook's map to drag and zoom when you tap Where you are (offered only once location is allowed; it never asks), and to measure the trips you record (MileWorks Pro). While a trip records, from Start until you tap Stop, the app keeps using location with the app in the background or the screen off: Android shows a "Recording a trip" notification the whole time (a location foreground service), and iPhone shows its location indicator. Location is never used in the background otherwise. The recorded track stays on your phone; only where the trip started and ended goes to your phone's address lookup (row 5). Trip recording needs precise location.
Location "All the time" and physical activity (Android, automatic tracking, MileWorks Pro + Automatic tracking; asked only when you turn it on, after the app explains what it collects): the phone's motion sensors tell when you start driving, and location then records the drive in the background, with the app closed too; Android shows "Recording a drive" while it does. With Start on the walk to the car on (off unless you turn it on), location also turns on when you start walking ("Watching for a drive"), so a drive is measured from where the car was; a walk is never saved as anything, and the tracking library deletes its locations after 3 days. Your drives stay on your phone; only each drive's start and end (and a crossing's spots) go to your phone's address lookup (row 12). Turning it off in Settings → Trips → Automatic tracking stops it.
Nearby devices (Android, from app build 1.0.9; asked only when you choose your car's Bluetooth on the Automatic tracking page): to list your phone's paired Bluetooth devices and tell when the phone connects to the car you chose (Android Auto connects through it), so a drive starts there. MileWorks keeps that car's Bluetooth name and address on your phone only, and Android's own dialog links the car to the app; Forget this car unlinks it. (Without automatic tracking, the bullet above holds: "While using the app" only, never "Always".)
Camera: to scan or photograph the pump's screen, the odometer, receipts and maintenance invoices (the scanner reads them on your phone as you aim, and keeps only the photo it takes, with the entry), to read your VIN's barcode, and to photograph receipts you attach. Only while the scanner or the camera is open; never the microphone.
Photos: to choose an existing photo. On Android, the app also asks to read where a photo was taken, so the station and address can come from it. On iPhone, choosing Save Image when you share a picture from the app (such as your year in driving) asks to add it to your photo library; that permission only adds pictures, it can't read them.
Notifications: for the reminders you turn on in Settings → Alerts (a fill-up check, monthly home-charging total, entries that need a look, a drop in fuel economy, a weekly summary of your driving, monthly recap, documents coming up for renewal, maintenance coming due, the Dash's welcome to a new country or state as a notification), and on Android for the "Recording a trip" notification while you record a trip (asked when you first start one), and for automatic tracking's notifications (the drive under way, and each drive to sort, whose buttons sort it from the lock screen). They're made and scheduled on your phone from your own log; no push service is used and nothing is sent.
Files and folders: to attach a PDF or image, import a CSV, or (Android) choose a backup folder. The app sees only the file or folder you pick.

No ads, no tracking, no selling

MileWorks shows no ads, contains no advertising or analytics tools, doesn't use the advertising ID, and doesn't track you across other companies' apps or websites. It has no crash-reporting tool: the only report of a problem is what its update service receives (row 8), which updates failed to start and, after a crash while starting, a short error message. We don't sell or share personal information, and we don't build profiles.

Apple and Google give app developers summary statistics about installs and, if you've allowed your phone to share diagnostics with developers, anonymous crash reports. These come from Apple and Google, not from the app, and don't identify you.

Purchases

MileWorks Lite is free. MileWorks Plus and Pro are bought through the App Store or Google Play, which handle the payment; we never see your card or bank details, name or email address.

Paid plans aren't on sale yet. Once they are, to verify purchases and restore them on a new phone, the app uses RevenueCat, Inc., which receives the store's receipt for your purchase: the product, price and currency, the store country, dates, trial and renewal status, and a random customer ID that RevenueCat creates. We see this purchase information (with no name or email) and use it only to unlock what you bought, handle refunds and keep accounts and tax records.

Children

MileWorks is made for drivers and isn't directed at children under 13 (or under the age your country sets). We don't knowingly collect personal information from children. If you think a child has sent us personal information, contact us and we'll delete it.

Keeping and deleting your data

Your log stays on your phone for as long as you keep it there. You can delete it at any time:

One entry: tap it in History, then Details → Delete. One vehicle and everything logged for it: Garage → Edit on the vehicle's card → Delete vehicle. Deleting an entry or vehicle also deletes its photos and documents.
Everything: Settings (the gear at the top right) → Data → Start over → Erase everything deletes every vehicle and everything logged, with its photos and receipts, and the automatic backup's copies: the ones on the phone, and the app's own backup file in a folder you chose. What the app keeps about the log goes too: a trip being recorded or not saved yet, the places and exchange rates looked up, the recalls and alerts you've seen, the home-screen widget's numbers, the map's cache of the streets you looked at, photos from forms you never saved, and the app's copies of files you exported or shared, and the drives automatic tracking found and their paths, with the tracking library's locations and its log (automatic tracking turns off). The weather lookup is turned off, so nothing is sent for a new log until you turn it on again; your other settings stay. Deleted entries are overwritten in the app's database file, not just marked as free. To keep a copy, use Export everything first.
Uninstalling MileWorks deletes everything the app keeps on the phone, including the backup copies on the phone. It doesn't reach a folder you chose for the automatic backup (Android): the app's backup file stays there until you delete it, or use Erase everything or Stop saving to this folder before uninstalling.
Not deleted by the app: files you exported or shared where you sent or saved them, other files in a backup folder you chose, and your phone's own iCloud or Google backup. Delete those where they are kept.

What we hold ourselves:

Emails you send us, kept as long as needed to help you and then for up to 24 months, unless you ask us to delete them sooner.
Purchase records (once paid plans launch), kept as long as the law requires for tax and accounting (Apple, Google and RevenueCat also keep their own records under their terms).

To withdraw consent, turn off a permission, stop using a lookup, or uninstall the app.

Your rights

Because your log is on your phone and not on our servers, the app itself covers most requests: you can see, export (Settings → Data → Your data → Export everything), correct and delete your data at any time. For anything else, such as a copy of the emails you've sent us or deleting them, write to [email protected]. We aim to answer within 20 business days, and always within the time your law sets. We won't treat you differently for using your rights.

European Economic Area and United Kingdom (GDPR and UK GDPR). MileWorks LLC is the controller. We rely on providing the feature you asked for (lookups, purchases) and on our legitimate interest in keeping the app working and up to date (update checks with their failed-update reports, ML Kit diagnostics). You have the rights to access, correct, erase, restrict, object and port, to withdraw consent, and to complain to your data protection authority. Some services above are in the United States or elsewhere: Expo is certified under the EU-U.S. Data Privacy Framework, with its UK Extension and the Swiss-U.S. Framework, and RevenueCat (once paid plans launch) works under its data processing addendum for the GDPR and UK GDPR. MileWorks isn't offered in the EU or the UK yet; before it is, this section will name our representative there if the law requires one.
California (CCPA/CPRA). We don't sell or share personal information and don't use sensitive personal information to infer anything about you. You can ask to know, delete or correct the personal information we hold (in practice, emails you've sent us and purchase records), and you won't be discriminated against for asking.
Canada (PIPEDA, and Quebec's Law 25). You can ask to see and correct the personal information we hold. The person responsible for personal information at MileWorks LLC is its managing member, reachable at [email protected]. Some services above are outside Canada (in the United States and Europe). You can complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information.
Mexico (Ley Federal de Protección de Datos Personales en Posesión de los Particulares, 2025). MileWorks LLC, 1209 Mountain Road Pl Ne, Ste N, Albuquerque, NM 87110, is responsible for your personal data. Every use described above is needed for the feature you're using; we have no secondary purposes such as marketing. You can exercise your rights of access, rectification, cancellation and opposition (ARCO) and revoke your consent by writing to [email protected]. A Spanish version of this notice will be published before MileWorks is offered in Mexico.

Security

Every connection the app makes uses encryption (HTTPS). Your log is as safe as your phone: use a screen lock, and keep exported files and backups somewhere private.

Changes to this policy

If we change this policy, we'll update the date at the top. If a change affects what leaves your phone (for example, optional accounts or cloud sync in a later version), we'll say so in the app before it applies and ask before anything new is sent.

Contact

MileWorks LLC 1209 Mountain Road Pl Ne, Ste N, Albuquerque, NM 87110 Privacy: [email protected] Support: [email protected]