RyeDC Privacy Policy

Pincab Pty Ltd (ABN 76 606 942 401) · Last updated: 12 October 2026

RyeDC is a logbook for rideshare and taxi drivers. This policy explains, in plain words, what the app records about you, where it goes, who else can see it, how long it is kept and what you can do about it.

If anything here is unclear, email hello@ryedc.com and ask.

What the app does depends on the version you have installed. Features are added and retired between releases, and this policy covers every version still in use: some of what it describes your copy may not do, and some of what your copy does may have been retired in a newer one. Where that difference matters, it is said on the spot.

---

The short version

• RyeDC keeps your driving records for you: your vehicles, your shifts, your trips, your fares, your odometer readings and your cleaning logs, and, if you make invoices, your business details and the invoices you made.
• If you turn on automatic mileage tracking, the app records where you drive in the background, without you starting anything — including a continuous GPS trace of each drive. That is the most sensitive thing this app does, and §1 and §2 set out exactly what it records.
• Your records are yours alone. No other driver can read your trips, your vehicles, your earnings or your locations.
• There is one feature that is shared — Around Me, where the cards you post are visible to every other signed-in driver, and your votes count towards the totals they see. No other driver can see which cards are yours or how you voted (§5).
• We do not sell your data, and no location, address, fare, name, email, phone number, ABN, bank details, accreditation number or Bluetooth address is ever sent to our analytics or crash-reporting tools.
• Adverts can be personalised. Google may choose the adverts you see using your device's advertising identifier. On iPhone that happens only if you allow it when the app asks; on Android your phone's ad settings decide (§4).
• You can switch off analytics and crash reporting and delete your account from inside the app. You change your ad choices in your phone's settings — or in the app, where Google's consent form applies to you (§7).

---

1. What we collect

Your account

Your email address, your name, which sign-in method you used (email, Google or Apple), and the Firebase user ID that identifies your account. If you sign in with Google, we also store the web address of your Google profile picture — the app never uploads a photo of its own.

If you sign in with Apple and choose Hide My Email, the address we hold is the Apple private-relay address. Mail sent to it still reaches you.

Your account record also holds your list of business reasons for the logbook — the ones you add, the built-in ones you remove, and the default a journey without a reason of its own is printed with.

We do not collect your date of birth, gender, marital status, driver's licence, insurance certificate, vehicle registration papers or payment card details. There is no field for any of them anywhere in the app. A phone number, an address and bank details are kept only if you enter them in Business details (below).

Your vehicles, shifts and cleaning register

For each vehicle you add: its registration number, the driver name and accreditation number you enter for it, the model or notes, the engine capacity, and — if you register your car for automatic tracking — the Bluetooth address and name of that car's stereo.

A Bluetooth address is a permanent hardware identifier for the car, not for your phone. We store it because it is how the app knows a drive was made in that particular vehicle rather than in another one. It is stored on your own vehicle record, it is never shared with anyone, and it is never written to any log.

Shifts hold the start and end odometer readings and times you record, the suburb the car was in at each end, and the reason for the journey — the one you give, or your default. The suburb is looked up at Start and End Shift only if the app already has location permission: those buttons never ask for it. The position is handed to the geocoder and dropped; only the suburb is kept, never a coordinate. If there is no position to be had, you type the suburb yourself. Cleaning register logs hold a status and a timestamp against your account. Fare settings hold the rates, fees and commission you enter for a service provider.

Fare Meter trips

When you run a trip on Fare Meter (called Live Meter in earlier versions), the app records the GPS trace of the route, the start and end times, the suburb at each end, the distance, the duration and the fare you enter — including its components: base fare, distance, time, tolls, tips, surge, service fee and the amount to you. The suburbs are looked up from the first and last points of the trace when the trip ends, or when you open the Trips list for a trip that has none yet. Only the suburb's name is added to the trip.

While a trip is running, the app also keeps a copy of it on your phone, in its own private storage: the route so far, the service and its rates, and any toll or surge you have added. It is there so that a trip the app was closed on can be resumed or ended when you come back. The copy is deleted once the trip reaches our servers, and when you sign out or delete your account. If you resume, the distance driven while the app was closed is estimated, and the trip says how much.

A trip made with an older version of the app may have an audio recording attached, if you made one. It stays in your own private storage, where only you can play, download or delete it.

Business details and invoices

If you fill in Business details, your account record holds what you enter: whether your business is in Australia or another country, its legal and trading names, its ABN (outside Australia, its tax number and what that is called), whether it is registered for GST, a phone number, an email address and a postal address, the bank account name, BSB and number, and your PayID (outside Australia, a line saying how to pay you), with your payment terms. Only the details for the country you chose are kept. They are used for one thing: printing on the invoices you make.

When you make an invoice from a trip, the app saves it on that trip: its number and date, whether it is paid or when it is due, the number of any invoice it replaces, the name, ABN or tax number, email and phone of the person you bill (if you enter them), and a copy of everything printed on it, so the same invoice can be shared again. It shows the trip's date and time, where it began and ended (a street address or suburb, which you can change or leave off), how far and how long it ran, and what the passenger pays. It never shows your service fee, your commission or the amount to you.

The PDF is made on your phone and goes only where you send it, with the app you choose. We do not send it to anyone, and we do not contact the person you bill. We hold a passenger's details for the driver who entered them, as part of that driver's records, and use them for nothing else. If you are named on an invoice made with RyeDC, ask the driver who sent it, or email us.

Automatically detected drives

Only when you turn automatic mileage tracking on. For each drive the app records:

• when it started and ended;
• the distance;
• the start and end coordinates;
• the street addresses those coordinates resolve to, stored as readable text;
• a continuous GPS trace of the whole drive;
• whether the drive is business, personal or unclassified, and whether you chose that or the app assumed it;
• the reason for the journey, if you gave one — otherwise it follows your default.

A trace like this is a continuous record of where you have been. It is the highest-sensitivity data the app produces, it is stored under your own vehicle where only you can read it, and §2 is entirely about it.

Odometer readings

The number off your dash, the unit you typed it in, when it was taken, where it came from, and any note you add. No coordinate and no place — a reading is a number and a time.

The logbook's change log

The ATO wants an electronic logbook that shows its own changes. So every edit or deletion you make to a detected drive, a shift or an odometer reading after that entry's first week is recorded as a line in your vehicle's change log: which entry, when you changed it, and each field's value before and after. Deleting an entry does not delete what it said — the line keeps its dates, distance, readings, suburbs, category and reason. The log is private to you, and it goes only when you delete the vehicle it belongs to.

Around Me cards

If you post a card: the name you type, the coordinate where you were and the timestamps, and a record that the card is yours. If you vote on a card: a record of how you voted. The card itself is visible to other drivers — see §5. The two records are not: no other driver can read them.

Your device

The app stores one device identifier on your account record. On iOS this is the identifier Apple gives our apps for your device; on Android it is the operating system's build number, which is the same on every phone running that build and identifies nobody. Nothing currently uses either: there is no push-notification system in this app.

Diagnostics and usage

In release builds only, and only while Help improve the app is switched on:

• Usage analytics to Google Analytics for Firebase — which screens you open, nineteen named events (signing in, adding a vehicle, starting and ending a shift, saving or discarding a detected drive, classifying or deleting a trip, exporting a report, sharing an invoice, and so on), and a small set of properties describing how you have the app set up: whether tracking is on and at what sensitivity, your distance unit, your home screen, your theme, and whether you have added a vehicle. Every value is a number, a category or a yes/no. Never free text you typed. On Android, in version 3.2.0 and earlier, Google Analytics also reads your device's advertising identifier. Later versions do not let it.
• Crash reports to Google Crashlytics and to Sentry — the error, its stack trace, your device model and your operating system version.

There is also a diagnostic log on your phone used to debug background tracking. It records decisions, never positions: no coordinate, no Bluetooth address, no device name. It rotates at 2 MB, it is switched off in the app you download from the store, and it is never uploaded anywhere.

The website

www.ryedc.com.au counts its visits with Google Analytics 4: the pages viewed, the type of device and browser, and the approximate region Google works out from the connection. It is a separate property from the app's analytics, it holds no name, email or account ID, and nothing on the website links a visit to a RyeDC account. Google keeps it for 14 months. If you visit from the European Economic Area, the United Kingdom or Switzerland, the site asks before it measures anything and measures nothing until you accept. Anywhere else, measuring starts when the page loads, and your browser's tracking protection or a content blocker stops it. The website sets no other cookies and runs no other script.

---

2. Location, in full

Location is the reason this policy is longer than most. There are two different things the app does with it.

While you are using the app

Fare Meter records a trip's route while you have the trip running. The map screens centre on you if you let them. Around Me pins a card where you stand.

Precise location is required to record a trip and to pin a card — a mileage log that is not precise is not a mileage log. It is never asked for just to browse a map: if you refuse, the map still works, it is simply not centred on you, and a notice over it says so.

In the background — automatic mileage tracking

When you turn automatic tracking on, the app asks for Always location access, for Motion & Fitness (iOS) or Activity Recognition (Android), and on Android for Bluetooth and for permission to send you notifications — notifications are also asked for, once, when you start your first Fare Meter trip, so the fare can stay on the lock screen. Those are what let the app record a drive without you opening the app or tapping anything. While tracking is on, the app collects your location even when the app is closed or not in use, and only to record your drives for automatic mileage tracking and the app's other driving features — nothing else. Turn tracking off in Settings and it stops.

While a drive is running the app keeps its GPS fixes in its own private storage on your phone, and writes them to your vehicle's record when the drive is saved.

Where a location leaves your phone

Apart from being stored in your own private records, a coordinate leaves your device to exactly three services, all of them named here rather than hidden:

1. To Apple or Google's geocoder, to turn a coordinate into a place name. That happens in four places: the start and end coordinates of a detected drive become street addresses when you open the list of detected drives; the first and last points of a Fare Meter trip become suburbs when the trip ends or when you open the Trips list, and street addresses when you make an invoice for it; the car's position at Start and End Shift becomes a suburb, only when location is already granted, and only the suburb is kept; and an Around Me card's pin becomes an address when the card is shown.
2. To Google's Routes API, to estimate a stretch the app could not record (part of a detected drive, or the distance a Fare Meter trip covered while the app was closed) and to price a quote. Two coordinates only: at most once per drive, once each time you resume a trip, and once each time you ask for a quote. For a quote they are its two ends, and the start is where you are unless you type a place. No trace, no trip, no vehicle and no identifier of you is sent with it. Only a quote asks for the line of the road back, to draw it on the map, and the line is not kept.
3. To Google's Places service, when you ask for a quote: the place names you type, and roughly where you are (to about 10 km), so it can suggest places near you. Nothing is sent as you move, only as you type. If you use the quote as the agreed price, the two place names and the road's distance stay on your phone until the trip is saved, so the lock screen can show them. They are not saved with the trip or sent anywhere.

Nothing else sends a location anywhere. An invoice prints a street address or suburb at each end of its trip, never a coordinate, and goes only where you send it (§1). Your traces and your addresses are not shared with any other driver, any advertiser, any analytics tool or any crash reporter.

When each permission is asked

Nothing is requested when you first open the app. Every permission is asked for at the moment you reach the feature that needs it, after a screen explaining what the feature does with it, and every refusal has a way back through your device's Settings. The one exception is the tracking question on iPhone: it is about the adverts shown throughout the app, so it is asked once, after you sign in.

The app asks for no storage permission — exports are written to its own private folder and handed to your device's share sheet.

---

3. Who we share it with

We use the services below to run the app. Each row says what that service actually receives. There are no other recipients: no data brokers, no list brokers, no promotional partners, no marketing lists, and no sale of anything to anybody. Google's advertising service is in the list below, and the row says exactly what it gets — an ad request and a device advertising identifier, with nothing about you attached to it. On iPhone the identifier is sent only if you allow tracking.

Cloud functions used by the app receive your user ID and your sign-in token, which proves the request is yours, and nothing else.

Where your data is stored

Your records are held in Google Cloud. Google's infrastructure, Sentry, and the account-deletion function this app calls operate in the United States and other countries in which those providers operate, so your personal information is disclosed to overseas recipients within the meaning of Australian Privacy Principle 8. We rely on those providers' contractual terms and security controls, which is the reasonable-steps basis APP 8 asks for. All traffic to every service above is encrypted in transit over HTTPS.

We may also disclose personal information where we are required to by law, or where it is necessary to investigate a suspected breach of our Terms or to protect someone's safety.

---

4. What we never do

These are commitments, and each one is enforced in the code rather than only promised here.

• We do not sell your personal information.
• Personalised adverts only on the terms your device sets. On iPhone the app asks with Apple's App Tracking Transparency prompt, once, after you sign in — and in the EEA and the UK only if you first agreed to Google's consent form. Allow it, and Google may use your device's advertising identifier to choose the adverts you see. Refuse, and adverts still show, just not personalised. You can change your answer at any time in iOS Settings › Privacy & Security › Tracking. On Android, your phone's own ad settings decide, together with Google's consent form where it applies. Either way, the app sends Google nothing about you with an ad request: no location, no trips, no name.
• Analytics never feeds adverts. The usage analytics in §1 are for improving the app, and Google is told not to use them for ad personalisation, on both platforms, whatever our analytics and advertising accounts are linked to.
• No coordinate, street address, fare, name, email address, phone number, ABN, bank details, accreditation number or Bluetooth address is ever sent to analytics or crash reporting, or written to any log. Automated tests in the app's codebase hold this, rather than it resting on intention: one checks every analytics event, and another checks the scrubber that strips identifiers out of a crash report before it is sent.
• We do not combine your data with information bought from third parties to profile you, and we do not obtain personal information about you from list brokers or any similar source.
• We do not upload the location data the app keeps on your phone for automatic tracking, or your diagnostic log. They stay on your phone.

---

5. What other drivers can see

Everything else in RyeDC is private to you. Around Me is not, and you should know exactly what that means before you use it.

When you post an Around Me card, every other signed-in driver can read the name you typed, the coordinate where you posted it and when. They cannot see who posted it. When you like or dislike a card, the count other drivers see goes up by one; they cannot see who voted, or which way.

Your email address, your name and your user ID are not part of a card. But a card is still a place you stood at, at a time. Post accordingly.

You can delete your own cards at any time, which deletes the card and its votes. Cards you set an expiry on disappear on their own. Deleting your account deletes your cards and takes your votes off every other card's counts.

---

6. How long we keep it

We are specific here because "as long as necessary" would be weaker than the truth.

You can delete any individual trip, detected drive, odometer reading, vehicle, shift, cleaning log, Around Me card or audio recording from inside the app at any time. A change or deletion made after an entry's first week leaves a line in the change log (§1). Deleting a vehicle deletes its detected drives, readings and change log with it.

Backups of our database and of sign-in accounts are kept for up to 14 weeks, so a record you delete can stay in a backup until it expires. Backups are used only to recover from a fault.

---

7. Your choices

Everything in this section is in the app, and none of it requires emailing us.

Deleting your account

Delete Account is under Account in the app's side menu (in the side menu itself in versions before 3.3.0) and asks you to type DELETE to confirm. The app's own words for what it does are: "This erases all your data for good. Export your logbook first: the ATO needs you to keep it for five years." — and, if a Fare Meter trip is running or waiting to be resumed, "The trip you are on now will be discarded too."

When you confirm, the app asks our server to delete your records, deletes your sign-in account, and removes the files it wrote for you on your phone — your exported reports, spreadsheets and invoices, which carry your name and accreditation number or your business details, any audio you downloaded, and the copy of a trip that was running. Your stored settings and credentials are cleared from the phone at the same time. The diagnostic log stays until you uninstall: it carries no identity, and it is the one thing that can explain a problem afterwards.

If you want written confirmation that every server-side copy has gone, email hello@ryedc.com and we will complete the erasure and confirm it to you. We would rather say that than claim an automatic result we cannot show you.

Copies in our backups expire within 14 weeks. If we ever restore one, we delete your account's data again.

---

8. Your rights

Everyone

You can ask us to:

• give you a copy of the personal information we hold about you;
• correct anything that is wrong;
• delete your account and your records;
• explain anything in this policy.

Most of this is faster to do yourself in the app. For anything else, email hello@ryedc.com. We will respond within 30 days, and usually sooner.

Anonymity

You may deal with us anonymously or under a pseudonym when you contact us with a general question. You cannot use the app itself anonymously: an account is what separates your driving records from everybody else's, so it needs an email address you control.

If you are in the European Economic Area or the United Kingdom

We process your personal information on these legal bases:

You also have the right to object to processing, to restrict it, to data portability, and to lodge a complaint with your local supervisory authority. Withdrawing consent does not affect anything done before you withdrew it. Your data is transferred outside the EEA and the UK to the providers named in §3, under the transfer terms in their data-processing agreements.

The data controller is Pincab Pty Ltd, contactable at hello@ryedc.com.

If you are in California

We do not sell personal information. If you allow personalised adverts, Google receives your device's advertising identifier and may use it for cross-context behavioural advertising, which the CCPA as amended treats as sharing. You can stop that at any time: refuse or turn off tracking on iPhone, or delete your advertising ID on Android. You have the right to know what we collect, to have it deleted, to correct it, and to not be discriminated against for exercising any of those rights. §1 is the notice at collection; §6 is the retention; §3 is every category of recipient.

---

9. How we protect it, and what we cannot protect

• Everything the app sends is encrypted in transit over HTTPS.
• Everything stored in Google Cloud is encrypted at rest by Google.
• Cards you post in Around Me are shared with every other driver, without your name, your email or anything that says they are yours. Everything else you record is private to you (§5).
• Credentials and sensitive settings on your phone are held in the iOS Keychain or Android Keystore.

Two things we would rather state than leave you to discover:

1. Some things on your phone sit in the app's private storage rather than in the Keychain or Keystore. The offline cache — copies of the records you have viewed, so the app works without a signal — is one; the copy of a running Fare Meter trip is another; and on Android part of the location data kept for automatic tracking is a third. No other app can read any of them, but none is separately encrypted by the app. All three go when you uninstall. The offline cache also goes when you sign out, once your last changes have reached us.
2. On iOS, the app's Documents folder is visible in the Files app, which is how exported reports are meant to be reachable. Anyone holding your unlocked phone can open that folder. Your exported reports carry your name and accreditation number. Lock your phone.

If something goes wrong

If a data breach happens that is likely to result in serious harm, we will notify the affected drivers and the Office of the Australian Information Commissioner as required by the Notifiable Data Breaches scheme, and any other regulator we are required to notify. No system is perfectly secure, and we would rather tell you that than imply otherwise.

---

10. Children

RyeDC is a record-keeping tool for working rideshare and taxi drivers. It is not directed to children. Our Terms and Conditions require you to be at least 18 years old to register, and we do not knowingly collect personal information from anyone under 18.

The app does not verify anyone's age, and this policy does not claim that it does. If you believe a child has created an account, email hello@ryedc.com and we will delete it.

---

11. Contact and complaints

Privacy questions, requests and complaints: hello@ryedc.com

You can also reach us at support@pincab.com.au.

Postal enquiries: Pincab Pty Ltd (ABN 76 606 942 401), Victoria, Australia.

If you want to complain about how we have handled your personal information, email us and say so. We will acknowledge your complaint and respond within 30 days.

If you are not satisfied with our response, you can escalate to the Office of the Australian Information Commissioner:

• Online: https://www.oaic.gov.au/privacy/privacy-complaints
• Phone: 1300 363 992
• Post: GPO Box 5288, Sydney NSW 2001

If you are in the EEA or the UK, you may instead complain to your local data protection authority, or to the UK Information Commissioner's Office at https://ico.org.uk/make-a-complaint/.

---

12. Changes to this policy

When this policy changes, the Last updated date at the top changes with it and the new version replaces this one at the same address. Material changes will also be announced in the app. Continuing to use RyeDC after a change means you accept the updated policy.

This policy should be read together with the RyeDC Terms and Conditions.