ARMED
ARMED · PRIVACY2026 · MACOS

privacy

ARMED collects nothing, because it has nothing to collect it with. There is no account to make, no analytics library linked into the app, and no code anywhere in it that opens an outbound connection. What follows is the mechanism, so you can check it rather than believe it.

what ARMED does not do
  1. no accountNothing to sign up for, sign in to, or activate. There is no licence key, no subscription and no purchase path in the app — choosing a folder is the whole setup.
  2. no telemetry, no analyticsNo usage reporting, no crash reporting, no product analytics. The app and the daemon link no analytics or error-reporting library of any kind.
  3. no outbound connectionsThe daemon has no HTTP client. Its git engine is built with network transports switched off, so it cannot reach a remote even by accident. The only socket ARMED opens is a file socket on your own machine, which is how the app and the daemon talk to each other; it never leaves the disk.
  4. no cloudNothing is uploaded, mirrored or backed up anywhere by ARMED. It works with the network off, permanently. If optional sync is ever built it will be exactly that — optional, and announced.
where your work is written

Your history goes into your own project folder, in plain git format, beside the songs it describes. It is not a database and not a private container: any git tool will open it, today or in ten years, with or without ARMED installed. Deleting the app leaves every version exactly where it is.

ARMED records the .als project file. Your audio — samples, recordings, bounces — is left alone where it already sits and is never copied into the history.

what ARMED keeps outside your project folder

Two places, both on your own Mac, neither of them sent anywhere:

  1. ~/.armedARMED's own settings: which folders you asked it to watch, the list of projects it found when it scanned, a cache it uses to work out what changed between saves, and the local socket. Delete the folder and you lose settings, not history.
  2. ~/Library/LaunchAgentsOne macOS launch file, written only if you switch on start at login, and removed when you switch it off.

The app also stores a single macOS preference of its own, used to remember that a project on disk has moved ahead of what Live has loaded. It holds no personal data and goes nowhere.

this website

Static pages on a CDN. No cookies, no analytics, no tag manager, no embedded third-party scripts, and no fonts fetched from anyone else at page load — every typeface is served from this site. Nothing here tracks you between pages or between visits. Your host's ordinary server logs are the only record that a page was served, and we do not read them for anything else.

check it yourself

Pull your Mac off the network and use ARMED normally — everything keeps working, because none of it needed the network. Point a connection monitor at the app and the daemon and watch nothing appear. Then open a project folder in any git client and read the history straight out of it. That is the whole point of keeping it in an open format: none of this has to be taken on trust.

questions

The support address is on the guide. A human answers.