EnergyBot NOVEC

Privacy policy

Last reviewed October 16, 2026. This policy describes the current EnergyBot Gmail notification integration. EnergyBot is a privately operated local Windows application maintained by Jeffrey Crook for electricity, solar and EV energy monitoring.

Access and purpose

With the account holder’s consent, EnergyBot requests only Google’s gmail.readonly permission. This permission technically permits mailbox-wide reading; Google does not limit it to NOVEC email. EnergyBot uses it to verify the connected mailbox and identify NOVEC bill-ready notices for local billing review and duplicate prevention.

The application searches for candidate NOVEC messages, reads their headers and text, and checks sender authentication, account identity and service location. Incremental Gmail history processing may receive identifiers for other messages, but EnergyBot does not open their contents or retain those unrelated identifiers. It does not send, modify or delete email.

Information retained

EnergyBot retains a hashed notification identifier, received time, notification month, hashed account identifiers, processing status, retry and audit records, and a Gmail history cursor. Hashes are pseudonymous identifiers, not a guarantee of anonymity. The current detector processes notification text in memory and does not save complete email bodies or download email attachments.

Separately imported utility PDFs and energy records may be retained by the local billing workflow for audit. They are distinct from the Gmail notification records described here. The supervised detector has been validated; unattended monitoring and automatic statement retrieval are not currently active.

Storage and security

OAuth tokens are protected with Windows current-user DPAPI encryption and stored outside Dropbox in the operator’s local application-data directory, with access restricted to the Windows user and system. Google API communication uses HTTPS. These protections do not prevent access by a compromised Windows session.

Sharing and Limited Use

EnergyBot does not sell Google user data, use it for advertising, or transfer it to advertising or data-broker services. It uses Google’s API to obtain the authorized data. Apart from operator-configured synchronization or backups, the current integration has no feature that sends notification contents to another service. It does not send Gmail data to these public informational pages.

EnergyBot’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, deletion and revocation

There is currently no automatic retention limit or automatic purge. Notification metadata and audit records remain until the operator removes them through controlled local maintenance. There is no self-service deletion button. Removal must account for audit dependencies and any synchronized copies, backup retention or service trash; deleting a local file alone may not remove those copies.

You can revoke EnergyBot’s Google access through Google Account third-party connections. Revocation prevents subsequent authorized access once Google invalidates the credentials; it does not delete data already retained locally or in backups. To request removal of retained information, contact the operator below. Gmail messages remain in your Google account unless you change them yourself.

This information website

These two static pages contain no application login, analytics scripts, advertising or tracking cookies. The hosting provider may keep normal website access logs, such as IP addresses and request times. Visiting a page does not grant Gmail access.

Contact and changes

For privacy, access or deletion questions, contact Jeffrey Crook at jeffreycrook1@gmail.com. Material changes to data handling will be reflected in this policy and the application’s disclosures before the changed use begins.