Legal

Privacy Policy

Last updated July 23, 2026

MileCheck (“the App”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our mobile application.

Information We Access

Location Data

The App accesses your device’s GPS location to:

• Display your nearest mile marker — the core function of the app, calculated on your device
• Show your current speed and direction — helps you stay oriented on the road
• Auto-detect your state — loads the correct milepost and alert data for your region
• Log trip sessions — if you choose to use the trip logging feature
• Plan a highway corridor — if you use the Premium route-planning feature, your current location and your typed destination are sent to Google Routes API and Google Places API via our server. See the Google Maps Platform entry under Third-Party Services for details.
• Alert you to nearby wildfires — if you turn on wildfire alerts (off by default), a rounded, approximate location is stored with your notification registration so we can notify you about new fires near you even when the app is closed. See Push Notifications below.

Important: Your precise GPS coordinates are processed on your device for milepost calculations, and your precise coordinates and trip history are never stored on our servers. Approximate location is sent to third parties to retrieve weather, route planning, and road alert data, as detailed below. The one exception where location is retained on our server is the optional wildfire-alert feature, which stores a rounded, approximate location with your notification registration — described in full under Push Notifications.

Trip Log Data

If you use the trip logging feature, the App stores on your device:

• Start and end timestamps
• Mile marker positions during your trip
• Route, direction, and distance
• Any notes you add to a trip
• An optional GPS path of the trip (used to draw a mini-map of your route in the Trips tab)

Trip data is stored locally on your device. You can configure how long trips are kept (3, 7, 14, 30, 90 days, or forever) in Settings, delete individual trips, or clear all trip history from the Trips tab at any time.

Subscriptions and Purchases

MileCheck offers an optional premium subscription to unlock additional features (map, alerts, and trip logging). Here is how subscription data is handled:

• Payment processing — All purchases are processed by Apple (App Store) or Google (Google Play). MileCheck never receives, stores, or has access to your payment information, credit card numbers, or billing details.
• Subscription management — We use RevenueCat to manage subscription status across platforms. RevenueCat receives an anonymous app user ID and your subscription status (active, expired, trial) from Apple or Google. RevenueCat does not receive your name, email, or payment details.
• What RevenueCat stores — Anonymous user identifier, subscription status, purchase dates, and platform (iOS/Android). See RevenueCat’s Privacy Policy.
• Free trial — Trial eligibility is determined by Apple or Google based on your Apple ID or Google account, not by MileCheck.
• Managing your subscription — You can manage or cancel your subscription at any time through your device’s App Store or Google Play settings.

Crash Reports and Error Logging

We use Sentry to collect anonymous crash reports and error logs to fix bugs and improve stability.

What Sentry does NOT receive:

• Your GPS location or coordinates
• Your trip log data or travel history
• Your name, email, or contact information
• Payment or subscription details
• Any personally identifiable information

We collect anonymous, aggregate feature-usage counters to understand which features are used (for example, how many times a crosswind warning was shown, or a route was planned). Each event records only the feature name, an optional two-letter US state, and an optional short category tag. These counters are never linked to you: they contain no coordinates, no routes or mileposts, no device, user, or session identifiers, no IP address, and no user-agent information. They cannot be used to identify you or reconstruct your travel.

Push Notifications

MileCheck offers two kinds of optional push notifications: Seattle drawbridge openings and nearby wildfire alerts. Both are off by default and both work even while the app is closed, which means we have to store a small amount of information on our server (Cloudflare) while they are turned on.

Drawbridge notifications

You receive these only if you choose to “follow” one or more Seattle drawbridges in the app. While you do, we store:

• An anonymous push notification token for your device (issued by Apple or Google via Expo). This is a device identifier used solely to deliver notifications. It is not linked to your name, email, or any personal information, and MileCheck has no user-account system.
• The list of bridges you follow, so we only notify you about the bridges you care about.

No location is stored for drawbridge notifications.

Wildfire alerts

If you turn on wildfire alerts in Settings, we store, alongside the same anonymous push token:

• A rounded, approximate location — your coordinates are rounded on your device before they are sent, to one decimal place of latitude and longitude (roughly 11 km / 7 miles, about the size of a city). We use it to work out which new fires are near enough to be worth telling you about. We never store your precise coordinates, your route, or a location history — only the single most recent rounded point, which is replaced (never appended to) and only re-sent when you have moved about 12 miles or more.
• Your alert preferences — the distance you chose and the minimum fire size you want to hear about.

This is the only feature that retains any location on our server. It exists solely to deliver the alerts you asked for — it is never used for tracking, profiling, advertising, or analytics, and it is never sold or shared with third parties.

Both types

The push token is shared with the notification delivery services — Expo Push, Apple Push Notification service (APNs), and Google Firebase Cloud Messaging (FCM) — for the sole purpose of delivering these notifications. We never use it for tracking or advertising.

Turning it off / deleting this data: unfollow all bridges, or switch wildfire alerts off in Settings, and the corresponding data is removed from our server. (If your device is offline at that moment, the removal is retried automatically the next time the app runs.) Registrations also expire automatically after 60 days without an update. Uninstalling the app stops all notifications.

Newsletter (The Monthly Road Report)

Our website (milecheckapp.com) offers an optional email newsletter, the Monthly Road Report. This is entirely separate from the App — the App itself never collects or asks for your email address, and subscribing is never required to use the App or the website.

• What we collect: only the email address you voluntarily type into the signup form.
• What it’s used for: sending the newsletter. Nothing else — no advertising lists, no selling or sharing, and it is not linked to any App data (the App has no accounts, so there is nothing to link it to).
• Who processes it: MailerLite, our email service provider, stores subscriber emails and delivers the newsletter on our behalf. See MailerLite’s Privacy Policy.
• Unsubscribing: every newsletter includes a one-click unsubscribe link. You can also email feedback@milecheckapp.com to have your address deleted from the list entirely.

How Your Data is Stored

• Location data — Processed on your device in real-time for mile markers; precise coordinates are never stored on our servers. Sent off-device only to provide an optional feature you use (weather, route planning, wildfire alerts), as described above.
• Trip logs — Stored locally on your device. You control when to delete them.
• Settings preferences — Stored locally (theme, display options, etc.)
• Bridge notification data — If you follow a bridge for alerts, an anonymous push token and the bridges you follow are stored on our Cloudflare server (no location, no personal information). Removed when you unfollow all bridges; auto-expires after 60 days.
• Wildfire alert data — If you turn wildfire alerts on, an anonymous push token, your alert preferences, and a single rounded, approximate location (rounded to about 11 km / 7 miles) are stored on our Cloudflare server. Removed when you turn wildfire alerts off; auto-expires after 60 days without an update.
• Subscription status — Cached locally by RevenueCat SDK for offline access. Synced with Apple/Google servers when online.
• Crash reports — Sent to Sentry for error analysis, anonymized, stored for 90 days.

Third-Party Services

The App uses the following third-party services. Where the App sends data to a third party, we describe what is sent.

• Cloudflare Workers (our server) — The App routes some requests through a Cloudflare Worker we operate, which proxies requests to state DOT APIs and Google Maps Platform APIs. No personally identifiable information is sent through the Worker; requests carry only the state code, route coordinates, or destination text needed to fulfill the request.
• State DOT APIs — Road condition, incident, and closure data from official state Department of Transportation APIs in 31 U.S. states (the current list of supported states is visible in the app’s Settings). Requests are proxied through our Cloudflare Worker. No personal data is sent to these services.
• National Weather Service (NWS) — The App fetches local weather (temperature, conditions, wind, sunrise/sunset) from the U.S. National Weather Service API. Your approximate location is sent to NWS to retrieve weather for your area. No personal information is sent.
• Google Maps Platform (map tiles) — Map display on both iOS and Android uses Google Maps tiles. Google may receive map tile requests for your viewport. See Google’s Privacy Policy.
• Google Routes API and Places API (Premium route planning only) — The Premium route-planning feature uses Google Routes API and Places API (via our Cloudflare Worker) to search destinations and calculate highway corridor route options. When you use these features, your current location, the text you type into the destination search, and the chosen destination coordinates are sent to Google via our server. This data is used to answer that request; we do not store it. If you do not use route planning, no data is sent to Google Routes or Places. See Google’s Privacy Policy.
• Expo Push, Apple Push Notification service (APNs), Google Firebase Cloud Messaging (FCM) — Used to deliver optional bridge-opening notifications. If you follow a bridge, your anonymous device push token is shared with these services solely to deliver those notifications. No personal information is sent. See Expo’s Privacy Policy.
• Sentry — Anonymous crash reports and error logs to improve app stability. See Sentry’s Privacy Policy
• RevenueCat — Subscription management service. Processes anonymous subscription data. See RevenueCat’s Privacy Policy
• Apple App Store / Google Play — Process subscription purchases. See Apple’s Privacy Policy and Google’s Privacy Policy

Data Sharing

We do not sell, trade, or share your personal data with any third parties for marketing purposes.

Your Rights

You have the right to:

• Access — Request information about data we have collected
• Delete — Clear all local data by uninstalling the app or clearing app data
• Delete bridge notification data — Unfollow all bridges in the app to immediately remove your push token from our server
• Opt-out of crash reporting — Contact info@milecheckapp.com to request deletion of any stored crash data
• Cancel subscription — Manage or cancel your subscription at any time through your App Store or Google Play settings

Children’s Privacy

The App does not knowingly collect information from children under 13. The App is intended for drivers and travelers of legal driving age.

Data Deletion

To delete your data:

• Trip logs can be deleted individually or all at once from the Log tab
• Uninstalling the app removes all locally stored data (trips, settings, cached subscription status)
• Bridge notifications: unfollow all bridges to remove your push token from our server (tokens also auto-expire after 60 days)
• Crash reports sent to Sentry are anonymized and automatically deleted after 90 days
• To cancel your subscription, use your device’s App Store or Google Play subscription settings

Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated revision date. Continued use of the app after changes constitutes acceptance of the updated policy.

Contact Us

If you have questions about this Privacy Policy or the App’s privacy practices, please contact us at:

Email: info@milecheckapp.com

Your Consent

By using MileCheck, you consent to this Privacy Policy and agree to its terms, including the collection of anonymous crash reports via Sentry and subscription management through RevenueCat.