This page explains how Bars and Nightclubs Australia treats personal information on a content directory. The site helps people plan a night in an Australian city. It is not a booking engine, payment processor, or account system. We do not need your date of birth to tell you that photo ID is commonly asked if you look under 25.
The rebuild is a content site. On day one it does not ship the old AdSense stack, Ezoic tags, or social pixels from the archive HTML. If analytics or advertising pixels are added later, this page should name the vendor and the cookies. Until then, do not assume a tracking stack that is not here.
Who we are and how to reach us
The public site is barsandnightclubs.com.au. Privacy questions and directory corrections go to [email protected], also listed on contact. That inbox is for corrections, advertising questions, guest-post pitches, and privacy requests. It is not a concierge. We will not use a privacy email as a guest-list request.
If you write to us, we receive whatever you put in the message: name, email address, and the body. Use the canonical venue path /{city}/all/{venue}/ when you are correcting a room so we do not need extra personal detail.
What we collect, and what we do not
Contact mail and the contact form. If you use the form or the inbox, treat the contents as correspondence. During the rebuild the form may be a placeholder that does not yet store submissions server-side. When it routes to an inbox, the message lives in that mailbox for the purpose you sent it — a listing fix, an ad question, a pitch. We do not sell that list. We do not use it to build a nightlife profile of you.
CMS and git. Editors change pages in git via Keystatic (local or GitHub). Commit metadata can include an editor identity. That is a publishing workflow, not an audience database.
Hosting and security logs. Any website’s host and content-delivery network will see IP addresses, user-agent strings, and requested URLs in ordinary server logs. Those logs exist to operate and secure the site, not to score your bar taste. Retention follows the host’s ordinary cycle.
We do not collect account passwords, payment cards, dates of birth, or guest-list names, because we do not offer accounts, payments, or lists. We do not ask you to upload ID. Responsible service happens at the venue, not here.
We do not revive archived comment stacks, newsletter tools, or advertising cookies from the old WordPress or magazine-era HTML unless they are added on purpose and named on this page.
Cookies and third parties
A basic content site may set a cookie that is strictly necessary for security or form-progress. It should not need an advertising identifier to render a Sydney hub or a nightclubs guide.
If a future deploy adds audience measurement or an ad server, the vendor belongs here by name, with what the cookie is for and how to refuse it where the law requires a choice. The advertise page’s 2014 CPM figures are historical publishing history, not a live pixel. Citing them does not mean AdSense is on the page.
Embedded maps, fonts, or video — if added — are third-party requests with their own privacy notices. We will prefer not to load a social pixel on a directory article.
Venue names, minors, and sensible use
Venue names and brands remain the property of their owners. A listing is not an endorsement and not a claim the room is open. See the footer disclaimer on every page.
This directory is 18+. We do not try to collect information about children, and a nightlife site is not meant for them. If you believe we have collected a child’s personal information in a message, write to the inbox and ask for deletion.
Do not send us other people’s personal data unless you are the operator correcting a public listing and the data is already public (a trading name, a street, a website). Do not send scanned IDs, staff rosters, or customer lists.
Your requests
You can ask what personal information we hold about you from correspondence, and you can ask us to correct or delete that mail where we still control it. Send the request to [email protected]. We may need enough detail to find the thread. Hosting logs are not a marketing file we can search by name.
If you want a listing changed, that is a content correction, not only a privacy request — same inbox, same contact rules.
How this sits with the rest of the site
About explains that venue canonicals are /{city}/all/{venue}/. The FAQ answers ID, lockouts, closing times, and type splits without collecting anything from you. City hubs and type guides are editorial. Read them without creating an account.
18+. Drink responsibly. A privacy policy is not a booking, not a cover price, and not a guarantee of entry.