Information Battery Hog processes locally
Battery Hog reads operating-system information needed to explain battery state and active work, including battery status and power data, process CPU and memory, process ancestry, cached working directories for recognized development activity, memory pressure, sleep assertions, power logs, uptime, and macOS thermal state.
That information is displayed inside the app and is not uploaded to Battery Hog or its developer.
Local storage
Settings, muted suggestions, and the local registry used by Battery-aware Agent Mode may be stored under the current user’s application-support area. Power and charge history comes primarily from the Mac’s own system logs. The repository documents the implementation so these behaviors can be reviewed.
Network access and updates
The app does not send monitoring analytics. For direct-download installations, the built-in updater can request a signed update feed hosted by GitHub when you manually check or after you enable periodic checks. Periodic checks are off by default. GitHub may receive ordinary request information such as IP address, app version, and request time. Homebrew-managed installations do not use the built-in updater and remain subject to Homebrew’s own update behavior and privacy terms.
Administrative prompts
Some optional system actions, such as Low Power Mode changes or detailed privileged readings, may use macOS authorization. A password entered into the macOS authorization prompt is handled by macOS; Battery Hog does not store it.
No sale or sharing of personal information
Battery Hog’s developer does not receive app monitoring data and therefore does not sell it, use it for advertising, or share it with data brokers.
Website
This static website is hosted by GitHub Pages and contains no analytics, advertising pixels, cookies, account system, or form. GitHub may keep ordinary request logs under its own privacy terms. If analytics or a contact form is ever added, this policy will be updated first.
Questions and security reports
Open a public question through GitHub Issues. Report vulnerabilities using the private process in the repository’s security policy.