RideLog
Privacy
Who we are
RideLog is run by Mohammed (Moe) Eldouma, a sole trader in Melbourne, Australia (ABN 46 732 475 655). "We" and "us" in this policy mean him. We follow the Australian Privacy Principles in the Privacy Act 1988 (Cth). Contact us about privacy at any time at hello@eldouma.dev.
What we collect
| Data | What it contains | Where it comes from |
|---|---|---|
| Uber trips | Trip ID, vehicle ID, pickup and drop-off times, status changes (accepted, arrived, started, completed, cancelled) with their times, fare, distance, duration, surge multiplier and the start city. | Uber, through the Driver API (partner.trips), after you connect your account |
| Uber payments | Payment ID, category, amount, cash collected, currency, time, the linked trip, and the fare breakdown (toll, Uber service fee, other) and rider fees. | Uber, through the Driver API
(partner.payments) |
| Uber access tokens | The keys that let RideLog read the data above. | Uber, when you connect |
| Files you import | For example your Linkt or EastLink statements and your own vehicle's drive log (times, odometer readings and places). | You |
| Contact details | Your email address, if you write to us. | You |
We do not ask Uber for your profile, licence, rating or any other personal-information scope, and RideLog has no advertising, tracking cookies or analytics.
How we use it
- To produce your own records: quarterly earnings, fee, toll and GST summaries, your car logbook, toll matching and the exports you ask for.
- To keep the service working and secure (for example, fixing an import that failed).
Nothing else. We never sell your data, never use it for advertising, never use it to train AI models and never combine your Uber data with data from other rideshare platforms.
Who we share it with
- Only you decide. Data leaves RideLog only when you ask, for example when you export a summary for your accountant or BAS agent.
- Uber receives nothing from RideLog. It only sees that you connected the app.
- If the law requires it (for example, a valid request from a court or regulator), we will share only what is required and tell you unless we are not allowed to.
Where it is kept and how it is protected
- Your data is stored in Australia, on a server we operate in Melbourne.
- Uber access tokens are encrypted at rest. The database is not reachable from the internet, and only we can access it.
- RideLog only reads from Uber. It cannot change anything in your Uber account.
- If a data breach is likely to cause you serious harm, we will tell you, and Uber where required, as soon as we can.
How long we keep it
- While your account is connected, we keep your data so your records stay complete.
- When you disconnect RideLog (in RideLog, or by removing it from your Uber account), or ask us to delete your data, we delete your Uber data and tokens within 30 days.
- The ATO expects you to keep your tax records for five years. Before you disconnect, download your exports: the files you download are yours to keep.
Your choices and rights
- Ask for a copy of your data, ask us to correct it, or ask us to delete it, by emailing hello@eldouma.dev. We reply within 30 days.
- Disconnect at any time. RideLog's access to Uber ends straight away.
- If you're not happy with how we handled a privacy concern, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Changes
If we change this policy, we'll update the date above. If a change affects how your data is used, we'll tell you before it applies.