Plain-language privacy information for this edition.
Search and saved links
Directory search and filters run in your browser. We do not operate an enquiry form or send your search text or shortlist to providers. If you save a provider, its directory identifier is stored in your browser’s local storage. This is not an account and it does not sync between devices. Stable business identifiers preserve saved choices when the directory grows; older saved lists are migrated automatically in this browser.
Clear your shortlist
Remove individual saved items using their save buttons or clear all locally saved links below. Clearing browser site data also removes the shortlist. Your browser may block or clear storage; the shortlist is a convenience, not a permanent record.
Outgoing links
External websites open in a new tab and have their own policies. Provider links include a generic referral label (utm_source, utm_medium and utm_campaign) identifying this directory. The browser may send this site’s origin as referrer information. We do not append your search, shortlist, name, contact details or project information.
Downloads
The shortlist download is generated locally in your browser. It contains only the selected provider names, categories, areas and website links. It is not sent as an enquiry.
Last updated 8 November 2026.
Cookieless traffic and referral counts
This edition includes a first-party event counter. When its reporting database is configured, it stores aggregate page-view and provider-website-click counts to understand which directory pages are useful and how visitors reach them. The browser sends the event type, approved public page path, public provider identifier where applicable, and broad source and channel categories to this website. It classifies a referrer or campaign label locally; it does not send the raw referring URL, campaign text, search terms, shortlist or contact details to the counter.
The database stores the UTC day, event type, public page and provider identifiers, source category, channel and aggregate count, plus the time collection first started. The counter does not create a visitor, session or event identifier, use fingerprinting, or retain IP addresses or browser user-agent strings in that database. Requests still pass through the hosting service, which receives connection data as explained below. No persistent analytics cookie is set. A maintenance request expires any legacy analytics cookie and clears retired analytics preferences; it does not grant consent or create a tracking identifier.
The event counter respects browser Do Not Track and Global Privacy Control signals and rejects recognisable bots. It does not display a cookie-consent banner. If the database is not configured or an event request fails, the counter does not store or backfill that event. The presence of this notice does not confirm that reporting has been activated.
These are event counts, not unique visitors, confirmed enquiries, bookings or sales. Repeat visits, tests and undetected bots can count; blocked scripts and failed requests can reduce totals. Owner visits are not automatically excluded. The source describes the current page entry, not a complete visitor journey. Daily counts can be added into weekly and monthly totals, but cannot establish how many different people visited. Aggregate counts have no automatic deletion schedule. Reporting is restricted to the authorised Cloudflare account; this edition has no public reporting endpoint or owner dashboard.
Hosting and separate Cloudflare services
Cloudflare delivers and secures this website. It receives technical request information such as IP addresses, browser information, requested URLs and request times, and may process logs, security information and infrastructure-level traffic statistics separately from our aggregate counter. Depending on the account configuration, security functionality may use essential cookies. Cloudflare operates internationally; processing may occur outside Australia. Its retention and handling of this data are governed by its services and privacy policy.
Cloudflare may provide separate browser performance and usage measurement through its RUM beacon, as described below. It is not our first-party counter, and public site code alone does not establish the hosting account configuration.
Cookies, storage and future changes
No advertising or behavioural remarketing script is included in this edition. Functional browser storage for saved choices is described above and is separate from analytics. External provider sites have their own cookies and privacy practices. This notice is information about the site, not a request for consent or a claim that using the site consents to unrelated tracking. New advertising, enquiry forms, analytics providers or other data uses require a fresh privacy review and an updated notice before activation. This cookieless design does not remove other applicable privacy obligations.
Analytics and hosting disclosure reviewed 8 November 2026.
Cloudflare browser performance and usage measurement
Cloudflare may automatically inject its Real User Monitoring (RUM) beacon into pages served through its network, depending on this site's account settings and the visitor's region. The beacon can support Web Analytics or Observatory performance measurement. It is separate from our first-party counter and its optional reporting database. Cloudflare's current documentation says RUM can be enabled automatically on its free service. This notice does not confirm the dashboard settings or that a particular visit has been recorded.
When enabled, the beacon runs in the browser and sends Cloudflare page and performance information, including a per-page-load identifier, landing-page and referring-page URLs, load and rendering timings, and browser performance metrics. This differs from the broad source categories sent to our first-party counter. Cloudflare says its RUM beacon does not read or write cookies or browser storage and does not persist an identifier to recognise a person across visits. A per-page-load identifier is not a count of unique people.
Cloudflare receives an IP address as part of delivering the beacon request. Its published RUM documentation says this address is discarded at the nearest Cloudflare data centre rather than stored in core RUM databases or logs. That statement concerns RUM only, not all hosting or security processing. Processing may occur outside Australia. See Cloudflare's RUM data and privacy documentation and Cloudflare's privacy policy.
Browser or network privacy tools may block the beacon, which can reduce reporting. We do not promise that our first-party counter's Do Not Track, Global Privacy Control or local opt-out settings also stop Cloudflare's beacon. The operator can disable or change Cloudflare RUM through the hosting account. Cloudflare account-level traffic figures and RUM reports are distinct from our first-party page and provider-click counts. The absence of analytics cookies is not a universal exemption from applicable privacy obligations.