Hosted in Queensland, and why it matters

A booking can carry a note like “uses a walker” or “needs help to the front desk”. We built for older riders first, so notes like that are common, and some of them are about health. Before writing a privacy promise, I wanted to be able to say exactly where all of it lives.

Where everything is

• The booking system runs on our own servers in Queensland, with a copy of the database taken every night, daily backups, and an alarm if a backup is missed. The alarm also sends a weekly note saying all is well, so we know the alarm itself still works.
• Our backups are also kept by Datto, in Australia.
• Our email is Microsoft 365, kept in Australia.
• Our phone system is 3CX, hosted in Sydney.
• Our texts go through CommsChannel, in Sydney.

So since 6 October 2026, our privacy page has said that riders’ information doesn’t go overseas.

The one exception we designed around

Notifications that pop up on staff phones travel through the phone makers’ push services, which are overseas. So staff notifications are fixed sentences that never name a rider or say where they are going. Notifications to riders’ own phones are built, but switched off, because the privacy page would have to change first.

What the public sees

Our list of shared rides shows a suburb, a 30-minute window, a direction and the seats free. Never a name, an address or an exact time. On an island this size, a suburb and an exact time can be enough to tell who someone is.

What we would tell you

Make every sentence on your privacy page something you can show is true. The list to check: the database, the backups, email, phone, texts and notifications.

We name our suppliers so you can see where the data goes, not as a recommendation.