Your activity stays on your Mac.
Awakepilot works without an account and does not include advertising, analytics, tracking, or telemetry.
Privacy summary
- No Awakepilot account is required.
- No advertising, analytics SDK, tracking pixel, or telemetry service is included.
- Your activity history and preferences stay in your macOS user account.
- Awakepilot does not sell or share personal data.
Data stored locally
Awakepilot stores preferences, session state, recent system measurements, and a limited activity history in your macOS user account. Saved automation settings can include Wi-Fi names, selected volume identifiers, automation profile names, selected device identities, DNS servers, and IP-network rules.
Command text and command output are not written to the activity history. Drive Alive creates a small .awakepilot-drive-alive marker on each selected writable drive and removes its own marker when the feature is disabled.
Network access
When automatic update checks are enabled, Awakepilot checks GitHub for the latest published version. Installing an update downloads a signed release package from GitHub.
GitHub may receive normal connection details, such as your IP address, under its own privacy policy. Awakepilot does not send usage events with this request.
Diagnostic reports
A report is created only when you request one and select where to save it. Nothing is uploaded automatically.
Reports exclude command text, command output, file paths, Wi-Fi names, volume names, automation profile names, watched application and process names, device names, DNS servers, IP rules, and activity history. Review any file before sharing it with support.
System permissions
Notification permission is optional. Reading the current Wi-Fi network name requires macOS Location Services permission; Awakepilot does not request or store geographic coordinates. Wake sessions use native macOS power-management APIs and do not require administrator access during normal use.
Launch at login uses Apple’s native service registration. The global shortcut does not require Accessibility or keyboard monitoring permission.
Bluetooth automation requires the standard macOS Bluetooth permission and checks connected paired devices locally. USB, audio-output, DNS, and IP rules use local system information.
Release integrity
Official Awakepilot packages are signed with a Developer ID certificate, notarized by Apple, and published with SHA-256 checksums. The public release history provides version notes and downloadable packages.