Your miles. Your privacy.

Information you save

• Your account: name, email address, an account identifier, password and recovery-code verification hashes, and sign-in sessions. Your Field Miles password is stored as a hash, not readable text.
• Your mileage: trip dates, starting points and destinations, distances, categories, purposes or notes, vehicles, reimbursement status, route locations, recording quality, and classification history.
• Your places and preferences: favorite names and addresses, optional map coordinates, matching radius, classification rules, reporting time zone, and other mileage settings.
• Files you choose to import: supported place and trip fields from your CSV or JSON file. Files are parsed on your device for preview; the records you confirm are sent to your account. The original upload file is not stored by the importer.

Location and automatic tracking

When tracking is enabled and you allow location access, Field Miles collects precise latitude and longitude, timestamps, location accuracy, and speed when the device provides it. Locations are temporarily queued on your device, then sent to the server to detect drives, calculate mileage, and match saved places. Raw recording batches and unfinished recordings are stored as well as completed trips.

The installed phone app can continue recording in the background after tracking starts in the foreground. You can pause tracking in the app or change location access in your phone settings. Reopen the app after a force-quit or phone restart; recording is not guaranteed while the app is terminated. Browser recording requires the page to stay visible.

Tracking and classification serve your mileage log. Uncertain trips require review, and your confirmed categories take priority over automatic rules.

Optional Site Clock connection

A Field Miles account works without Site Clock. If you connect it, your Site Clock email and password are sent to Site Clock to verify the connection. Field Miles does not retain that password. It stores an encrypted address-access token and a linked account identifier to refresh your work addresses.

The connection imports jobsite names, addresses, available coordinates, and active or deleted status. It does not import payroll, invoices, or timeclock entries, and it does not send your Field Miles trips or personal favorites to Site Clock.

Past jobsites stay saved. Making a job inactive or deleting it in Site Clock does not delete its saved address or existing trip rule in Field Miles. Disconnecting Site Clock also leaves saved places in your mileage account. Deleting your Field Miles account does not delete your Site Clock account or its original records.

Hosting, security, and sharing

Field Miles uses Cloudflare Workers and database storage to provide the service. Existing beta installations may use the earlier ChatGPT Sites hosting address during the transition to independent hosting. Your account and mileage records are sent over HTTPS and separated by account. Service operators and hosting providers may access data as needed to operate, secure, or troubleshoot the service.

Sign-in cookies keep you authenticated. Device storage holds pending locations, session-completion receipts, automatic-tracking preferences, and any unfinished account-deletion request. The browser cache stores an offline page and app icons, rather than your mileage log. Hosting infrastructure also processes network and request information; sign-in protection uses short-lived, hashed attempt counters.

Field Miles does not include advertising or cross-app tracking code. There is no automatic upload of the bug report you write: you preview it and choose whether to save or share it. Automatic diagnostic fields exclude account identifiers, email, addresses, route coordinates, credentials, and raw error messages; your own description can contain information you enter.

CSV, JSON, and bug-report exports go to the destination you choose. Copies you download, email, or share are outside the app's deletion control.

Retention and deleting your account

Your saved records remain available until you remove them or delete your account. Deleting an individual visible trip does not erase its underlying raw recording history. The beta does not currently apply an automatic age limit to mileage records.

Use Settings → Delete account to verify your identity and permanently remove the account and its active service records, including saved trips, favorites, preferences, raw recordings, sign-in sessions, import receipts, and the stored Site Clock connection. Tracking stops and this account's pending locations are erased on the device completing deletion. Keep any exports you need before continuing.

Deletion cannot remotely erase an offline phone, another browser's local storage, or files you have already exported. Open other installations to stop tracking and clear remaining local data, or remove the app from those devices.

A minimal deletion marker containing an opaque account identifier and deletion time is retained to reject old account recordings. Hashed old-session markers and deletion receipts remain valid for up to 30 days so interrupted requests can be recognized; expired receipts are removed during later account-service activity. These markers do not contain your name, email, addresses, or trip locations.

Operational backups and private migration copies may retain earlier data separately from the active database. They are not erased immediately by the in-app action. A verified deletion schedule for those copies has not yet been established for this beta; do not assume that active-database deletion instantly removes every backup.

Your choices and questions

You can review and edit trips and places, pause recording, turn off automatic classification or route learning, disconnect Site Clock, and export your saved records in Settings. The JSON export includes saved trips, places, and preferences; it does not include raw capture batches or unfinished server recordings.

For account, privacy, or recording questions, see Help & support. This page will be updated as the beta's hosting and data controls change.