Security at MacBuildCloud
You are handing a stranger your source code and your signing certificates. This page says exactly what we do with them, what we deliberately do not do, and what we have not built yet.
01What happens to your code
- Every build gets a fresh machineYour build runs in a macOS virtual machine created from a clean image. Nothing from another customer's build is present, because the machine did not exist a moment earlier.
- The machine is destroyed when the build endsWe delete the virtual machine and its disk. We keep your build artifacts and logs — because you asked for them — but not a working copy of your source tree.
- Artifacts expireBuild outputs and build logs are deleted 30 days after the build, and you can set a shorter window for your account. Download links you share expire after 24 hours, or sooner if you shorten that too.
- No one here reads your repositoriesOur staff cannot open a running build or browse your source. When you ask for support, you decide what to share with us.
02Secrets and signing certificates
- Encrypted at restCertificates, provisioning profiles, App Store Connect keys and environment variables are encrypted before they are stored.
- Masked in logsValues you mark as secret are redacted from build output. If a secret is printed by accident, it does not survive into the log we keep.
- Injected only when namedA build receives only the secrets its build configuration names, and only inside that build’s virtual machine for the life of the build. Secrets belong to your account, so any of your repositories can name them — keep repositories you don’t trust in a separate account.
- Scoped API tokensTokens carry one of three permission levels — read, trigger, or admin — and an expiry date. We store a one-way hash, so a token is shown to you exactly once and never again.
03Where your data lives
Builds run on Apple hardware we own, operated from Hong Kong. Build artifacts and account data are stored in the same place. We do not move customer data to another jurisdiction to process it.
A short list of third parties necessarily sees some data — a payment processor sees your billing details, an email provider sees your address. Every one of them is named in our Privacy & Cookie Policy, and the list changes only with notice.
04What we deliberately do not run
We also run at most two virtual machines per physical Mac. Our reading of Apple's licence for the build service is on the software licensing page. We do not oversubscribe. A dedicated Mac mini has one customer on it and nobody else. On the shared build cloud, another customer's build may run in the other virtual machine on the same Mac; each build gets its own virtual machine, destroyed when the build ends.
05Your account
- Two-factor authenticationA code from any standard authenticator app, required on every sign-in — including sign-in with GitHub. Ten single-use recovery codes are issued when you turn it on.
- New device alertsWe email you whenever your account is used from a device we have not seen before.
- Passwords are never storedWe keep a scrypt hash. We cannot read your password, and neither can anyone who steals the database.
- Sign-in with GitHub reads almost nothingWe ask GitHub for your username and verified email address, and nothing else. We do not request access to your repositories at sign-in.
06Continuity
Account and billing data is backed up daily on our server. Every day a copy is also pulled off-site to a computer the company owns, outside our hosting provider, where it is stored encrypted. Each backup is checked when it is written (the database opens and holds data, and stored credentials still decrypt with the backed-up key) and checked again after it is copied. Once a month we restore the latest backup into a scratch area and run the same checks — an actual restore, not a file listing — on a schedule rather than after an incident. Build artifacts are not in these backups, so a total loss of our server would lose the artifacts stored on it.
The Mac minis do not use FileVault disk encryption, because they must be able to restart without someone typing a password at the machine. Build artifacts and your saved credentials are encrypted separately, but files you leave on a dedicated Mac are not. Do not rely on us for the encryption of files on a dedicated machine.
Compute nodes are treated as disposable. The ledger is not.
07Reporting a vulnerability
Email security@macbuildcloud.com. Tell us what you found and how to reproduce it. We will acknowledge within two business days and keep you updated until it is closed.
We will not pursue legal action against anyone who reports a genuine issue in good faith, does not access or modify other customers' data, and gives us reasonable time to fix it before publishing.
08What we have not done yet
Trust pages usually stop at the previous section. Here is the honest remainder, because you can check most of it yourself and would rather hear it from us:
| Item | Status |
|---|---|
| SOC 2 Type II | Not started. It is planned once revenue supports the audit cost. We will not imply otherwise in the meantime. |
| Third-party penetration test | Planned before we operate at data-centre scale. The report will be available to business customers under NDA. |
| Published uptime SLA | Published — see the Service Level Agreement. Dedicated machines get a hardware-replacement commitment rather than an uptime figure, because a single Mac mini has no redundant parts. |
| Public status page | Live at /status. It currently runs on the same infrastructure as the service, so a full outage can take it down too; moving it to an independent host is planned. |
Questions about anything on this page: security@macbuildcloud.com.
09No device management on your Mac
A dedicated Mac mini we hand you is not enrolled in any mobile device
management system, and we do not install configuration profiles on it.
We checked this on every machine in the fleet, most recently on 4 November 2026:
profiles status reports MDM enrollment: No and
Enrolled via DEP: No.
What that means in practice: nothing pushes settings or software to your machine, and nothing can wipe it from a console. Please do not enrol it in your own device management service either, or turn on Find My for it: either one ties the hardware to you after your lease ends, and section 2.8 of the Acceptable Use Policy asks you not to.
One honest detail, because it looks alarming if you go looking: every Mac runs
Apple's own mdmclient process whether or not it is enrolled
anywhere. Seeing it running does not mean the machine is managed. Enrolment
status is what matters, and ours is none.
What we can do is what you would expect of a landlord: we hold an administrator account used to create and remove your tenant account, to restart the machine when you ask, and to reclaim it when the lease ends. That account is not used to look at your files, and the machine leaves our build cluster for the whole time it is yours.