privacy
Your projects never leave your Mac. The engine that records your versions has no network code at all. The app talks to one site, armed-site.pages.dev: it checks for updates, sends crash reports, and sends the reports you choose to send. Everything that goes is listed below, field by field, so you can check it rather than believe it.
- 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.
- no project uploadYour sets, your samples and your history are never uploaded. There is no sync, no backup service and no cloud copy. If optional sync is ever built it will be exactly that: optional, and announced.
- no network code in the engineThe daemon that watches your folders 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 it opens is a file socket on your own disk, which is how the app talks to it.
- no third-party trackingNo analytics, advertising or crash-reporting library from anyone else is linked into the app. What it sends goes to this site and nowhere else.
Four things, all to armed-site.pages.dev over HTTPS. Nothing else in ARMED opens a connection.
- the update checkOnce a day, and whenever you press Check in Settings, the app asks this site whether a newer ARMED exists. It uses Sparkle, the standard updater for Mac apps. When there is one, Sparkle shows you what changed and installs it only when you say so, unless you have ticked its box to install updates automatically. The check runs whether or not sharing is on, because an app that cannot be updated is the bigger risk to your work.
- usage counts, with the checkUnless you switch sharing off, the check carries eight values in its address. They are listed in the next section. They are numbers and versions only: no names, no paths and nothing about your music.
- crash reportsWhen ARMED or its engine crashes, macOS writes a crash report on your Mac. The next time the app starts, it sends the new ones to this site, up to five at a time, together with its version and install number. The very first time the app runs it sends none, only reports written after that. Each one goes whole, exactly as macOS wrote it, cut short only if it runs past 120 KB. It records where in the code the crash happened, your Mac model, your macOS version and how long ARMED had been running. It also carries what macOS stamps on every crash report: its own crash reporter key for your Mac, IDs for the current boot session and the last sleep and wake, your numeric user ID, when ARMED started and when it crashed, the process that started it, Apple's experiment and rollout IDs for your Mac, whether System Integrity Protection, Developer Mode and Apple Intelligence are on, and file paths that include your macOS account name. Crash reports follow the same switch as the usage counts.
- reports you sendReport a Problem, in Settings, sends nothing on its own. You write what happened, add an email address if you want a reply, and see the whole report, which you can edit, before you press Send. It 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's log, which names your project folders and files. Send posts it to this site, with your install number while sharing is on. If the site cannot be reached, Send opens a draft in your own mail app instead, and nothing moves until you send that draft yourself.
- install number
idis a random number the app makes the first time it runs and keeps as a macOS preference. Nothing about you or your Mac goes into it. It lets the site tell one install from another, so it can count how many come back. - version
vandbare the ARMED version and build, such as 0.3.0 and 300. - system
osis your macOS version, such as 14.6.1.archsays whether the app runs on Apple Silicon, on Intel, or on Apple Silicon through Rosetta. - counts
m,sandrare how many merges, variation switches and restores you made in the app since the last check that reached the site. Actions taken with the command-line tool are not counted.
The download sits behind a short form on the access page. It asks what computer you use, your macOS version, your DAW and, if it is not Live, its name, your Live version, roughly how many projects you have, how you keep versions now, and, only if you choose, an email address. The site keeps those answers, the time, and the outcome: the download, the waiting list, or not supported yet.
If the outcome is the download, your browser also notes that in its own storage, so coming back to the access page shows the download again instead of the form. The note holds the file's name, version and size, never your answers, and it is never sent anywhere. Clearing this site's data in your browser removes it.
Your IP address is not stored with your answers, or with a report. The site keeps a keyed hash of it that changes every day. Without the site's secret key it cannot be turned back into the address, and it is used only for daily rate limits, to stop one person or a bot from flooding the list or the reports. An email, if you give one, is used to tell you when a place opens or when something big changes, and for nothing else. It is never sold, rented or shared, and there is no newsletter.
- the developerRandev Ranjit decides what is collected and is the only person who reads it, on a password-protected page of this site.
- cloudflareHosts this site and the database it writes to. The database was created in Cloudflare's EU jurisdiction, so it is stored and processed inside the European Union. Like any host, Cloudflare sees your IP address while it serves a request.
- resendSends the developer at most one email a day, saying how many signups, reports and new installs arrived, with a link to that page. It receives the counts and the link, never your answers, your email address or a report.
- gmailThe support address is a Gmail mailbox. A mail you send to it, including a report's fallback draft, is held there.
- usage countsOne row per install per day. Rows are deleted once they are twelve months old.
- answers and reportsKept until you ask for them to be deleted.
Open Settings in ARMED and go to Updates. Share usage and crash reports is on when you install. Switch it off and the daily check goes out without any of the eight values, and no crash report is sent. The request itself still names ARMED and its version in its User-Agent header, as every Sparkle check does; this site does not keep it. Updates keep working. A report you send with Send still goes, because you chose to send it. A report you send then carries no install number.
Write to randevpratap+armed@gmail.com and say what you want deleted. For your form answers and reports, give the email address you used, or, if you left it blank, the day you filled in the form or sent the report and your time zone, plus something that identifies which one was yours — the answers you gave, or the first line of your report. For usage counts and crash reports, give your install number. The app does not show it; in Terminal, defaults read io.armed.app installID prints it. Everything that matches what you described is deleted, and you get a reply when it is done; if nothing does, or more than one entry could be yours, that reply asks which before anything is removed.
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:
- ~/.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 read by nothing else, except that the end of the log goes into a problem report when you send one. Delete the folder and you lose settings, not history.
- Login ItemsARMED adds itself to your Login Items when you add your first project, so it opens, and starts its engine, the next time you log in. You do not have to switch anything on, and it opens nothing until you have given ARMED a project. Turn it off with Start at login in Settings, or in System Settings > General > Login Items. An ARMED older than 0.3.0 kept a launch file,
io.armed.daemon.plist, in ~/Library/LaunchAgents instead; this version replaces it with the Login Items entry the first time it runs.
The app also keeps a few macOS preferences of its own: whether a project on disk has moved ahead of what Live has loaded, the install number, whether sharing is on, the counts waiting for the next check, the time of the last crash report it sent, and Sparkle's record of when it last checked. None of them holds your music or your name.
Pages on a CDN. No cookies, no tag manager, and no fonts fetched from anyone else at page load: every typeface is served from this site. The one script from anyone else is Cloudflare Web Analytics, which counts page views: the page, the site that linked you here, your browser and type of device, your country and how fast the page loaded. It sets no cookie, stores nothing on your device and gives you no identifier, so nothing here tracks you between pages or between visits. Apart from those counts, the access form, the update check and the address reports are sent to are the only parts of the site that write anything down, and they keep exactly what this page lists.
Point a connection monitor at ARMED. The engine opens no connection at all, and the app connects to armed-site.pages.dev and to nothing else. Then open a project folder in any git client and read the history straight out of it. That is the 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.