Device-local household data
Wattwise does not require a login. Calculator drafts, regional settings, household details, appliances, bills, scenarios, budgets, and preferences are stored in this browser. They are not uploaded to a Wattwise user profile or synchronized across devices.
Saving, exporting, and deletion
The header confirms when work is saved on this device. Reports offers print/PDF, JSON, CSV, and copy options. Settings can download a complete portable backup or clear Wattwise household, bill, scenario, setting, and draft data from the current browser.
Purpose and sharing
Device-local data is used in the browser to calculate, forecast, reconcile bills, build scenarios, and create user-requested exports. It is not public and is not supplied to advertising adapters.
A share link contains calculation assumptions placed in the URL by the user-facing share action; it does not include the complete household, bills, or other private workspace data.
Consent and regional choices
Users can accept, reject, manage, and withdraw optional analytics and advertising choices. Global Privacy Control is handled as an opt-out signal in the technical integration. EEA, UK, and Swiss personalised advertising must remain unavailable until the owner configures an appropriate Google-certified consent platform and verifies its signals.
Storage limits and backups
Browser storage can be cleared by browser controls, private-browsing cleanup, device reset, or the Wattwise Settings page. Because there is no user account or cloud recovery, users should download a backup before clearing site data or moving to another device.
Security and retention
Device-local records remain under the browserโs same-origin protections. Wattwise limits advertising to eligible public or house placements and keeps it out of bill, settings, report, and other sensitive data-entry surfaces.
International processing and contact
Cloud hosting, monitoring, analytics, consent, or advertising providers may process technical request or consent data in other countries when the deployment owner enables them. The owner must document the selected providers, locations, safeguards, retention schedule, and applicable user rights before launch.
Use the Contact page for privacy requests. This policy describes the present technical design and requires professional legal review for the ownerโs jurisdictions, organisation, and provider contracts.