Acceptable Use Policy
This policy lists what you must not do with MacBuildCloud. It is short and specific on purpose: you should be able to tell, before you sign up, whether your workload is welcome here.
1What this service is for
MacBuildCloud exists to compile, test and package software, and to provide managed macOS development environments. If that is what you are doing, the rest of this page will not trouble you. Apple's licence allows a dedicated Mac to be leased only for developer services, so a dedicated machine must be used for software development, building and testing and the tools that support them.
2Prohibited workloads
You must not use the Service for any of the following, whether directly or by arranging for someone else to do it:
2.1 Cryptocurrency mining
Mining, minting, or any proof-of-work or proof-of-stake validation, and running blockchain nodes for profit. Compiling software that happens to relate to cryptocurrency is fine; using our CPUs to earn coins is not.
2.2 AI or machine learning training and inference
Training, fine-tuning, or serving machine learning models, and running inference workloads at scale. Building an application that calls someone else's AI API is fine. Using our hardware as the compute for the model itself is not.
2.3 Unlawful content and activity
Anything unlawful under Hong Kong law or the law where you are: material that sexually exploits children, content that infringes copyright or trademark, fraud, and the distribution of malware or credential-stealing software.
2.4 Attacking or probing other systems
Port scanning, vulnerability scanning, denial-of-service traffic, brute-force or credential-stuffing attacks, or penetration testing against systems you do not own — regardless of whether you believe you are authorised. Security research against your own targets is permitted; tell us first at security@macbuildcloud.com so we do not mistake it for an attack.
2.5 Unsolicited messaging
Sending spam, or operating infrastructure that supports it.
2.6 Reselling our capacity
Reselling, sublicensing or sharing your access with third parties as a compute service of your own. Building software for your clients is normal agency work and is fine. Selling them build minutes on our hardware is not. If you want to resell, talk to us — there may be a partner arrangement, but it must be agreed in writing.
2.7 Evading limits
Registering multiple accounts to multiply free allowances, sharing one account across a team to avoid seat fees, or circumventing rate limits, quotas or timeouts.
2.8 Locking a dedicated machine to your Apple Account
On a dedicated machine you may sign in with your Apple Account for Xcode, the App Store and other development work. You must not turn on Find My Mac, enrol the machine in a device management service or Apple Business Manager, or set a firmware or recovery password. Any of these ties the hardware to you after your lease ends, and we could not prepare it for the next customer.
We check for Find My on every dedicated machine. If we find it on, we will email you and ask you to turn it off in System Settings, or to remove the Mac at icloud.com/find. Please do so within 48 hours of our email, and before your lease ends.
3Fair use of shared capacity
- Every build has a maximum duration. A build that hangs is stopped, and you are not charged for the time after we stop it.
- Do not run a build whose purpose is to hold a machine rather than to produce an artifact.
- Storage is for build inputs and outputs, not general file hosting or backup.
4How we enforce this
Proportionately, and with an explanation.
| Situation | What we do |
|---|---|
| Probably accidental — a misconfigured job, an unfamiliar limit | We email you, explain what we saw, and ask you to change it. No penalty. |
| Repeated after notice | We rate-limit or suspend the affected workflows and set a deadline. |
| Deliberate and serious — mining, unlawful content, attacking others | Immediate suspension. Fees are not refunded. We may be obliged to report it. |
In every case we tell you the specific reason. We do not send unexplained lockout notices, and there is always a route to a human at legal@macbuildcloud.com, or by replying to our notice.
5How we detect problems
We monitor resource use and known mining and scanning process names, including on dedicated machines, where we read process names but not your files. Builds are also checked for connections to common mining ports. If we receive an abuse report about your machine, we investigate and may lock it. We do not read your source code to enforce this policy, and we do not need to.
6Reporting abuse
If you believe someone is using MacBuildCloud to harm you, write to abuse@macbuildcloud.com with the details and any evidence. We acknowledge reports within two business days.
7Changes
We will post any change here with a new version number and date. The policy that applies is the one in force when you use the Service.
Version 1.2, 6 November 2026. Section 1 says what Apple allows a dedicated Mac to be used for. Section 5 describes what we actually monitor.
Version 1.1, 3 November 2026. Added 2.8: do not lock a dedicated machine to your Apple Account with Find My, device management or a firmware password.
This policy forms part of our Terms of Service. English is the authoritative language.