Privacy policy

1. WHAT RIDE DOES

RIDE is a motorcycle cockpit, navigation, weather, and ride-recording application. It uses the information described below to provide the features you choose. RIDE does not offer a RIDE account, ride-history cloud sync, or a developer cloud program for your saved ride history. Information you choose to export, share, or send to another service can be handled by that service after it leaves RIDE.

2. LOCATION, RIDES, AND SENSORS

With Android location permission, RIDE uses precise or approximate device location for the map, route planning, guidance, route-aware weather, and ride recording. A ride or explicitly enabled automatic ride tracking can continue while the app is not visible, with an Android foreground notification. Automatic ride tracking is off by default.

Recorded rides can include locations and times, route points, speed, bearing, altitude, distance, motion and data-quality estimates, dashboard settings, and a destination label. Phone-derived speed, motion, lean, pitch, performance, navigation, and weather values are estimates and may be delayed, incomplete, stale, or wrong. They are not medical advice or certified measurements.

3. ROUTES, PLACES, MAPS, AND SAVED PINS

Online routing and rerouting use Stadia Maps. Requests can disclose ordinary network information such as an IP address, viewed map area, route origin, stops, destination, heading, selected road preferences, and language. Destination and nearby-place searches can send the search text or category, language, and available location focus. Selecting a result can send its place identifier for details. To show place names, RIDE asks your phone's built-in location service (on most phones, provided by Google) for the name of a map position.

RIDE keeps saved routes, route inputs, imported-route provenance, saved places, and saved pins in local app storage with separate controls. Opening a saved route or imported GPX for planning can request a fresh online plan; returned roads and timing can change. A bounded map cache does not guarantee that a new route can be calculated offline. Stadia Maps and other providers apply their own terms, privacy practices, availability limits, and retention practices.

4. WEATHER

When weather is enabled, RIDE's weather service is hosted on Cloudflare and relays requests to the paid Open-Meteo Standard service. Weather-tab requests use up to four forecast coordinates. Rain-avoidance requests use up to twelve coordinates per request and can require more than one request. Coordinates are rounded to two decimal places before these weather requests are sent.

The worker and Open-Meteo may receive request information such as an IP address and forecast parameters, together with the rounded sample coordinates. The worker keeps a limited in-memory cache to reduce repeated requests. On the device, RIDE stores the latest forecast cache, which can include a coarse current-location coordinate and available location labels. A later forecast replaces it. A 30-minute stale status does not itself delete that cache; clearing app data or uninstalling RIDE removes it.

5. LEARN MY ROUTES

Learn my routes is off by default. If you turn it on, RIDE keeps a compact summary of qualifying recorded rides (coarse start and end areas, local departure day and time, and a simplified road corridor) in the encrypted database. When learning runs, including a scan of past rides, RIDE removes summaries older than 180 days and limits how many it keeps. Turning learning off stops learning and use of these summaries but does not delete them. Forget learned routes removes the summaries; deleting a recorded ride removes its summary. Routes you saved yourself stay in Saved routes until you delete them. Past rides can be learned again if you explicitly choose Learn from past rides. Planning a learned route may send selected points along its corridor to the routing provider. These points are location data, not anonymous data.

6. WEAR OS, HEART RATE, CONTACTS, MEDIA, AND SPEECH

If you enable the Wear OS companion, RIDE uses Google Play services to exchange navigation instructions, road text, distances, estimated arrival information, ride metrics, settings, and authorized companion state between the phone and watch. Heart-rate use requires the applicable watch permission, the relevant choice, and an authorized recording session. Heart-rate history is optional and remains separate from any RIDE server; turning off future history does not erase samples already saved.

If you enter an emergency contact or select one through Android's contact picker, RIDE receives and stores the selected name and phone number locally. A call, SMS, or external-map action passes the necessary information to the app you choose. An SMS action opens a composer for your review; RIDE is not an emergency dispatch service and does not guarantee delivery or assistance.

Optional media access reads an active media session after you grant notification-listener access so RIDE can show the current track and controls. It can include track title, artist, artwork, and a preferred player package. Spoken navigation uses the Android text-to-speech engine you choose and its settings.

7. GOOGLE PLAY PURCHASE DATA

When a Google Play purchase or entitlement is enabled, Google Play handles payment and entitlement processing. RIDE can receive product, purchase-token, and ownership or acknowledgement information needed to check an entitlement, but RIDE does not receive payment-card details.

8. LOCAL STORAGE, RETENTION, AND EXPORTS

Ride history and route points remain in the encrypted app-private database until you delete them, clear app data, or uninstall RIDE. Settings, saved routes and places, saved pins, the last-known position, and other caches use separate local storage and controls. Optional diagnostics are off by default; if enabled, a diagnostic file can contain location, timestamps, ride or navigation events, device/build/settings information, and performance information.

RIDE does not automatically upload saved ride history. A GPX, JSON, health, or diagnostic export is sent only when you choose a document provider, sharing app, or recipient. Exported files can reveal where or when you rode and can include health or contact information. Copies outside RIDE are under the recipient's handling and deletion rules.

Android cloud backup and device-to-device transfer are disabled for RIDE app-private data. This does not erase an export or a record held by Google Play, a provider, a document service, or another app.

9. PERMISSIONS, SECURITY, AND CHOICES

You can deny or revoke location, notification-listener, health, and other optional access in Android Settings. RIDE uses Android app isolation, Android Keystore, and HTTPS for RIDE network transports, and encrypted ride storage. These measures do not encrypt every preference, cache, diagnostic file, or exported file, and an unlocked, rooted, or compromised device can defeat them. Set up the app while parked and rely on road signs and real conditions first.

10. SUPPORT, PRIVACY REQUESTS, AND CHANGES

For support or a privacy question, use ridesupport@proxiedmail.com. Do not send passwords, authentication codes, provider keys, purchase tokens, payment-card details, precise locations, or a full ride or diagnostic file unless you deliberately choose to provide it. The contact method and any process for developer-held submissions must be kept current.

This policy shows its effective date above. Material changes should be reflected in the in-app copy, the public policy page, and the applicable Google Play disclosures before they apply.