Privacy

Privacy Policy

Last updated November 9, 2026

This policy covers the Armada app for macOS, the Armada iPhone app (“Armada: Agent Fleet” on the App Store), the Armada relay service, and this website, armadafleet.dev. “Armada”, “we” and “us” mean the developer of Armada.

The Mac app

Armada runs your coding agents and terminals locally. What it stores lives in its data folder on your Mac:

• Your project list, session names, layout and settings.
• Paired phones: a name, a key used to encrypt relay traffic, and a hashed access token.
• A random identifier and secret that your Mac uses to register with the relay.

Terminal output and agent conversations aren't sent to us. The agents themselves (Claude Code, Codex, OpenCode and anything you run in a shell) are third-party tools that use your own logins and talk to their providers under those providers' terms and privacy policies. Armada doesn't proxy or log that traffic. For Claude Code sessions, Armada passes its own settings file so it can receive hook events; your own configuration isn't changed.

When the app checks for updates, it downloads a release manifest and, if there's an update, the new version. Like any download, the server sees your IP address.

The iPhone app

• Pairing. The pairing QR code contains your Mac's addresses, its certificate fingerprint and a one-time secret. After pairing, the phone stores its access token and relay key in the iOS Keychain.
• Content. Sessions, prompts, chat, terminal output and diffs come straight from your Mac and are kept in memory while you use them. They aren't sent to us.
• Notifications. If you allow notifications, the phone gives your Mac its Apple push token. Your Mac sends alerts through the relay to Apple Push Notification service, which delivers them. Alert text is encrypted on your Mac and decrypted on your phone, so neither the relay nor Apple can read it. Live Activity updates can't be encrypted, so they carry only counts and generic wording (for example “1 needs you · 2 working”), never code, commands or project content.
• Camera. Used only to scan the pairing QR code. Images aren't stored or sent anywhere.

The relay

The relay lets your phone reach your Mac when they aren't on the same network. It stores, per Mac, a random identifier, a hash of that Mac's secret and the date it registered. Every frame between your phone and your Mac is sealed with AES-256-GCM using a key only those two devices share; the relay passes frames along and cannot decrypt them. To run the service, it keeps operational logs (timestamps, shortened Mac identifiers, push delivery results) and our web server keeps standard access logs (IP address, time, request and user agent). Logs are rotated and deleted after about 14 days.

This website

armadafleet.dev sets no cookies and runs no analytics. Our web server keeps the standard access logs described above. Fonts are loaded from Google Fonts, so Google receives your IP address and browser details when you visit (see Google's privacy policy).

Sharing

We don't sell, rent or share personal data. The only third party involved in normal operation is Apple, which delivers push notifications. We would disclose information only if required by law, and we hold very little to disclose.

Your choices

• Turn off phone access in the Mac app's Settings to stop the bridge and the relay connection.
• Remove a paired phone from Settings to revoke its access and stop its notifications.
• Delete the apps to remove everything they store locally. To have your Mac's relay registration deleted, email us and we'll help you find and remove it.

Children

Armada is a developer tool and isn't directed at children under 13. We don't knowingly collect data from them.

Changes

If we change this policy, we'll update the date above and, for meaningful changes, mention it in the app's release notes.