Privacy

Location and navigation services

With your iOS permission, Moto ETA uses precise location for your starting point, route progress, live turns and rerouting. An active trip can use location in the background or while the screen is locked. End the trip explicitly when finished. You can change location permission in iPhone Settings → Apps → Moto ETA → Location. Denying permission prevents live GPS guidance; you can still plan with a typed starting point or explicitly simulate a trip.

Mapbox provides maps, place search, routes, traffic and navigation. Requests can include your search text, search proximity, origin and destination coordinates, current position and requested map area. Mapbox also processes technical information such as network identifiers and service usage. These requests leave the phone to provide the features you use.

Mapbox SDKs also support location and usage telemetry. Use the map’s information button (ⓘ / About this map), then Mapbox Telemetry / Make Mapbox Maps Better to review its sharing control. Opting out of telemetry does not stop requests needed for maps or navigation. See Mapbox’s privacy policy and telemetry information for its processing, retention and privacy-request options.

Internal debug mode can request a separate automobile ETA from Apple using the trip’s endpoints. Explicit developer Simulator fixtures may also use Apple place search. See Apple Maps & Privacy. The phone app does not send lane-count requests to TomTom.

What stays on your phone

Moto ETA saves settings, beta setup completion, Home/Work favorites and up to five recent typed search queries. Search result lists remain in memory. Favorites contain their place names and coordinates.

Local ride history stores up to 100 recent ride records: dates, endpoint names and coordinates, elapsed time, initial traffic estimate, arrival status and build iteration. It supports your ride list, directional commute grouping and Personal ETA. These records are not anonymous and can reveal places you visit. Moto ETA does not automatically upload this history to Traverse Labs.

These app-managed records persist across launches and upgrades. iOS backups or transfers may also retain app data according to your Apple settings; Moto ETA does not provide its own cloud account or sync service.

Optional internal debug recordings

Debug recording is available in internal builds and requires a separate explicit choice in Settings. While enabled, navigation sessions save detailed local files containing precise positions, routes, speed, timing, app state, build information and any ride notes you add. The choice persists across launches. Turning Debug off stops recording; it does not delete existing files. Beta setup alone never enables it.

Internal lane-audit observations can also save coordinates, dates and your road/lane observations locally. Debug files and lane observations have no automatic expiry or automatic upload. Export uses the iOS share sheet: you choose whether, where and with whom to share. Exports and screenshots can reveal your home, workplace or travel history. Review them before sharing.

Deletion and your choices

• Menu → Rides → Clear history removes local ride records.
• Menu → Settings → Clear recent searches removes saved typed queries.
• In internal builds, turn Debug off and use Menu → Debug → Delete all traces to remove saved traces. Clearing ride history alone does not delete traces; retained completed traces can repopulate history on a later launch.
• Favorites can be replaced in Settings. To remove all app-managed local data, use iOS Delete App, rather than Offload App. Manage retained backups and previously exported copies separately.

Removing local data does not recall copies you exported or data already processed by a provider. Use the provider privacy links above for its request procedures.

Support, website and future contributions

If you email us or send beta feedback, we receive the message, contact information and attachments you choose to include. We use these to respond, investigate problems and improve Moto ETA, and retain the correspondence for support and follow-up. Ask us to delete correspondence or supplied files at info@traverselabs.net. Applicable recordkeeping requirements may limit deletion. You do not need to send a complete ride trace to get help.

This static website has no signup, advertising or added analytics. Its hosting provider, Amazon Web Services, processes network requests and technical information to serve and secure the pages. Email and TestFlight feedback are handled through their respective providers. See AWS Privacy and TestFlight & Privacy.

A future service for rider contributions is planned but inactive. The current app does not collect a contribution-sharing choice or queue/upload contributions to that service. Any activation will require an updated policy and a separate, scoped choice. Local history, debug consent and Mapbox telemetry are separate from that future service.

We will update this page when data handling changes. For privacy questions or requests concerning information you shared with Traverse Labs, contact info@traverselabs.net. See Support for app help.