Your miles. Your privacy.

Who operates Field Miles

Field Miles is operated by Ruvim Labs. For privacy questions or data requests, email kucheruvim00@gmail.com. You can also use our account deletion page.

Information you save

• Your account: name, email address, optional phone number and report profile, 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.
• Background saving: a random identifier for this app installation is stored with your account to associate and confirm background location uploads. The phone keeps a protected authorization limited to uploading its recordings. The installation identifier is used for app functionality, not advertising or tracking across other companies' apps and websites.
• 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, JSON, or values-only spreadsheet 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. On supported iPhone builds, you can grant Always location access to let the phone monitor movement and an area around your recent position, wake Field Miles after it closes, and resume recording. Turning off Auto drive detection stops precise recording and these recovery monitors. On current iPhone builds, queued locations can upload in the background when a connection is available and remain on the phone until the server confirms them. iOS controls wake-up and transfer timing, so uninterrupted recording is not guaranteed. Reopen Field Miles after force-quitting it or restarting your phone to check recording status. Older builds require the app to be open to finish syncing. 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.

Home base and driving habits

Field Miles can use your recorded evening arrivals and next-morning departures to suggest a possible home location. The suggestion stays unconfirmed until you accept it. A saved home is kept until you change or remove it, and a street address is used only when you enter it or it is already in your saved places. If you dismiss a suggestion, the app keeps that rejected location in your account settings so a small GPS change does not prompt you again.

Trip predictions use saved places, your vehicle, work hours in your reporting time zone, and categories you manually confirm. The default work schedule is Monday through Friday, 7 AM–6 PM, and you can change it. Automatic categories do not train themselves. Work hours alone do not establish a trip's purpose.

These comparisons run within Field Miles; your location history is not sent to an external AI service. Address lookup and map display are described below, and their results do not establish whether a trip was for business. You can turn off home suggestions, route learning, or automatic classification in Settings. Deleting your account removes these settings with the other active account records.

Trip addresses and maps

When you view GPS trips or places you visit often, Field Miles first uses names and addresses from your saved places. External address lookup is off until you enable it in Settings → Address lookup. If you allow it, for endpoints that still need a recognizable label the server can send the starting or ending latitude and longitude to Photon, an OpenStreetMap-based address service operated by komoot. These requests include a Field Miles service identifier and lookup parameters, but not your name, email, trip identifier, vehicle, category, or full route. Nearby results are labeled as approximate; they do not prove which business you visited.

With your address-lookup permission, to locate saved places without a manual pin Field Miles also sends the saved street address to Photon. A confidently matched location is stored with that place for trip matching and your chosen work-area radius. Failed lookups retry later; an unclear address stays unmatched. These requests do not include your name, email, account identifier or trip history.

You can turn Address lookup off in Settings at any time to stop future requests. Recording, manual addresses and saved locations continue to work without it. A lookup already sent may finish; previously saved addresses remain until you edit or delete the record or account.

Resolved labels stay with the trip. A separate cache of endpoint lookups is kept in your account to avoid repeated requests; expired cache entries are removed during later lookup activity. Cached endpoint locations and addresses are removed when you delete your account.

Your recorded route, endpoint pins, and work-radius preview can be shown without contacting a street-map provider. Choose Load street map after reading its disclosure to load OpenStreetMap tiles for that view. The provider receives your IP address, the Field Miles site origin, and the map areas requested. Your full recorded route is drawn on your device and is not sent as a route file. Choose Hide street map to stop further tile requests; requests already sent may finish. This choice applies only to the current trip or place preview; it is not saved across app reloads. Standard browser caching may retain map tiles; the app does not download offline map areas. Opening a link labeled Google Maps sends the selected pin to Google Maps.

Address lookup and street tiles depend on external services and may be temporarily unavailable. You can still use saved labels, edit trip names, and review the recorded route. See Photon and OpenStreetMap privacy information for those services.

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.

Optional Apple and Google sign-in

On versions that offer these options, you can choose Apple or Google to create or sign in to a Field Miles account. We receive a provider-specific account identifier and the name and email address the provider shares with your permission. Apple may provide a private relay email address if you choose Hide My Email. Field Miles does not receive your Apple or Google password.

We use this information to identify your Field Miles account, protect sign-in, and display your account name. We keep the linked provider identifier and encrypted authorization tokens so we can maintain the connection and revoke its authorization when you delete your Field Miles account. We request basic sign-in information; this feature does not request your email messages, contacts, files, calendar, or location history. Field Miles does not send your mileage records to Apple or Google as part of signing in.

If you already have Field Miles records, sign in with your existing method and choose Continue with Apple or Continue with Google in Account → Sign-in & security. Linking is an explicit action within your signed-in account. Matching email addresses alone do not merge accounts or move trips or subscriptions.

Sign-in uses short-lived verification records, a browser cookie, and temporary browser-session storage to connect the provider response to the request you started. A separate, one-use confirmation can verify account deletion for up to five minutes. Expired server sign-in attempts are removed during later sign-in activity. These controls are for authentication, not advertising.

Deleting your Field Miles account revokes stored provider authorization and removes its active linked sign-in records. It does not delete your Apple or Google account. The provider operates its own sign-in service under its privacy policy: Apple privacy and Google privacy.

Your own backup copies

Settings → Your backups lets you save a separate copy of the records already saved to your Field Miles account. A backup includes saved trips and their route locations, places, and selected report settings. It excludes passwords, recovery codes, sign-in tokens, payment records, subscription access, unfinished recordings, and locations still waiting to upload from a device. Saving a backup does not clear a device's upload queue.

You choose where a downloaded or shared backup goes, such as Files, iCloud Drive, or an installed Google Drive app. Field Miles does not request Google Drive access or automatically upload to Google Drive. Signing in with Apple or Google does not turn on backups or give Field Miles access to your other cloud files.

On supported iPhone versions, you can separately enable automatic iCloud backups. After the app syncs while open, it can save a copy in its dedicated folder in your iCloud Drive; Apple controls when that file finishes uploading. The app distinguishes a file waiting to upload from a confirmed iCloud upload. This is not a guaranteed daily backup while the app remains closed. Copies use your existing iCloud storage, and a full or unavailable iCloud account can prevent a backup.

Automatic iCloud permission is specific to the Field Miles account and the iCloud account on that device. Signing out, deleting your Field Miles account, or changing the iCloud account stops automatic saves. Previously saved or shared copies remain under your control; remove copies you no longer want from Files or your chosen storage service. Account deletion cannot erase those copies remotely.

Backup and restore are available without an active subscription. Restore requires the same Field Miles account, a preview, and confirmation. It adds missing saved records without replacing existing ones; records intentionally deleted since the backup may be among the missing records shown in the preview. It does not restore subscription access, sign-in methods, recording permission, or external-service consent.

Subscriptions

Apple processes subscription payments. Field Miles stores your plan, Apple transaction identifiers, an account-linked purchase token, purchase and expiration dates, and refund or revocation status to verify access and restore purchases. Field Miles does not receive your payment-card details. You can manage or cancel your subscription in Apple Settings. Deleting your Field Miles account does not cancel your Apple subscription.

Hosting, security, and sharing

Field Miles currently uses ChatGPT Sites hosting with Cloudflare Workers and database storage to provide the service. 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.

The ChatGPT Sites Data Processing Addendum governs hosted personal data. It requires confidentiality, appropriate security measures, and comparable contractual obligations for hosting subprocessors.

Sign-in cookies keep you authenticated. Device storage holds pending locations, session-completion receipts, automatic-tracking preferences, pending trip-classification choices and Undo requests, and any unfinished account-deletion request. Classification choices are saved on your device before the screen advances, then synced to your account; unfinished saves resume when the app is open and connected. The browser keeps an offline page and app icons. Separate device storage can cache your signed-in account's trips, places, and preferences so they display quickly while current records load. This cache is separated by account and cleared on sign-out or account deletion. Hosting infrastructure retains request and error diagnostics used to operate and secure the service, including IP address, approximate country, request path and time, browser or app information, response status, and server timing. These records may be associated with a signed-in request. Sign-in protection also 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. The diagnostic summary included in a bug-report export excludes account identifiers, email, addresses, route coordinates, credentials, and raw error messages; your own description can contain information you enter. Hosting request logs are separate from this optional export. ChatGPT Sites also automatically measures site traffic and provides visitor and page-view totals over time. These hosting analytics are not used for advertising or cross-company tracking.

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 Account → Delete account to verify your identity and permanently remove the account and its active service records, including saved trips, favorites, preferences, raw recordings, cached endpoint addresses, sign-in sessions, background-upload authorizations and receipts, 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.

Private operational backups are encrypted. Each backup run removes copies older than 28 days; our operator retention limit is 30 days. Before a recovered service is reopened, we apply current account-deletion markers and invalidate restored sign-in sessions and upload credentials.

Cloudflare D1 recovery history can retain earlier database states for up to 30 days. An account deletion is applied to the active service immediately; it does not immediately erase that recovery history. Before restoring earlier records, we apply the current account-deletion markers so deleted accounts are not reactivated. Other provider-managed backups and historical private migration copies have separate controls whose deletion timing has not yet been verified for this beta. Contact us for the status of a deletion request; we do not promise that active-service deletion immediately 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.