AwakeFlow is developed by Mehdi Hosseini. This policy explains what information AwakeFlow handles and how it is used. Keep-awake on the Mac works locally. Signing in is optional.
Summary
- AwakeFlow does not sell your data.
- AwakeFlow does not include third-party analytics, advertising, or tracking SDKs.
- AwakeFlow does not read your flows, files, or agent prompts on our servers. Traffic between your linked devices is end-to-end encrypted.
- Keep-awake data you configure stays on your Mac. Sign in with Apple is optional and used only to link your own devices.
Information stored on your Mac
AwakeFlow may store the following locally in your user account:
- Saved flows — your most recent flow configuration (wait conditions, finish action, and related settings) in Application Support.
- Security-scoped bookmarks — references to folders you explicitly choose for folder watching, command working directories, download destinations, or output file watching.
- Flow settings you enter — such as app names, URLs, timer durations, notification text, and Bluetooth device selections.
This information is used only to run AwakeFlow features you configure.
Optional account
Signing in is optional, and every keep-awake feature on the Mac works without it. AwakeFlow uses Sign in with Apple so your own devices, including AwakeFlow on iPhone, can find this Mac and link to it when they are signed in to the same Apple Account. If you sign in, our relay stores:
- a one-way hash of your Apple user identifier
- device names, models, and public keys used for linking
- notification tokens for linked devices, so they can be alerted when an agent needs you
- linking timestamps
Live status, approval questions, and file paths travel in sealed messages. The relay routes them and cannot read them. Choose Settings → Account → Delete account in AwakeFlow to remove the stored identifiers and tokens from the relay.
In version 1.3
Version 1.3 adds local run history, render monitoring, and agent connections. Run history keeps up to 100 records on your Mac, including flow configurations, completion reasons, and requested finish actions. It does not record command output; saved flows can contain the paths and commands you enter.
The connection between an agent and AwakeFlow stays on your Mac. Your selected agent may use its own external services under its own privacy policy. AwakeFlow does not send your flows or history to developer-operated servers.
In version 1.4
Version 1.4 adds schedules. A schedule is stored on your Mac next to the flow it starts, with its time, repeat days and finish choice. Schedules are not sent to developer-operated servers.
In version 1.4.2
Version 1.4.2 stores two more choices with a schedule: whether to keep the Mac awake until the schedule starts, and whether to turn the display off while waiting. Chip temperature may be read on this Mac to estimate fan effort for Quiet Mode when a fan reading is unavailable. Starting a render saves a script you approve into AwakeFlow’s scripts folder on this Mac. It starts the render tool you chose and nothing else. Those choices, readings, and the script stay on your Mac and are not sent to developer-operated servers.
In version 1.5.0
Version 1.5.0 can show GitHub Actions. The token you connect is sent only to GitHub, at api.github.com, and AwakeFlow’s servers do not receive it. A render AwakeFlow starts can be limited to a share of the CPU. That limit stays on your Mac. AwakeFlow Pro is $4.99 a year, billed by Apple, with a free trial. A lifetime unlock bought before Pro is unchanged. Render progress and an app icon may be included in the sealed messages already sent to a linked device. The relay still cannot read those messages.
In version 1.6.0
Version 1.6.0 can also show GitLab pipelines, on gitlab.com or on a GitLab server you name. The token you connect is sent only to that server, and AwakeFlow’s servers do not receive it. A folder you pick so AwakeFlow can show local repository changes is read on this Mac. The screen saver and the time left it shows stay on this Mac. None of this is sent to developer-operated servers.
Permissions and system access
Depending on the features you use, AwakeFlow may request access to:
- Notifications — to show finish alerts and failure messages.
- Bluetooth — to list paired devices so you can finish a flow when a selected device disconnects. Device names and identifiers are read from macOS and used only for that feature.
- Files and folders you select — to watch folders, save downloads, or monitor output files in the locations you choose.
- Network — to download files from HTTP/HTTPS URLs you provide and to detect network connectivity changes.
- Power management (IOKit) — to keep the Mac awake and, when selected, request system sleep through Apple’s public power APIs.
Direct distribution edition only
If you use the direct (non–App Store) build, AwakeFlow may also request:
- Automation (Apple Events) — to lock or shut down your Mac when those finish actions are selected.
- Shell command execution — to run commands you explicitly configure in a “Run Command” wait step.
These capabilities are not included in the Mac App Store edition.
Data we do not collect
- No email-and-password account. Sign in with Apple is optional and used only to link your own devices.
- No crash or analytics reports are sent to the developer by default.
- No contact list, photos, microphone, camera, or location data is accessed.
Third-party services
When you use Download mode, AwakeFlow connects directly to the HTTP/HTTPS URLs you enter. Those servers are operated by third parties and are subject to their own policies. AwakeFlow does not proxy those requests through developer-operated servers.
The optional account uses Apple’s Sign in with Apple and Apple Push Notification service, which are
subject to Apple’s policies, and a developer-operated relay at
awakeflow-api-production.up.railway.app that only stores the account identifiers
listed above.
Distribution channels, such as the App Store, may collect information according to Apple’s own policies. That collection is outside AwakeFlow itself.
Children’s privacy
AwakeFlow is not directed at children under 13, and we do not knowingly collect personal information from children.
Changes to this policy
We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will reflect the latest revision. Continued use of AwakeFlow after changes means you accept the updated policy.
Contact
Questions about this Privacy Policy or AwakeFlow’s data practices:
- Email: support@awakeflow.app
- Support: awakeflow support page