This initial directory is free to browse and does not collect enquiries, payments or account registrations.
Shortlist storage
If you save providers, their directory identifiers are stored in this browser’s local storage so your shortlist survives a page refresh. Use “Clear shortlist” to remove them. This directory does not save a persistent analytics identifier in your browser.
Outbound referral tags
Official website buttons include UTM parameters identifying Access Atlas Australia, the directory referral campaign and the provider’s public listing ID. They do not contain your name, contact details or shortlist. A receiving website may read these parameters under its own privacy policy. It can also receive ordinary connection information, such as your IP address. External links use an origin-only referrer policy for cross-site navigation, so the directory’s page path and search terms are not sent in the referrer header. Source-reference links also carry directory UTM tags, using a separate source_reference campaign. Provider clicks are measured only when PostHog is activated as described below. A referral label does not establish that an enquiry or sale occurred.
Advertising
No Google AdSense code or other advertising technology is active on this site. There are no ad impressions, ad personalisation or advertising cookies from this directory. Any future advertising setup will require an updated privacy notice, appropriate consent controls and the relevant platform approval before activation.
Commercial transparency
Listings are currently displayed alphabetically. We don’t currently accept payment for placement or rank providers as the best. There are currently no star ratings or affiliate payment arrangements. If paid listings, sponsorships or referral arrangements are introduced, they will be clearly labelled and this notice will be updated.
Traffic and provider-link measurement
PostHog is configured for limited cookieless measurement on this directory. Delivery depends on browser settings, service availability and the account limits. This release has no first-party event database or public owner-reporting endpoint.
When measurement is active, PostHog receives approved public page views and provider-link clicks, a directory identifier, public provider identifiers and broad source and channel categories such as Google search or a social referral. This integration excludes search and filter text, saved shortlists, form content, raw referring URLs, arbitrary campaign values, URL queries and fragments from event properties. A provider click is not a confirmed enquiry, booking or sale. Autocapture, person profiles, session replay, keystroke recording, advertising pixels and personalised advertising are disabled.
Cookieless counts and their limits
The integration uses PostHog's always-cookieless mode. It does not save an analytics identifier in cookies, local storage or session storage. PostHog receives your IP address as part of the connection, together with your browser’s user-agent string, which describes browser and device software. The user-agent string is included in event properties because PostHog requires it for cookieless processing. PostHog uses this technical information, a daily rotating server-side hash and hostname to calculate a daily identifier. This processes connection data; it is not a claim that no personal information is processed.
Daily unique-visitor figures are estimates. The identifier changes each day, so weekly and monthly reports can show page-view and provider-click totals but cannot reliably deduplicate different people across days. Different people can merge in a count and one person can count more than once. Geographic enrichment and IP-based bot enrichment are not available in this mode. Owner visits, tests and undetected automation may count; blockers and failed requests can reduce totals. Source categories describe a page entry, not a complete visitor journey.
Your choices and local browser storage
Do Not Track and Global Privacy Control prevent this script from loading PostHog or sending new events. Temporary preview hostnames do not collect. You can also stop measurement with the control below, which saves only your choice in this browser. Reload after changing the setting. These choices do not necessarily stop separate Cloudflare services. Saved shortlists and checklist choices remain separate functional browser storage.
PostHog measurement is not activated.
Processing location, retention and access
Events are sent directly to PostHog's European Union service. PostHog receives technical connection information including IP address and browser information; processing and storage occur outside Australia. Access is through the operator's account, not a public analytics dashboard.
The current PostHog plan reports a 12-month default retention period. Automatic deletion after 12 months is not currently confirmed, so event records may be retained longer. Daily identifier rotation does not delete stored events. Retention is controlled in the operator’s PostHog account. See PostHog’s event-retention documentation. Missing or blocked events are not backfilled. See PostHog's privacy policy and cookieless measurement documentation.
Hosting and future changes
Cloudflare delivers and secures the website and receives technical request information such as IP addresses, browser headers, requested URLs and request times. Its hosting and security processing is separate from PostHog. Processing may occur outside Australia, and security functions may use essential cookies. The separate Cloudflare RUM disclosure below still applies.
This release does not display an analytics-cookie consent banner. No-banner design is not a universal exemption from applicable privacy and consent requirements. Any future advertising, contact forms or materially different tracking require an updated notice and any legally required choices before activation. Reviewed 11 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 the PostHog measurement described above and does not use the PostHog settings. 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 hosting measurement can include full landing-page and referring-page URLs, rather than only broad source categories. 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. This release does not provide a Cloudflare RUM opt-out control. Browser privacy preferences are not a guarantee that the hosting service's beacon is blocked. The operator can disable or change Cloudflare RUM through the hosting account. Cloudflare account-level traffic figures and RUM reports are separate hosting services and are not PostHog page-view or provider-click reports. The absence of analytics cookies is not a universal exemption from applicable privacy obligations.