Privacy and your journey

RideOn and RideOn Driver privacy notice · Updated October 19, 2026

Christian Missionary Fellowship International Corp operates RideOn for community transportation. Participating organizations manage their transportation activities and access to their organization records. Privacy questions and requests can be sent to admin@cmfinl.ca.

Information RideOn handles

This includes account and contact details, sign-in information, organization memberships and access requests, saved addresses and pickup coordinates, ride requests, passenger counts and dependent ages where provided, assignments, trip status and history, and notification preferences and device push tokens. Driver also handles driver profile and licence information, availability, and vehicle details such as plate number and VIN where provided.

Why it is used

Information is used to authenticate accounts, coordinate requested transportation, communicate journey changes, support safety and operations, and maintain the service.

Driver location sharing

During an active trip, RideOn Driver sends precise device location to support pickup coordination and trip visibility for authorized coordinators and assigned riders, including guests using their secure management link during an active trip. Sharing may continue while the screen is locked or another app is open. Accepting an event alone does not start live sharing. Completing or cancelling a trip, signing out, or clearing the session stops sharing; remote changes take effect on a subsequent upload or refresh.

Each live location value expires after 30 seconds. This feature does not create a durable GPS history. That expiry does not remove saved addresses, pickup locations, trip records, or maps-provider data. You can change location permission in your device settings; features that need location may then be unavailable.

Service providers and diagnostics

RideOn also records limited operational diagnostics on its own infrastructure: app, platform, version/build and fixed connection or service-failure codes. These reports require an authenticated session and omit message content, credentials and location details. Routine operational logs have a 30-day retention target.

Authorized organization coordinators and assigned participants receive the information needed for their transportation workflows. Hosting, database, maps, and messaging providers process information needed to operate the service. Google Maps receives relevant search, address, coordinate, and routing inputs and collects device and SDK diagnostic information. The guest trip map loads only after you choose Show map; it displays your pickup, event destination and fresh vehicle location without exposing other passengers’ stops.

Both mobile apps use Firebase Cloud Messaging for push notifications and Firebase Crashlytics for crash diagnostics in release builds. RideOn Driver also uses Firebase Analytics for usage events, including sign-in, screen and trip actions. These services process app/device identifiers, operating-system information, and relevant usage or diagnostic data. Analytics can include advertising identifiers and location inferred from IP addresses. Device permission for notifications or location is separate from diagnostic and usage collection. See Firebase privacy information and Google’s privacy policy.

Service providers may process information outside Canada. We do not represent that all RideOn or provider records are stored in Canada. Provider processing locations and disposal arrangements are still being verified for the pilot.

Retention and deletion

The approved pilot targets are to remove sensitive pickup details 30 days after an event finishes or is cancelled; remove or anonymize identifiable ride requests, assignments and trip history after 365 days; expire notification content after 90 days; and expire routine logs and backups after 30 days. Notification delivery evidence has a separate 90-day clock after the most recent receipt. Active work and documented, scoped preservation needs can affect cleanup.

These are operational targets, not a guarantee that every copy has already been removed. Some organization-record cleanup, provider disposal, backup configuration, and deletion-request tracking are not yet fully enforced or verified. Firebase Crashlytics begins removal after its 90-day holding period; provider completion is outside RideOn’s direct control. Analytics, maps, driver/vehicle compliance records and other provider copies require separate retention verification.

Access and questions

To delete your account in RideOn or RideOn Driver, or request deletion without the app, follow our account-deletion instructions. The page also explains what is removed and which records may remain.

Account deletion affects the shared account across apps and organizations. It de-identifies core account identity and contact fields, clears password and linked sign-in records, revokes sessions, suspends memberships, and removes registered device tokens and saved addresses. It does not guarantee immediate erasure of all trip, organization, audit, backup or provider records. The target for follow-up cleanup is 30 days after ownership is verified, subject to the limitations above. Do not send your password or unnecessary sensitive details in an initial email request.

Access is limited by role and organization. Contact your organization’s RideOn coordinator for questions about your information or to request an account change. Security concerns can be sent to admin@cmfinl.ca.

You can update available profile fields and saved addresses, manage communication preferences, and change device location and notification permissions. RideOn uses authenticated access and organization/role checks. Release API requests use HTTPS and app authentication tokens use device-backed secure storage.

Dependent passengers and updates

RideOn Driver is intended for approved adult volunteer drivers. Adults may coordinate transportation for dependent passengers. Assigned passenger information should be used only for the transportation workflow. We will update this notice as pilot operations and provider arrangements are verified; the date above identifies the latest revision.