Brisbane Airport Parking
Brisbane Airport parking — site documentation
Privacy Policy
This policy describes how this website handles personal data.
Last updated 15 October 2026
What this document covers
This policy applies to visitors to brisbaneairportparkinmg.com and to anyone who submits an enquiry through the contact form. The site is an information resource about parking at Brisbane Airport. It does not sell parking, process bookings, or handle payments, and it therefore does not collect booking or payment data. Below you will find what is collected, why it is collected, how long it is kept, and how to make a request about your own data.
Where this policy applies
Brisbane Airport Parking is a comparison and information resource for travellers deciding how to leave a car while flying out of BNE. We write up terminal-side parking, undercover decks, long-stay and budget products, valet handover, and the shuttle services that connect off-airport sites to the terminals. That work is editorial and reference material; every actual bne airport parking booking is made with the operator who owns the car park.
Because of that split, this site collects far less than an operator's booking engine would. There is no account to create, no card to store, no booking record to keep. The only personal data that reaches us is what you choose to type into the contact form or tell us by phone or post. Everything else is routine server information.
Two related documents sit alongside this one. The Cookie Policy explains the small files that may be stored in your browser when you use the site, and it forms part of this privacy documentation. The Terms of Service cover how you may use the content published here. If a question about your data is not answered on this page, the contact details at the bottom are the right place to send it.
Information we collect
Three sources produce data on this site. Each one is listed below with what it contains and what it is used for, so you can see exactly which of them applies to you.
- Contact form entries
- The details you type into the form on the contact page, which typically means your name, your email address, and the content of your message. If you ask us to check a correction against published brisbane airport parking information, whatever you include in that message forms part of the record.
- Phone and postal contact
- If you call or write to us, we receive the details you choose to provide through those channels. That might be your name and number, a return address, or notes about a car park you want us to look at. We keep only what is needed to answer the enquiry.
- Technical information
- Standard information generated by web servers as pages are requested, such as which page was opened and general request metadata. This is used for security and to keep the site operating. It is not used to build a profile of you, and it is not matched against contact form entries.
- What we do not collect
- No booking or payment data, no card details, no vehicle registration when you are only reading, and no precise location tracking. There is no membership system on this site, so there is no password or account history to hold.
Why we collect it
Contact form information is used to read, route, and respond to your enquiry. That includes checking corrections against published airport information and answering questions about parking products. Technical information is used to keep the site available and to detect abusive or automated traffic. We do not use contact form details for marketing, and we do not sell or rent personal data to third parties.
One purpose per collection
If you write to us about Airport Parking at Brisbane and ask whether a car park really offers undercover bays, we use your message for that answer and nothing else. It does not become a mailing list entry, it is not handed to a car park operator to sell you a space, and it is not used to build an advertising audience.
Technical logs follow the same logic in reverse. They are read when something on the site misfires or when automated traffic needs blocking, then they are cleared on the schedule described further down this page.
Cookies and similar technologies
The site may use cookies or similar browser storage for basic functionality and to understand aggregate usage — for example, remembering that a preference was set, or counting how many visitors opened a guide page without identifying any of them. Where cookies are used, they are described in full in the Cookie Policy, which forms part of this privacy documentation.
You can control or block cookies through your browser settings at any time. Blocking functional cookies may affect how parts of the site behave, such as a map or embedded element failing to load, but the informational content about bne airport parking remains accessible and readable.
Data retention
How long something is kept depends on what it is. The list below sets out each category and the rule that applies to it.
- Contact form submissions Kept for as long as needed to handle the enquiry and any follow-up, plus a reasonable period afterwards to keep a record of corrections made.
- Correction records Kept while the correction remains live on the site, so we can show where a published detail came from.
- Technical logs Kept for a shorter operational period, then discarded. They are not archived for analysis.
- Booking and payment data Never retained, because no bookings or payments are made through this site.
- When the period ends Data that is no longer needed is either deleted or anonymised so it can no longer be linked to you.
Sharing and disclosure
Service providers who host or maintain the site see data only as far as operating it requires.
We do not disclose personal data to third parties for their own marketing. Data may be shared with service providers who host or maintain the site, strictly as needed to operate it, and where required by law or a lawful request from a public authority.
If a service provider processes data on our behalf, it is expected to handle that data consistent with this policy — limited to the purpose of running the site, under confidentiality obligations, and without rights to use it for anything else. We do not sell contact details, and we do not pass enquiries to car park operators as sales leads.
Where a lawful request arrives from a public authority, we respond only within what the request actually requires and, where it is permitted, tell you that a request has been made about your data.
Security
We take reasonable technical and organisational measures to protect the data we hold, including limiting access to contact form submissions and technical logs to the people who need to read an enquiry or check a fault. Access is reviewed when someone's role changes, and old copies are cleared rather than left on personal machines.
No method of transmission or storage is completely secure, so we cannot promise absolute security. If you believe your data has been compromised through this site, contact us so we can investigate and, where needed, change how the site handles enquiries.
Access to enquiry records is limited to the people who answer them.
Your rights and how to use them
You can make any of the requests below by contacting us using the details on this page. We may need to verify your identity before acting, and requests are handled within a reasonable period.
Ask what data we hold about you
Send a request in writing and we will confirm whether any personal data relating to you is held, and if so, what it contains. In practice this is almost always the text of a contact form message. We will describe where it came from, why it is kept, and who has seen it.
Request a correction
If something we hold about you is wrong, or if a published detail about a car park needs fixing, tell us which part is incorrect and what it should say. Corrections are applied to the record and to the published page where the detail appears.
Request deletion
You can ask for contact details and message content to be deleted once an enquiry is closed. Where a correction record needs to stay live to show where a published detail came from, we will tell you that before deleting the rest, and we will not keep identifying details alongside it.
Object to processing or ask for a copy
You can object to how a particular enquiry is being handled, or ask for a portable copy of the data you provided to us. Both requests are answered in writing so you have a record of what was decided.
How long a request takes
Straightforward requests are usually answered within a few working days. If identity verification is needed, or the request covers a longer history of correspondence, it will take longer — we will tell you which part is holding it up rather than leaving you with silence.
Changes to this policy
We may update this policy when our practices or the law change. The current version is the one published on this page, and the date at the top of the page shows when it last changed. If an update affects how contact form enquiries are handled, we will say so plainly here rather than leaving you to compare versions.
Privacy questions and requests
- Post
- Brisbane Airport Parking, 11 The Circuit, Brisbane Airport QLD 4008, Australia
- Phone
- +61 7 3406 3000
- [email protected]
- Hours
- Open daily, 24 hours
Related pages