Legal · Privacy
Privacy Policy
1. Scope
This policy describes how WSI Airport Transfers handles personal information for transfer bookings and this website, consistent with the Privacy Act 1988 (Cth) and the Australian Privacy Principles.
It is written to be accurate rather than comfortable. Some of what follows — particularly section 5 — describes limits most privacy policies leave out. We would rather tell you plainly than imply we can do something we cannot.
2. What we collect when you book
- Passenger details: the name, mobile number and email address entered in the booking form. The form asks for the passenger's details — if you book for someone else, you are giving us their information, and this policy covers it.
- Trip details: pickup address, airport and terminal, date and time, passenger and luggage counts, and the number of children and infants travelling.
- Accessibility and equipment needs: whether a wheelchair or pram is coming, and child seat requirements including the ages needed to fit a restraint correctly.
- Flight number and date, if you give one, so we can track your arrival.
- Your name, mobile and email once you have entered a name and a valid mobile, even if you do not press "Send my request". The quote form saves them, with the trip and the fare it showed you, when you leave the page or a minute after you typed them, whichever comes first, so that we can call you back about the fare even if you close the tab. The form says so beside those fields. Nothing is charged at that point. Unless the request became a booking, you can ask us at any time to erase your details from it (section 9).
- A call-back request. If you ask us to call you back from the quote form's "Need a hand?" box, we receive the name, mobile and email you enter there, the part of the form you were on, and the trip details you had typed so far. They reach us by email and are used only to call you back about your trip.
- Anything you type into the notes field. It is a free-text box and we store exactly what you write. Please keep health information, door codes and anything else sensitive out of it — section 5 explains why that matters more here than on most websites.
- Payment details are handled by Stripe. Card numbers never reach our systems; we keep a payment reference and the amount.
- Correspondence — emails, SMS and enquiries you send us.
3. What Google receives while you type an address
The pickup address box uses Google Places. What you type goes straight from your browser to Google as you type it — including text you type and then delete, and including visits where you never book anything. That exchange is between your browser and Google; it does not pass through our systems and we do not keep it. Google handles it under Google's own terms.
We keep only the address you finally select.
4. How we use it
To quote and provide the transfer: pricing, dispatching a driver, tracking your flight, sending confirmations and updates, taking payment, handling refunds, and keeping the records we must keep as a NSW booking service provider. We do not sell personal information and we do not run third-party advertising.
5. Where your booking is stored — and why we cannot delete it
This is the section most policies do not have, and the one most worth reading.
Your booking record is stored on the Internet Computer, a public blockchain. The record — your name, mobile, email, pickup address, trip and flight details, and anything you typed in the notes field — is copied across many independent computers run by different operators, in more than one country.
The consequence is blunt: we cannot delete it. There is no erase function, and we are not being coy — the software has no such capability. Once a booking is written it stays. The same is true of the record of every status change on your trip and every refund, which together form an audit trail we must be able to produce.
Booking records are also records we must keep under NSW point-to-point transport rules. We keep them for at least 8 years, and during that time nobody can delete or erase them: not on request, and not our own staff.
This is deliberate. It means booking and payment records cannot be quietly altered after the fact, which protects you in a dispute. But it also means our answer to a deletion request differs from most businesses', and you should know that before you book rather than afterwards. See section 9.
6. How long we keep things
- Booking records: at least 8 years, and they cannot be deleted on request during that time (section 5).
- A quote request that never became a booking: kept, but your name, mobile, email and pickup address are erased from it if you ask (section 9).
- Complaints: at least 8 years (section 12).
- Your saved quote, and the record used to show your booking reference after payment: short-lived caches — minutes to 24 hours — which expire on their own.
- Flight lookups: cached for about 90 seconds.
- Server logs held by our hosting provider, which include the IP address a request came from.
- Emails and SMS we have already sent remain with our delivery providers and in your inbox.
7. Who else receives your information
Each provider gets only what its job requires. Several are outside Australia.
- Stripe — payments. Receives your email for the receipt, plus payment data.
- Resend — sends your confirmation and update emails, and the emails that tell our team a quote request or a complaint has arrived.
- ClickSend — sends your SMS. Receives your mobile number.
- Google — address lookup and route/distance calculation.
- Google Maps — the map on each area page. It is Google's own page shown inside ours, so when it loads your browser sends Google your IP address and browser details. It loads only when you scroll to it.
- YouTube (Google) — the Western Sydney International video on our Western Sydney Airport page, shown in YouTube's privacy-enhanced mode (youtube-nocookie.com). When the player loads, your browser sends Google your IP address and browser details, and YouTube may store cookies if you play the video. It loads only when you scroll to it.
- AeroDataBox — flight status. Receives the flight number and date only, never your name or contact details.
- tawk.to — runs the chat box on our information pages. Receives anything you type into the chat, plus the page you are on, your browser and device, and your IP address, from which it works out your approximate location.
- Cloudflare — runs our booking server, holds the short-lived caches and logs, and stores drivers' documents (section 11) and complaints with any photos sent with them (section 12).
- Internet Computer node providers — hold the replicated copies described in section 5.
- Your driver — receives what they need for the pickup, passed on by our operator.
- Our channel partners — partner transport operators whose vehicles and drivers we use when our own drivers are not available. When a channel partner carries out your trip, it receives what its driver needs for that trip: your name, mobile number, pickup and drop-off details, date and time, flight number and any notes you gave us. It uses them for that trip only.
- Authorities — where the law requires, including NSW point-to-point transport regulation.
8. Your manage link
Your confirmation email contains a link that opens your booking. That link is the key — anyone holding it can view and cancel your booking, with no password. Treat it like a password and do not forward the email.
The link stops working 30 days after your trip. We cannot revoke a single link before then. If you think someone else has yours, contact us and we will cancel and rebook you under a new reference, which retires the old link.
9. Your rights, answered honestly
Access — yes. Ask and we will give you what we hold. Quote your booking reference if you have one; we compile it by hand, so allow up to 30 days.
Correction — yes for anything operational. We will correct the record and note the correction in the audit trail. The original entry stays visible beside it, because that trail only ever appends.
Deletion — this is where we differ. We can delete material held in our short-lived caches. We cannot delete your booking record, for the reason in section 5: booking records are kept for at least 8 years and cannot be deleted on request during that time.
If you asked for a quote and it never became a booking, we can erase your name, mobile, email and pickup address from that request when you ask. What stays is what identifies nobody: the airport, the date, the passenger and bag counts, the vehicle and the fare.
If you are unhappy with how we have handled a privacy matter, contact us first. You can also complain to the Office of the Australian Information Commissioner (OAIC).
10. If something goes wrong
If we become aware of a data breach likely to cause you serious harm, we will notify you and the OAIC as required under the Notifiable Data Breaches scheme. Given the storage described in section 5, we will tell you plainly what can and cannot be contained.
11. Drivers
We hold each driver's name and mobile number, their vehicle details, the expiry dates of their licence, insurance and driver authorisation, an authorisation reference, and operator notes about their work. Completed job counts and punctuality are recorded from real trip events. This is stored the same way as bookings, so section 5 applies to it too.
Documents that show a driver may lawfully drive passengers. Through their own form, each driver gives us their licence number, state and class, photos of both sides of their licence, whether their licence carries a PT code (and, only if it does not, a medical certificate for the commercial vehicle standard), their driving record, a National Police Check certificate and the dates both were issued, vehicle registration papers, the latest annual safety check, CTP and third-party property insurance documents (with the insurer, policy number and expiry), optionally a service record, the registered owner's name and written permission if the driver does not own the car, which child restraints they carry, a wheelchair competency certificate if they offer wheelchair transport, an emergency contact, their ABN and GST status if they work as a contractor, and their declarations about eligibility and fitness to drive. NSW rules require the booking service to check these and to keep each driver's full name and licence number.
These are not stored in the system section 5 describes. They are kept in a separate private file store run by Cloudflare, encrypted at rest, readable only through our operator console, and they can be deleted. Only the expiry dates and the police check date are kept with the driver record (and the issue dates used for regular re-checks), so that a driver whose documents do not cover a trip cannot be given it. A form a driver saves but never submits is deleted automatically after 60 days; documents we do not approve are deleted when we decline them; approved documents are kept while the driver works with us and for as long as the law requires afterwards, then deleted.
Drivers’ licence photos, driving records and police checks usually show their date of birth and home address, so we hold those inside the documents, in the private file store described above.
Deletion, for drivers specifically. If you have never been assigned a job with us, we can delete your record completely on request — nothing else refers to it. Once you have driven for us we cannot: your record is referenced by booking records, the payment ledger and the audit trail we are required to keep, and section 5 applies. In that case we mark the record inactive so you are no longer dispatched, and it stops being used.
Photographs you send us are stored separately from the records above and can be deleted on request. Photos you submit are reviewed by a person before any of them are used, and any we do not keep are deleted at that point.
Driver payments are recorded here but made outside this system, and the bank details for them sit in the operator's own payroll records.
12. Complaints
If you make a complaint through our complaints page, we collect your name, the date it happened and what you tell us happened. Your email address, your phone number and a reference number from a message we sent you are optional, and so are photos: up to six, if you choose to send any. Photos are kept as you send them, including anything your phone stores inside the file, such as when and where it was taken.
Your complaint and its photos are not stored in the system section 5 describes. They are kept privately in a separate file store run by Cloudflare (Cloudflare R2), encrypted at rest. They can only be opened with a private link that only our admins can see. What is kept in the system section 5 describes is a short register entry: the complaint's reference number, what it is about (a driver, a trip, charges or a lost item), when it arrived, the date it happened, its status, and our team's notes on how it was handled, with who wrote each note and when. Your name, contact details, description and photos are not part of it.
Our admins can see your complaint. When one arrives, an email telling them about it is sent through Resend, with your name, the contact details you gave and the start of your description. If our system could not save your complaint, that email carries all of your description instead, so that it is not lost. We use what you send only to look into your complaint, to reply to you, and to keep a record of how it was handled.
Complaints are records, and we keep them for at least 8 years. We do not delete them on request during that time.
13. Our staff
Our operators sign in with Internet Identity. Their sign-in identifier is written permanently into the audit trail beside every action they take, so it is always clear who did what. Removing someone's access does not remove them from that history.
14. Cookies, browser storage and analytics
The booking form keeps what you have typed, including your name, mobile and email if you have entered them, in your browser on this device for up to 7 days, so you can come back and finish. It is deleted when you send the request, when you press "Start again", or after 7 days. It is not sent to us until you send a request or ask for a call back, except for the details described in section 2, which the form saves once you have entered a name and a valid mobile. Stripe and Google set and receive information in your browser on the booking page as part of taking payment and looking up addresses. Our operator console stores a sign-in session on the operator's own device.
We use Google Analytics to count visits and to see which pages people find
useful. It sets cookies in your browser (their names start with _ga) and sends
Google the pages you view, the site that sent you here, your device and browser type, and
your approximate location, which is worked out from your IP address. Google Analytics does
not store IP addresses. We do not send it your name, phone number, email address or booking
details, and it does not run on the page where you manage a booking.
We do not use it for advertising, and apart from the chat box described below the site runs no other tracking. Google handles this data under its own privacy policy. You can stop it by blocking cookies for this site or by installing Google's Analytics opt-out browser add-on.
Live chat. Our information pages carry a chat box run by tawk.to. It loads a few seconds after the page opens and, even if you never open it, tells tawk.to which page you are on, your browser and device, and your approximate location (worked out from your IP address). It sets cookies and browser storage so a conversation carries on as you move between pages. Whatever you type into the chat, including any name, phone number or email address you give, is stored by tawk.to and seen by our team. The chat box is not on the booking form or on the page where you manage a booking. tawk.to handles this data under its own privacy policy.
15. Security
Payment credentials are held by Stripe, not by us. Reading full booking records through our operator console requires an Internet Identity sign-in on an account we have specifically granted. Our booking server also reads booking records automatically, under its own credential, in order to send your notifications and track your flight.
Please keep sensitive details out of the free-text notes field — see sections 2 and 5.
16. Contact and changes
Reach us through the contact page for any privacy request. If we change this policy we will update it here with the date, and material changes will be described rather than slipped in.