Updated August 17, 2026
This policy explains the data practices used on WattCostLab, including Google Analytics, Google AdSense and Google's consent management platform.
WattCostLab calculators run in your browser. Calculator values are used to perform the calculation on the page and are not intentionally sent to WattCostLab as analytics parameters. WattCostLab does not currently operate homeowner lead forms or a user account system.
WattCostLab uses Google Analytics 4 (measurement ID G-47VETLFFZP) to understand aggregate website usage, such as page views and interactions with site features. Google Analytics may process information such as device and browser information, approximate location derived from IP address, referral information and other identifiers in accordance with Google's policies and the consent choices applicable to the visitor.
WattCostLab is connected to Google AdSense (publisher ID ca-pub-6459318067427691) for site monetization. Google and other advertising technology providers may use cookies, web beacons, IP addresses or other identifiers for ad delivery, measurement, fraud prevention and, where permitted, personalization.
For visitors in regions where it is required, WattCostLab uses Google's certified consent management platform (CMP). The CMP can present choices such as consent, refusal and management of options. WattCostLab has enabled Google consent mode for both advertising and analytics purposes so participating Google services can interpret the visitor's consent choices.
Google services and advertising partners may place or read cookies or use similar technologies when permitted by applicable consent choices. These technologies can support analytics, advertising, security, fraud prevention, frequency controls and measurement.
WattCostLab does not control the independent privacy practices of third-party services. For information about how Google processes information from sites and apps that use Google services, see How Google uses information from sites or apps that use our services.
Display advertising may be used on WattCostLab. Affiliate relationships or contractor referral programs may be added in the future only with appropriate disclosures. No homeowner lead marketplace or contractor referral form is active at the time of this policy update.
Where a Google privacy message is displayed, visitors can use the options in that message to manage applicable advertising and analytics consent choices. Browser settings may also allow cookies or site data to be deleted or restricted.
Factual or calculator corrections can be reviewed through the site's Corrections Policy. This policy is updated when additional forms, account features or data-collection functions are introduced.
WattCostLab may store location, currency and user-entered energy-rate preferences in local browser storage so calculators can reuse them across pages. These preferences are not used to create a homeowner profile and WattCostLab does not send the numeric tariff values you enter as analytics event parameters.
The Climate Adaptation Planner stores selected concerns, action status and any cost/benefit values entered by the user locally in the browser using a key beginning with wcl_climate_plan_v1. The plan is separated by the selected Location and Currency.
These planner inputs are not sent to WattCostLab servers by the planner. If Google Analytics is enabled under the applicable consent state, the planner may send a generic calculator-interaction event and page path; user-entered hazards, project costs, benefit values and action statuses are not included in that event.
When the user loads Location Climate Intelligence, the selected reference-city coordinates, custom coordinates or approximate hosting-derived location are sent to a WattCostLab Netlify function. That function requests the corresponding climate baseline from NASA POWER. The resulting climate response is returned to the browser.
WattCostLab does not add the selected coordinates, climate-screening values or adaptation suggestions to the Google Analytics calculator-interaction event. Hosting and upstream data providers may process request information under their own infrastructure and privacy terms.
Offer files selected in the V16.17 comparator are parsed locally in the browser with JavaScript. WattCostLab does not upload the CSV, TSV or XML contents to its server. Added/imported offer rows are stored in browser localStorage under a market-specific key so the user can return to the comparison on the same browser.
Comparator analytics send only non-personal operational metadata such as the market code, imported row count and rendered offer count. WattCostLab does not send ZIP/postcode values, supplier names, offer prices, annual electricity use, current bill values or imported file contents to GA4.