HEAT PUMP FINDER · SYDNEY
Privacy Notice
This notice describes the information used by the Heat Pump Finder directory. You can browse the public directory without creating an account or giving us your name, email address, phone number or home address.
Saved items on your device
If you save installers or tick checklist items, the site stores the selected listing identifiers and checklist choices in your browser’s local storage under “heat-pump-finder-v1”. These preferences are not uploaded to the directory’s analytics database or sent to installers. They stay until you clear them or your browser removes them.
Use “Clear my saved shortlist and checklist” in the directory’s visitor-information section, or clear this site’s data in your browser settings. If storage is blocked, the features work for the current visit where possible. Search and filter terms are used in the page and are not sent to our event counter.
When you visit a provider
Website buttons add source labels such as “heatpumpfinder” and a fixed HPF business reference to the destination URL. These identify this directory and a business listing, not you. The destination business can receive these labels and process your visit under its own privacy practices. Official-source links use the same fixed referral labels; clicking a provider link with a counting identifier can contribute to the aggregate website-click count when reporting is connected.
The directory publishes referral links rather than provider contact details. Information you choose to give a business is handled by that business. Historical reports, if retained separately from an earlier platform, are not part of this deployment.
Commercial relationships
We don’t currently accept payment for placement or rank providers as the best. There are currently no affiliate commission arrangements. If paid listings, sponsorships or referral arrangements are introduced, they will be clearly labelled and this notice will be updated.
Advertising and other services
No Google AdSense advertising or Google Analytics code is active on this site. We do not currently send directory events to Google advertising products. There are no enquiry forms, newsletters or payment forms on the directory.
If advertising or other tracking services are introduced, this notice and any required consent controls must be updated before those services are enabled. Their data handling must not be assumed to be the same as the current first-party counter.
About this notice
This notice covers the directory’s implemented features, not the privacy practices of external businesses. Read their notices before supplying personal information. See how the directory is compiled for its scope and limitations.
Privacy contact
A publisher privacy contact has not yet been published. This notice will be updated when a public contact route is available.
Editorial update: 8 November 2026
Cookieless traffic and referral counts
This version includes a first-party counting script. It sends page-view and selected provider-link click events to this website's own endpoint to help us understand which pages and listings are useful. The browser reduces the referring website or recognised campaign labels to broad source and channel categories before sending an event; raw referring URLs, search terms and arbitrary campaign text are not included.
When the Cloudflare reporting database is configured, the counter stores aggregate totals by UTC day, approved public page, public listing identifier (for clicks), source category and channel. It does not store IP addresses, browser or session identifiers, names, contact details or saved shortlists in that database. It does not use fingerprinting or create analytics cookies. These are event counts, not unique visitors, confirmed enquiries, bookings or sales. Repeat visits, testing and some automated activity may count. Blocked scripts, privacy controls and failed requests may cause undercounting. Owner visits are not automatically excluded. Source categories describe the current page entry, not a visitor's complete journey.
The script can send requests before the reporting database is connected, but the counter cannot persist events without that connection. Failed events are not backfilled. Daily counts can be totalled over a week or month but cannot identify unique people. Aggregate counts currently have no automatic deletion schedule. They are accessible through the authorised Cloudflare account; this deployment does not provide a public owner dashboard or reporting API.
Your choices and browser storage
Our first-party counter does not create analytics cookies or persistent visitor identifiers, and this site does not display an analytics-cookie consent banner. This is not a claim that every data-processing activity is exempt from applicable privacy law. Our first-party counting script respects browser Do Not Track and Global Privacy Control signals. These controls apply to our counter, not necessarily to the separate Cloudflare service described below. Where an optional stop-counting control is shown, it stores only that preference locally in your browser. It is not an identity or tracking value. Saved shortlist and checklist features use local browser storage as described above. An earlier analytics cookie, if present, is expired rather than renewed; retired analytics preference values are removed. This does not install a new tracking cookie.
Hosting and infrastructure data
Cloudflare delivers and secures this website and processes technical request information, such as IP addresses, browser headers, requested URLs and timing, separately from the aggregate counter. Infrastructure logs or account-level analytics may include information not stored in our counter. Cloudflare's handling and retention are governed by its services and policies; processing may occur outside Australia. See Cloudflare's privacy policy. The absence of analytics cookies does not mean no technical or personal information is processed when you use the internet.
Cloudflare browser performance and usage measurement
Cloudflare also injects its Real User Monitoring (RUM) beacon into responses from this site. This is separate from our first-party counter and its optional database. Depending on Cloudflare account settings, the beacon supports Web Analytics or Observatory performance measurement. The presence of the beacon does not mean every visit is measured or that all dashboard reports are configured.
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 can differ from the broad source categories sent to our own 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. The scope of collection can vary with account settings and the visitor's region. 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 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. This notice does not claim that successful collection or particular dashboard metrics have been verified.
Changes to this setup
This site does not include Google Analytics, advertising pixels or personalised advertising. The separate Cloudflare beacon is described above. Enabling another hosting-dashboard integration, contact service or advertising technology can change data handling. We will review the actual data collected, update this notice and implement any legally required choices before introducing those features. A future change will not be treated as authorised by this notice alone. Last reviewed: 8 November 2026.