Data we may process
The site may process standard server logs, page URLs, browser information, approximate location inferred from network data, error logs, consent choices, and aggregated analytics. Inputs in the standalone calculators are processed in the browser. If you send those details to the AI assistant, they are also processed by the assistant service as described below.
Server logs are used for security, debugging, abuse prevention, and performance monitoring. Analytics, if enabled, should be configured to understand aggregate content performance rather than to identify individual readers.
Google Analytics is only loaded when the site is configured with a real GA4 measurement ID. The integration is intended for aggregate traffic monitoring, landing-page performance, and content planning for the English global site.
Optional AI assistant
Sending a question shares your message and up to three recent question-and-answer pairs with our server and its configured AI service. Relevant public site guides and calculator results may be included to prepare a reply. Avoid including names, contact details, precise addresses, credentials, or other sensitive information.
This site does not store raw conversations or add them to analytics. The conversation stays in the current page's memory until you clear it or leave the page. The AI service processes the messages under its own retention and data-handling terms; we do not promise that it retains no data. AI replies can be wrong and are not a professional diagnosis.
To limit abuse and spending, the server keeps request counts, estimated usage costs, random response identifiers, a daily salted hash of your network address, and any helpful/not-helpful feedback. This ledger is replaced on the next assistant request after the UTC date changes. It contains no message text or raw IP addresses. Standard web-server access logs may separately contain network addresses as described above. Analytics may record that the assistant was opened, answered, or received feedback, without the conversation.
Advertising and cookies
If advertising is enabled, ad partners may use cookies or similar technologies subject to consent requirements. Users in the EEA, United Kingdom, or Switzerland should receive a consent-management experience before personalized advertising is enabled.
The site should not enable personalized advertising in regulated regions until a CMP is configured. Non-personalized ads may still require notice or consent depending on the visitor's location and the partner's policies.
Weather and location pages
Climate pages are based on city-level weather data and do not require a visitor to submit precise personal location. API cache metadata is used to show source, update time, and stale status, not to identify individual readers.
If a future feature adds saved locations, alerts, accounts, comments, or newsletters, this policy must be updated before the feature is released. The current site does not need personal accounts to deliver its guides, calculators, or city-level climate pages.
Data retention, Google Analytics settings, and vendor controls should be reviewed again before any advertising or analytics expansion is enabled.
Contact
For privacy questions, use the contact page and include the page URL, region, and privacy concern involved.