RideLogger is operated as a tool for volunteer drivers. This policy explains how we manage personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).
We collect and hold the following personal information:
Account information
Passenger profiles
Saved locations
We do not collect sensitive information as defined under the Privacy Act (e.g. health, financial, or government identifier information).
We collect personal information directly from you when you:
We do not collect personal information from third parties or through automated means such as tracking pixels or analytics tools.
We collect and use personal information solely to provide the RideLogger service, including:
We do not use personal information for direct marketing, profiling, or any purpose beyond operating the service.
All personal information is stored in a PostgreSQL database provided by Supabase, with data hosted in the ap-southeast-2 (Sydney) region.
Security measures include:
sessionStorage, which is cleared when the browser tab is closedWe take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access, modification, or disclosure. When personal information is no longer needed, we will take reasonable steps to destroy or de-identify it.
We set one cookie:
| Name | Purpose | Duration | Type |
|---|---|---|---|
| Refresh token | Maintains your authenticated session | 30 days | httpOnly — not accessible to JavaScript |
This cookie stores a securely hashed token, not your password or any personal information. It is strictly necessary for the service to function.
We disclose personal information to the following overseas recipients as part of operating the service:
| Recipient | Country | Purpose | Privacy policy |
|---|---|---|---|
| OpenRouteService | Germany | Calculating routes and distances — addresses from your drive plan are sent to their API | openrouteservice.org/privacy |
| Vercel | United States | Hosting the web frontend — standard request metadata is processed | vercel.com/legal/privacy-policy |
| Supabase | United States (data stored in Australia, ap-southeast-2) | Hosting the database — all personal information at rest | supabase.com/privacy |
| AWS | Australia (ap-southeast-2) and potentially other regions | Hosting the API | aws.amazon.com/privacy |
Before disclosing personal information to these overseas recipients, we take reasonable steps to ensure they handle information in a way consistent with the APPs. By using RideLogger, you acknowledge that your personal information may be disclosed overseas. Under APP 8.1, we remain accountable for how overseas recipients handle your information unless an exception under APP 8.2 applies.
Under APP 12, you have the right to request access to the personal information we hold about you. To make an access request, contact us directly (see section 10). We will respond within a reasonable time and may ask you to verify your identity before providing access.
We will not charge a fee for an access request, though reasonable fees may apply for providing access in some circumstances.
We may refuse access in limited circumstances permitted by the Privacy Act and will explain the reason for any refusal in writing.
Under APP 13, if you believe personal information we hold about you is inaccurate, out of date, incomplete, irrelevant, or misleading, you may request correction by contacting us (see section 10). We will take reasonable steps to correct it within a reasonable time.
If we decline to correct the information, we will give you our reasons in writing and explain how you may complain about our decision.
If you believe we have breached the APPs or the Privacy Act 1988, please contact us first (see section 10). We will investigate and respond within 30 days.
If you are not satisfied with our response, you may escalate your complaint to the Office of the Australian Information Commissioner (OAIC):
For privacy enquiries, access or correction requests, or complaints, contact the RideLogger administrator directly.
We may update this policy from time to time. The Last updated date at the top will reflect any changes. Continued use of RideLogger after a material change constitutes acceptance of the updated policy.