Effective Date: October 11, 2026
iOS Bundle ID: com.roadstance.app
Android Package: com.roadstance
RoadStance ("the app") is developed by AutoTripLog Inc. ("we", "us"). It is a vehicle mileage tracking and receipt capture app for iOS and Android. Privacy is a core design principle: all trip data, receipt data, vehicle data, and mileage records are stored locally on your device and are never transmitted to our servers (we operate no servers for user data).
This policy describes the limited technical data that does leave your device, how it is used, and your rights.
Scope and Consistency. This Privacy Policy applies to your use of the RoadStance mobile app and the RoadStance website (roadstance.com), which exists solely to support and promote the app. The version presented within the app and on the website is maintained from a single source and is intended to be identical in all material respects. In the event of any inadvertent discrepancy, the version bearing the later Effective Date shown above governs. This policy does not apply to any third-party websites or services linked from within the app.
Website analytics. The RoadStance website (roadstance.com) does not use Google Analytics, advertising pixels, or any third-party behavioural tracking or analytics scripts.
The following data is created and stored exclusively on your device. It is never transmitted to our servers:
| Data Type | Examples | Purpose |
|---|---|---|
| Location / GPS | Trip routes (lat/lon coordinates), trip start/end points | Record vehicle trips for mileage logs |
| Trip records | Date, distance, duration, business purpose, classification | Mileage log for tax reporting |
| Receipt data | Vendor name, date, amount, address, expense type | Business expense records and trip corroboration |
| Vehicle records | Make, model, year, odometer readings | Per-vehicle mileage tracking |
| Subscription status | Free/Pro tier, original installation date, included-report status, current UTC month, aggregate monthly trip and saved-receipt counts | Feature gating and preventing Free-plan allowances from resetting after reinstall |
| App settings & preferences | Jurisdiction, fiscal year, notifications, Trip Tracking toggle and automatic/manual mode | Personalisation and respecting your tracking choices |
| Local tracking diagnostics | Tracking-state changes, location-service status, recovery attempts, motion/activity labels and step-count summaries | Explain tracking behavior and troubleshoot problems on your device |
You control where backups of this data go (iCloud Drive, USB, AirDrop, etc.). RoadStance does not receive copies of your backups.
The app uses Firebase Crashlytics (Google LLC) to automatically collect technical reports when the app crashes or encounters selected non-fatal errors. These reports help us identify and fix software defects.
What a crash report contains:
Data the app does not intentionally attach to crash reports:
Crash diagnostics are collected automatically and are used solely to identify and fix software bugs. They are processed by Google LLC under Google's data processing terms. See firebase.google.com/support/privacy for Google's practices.
RoadStance uses Firebase Remote Config (Google LLC) to retrieve operational settings, currently the map-tile URL used to select the active map provider. This allows us to change that setting without requiring an app update. Remote Config is separate from crash reporting and from the map-tile requests made to the selected provider.
When requests occur: The app checks configuration during normal app startup, even if you do not open a map or Trip Tracking is off. When online, the Firebase SDK may fetch configuration subject to caching and throttling; release builds currently use a 12-hour minimum fetch interval. This is not a timer that continuously contacts Firebase, and it does not guarantee a request on every launch. If a refresh is unavailable, the app uses built-in map-provider defaults or an override already applied in the running app. Local record-keeping does not require a successful configuration fetch.
Information processed: Firebase Remote Config uses a Firebase installation ID, an identifier for an app installation rather than your name or an advertising identifier, to return configuration values. Google also processes ordinary connection and technical service information, which may include your IP address and app/SDK metadata. These requests are not anonymous or IP-free. RoadStance does not intentionally include trip routes, GPS coordinates, receipt contents, vehicle records, user-entered text or legal-document acceptance history in Remote Config requests. A map-provider API key in the returned configuration identifies the provider account, not an individual RoadStance user.
Purpose and controls: RoadStance uses Remote Config for operational configuration, not advertising, behavioural analytics or Remote Config personalization. Turning Trip Tracking off stops automatic tracking as described in Section 1.5; it does not disable this separate startup configuration check. No separate Remote Config opt-out is currently provided in the app. Offline operation avoids online configuration fetches, but previously processed identifiers or service information remain subject to Google's retention practices.
Provider processing: Remote Config runs on Google's global infrastructure; processing is not restricted to the United States. Google describes installation-ID retention and deletion separately from Crashlytics report retention (see Section 4). See Firebase Privacy and Security, Firebase Data Processing and Security Terms and Google's Privacy Policy for provider practices. Cloudflare's role in Geoapify's request infrastructure, described below, is distinct from Firebase Remote Config.
These services are contacted when you use specific features. They receive only the minimum data needed to fulfil the request and do not receive your trip history or receipt data.
| Service | Provider | When Used | Data Sent |
|---|---|---|---|
| Geoapify Geocoding | KEPTAGO LTD (Geoapify), Cyprus, EU | Converting GPS coordinates to addresses; receipt address lookup | GPS coordinates or address text |
| Geoapify Routing | KEPTAGO LTD (Geoapify), Cyprus, EU | Calculating road distance between two points | Two coordinate pairs |
| Geoapify Map Tiles | KEPTAGO LTD (Geoapify), Cyprus, EU | Displaying maps in the app | Tile coordinates (map region being viewed) |
| Stadia Maps Map Tiles | Stadia Maps, Inc., United States | Displaying maps in the app when Stadia Maps is the active tile provider | Tile coordinates (map region being viewed) |
| Nominatim (OpenStreetMap) | OpenStreetMap Foundation (OSMF), UK | Fallback geocoding — converting GPS coordinates to addresses when Geoapify is temporarily unavailable | GPS coordinates or address text |
| OSRM public demo service | Open Source Routing Machine project | Fallback road-distance and route calculation when Geoapify routing is unavailable | Start and end coordinates |
Geoapify's privacy policy: geoapify.com/privacy-policyGeoapify's Terms and Conditions: geoapify.com/terms-and-conditions
OpenStreetMap Foundation privacy policy: osmfoundation.org/privacy-policyOpenStreetMap map data attribution: openstreetmap.org/copyrightStadia Maps privacy policy: stadiamaps.com/privacy/privacy-policyStadia Maps Terms of Service: stadiamaps.com/terms-of-serviceStadia Maps Data Processing Addendum: stadiamaps.com/legal/data-processing-addendumStadia Maps attribution requirements: docs.stadiamaps.com/attributionOSRM project: project-osrm.org
Where this data is processed: Firebase services, including Crashlytics and Remote Config, run on Google's global infrastructure; processing is not limited to the United States. Geocoding and routing data is processed by KEPTAGO LTD (Geoapify), an EU company (Cyprus) whose backend infrastructure is located in Germany and Finland. Geoapify's standard API and map-tile endpoints use Cloudflare's globally distributed network, so request data may also be routed through or handled at network locations outside the UK and European Economic Area. When Geoapify is temporarily unavailable, geocoding requests may fall back to the OpenStreetMap Foundation's Nominatim service, operated from the United Kingdom, or to the OSRM public demo service for routing. Map tile requests may be processed by Stadia Maps, Inc. in the United States when Stadia Maps is the active tile provider. OSRM hosting and availability may change because it is a public fallback service. Recorded trip, receipt, vehicle and mileage records remain on your device except for the limited requests, backups and sharing described in this policy.
These services are contacted only when the relevant feature is used and only when your device has an internet connection. The app is fully functional offline except for address resolution and map display.
Automatic tracking is an ongoing choice, not a separate action for each trip. When you enable Trip Tracking in automatic mode, RoadStance may monitor location and supported motion signals to detect trips without a start/stop button. This can include business and personal vehicle travel; you review and classify the resulting records.
iOS background relaunch. With automatic tracking enabled and the required permissions and setup in place, RoadStance may register with iOS for significant location changes. iOS may then relaunch the app in the background following an interruption, without you opening its interface. This monitoring is used only to support automatic trip detection and recording. It is not a general phone-boot notification, does not guarantee immediate tracking after a restart, and does not authorize tracking when your saved Trip Tracking setting is off.
Turning tracking off. Turning Trip Tracking off stops automatic GPS and motion tracking and unregisters the location-change monitoring used for automatic relaunch. Selecting manual mode also disables automatic relaunch. Your saved choice is checked before background tracking starts and is not intentionally overridden by an app restart, phone reboot or update. Previously saved records are not deleted by turning tracking off. Separately requested features, such as viewing a map or resolving an address, may still use the limited data described in Section 1.3; the tracking toggle is not a global switch for all location-related features.
Local diagnostics and support sharing. The local Trip Activity timeline is a troubleshooting aid, not a complete compliance or audit record. Timeline entries are normally pruned after 30 days. A diagnostic export may contain a shorter incident window and selected tracking details. We receive a support report or backup only if you choose to share it with us; review its contents before sharing. Background relaunch does not create a new server-side trip record or an advertising profile.
| Data | Purpose |
|---|---|
| Crash diagnostics (via Crashlytics) | Identify and fix software defects |
| Firebase installation ID and technical connection/service information (Remote Config) | Retrieve operational settings, currently the active map-tile provider |
| GPS coordinates (local) | Record trip distance and route |
| Motion/activity signals and local tracking diagnostics | Detect trips, support background tracking and explain tracking interruptions |
| Receipt OCR output (local) | Populate business expense records and suggest trip data |
We do not use your data for advertising, profiling, or any purpose other than operating the app's stated functions.
Local data: Most local data is stored on your device until you delete it or uninstall the app. You can export and delete database records through the Backup & Restore screen.
Device-local entitlement state: On iOS, limited Free-plan entitlement information stored in the device Keychain can remain after uninstall: the original installation date, whether the included report was used, the current UTC month, and aggregate monthly trip and saved-receipt counts. RoadStance uses this information only to prevent trial and Free-plan allowances from resetting through reinstall. It contains no trip details, locations, receipt contents, identity, payment information, or advertising identifiers and is never transmitted to RoadStance. The record is device-bound, monthly counts are replaced when a new UTC month begins, and erasing or resetting the device removes it. Android secure preferences are normally removed when the app is uninstalled.
Crash reports: Retained by Google/Firebase according to their standard retention policies (typically 90 days in the Crashlytics console). We do not have separate control over Google's retention schedules.
Remote Config identifiers and service information: According to Firebase's published practices, Firebase installation IDs used by Remote Config are retained until the Firebase customer requests deletion through the relevant API; after that request, Google removes the data from live and backup systems within 180 days. This is not the 90-day Crashlytics report period. Other connection/service information is governed by Google's applicable terms and retention practices; we do not promise that it is immediately deleted or subject to the same period. RoadStance does not currently offer an in-app Firebase installation-ID deletion control. Contact us about privacy requests; we may need additional information to determine what provider-held data can be identified and addressed, because RoadStance has no customer account directory linking you to an installation ID.
Geocoding cache: Resolved addresses are cached locally on your device for up to 7 days to reduce repeated network requests. This cache is part of your local database and is deleted when you clear app data.
We do not sell, rent, or trade your personal information or usage data to any third party, now or in the future.
We share data only with the service providers described in Section 1 (Google/Firebase for crash diagnostics and operational configuration; Geoapify, Stadia Maps, Nominatim, and OSRM for map, geocoding, and routing fallbacks) as needed for the technical purposes described. Their handling of information is governed by their own terms and privacy policies. We do not direct these providers to use the data for advertising or profiling on our behalf.
When you export a mileage report or backup and share it with a third party (employer, accountant, tax authority, cloud storage), that data is outside our control. You are responsible for sharing reports only with parties who handle the data appropriately.
International data transfers: Firebase crash diagnostics, Remote Config installation identifiers and technical service information may be processed on Google's global infrastructure, including in the United States and other countries where Google or its agents maintain facilities. Geoapify's backend infrastructure is located in EU data centres (Germany and Finland), but its standard API and map-tile endpoints use Cloudflare's globally distributed network, so request data may also be transferred to or processed in locations outside the UK and European Economic Area. Stadia Maps is based in the United States; Nominatim is operated from the United Kingdom; and OSRM is a public fallback service whose hosting may change. See the provider references in Sections 1.2a and 1.3 for details.
Depending on where you are located, you may have the following rights:
All users:
EU/EEA and Switzerland: RoadStance is not available for download in EU/EEA member states or Switzerland. If you access the RoadStance website from these territories, we do not use website analytics or advertising tracking. Infrastructure providers may process standard technical request logs to deliver and secure the website.
United Kingdom (UK GDPR):
RoadStance is a Canadian company with no UK establishment. We rely on the UK GDPR Article 27(2) exemption (occasional, low-risk processing) and have not appointed a UK representative. To exercise any of the above rights, contact us at support@roadstance.com.
Canada (PIPEDA / Quebec Law 25 / provincial privacy laws):
Quebec residents (Law 25 / Bill 64): If you are a resident of Quebec, you have additional rights under Quebec's Act respecting the protection of personal information in the private sector (Law 25). The limited personal information processed through our providers includes Firebase crash diagnostics, Remote Config installation identifiers and technical service information, and mapping/geocoding requests described in Section 1. Processing may occur outside Quebec. Applicable provider agreements and safeguards do not remove our obligations under applicable law. To request access, correction, or portability of personal information, contact us at support@roadstance.com.
California (CCPA / CPRA):
Sensitive personal information (CPRA): Precise geolocation data is classified as "sensitive personal information" under the CPRA. Recorded trip routes are stored locally on your device. Limited coordinates or address text may be disclosed to the mapping, geocoding and routing providers described in Section 1.3 to perform those features, including resolving addresses during automatic tracking. We do not sell geolocation data or share it for cross-context behavioural advertising. You control automatic tracking through the Trip Tracking toggle and device permissions, and choose whether to use features that make provider requests.
Do Not Sell or Share / Global Privacy Control: We do not sell or share personal information for cross-context behavioural advertising. We therefore do not treat Global Privacy Control (GPC) opt-out signals differently from any other request, but we honour the spirit of such signals — your data is not sold or shared regardless.
Australia (Privacy Act 1988):
Other US states: If you are a resident of any US state with applicable privacy legislation (including Virginia, Colorado, Connecticut, Texas, Utah, and others), you have the same rights as described for California above, to the extent required by your state's law.
To exercise any right, contact us at: support@roadstance.com
Because all meaningful user data is stored locally on your device, the primary way to access, export, or delete that data is through the app itself. We can process requests only for personal information we control; we cannot remotely access or delete data stored only on your device or in your personal iCloud account.
RoadStance is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13.
If you are under 13 years old, do not use this app. If you are a parent or guardian and believe a child under 13 has used RoadStance or provided personal information to us, please contact us at support@roadstance.com. We will investigate the report, determine what information, if any, we received, and delete information under our control where required by applicable law. Trip, receipt, vehicle, and mileage data stored only on the device is not accessible to us and cannot be deleted by us remotely.
Your data is stored in a local SQLite database on your device, protected by your device's own security (device passcode, Face ID / Touch ID, disk encryption). We do not have access to your device or its data.
For iCloud backups: files are encrypted in transit and at rest by Apple's iCloud infrastructure.
For crash diagnostics and Remote Config: requests are transmitted over HTTPS to Firebase and processed under Google's security practices. HTTPS protects the connection; it does not conceal your source IP address from the service provider.
Data breach notification. In the event of a security incident affecting personal information for which we have responsibilities, including relevant provider-held diagnostic or configuration information, we will assess the incident and notify affected individuals and authorities as required by applicable law (including PIPEDA, UK data protection law, and applicable US state breach notification laws). The scope depends on the information and circumstances involved; installation identifiers and IP addresses should not be assumed to be anonymous.
Automatic device backup (iOS): iOS automatically backs up app data — including the RoadStance database — to iCloud as part of your standard device backup, subject to your iCloud settings. This is controlled by you through iOS Settings → [Your Name] → iCloud → iCloud Backup. RoadStance does not control or have access to this backup.
Pro Backup & Restore: The Pro tier includes an explicit Backup & Restore feature that saves a copy of your database to your personal iCloud Drive. This data is stored in your own iCloud account and is not accessible to RoadStance. It is governed by Apple's Privacy Policy.
Family Sharing and device separation: Apple Family Sharing may share an eligible RoadStance Pro subscription entitlement, but it does not share or synchronize RoadStance records. Each family member keeps a separate local database containing their own trips, receipts, vehicles, settings, and reports. App-managed iCloud backups remain in each member's own iCloud account and are not made available to other family members by RoadStance. Sharing an iCloud+ storage plan shares storage capacity, not RoadStance backup files. Backups are dated recovery snapshots and are restored or merged only after an explicit user action; RoadStance does not continuously synchronize records between devices.
In-app purchases are processed entirely by Apple (App Store) or Google (Google Play). RoadStance does not collect or store payment card details, billing addresses, or any other payment information. Subscription status is verified via secure tokens provided by the respective platform.
RoadStance stores the limited device-local entitlement state described in Section 4 to administer the Free plan across reinstallation. Within the same UTC month, the app retains the highest known aggregate trip and saved-receipt counts from its local database and secure device storage; it does not combine or retain individual usage events.
We may update this policy when the app's features or legal requirements change. When we do, we will update the Effective Date at the top of this document and post the updated version at the same URL. Continued use of the app after a policy update constitutes acceptance of the revised policy.
For significant changes we will add a notice within the app.
Company responsible for RoadStance:AutoTripLog Inc. 1750 The Queensway Suite 529-3 Etobicoke ON M9C 5H5 Email: support@roadstance.comWebsite: https://roadstance.com
For privacy questions, data access requests, or to report a concern, email us at the address above. We aim to respond within 30 days.
This policy applies to the RoadStance iOS app (bundle ID: com.roadstance.app), the Android app (package: com.roadstance), and the RoadStance website. It does not apply to any third-party websites or services linked from within the app.