Current scope: website and enquiries. Ride’s public service has not launched. App-specific sections are pre-launch information and must be confirmed before they become the policy for a live app.
1. Who we are
Ride is the brand operated by RIDE MOBILITY TECHNOLOGY PTY LTD in Australia. This policy covers our public corporate website at ridemobility.com.au and enquiries sent to Ride. It also explains the categories of information that may be needed for our planned rider and driver services.
Ride is preparing to launch in Melbourne. This website does not create rider or driver accounts, take ride bookings or payments, or accept document uploads. The planned-service information below is subject to confirmation before the public apps or service collect that information.
Privacy enquiries can be sent to support@ridemobility.com.au. Our approach is to handle personal information in accordance with applicable Australian privacy law, including the Privacy Act 1988 (Cth) where it applies.
2. Website and enquiry information
If you email Ride, we receive the information you choose to send. This may include your name, email address, other contact details, your driver expression of interest, and the content and attachments of your message. We collect it directly from you to respond to your enquiry, manage expressions of interest, or handle feedback and requests.
Our website hosting providers may process technical information needed to deliver and protect the website, such as your IP address, browser information, requested page and access time. This website’s code does not request your device location, set browser storage, or include advertising pixels or analytics trackers.
Please share only what is needed for your enquiry. Do not send identity documents, licence scans, bank details, passwords, full card numbers or card security codes with a general enquiry or initial driver expression of interest.
You can read the website without providing your name. You may make a general enquiry without identifying yourself where practical, but we may be unable to respond, assess eligibility or verify an account-related request without relevant information.
3. Information for the planned service
This section describes anticipated categories, not a statement that this public website currently collects them. The final scope and actual collection practices must be confirmed for each app before launch.
- Account and contact information
- Information needed to create and manage a rider or driver account, contact the account holder and provide service communications.
- Bookings and trips
- Pickup and destination details, booking requests, trip status and history, and relevant records of the trip. The precise fields and sharing arrangements will be confirmed.
- Location information
- Pickup and destination locations, and device location where needed for confirmed trip or driver functions. Device permissions, whether precise or background location is used, when it is collected and the consequences of disabling it must be explained in the app before collection.
- Driver, vehicle and verification information
- Information needed to check applicable identity, licence, accreditation, vehicle and eligibility requirements. Required documents and any sensitive information or verification provider involvement must be confirmed before onboarding.
- Payments and transaction records
- Information needed for payment processing, transaction records and any confirmed driver payment arrangements. Payment providers, the data Ride receives or retains, and any refund or dispute records must be confirmed. This website does not process payments.
- Device and technical information
- Technical data necessary for confirmed app functions, reliability and security. Actual identifiers, logs, diagnostics and third-party SDK practices must be checked before launch.
- Support and safety communications
- Messages and relevant information submitted with a support request or incident report. Any additional collection, including recordings or sensitive information, requires a confirmed purpose and appropriate notice before use.
The public app policy and collection notices will explain which of these categories are actually used. Additional sensitive information will not be requested merely because it appears in a general list of possible data.
4. How information is used
For the current website and enquiries, information is used to deliver the website, respond to you, manage driver interest, protect the website and communications, and handle privacy requests or complaints. If you request launch information, relevant follow-up may be sent in response to that request. You can ask us to stop those updates.
For the planned service, purposes may include managing accounts, connecting riders and drivers, administering trips and payments, checking eligibility, providing support, addressing safety concerns and meeting applicable legal obligations. These purposes must be mapped to the actual information collected before launch. We will explain materially different uses before introducing them where required.
6. Overseas handling
Technology and email service providers may process or store information outside Australia. The countries involved depend on the services and configurations used. The provider processing locations, contractual protections and applicable cross-border obligations require confirmation.
Before public app launch: identify the likely overseas recipients and, where practical, their countries in the updated policy. Confirm current website and email processing locations as part of this review. We do not make a claim that all information stays in Australia.
7. Security and retention
We aim to use reasonable technical and organisational measures appropriate to the information and its purpose, including controlled access and secure transmission. No online service or method of transmission can guarantee absolute security.
Our approach is to retain enquiry and interest information only for as long as needed for the purpose, applicable legal obligations and the handling of related requests or disputes, then delete or de-identify it where appropriate. You can ask us to remove your expression of interest.
Specific retention periods, deletion procedures and backup treatment for accounts, trips, driver documents, payments, logs and incident records must be documented and checked before public service launch. Any information that must be retained by law will be handled accordingly.
8. Access, correction and deletion
You can ask about the personal information Ride holds about you, request access, seek correction, or ask for deletion by emailing support@ridemobility.com.au. Tell us what you are requesting and how we can reply. We may need to verify your identity in a proportionate way before providing or changing personal information.
Access, correction and deletion will be considered under applicable law. Deletion may be limited where information must be retained for a legal obligation or another lawful reason. If a request cannot be fulfilled, we will explain the relevant reason and available next steps.
The public website does not create accounts. The public apps’ account deletion process, permission controls and any platform-specific data request tools must be confirmed before launch.
9. Privacy concerns and complaints
If you are concerned about how Ride handles personal information, email support@ridemobility.com.au with the issue and relevant details. We will assess the complaint, may seek further information, and respond within a reasonable period. Please do not include unrelated sensitive information.
If you are not satisfied with our response, you may contact the Office of the Australian Information Commissioner, where the matter falls within its jurisdiction. Other rights or complaint avenues available under applicable law are not affected.
10. Policy changes
We may update this policy when our services or practices change. The current version and its update date will remain available at /privacy. Material app-related changes and collection notices will be communicated through appropriate channels before new processing begins where required.
If you need this policy in another accessible format, contact Ride using the support email.
11. Items to confirm before app launch
Implementation confirmation and legal review required
This is the starting policy for a business preparing to launch. It must be reconciled with the actual apps and reviewed professionally before live onboarding, public trip bookings or app-store submission using it as the final app policy.
- Actual account, trip, driver, payment, support and technical data collected; whether any sensitive information is required.
- Device permissions, precise and background location, third-party SDKs, collection notices and participant data sharing.
- Service providers, overseas recipients and processing countries, including website and email providers.
- Payment data Ride receives or retains, verification processes and provider responsibilities.
- Retention schedules, backup handling, account and data deletion, access/correction and complaint procedures.
- Any automated decisions with significant effects and the disclosures required by applicable law.
- Applicability of Australian privacy legislation and alignment with Apple and Google privacy disclosures.