Privacy

Walkie collects no data. There is no account, no analytics, no advertising and no server of ours in the path between your phone and your Mac.

What the app does with your data

The iPhone app talks only to the Mac you paired it with, over your own network (Tailscale or Wi-Fi), authenticated with a key the bridge generated on your Mac. The key is stored in the iPhone's Keychain.
Conversations, files and settings stay on your Mac, where your CLIs keep them. The app holds a copy of what's on screen and your unsent messages, on the phone, so it can show them offline.
Photos and files you attach are sent to your Mac and saved there (~/.walkie/uploads) so your agent can read them. They go nowhere else.
The built-in demo uses sample data bundled in the app and makes no network requests.

What the Mac bridge does

It runs the CLIs you installed (Claude Code, Codex, Antigravity, Grok) on your own sign-ins. What those tools send to their providers is governed by those providers' terms, exactly as when you use them in a terminal.
It reads the CLIs' own session records to list and show conversations, and reads each plan's usage meter. It writes names and archive flags back to those records when you rename or archive in Walkie.
It removes API-key environment variables before starting a CLI, so nothing runs on a metered key by accident.
Push notifications are sent only by a bridge that holds an Apple Push Notification key for the app. The public bridge has none, so the app does not ask for notification permission unless the bridge reports it can send.

Purchases

The optional purchase is handled by Apple through StoreKit. We never see your payment details. The purchase state is stored on your device and in your Apple Account.

Third parties

None. No SDKs other than Apple's. The source of both the app and the bridge is public at github.com/pauljump/walkie.

Contact

github.com/pauljump/walkie/issues

Last updated October 11, 2026.