Last updated: 2026-07-22
Draft requiring Australian privacy/legal review before publication or launch.
NEXTRISE LOGISTICS PTY LTD (ABN 91 653 334 840) operates ORide. This policy describes the personal information used by the rider app, driver app, website, administration and support systems.
Depending on your relationship with ORide, information may include identity and contact details, Australian addresses, account credentials, ride and payment records, support communications, consent history, device and security data, and precise location. Driver records may also include licence, accreditation, ABN/GST status, checks, vehicle, insurance, inspection and encrypted payout details.
ORide must not store raw card numbers or CVV. Payment tokens and private compliance documents are handled through restricted systems and providers.
Rider foreground location is used to help choose pickup locations and support an active booking. Driver foreground and background location is used only when operationally required for availability, dispatch, navigation and an active trip. Background tracking must not begin before clear permission and an operational need, and must stop when that need ends.
Information may be used to provide trips, calculate GST-inclusive fares, process payments and payouts, verify compliance, manage safety and support, prevent fraud, meet recordkeeping/reporting obligations, and improve reliability. Necessary information may be disclosed to riders, drivers, payment, mapping, messaging, hosting, identity/compliance and professional service providers, and to authorities where required or authorised.
Transactional ride messages do not enrol a user in marketing. Marketing email, SMS or push requires an appropriate consent record and must provide an unsubscribe or preference mechanism.
Retention periods must be configured by record category and reviewed against Australian legal, tax, safety, dispute and regulator requirements. Users can request access, correction, export or deletion through the privacy-request workflow. ORide may retain records where a legal, safety, fraud, tax or dispute obligation requires it.
ORide uses role-based access, audit trails, encrypted sensitive fields, private file storage, signed access, rate limiting, token revocation and provider webhook verification. Suspected data incidents are recorded and assessed through the data-breach response workflow.
Obtain Australian legal and privacy review, confirm cross-border processing and retention periods, and configure the privacy contact before activation.