On your Mac
The afk hub runs on your Mac and keeps everything in ~/.afk: thread history, settings, the keys of the phones you paired (stored hashed), and logs. Nothing in it is sent to us; there is no "us" server to send it to.
Between your Mac and your phone
The app talks to your Mac directly, either over your local Wi-Fi or through Tailscale. Over Tailscale the connection is HTTPS and only reachable from your own devices. On Wi-Fi it's plain HTTP on your local network, protected by your phone's key.
Push notifications
Notifications are the one thing that leaves your devices through third parties. The hub sends them through Expo's push service, which delivers them via Google Firebase Cloud Messaging (Android) or Apple (iPhone). Each notification contains the project name, the thread title and a short snippet (up to about 180 characters) of the agent's message or question. You can turn notification types off in the app's settings.
The app
The app has no analytics and no ads. It stores the Macs you paired and your preferences on the phone. App updates are downloaded from Expo.
Launch emails
If you ask to be told when afk is on the App Store or Google Play, we store your email address, the phones you picked and your country (from Cloudflare) in Cloudflare's storage, only to send that one announcement. We don't share it or use it for anything else. Ask on GitHub and we'll delete it.
This website
goafk.dev sets no cookies and loads no third-party fonts or ad trackers. It's served by Cloudflare, which processes standard request data (like IP addresses) to deliver it. We count visits with Umami, a privacy-friendly analytics tool we host ourselves: it uses no cookies, stores no personal data or IP addresses, and only shows us aggregate numbers like page views, referrers and countries.
Questions
Open an issue on GitHub.
Last updated 5 October 2026.