Your mileage belongs to you.

1. Who this policy covers

This Privacy Policy applies to the Milelight iPhone app and the Milelight website. “Milelight,” “we,” “us,” and “our” refer to the developer or legal entity identified as Milelight’s seller on its App Store product page. That developer is responsible for the processing described in this policy. Contact us through the public support form linked below.

The app does not require an account. We therefore do not maintain an online Milelight profile tied to your trip history.

2. Information the app keeps on your device

Milelight stores mileage records locally using Apple’s on-device storage technologies. A saved or pending drive may include its date and time, duration, distance, purpose category, business purpose, notes, place labels, start and end coordinates, and the GPS points that form the route. Manually entered trips may contain the details you choose to enter.

Local preferences may include working hours, Auto Track and notification choices, display settings, an optional report name, vehicle name, odometer values, estimate preference, onboarding status, and a legacy device-local drive allowance record retained from earlier app versions. That record no longer grants new-drive access. Active-drive recovery files and unreviewed detected drives are also stored on the device so an interrupted recording can be recovered.

Ordinary recording does not upload your saved mileage log or full route history to a Milelight cloud-sync service. Automatic reliability reports, optional product analytics, subscription reporting, and optional support diagnostics are separate data flows described below. Diagnostic sharing can include selected settings and limited pending-drive information.

3. Location, routes, motion, and notifications

GPS recording requires Precise Location. When you tap Start with only Approximate Location enabled, Milelight explains how to enable Precise Location or add the trip manually instead. Manual mileage entry does not require location permission. A manually started recording may continue while Milelight is in the background or your iPhone is locked. If you choose to enable Auto Track, Milelight uses background location and Motion & Fitness activity to help recognize drives while the app is not open. Auto Track requires Always and Precise Location, Motion & Fitness, and Background App Refresh.

Working hours, when enabled under Automatic Drive Detection, limit which automatic trips are recorded. Low-power wake mechanisms can remain available between work periods. If Improved (Beta) and Always ready outside working hours are enabled, Milelight can also retain limited, protected departure evidence on your iPhone outside the schedule. This does not save out-of-hours automatic trips or enable remote sharing. Precise departure collection can begin before a drive is confirmed and uses battery. iOS controls update delivery and may delay a wake; opening Milelight rechecks readiness. Manual recording remains under your control outside scheduled hours.

Motion activity is evaluated on your device to help distinguish driving from walking and confirm parking, using limited recent arrival step counts. It is not added to the saved mileage log. Motion and step evidence can be included in optional diagnostic sharing or a report you send to support. Detected drives remain on your device for review and do not enter saved history or reports until you approve them.

Locking your iPhone or switching apps does not itself stop a supported background recording. Force-closing Milelight by swiping it away can prevent background tracking until you open it again. On reopening, the app keeps the last available recording checkpoints and evaluates available recovery evidence; it cannot reconstruct locations or miles that were not recorded during an interruption.

If enabled, drive alerts are scheduled locally through iOS. Milelight also uses a Live Activity to show an active drive on the Lock Screen or Dynamic Island. Separately, optional remote diagnostics can register an Apple push token to request diagnostic refreshes during a paired session; this does not guarantee delivery or continuous background execution.

4. Apple services

Milelight uses Apple mapping and geocoding services to display maps and turn endpoint coordinates into readable place names. Apple therefore receives endpoint coordinates for place lookup and map-area requests when maps are displayed. Apple processes those requests under its own terms and privacy practices.

Apple processes App Store purchases and payments. Milelight reads StoreKit product information and verified transaction and entitlement information to show plans, complete purchases, restore purchases, and enable Milelight Pro. Milelight does not receive your payment card number.

Depending on your Apple and device settings, Apple may process App Store, diagnostic, or aggregated app-usage information, and may provide the developer with transaction, sales, or aggregated reporting. Device backups may include Milelight’s local data. Milelight does not operate a separate cloud-backup service.

5. Automatic reliability reporting

Milelight uses Sentry to automatically receive technical crash, watchdog-termination, serious app-hang, and storage-opening error reports. Reports can include stack traces, app and iOS versions, device characteristics, lifecycle and session information, and technical device/app or installation identifiers. These identifiers can associate reports with a device or installation; the reports should not be treated as anonymous. Connection information and approximate geographic context may also be processed by the reporting service.

We use this information to diagnose failures, improve reliability, and provide support, not for advertising. Milelight disables screenshot and view-hierarchy capture, session replay, automatic screen and network breadcrumbs, and performance tracing. Its Sentry configuration does not attach GPS routes, precise coordinates, trip addresses, labels, purpose notes, or mileage reports. Automatic technical reporting is separate from the optional diagnostic controls below.

5a. Optional product analytics

This section applies to builds that include “Help improve Milelight”; older builds may not include product analytics. On new installations of build 74 and later, the setting is on by default. Earlier builds used an off-by-default setting. Saved choices, including an explicit opt-out, are preserved; an upgrade does not deliberately override your saved choice. Check your current setting in Settings → Privacy → Help improve Milelight. When enabled, Firebase/Google Analytics receives feature actions, onboarding and permission outcomes, saved-trip and classification actions, successful report exports, sharing outcomes, paywall interactions, and technical task results and durations. We use this information to improve Milelight and understand usage and subscription conversion, not for cross-app advertising.

Reports include app version/build, distribution environment, timestamps, random event identifiers, and a random analytics installation identifier. These identifiers associate reports from the same installation; reporting is not anonymous. Our custom analytics fields do not contain GPS coordinates, routes, addresses, trip names or notes, report contents, raw error text, or specific medical or charitable classifications. Trip categories are limited to business, personal, other, or unclassified.

With analytics enabled, Google also automatically measures app lifecycle and sessions, derives approximate region from masked IP addresses, and records StoreKit purchase and subscription events with product information and prices. It uses an app-instance identifier. This is separate from GPS location access. Milelight disables advertising storage, ad personalization, automatic screen reporting, and vendor-identifier collection in its analytics configuration.

You can turn this optional reporting off in Settings → Privacy → Help improve Milelight at any time. A default-on setting is not an affirmative consent action. Turning the switch off stops new product-analytics reporting, clears queued local analytics events and milestones, and resets the analytics identifier. Re-enabling starts with a new identifier; actions taken while analytics was off are not backfilled. The switch does not automatically erase reports already received by a provider. Location permissions, automatic tracking, purchases, and your subscription remain available with product analytics turned off.

5b. Operational subscription reporting

Apple’s StoreKit continues to manage purchases and determine access to Milelight Pro. This section applies to builds that include RevenueCat reporting; older builds may not include it. In builds with this feature, we use RevenueCat to report and reconcile purchases, restores, and subscription outcomes. RevenueCat receives App Store transaction information and a randomly generated subscription identifier. Milelight does not send GPS routes, addresses, trip notes, or report contents to RevenueCat, and does not receive your payment-card details.

This operational reporting is separate from optional product analytics and continues when “Help improve Milelight” is off. Product analytics and RevenueCat currently use separate identifiers. A private service for linking those identifiers is not available in this version, so Milelight does not currently create that cross-service mapping. Any future private identity link would require analytics consent and an accurate updated disclosure. Google can still measure purchases within its own analytics stream when analytics is enabled.

6. Optional private diagnostic sharing

Remote sharing is off by default. It starts only after you pair your phone with the private Milelight Diagnostics dashboard and choose to start sharing. The dashboard is hosted through OpenAI Sites and its hosting infrastructure. It receives detector state, sensor timing and quality, motion classifications and confidence, limited arrival step counts, permissions, app lifecycle and diagnostic settings, recording-access availability and check state, issue markers you choose to create, and summaries of an active drive and up to ten pending drives. Summaries include recorded times and mileage. A pairing/session identifier and, when registered, an Apple push token support delivery. The dashboard owner can associate the information with the pairing label for your phone.

A separate location-sharing switch is off by default. Turning it on includes precise diagnostic coordinates and displayed starting and destination addresses or user-edited place labels for pending drives. These details can reveal sensitive places. Remote sharing does not upload your full saved mileage log, saved route history, purpose notes, or payment details. It uses existing execution opportunities rather than guaranteeing live updates.

Turning location sharing off removes location details still queued on your phone, but cannot recall delivered information. Stopping remote sharing clears the local queue and pairing credentials and attempts to revoke the server session. It does not erase already uploaded records. The dashboard owner can separately delete the session and its uploaded records. Retention details are below.

7. Reports, temporary files, and sharing

Milelight creates PDF and CSV exports from your local records. PDF previews also prepare protected temporary files for sharing. Temporary PDF files are removed when sharing completes or is dismissed, or when their preview is dismissed. If the app is interrupted, leftover report folders older than 24 hours are cleaned up on a later launch. A report can contain trip dates and times, locations, mileage, purposes, notes, estimates, and any optional driver, vehicle, or odometer details you choose to add.

An export leaves Milelight only when you use the iPhone share sheet or another export action. You select the recipient, app, or storage service. Copies you send, save, print, or back up are then controlled by you and the receiving service.

Recording a local diagnostic session is a separate, optional control. While enabled, its protected, size-limited local report includes detailed GPS samples and times, selected endpoints, resolved addresses, motion and step evidence, and diagnostic decisions and issue markers. It can also include subscription-status checks, such as verified active, expired, revoked, or upgraded status, and purchase or restore check triggers. These diagnostics do not include payment-card details, prices, receipts, or transaction identifiers. The report is not automatically sent to Sentry or the dashboard. Turning recording off preserves existing diagnostic data; Clear diagnostic data removes it. You decide whether and where to share the export. A separately requested motion-history report contains activity classifications, not GPS routes.

If you send a diagnostic file to us, we receive its contents and any identifying information in your message. Review files before sharing and send only what is needed to investigate your request.

8. Website visits and support requests

This website does not use a Milelight advertising or behavioral analytics system. As the hosting provider, Netlify may process ordinary web-request information such as an IP address, browser or device information, requested page, and request time to deliver and secure the website.

If you submit the support form, we receive your email address, selected support topic, message, and any optional name or app and device details you provide. We use that information to investigate and respond. Please do not submit full routes, tax documents, payment-card details, or other sensitive records.

Netlify processes and stores the form submission on our behalf. Netlify may also apply automated spam and abuse filtering. Support information is not added to an advertising profile or marketing list.

9. Why we process information

We process technical diagnostics and support information to provide the help you request, troubleshoot Milelight, maintain service quality, protect the website and support channel from abuse, keep necessary business records, and comply with legal obligations.

When enabled, we process product analytics to understand feature use, setup outcomes, reliability, and conversion. We separately process subscription information for purchase and restore reconciliation and operational subscription reporting.

Where privacy law requires a legal basis, the basis may be taking steps at your request, performing our agreement with you, complying with law, our legitimate interests in operating and securing Milelight, or your consent when that basis is required.

10. When information is disclosed

We disclose information only as needed to service providers such as Google/Firebase, RevenueCat, Sentry, Netlify, and OpenAI Sites and its hosting infrastructure, to Apple services you choose to use, to recipients you select through the share sheet, when required by law or valid legal process, or when reasonably necessary to protect users, rights, safety, and service integrity.

Service providers that process personal information on our behalf are required to protect it consistently with this policy and applicable law. Apple services are governed by Apple’s own terms and privacy commitments.

Milelight does not sell or rent personal information, share it with data brokers, or share it for cross-context behavioral advertising. Technical identifiers support the product analytics, subscription reporting, troubleshooting, and support described above, not cross-company advertising profiles. The app contains no advertising SDK.

11. Retention and deletion

Saved trips remain on your device until you delete them or remove the app. You can delete individual trips from Trips and discard a detected drive during review. Deleting Milelight and its data in iOS generally removes its local data from that device. Offloading the app may retain its documents and data. Apple device backups and copies exported elsewhere remain separately controlled.

Milelight has no user account to deactivate. Apple manages trial eligibility and subscription history through your Apple Account. Deleting trips or reinstalling Milelight does not reset Apple’s introductory-offer eligibility or cancel a subscription.

The app-owned offline analytics queue is limited to 100 events and a maximum age of seven days. These local limits are not Google or RevenueCat server-retention periods. Reports already received follow the providers’ configured retention and deletion processes. Turning analytics off, resetting its identifier, or removing the app does not automatically delete those reports or operational subscription records. Contact support about retention or a deletion request. We may need additional information to locate pseudonymous records; an email address alone may not identify them, and some records may need to be retained for legal or operational obligations.

Remote pairings expire after 24 hours. Uploaded diagnostic events are available only within their 24-hour window. Expired events are physically removed on a later authenticated dashboard or upload request, not by a guaranteed deletion timer. Session metadata becomes eligible for cleanup 24 hours after the session expires. Revocation removes its push registration but does not itself erase uploaded events. A dashboard session deletion removes its records and push registration. Exported copies are separate.

Sentry reports follow the service’s configured retention and deletion processes. Hosting and security logs may have separate retention periods. Contact us to request deletion of information we can identify; a technical report may not be identifiable from your email alone. Stopping optional sharing or deleting the app does not erase reports already delivered to service providers.

Support messages and diagnostic files sent to us, including email and downloaded copies, are kept only as long as reasonably needed to resolve and follow up on the request, protect the service, keep appropriate records, and meet legal obligations. We delete or de-identify them when they are no longer needed for those purposes. You may request deletion through the support page.

12. Your device choices

Auto Track is optional and can be turned off inside Milelight. You can review or revoke Location, Precise Location, Motion & Fitness, Background App Refresh, Live Activities, and notification access in iPhone Settings. Features that need a permission may stop working when that permission is removed.

You can edit or delete saved records in the app, discard pending detected drives, control Apple backup settings, choose whether and where to export a report, and remove the app to delete its local data from the device.

Local diagnostic recording, remote diagnostic sharing, and remote location sharing have separate controls. Turning them off does not disable automatic Sentry reliability reporting. You can request deletion of information already received through support.

Optional product analytics has its own “Help improve Milelight” control in Settings → Privacy. New installations on build 74 and later default to on; saved opt-outs are preserved. Turning it off does not disable operational RevenueCat subscription reporting, automatic Sentry reliability reporting, or separately enabled diagnostic sharing. Those controls do not change Apple’s subscription or payment records.

13. Privacy requests and rights

Depending on where you live, you may have rights concerning personal information we hold in analytics, subscription, diagnostics, or support records, including access, correction, deletion, restriction, portability, or objection. You may also have the right to complain to your local privacy regulator.

Submit a request through the support page using the same email address used for the original request, when applicable. Include the approximate report time or diagnostic session identifier if available, not your full route history. We may need to verify the request and may retain information when required by law. We cannot retrieve or delete your locally stored mileage log remotely; diagnostic information you shared is handled separately.

14. Security

Milelight relies on iOS protections and writes active-drive recovery and detected-drive files using Apple data-protection options. We also use reasonable administrative and technical measures for support information. No storage or transmission method is guaranteed to be completely secure, so protect your device and review exports before sharing them.

15. Children

Milelight is a mileage-recordkeeping tool and is not directed to children under 13. We do not knowingly solicit personal information from children through the support form. If you believe a child submitted personal information, contact us so we can review and delete it as appropriate.

16. International processing

Apple, Google/Firebase, RevenueCat, Sentry, Netlify, and OpenAI Sites and its hosting providers may process information in countries other than the one where you live. Their processing is governed by their terms, privacy statements, and applicable transfer safeguards. We use service providers subject to contractual and legal protections appropriate to their role.

17. Changes and contact

We may update this policy when Milelight, its website, or legal requirements change. The effective date above identifies the current version. Material changes will be highlighted where appropriate.