Treat energy-monitor privacy as a map of accounts and copies, not a single “local” or “encrypted” label. Write down who can access the readings, where they persist and how access can be removed. Fine-grained history may expose household routines even when it contains no camera footage.
Draw the data path
Use one row for each destination rather than recording only the device vendor.
| Destination | Evidence to collect | Exit action to confirm |
|---|---|---|
| Device or local controller | Stored fields, retention and access controls | Supported reset or removal procedure |
| Vendor account | Cloud history, shared users and policy date | Account deletion and stated retention exceptions |
| Connected platform | Permissions, tokens and copied history | Revoke integration and address retained copies |
| Downloaded CSV or backup | Storage location and other people with access | Remove or retain deliberately |
| Installer or previous occupant | Account ownership and delegated access | Remove access after handover |
A local interface does not establish that the device never communicates with a cloud service. Deleting a vendor account does not automatically erase a CSV you downloaded or records already copied into another platform.
Ask concrete questions before connecting
Find the current privacy policy and support documentation for the exact service. Record what they say about detailed energy data, retention, sharing and deletion. Distinguish a documented statement from an unanswered question. Do not assume “encrypted” means the provider cannot read data; that depends on the system’s design.
Confirm whether separate household users can be invited and removed. Prefer supported individual access over sharing the owner’s password. Use a unique password and multifactor authentication where available. Keep account recovery details securely, and review permissions for integrations you no longer use. The FTC’s connected-device guidance supports these basic account and update practices.
Plan for a roommate change or house move
Before a transfer, decide whether the hardware stays and which historical records belong with it. Export only the information you intend to retain, remove shared access and integrations, then follow the maker’s ownership-transfer or reset instructions. A factory reset and cloud-account deletion are separate operations unless the documentation explicitly combines them.
Do not leave an installer as the permanent account owner merely because they completed setup. Agree the handover before installation. In a shared home, also agree which equipment will be monitored; a household energy project should not quietly become personal-room surveillance.
Choose less collection when it answers the question
One passive meter can answer a compatible appliance question without another cloud account. A utility portal may already provide whole-home intervals, though that service has its own data policy. Neither option is universally private; compare the actual information and access involved.
Use the data-export guide to check what can leave an app, and the local-versus-cloud comparison for operating dependencies. This checklist does not audit a vendor’s security or guarantee deletion; it gives you a record of what is documented and what remains unresolved.