Draft for review. This is a draft privacy notice. Confirm actual data collection, providers, retention and user rights before using it for a live product.
1. Scope
This draft describes the information a RideOn ride booking platform may handle. Actual collection, location permissions, payment methods and service providers must be verified against the deployed passenger and driver applications before this notice is adopted.
2. Information involved
A ride booking service may need account and contact details, passenger pickup and drop-off points, trip requests and history, driver and vehicle details, and support messages. Location information may be used when a passenger or driver enables location features. If payments, identity verification or ratings are added, the final notice must describe those flows specifically.
3. How information is used
Ride information is intended to support ride requests, matching, pickup, navigation, trip updates, support, fraud prevention and service operations. The final notice should state which of these functions are active and whether any analytics or marketing uses apply.
4. Sharing needed for rides
A driver may need the passenger’s pickup point and trip details; a passenger may need the assigned driver’s name, vehicle and trip status. The final notice must identify any map, notification, hosting, payment or verification providers that receive information.
5. Location choices
Device location should be used only when the user enables the relevant permission. A passenger may enter pickup and destination details manually if the application supports that option. Precise background location use by drivers, if enabled, must be separately described in the final notice.
6. Security and retention
Access to account and trip records should be limited to authorized personnel and protected with suitable safeguards. The final policy must specify actual retention periods, deletion procedures and security contact details.
7. Your requests
To ask about access, correction or deletion of your information, contact Trackia Tech at trackiatech@gmail.com. Available options depend on the deployed product and applicable law.
8. Changes and contact
The final policy should state its effective date and be revised when booking, payments, location or sharing practices change. Contact Trackia Tech at trackiatech@gmail.com.