privacy

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.

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. The layout, and the commands to read it without ARMED, are on the format page.

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.

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, the local socket, and the engine's own log — which records the paths and filenames of the projects it watches, so that it can tell you what it did. It is written on your disk, read by nothing else, and sent nowhere. Delete the folder and you lose settings, not history.
2. ~/Library/LaunchAgentsOne macOS launch file, io.armed.daemon.plist. It is written automatically when you add your first project, so the engine is running the next time you log in — you do not have to switch anything on, and it starts nothing until you have given ARMED a project. Turning off start at login in Settings removes it, and so does deleting the file yourself. Uninstalling ARMED does not: delete it by hand, or the system keeps trying to start an engine that is no longer there.

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.

Settings has a Report a Problem control. It is the only part of ARMED that can move anything off this Mac, and it cannot do so on its own: it assembles a message and shows you the whole of it before there is anything to press. Copy puts that text on your clipboard. Send does the same and opens a draft in your own mail app, addressed to support, which sits there until you send it yourself. ARMED has no way to transmit it.

The message carries your ARMED version and build, your macOS version and processor, whether the engine is connected, how many projects it watches, any error on screen, and the end of the engine log — which names your project folders and file names. That is why it is shown to you in full first. Nothing is gathered that you are not looking at.

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.

ARMED is in a gated alpha, so the button reads request access rather than download. There is no form on this site, no database behind it and no form-handling service in front of it. The button is an ordinary mail link: it opens a draft in your own mail app, addressed to us, and nothing leaves your machine until you press send yourself. This site never sees it.

What we hold afterwards is the mail you chose to send, sitting in a mailbox — your address and whatever you wrote in it. It is used to send you a build and to answer you, and for nothing else: no list is sold, rented or shared, and there is no newsletter to be added to. Ask and it is deleted. It is the same address the Report a Problem control writes to, so one mailbox holds both and neither is joined to anything else.

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.

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