Data Processing Agreement
The terms under which we process personal data on your behalf. This is the document your data protection officer will ask for, and it is written to be read by one.
1When this applies, and who is who
This Data Processing Agreement applies when you use MacBuildCloud to process personal data that is subject to the EU or UK General Data Protection Regulation, or to a data protection law with equivalent requirements. It forms part of our Terms of Service and takes effect automatically when you create an account. You do not need to sign a separate copy, though we will sign one if your procurement process requires it — write to legal@macbuildcloud.com.
You are the controller. You decide what personal data reaches our service and why. We are the processor. We act on your instructions and do not decide the purposes of the processing.
There is one exception, and we would rather state it plainly than bury it: for your own account data — the name, email address and billing details of the people who administer your MacBuildCloud account — we are a controller in our own right, because we decide to collect that data in order to run and bill the service. That processing is described in our Privacy Policy, not here. This agreement covers the personal data that flows through the build service.
2What we process, and why
| Subject matter | Providing a managed macOS and iOS build service. |
| Duration | For as long as your account is open, plus the retention periods in section 8. |
| Nature and purpose | Receiving your source code, compiling, code-signing and packaging it on Apple hardware, returning the resulting artifacts, and keeping the logs needed to show what happened. |
| Types of personal data | Whatever your repository, environment variables, test fixtures or build logs happen to contain. Commonly: author names and email addresses in commit metadata; names in code comments; occasionally test data. We do not ask for or expect any of it. |
| Categories of data subject | Your developers and contributors; any individuals whose data appears in your repository or test fixtures. |
| Special category data | Not expected. The service is not designed for it. If your repository contains special category data or criminal offence data, tell us before you start, because it changes what we both have to do. |
The honest summary is that we are a compiler with a bill attached. We do not analyse the content of what you send us, we do not build profiles from it, and we do not use it to train anything.
3Our obligations
We will:
- process personal data only on your documented instructions — your use of the service, this agreement and the Terms of Service are those instructions — unless a law we are subject to requires otherwise, in which case we will tell you before processing unless that law forbids it;
- make sure the people who can access the data are bound by confidentiality and have been told what that means in practice;
- apply the security measures in section 5, and not weaken them during the term;
- not engage a sub-processor except as described in section 6;
- help you respond to data subject requests, as described in section 7;
- help you with security, breach notification and data protection impact assessments, taking into account what we know and what you know;
- delete or return personal data at the end, as described in section 8;
- give you the information you need to show that we are meeting these obligations, and allow audits as described in section 9.
If we think an instruction from you breaches data protection law, we will say so rather than quietly comply.
4Your obligations
You are responsible for having a lawful basis for the personal data you send us, for telling the people concerned what is happening to it, and for not sending us data you have no right to send. In practice this rarely bites: most repositories contain little more than commit metadata. But if you are about to run builds over a database dump of real customers, that is your decision to justify, not ours.
Please do not put personal data into repository names, build names or support tickets, where it ends up in places designed for debugging rather than for privacy.
5Security
The measures below are the ones we actually run. A fuller description, including what we have deliberately not done yet, is on our security page.
- Isolation. Every build runs in a fresh macOS virtual machine created for that build and destroyed when it ends. Virtual machines are not reused between builds or between customers. At most two virtual machines run on any physical Mac; we do not oversubscribe.
- Source code retention. Your source is present only for the duration of the build and is destroyed with the virtual machine. We do not keep a copy.
- Encryption. TLS 1.2 or better for everything in transit, with HSTS. Disk encryption at rest on the machines that hold artifacts and account data.
- Secrets. Signing certificates and environment secrets are encrypted at rest, injected into the build virtual machine at run time, and never written to build logs.
- Access control. Administrative access requires two-factor authentication. Access to production is limited to people who need it, and is logged.
- Monitoring. Infrastructure is monitored continuously from a second site, so that a failure of the primary site does not also silence the alerting.
- Backups. Account and billing data is backed up daily, with integrity checks, and restores are rehearsed rather than assumed.
We will not describe a control here that we have not implemented. If we add something material we will update this list.
6Sub-processors
You give us general authorisation to use sub-processors. The current list:
| Sub-processor | What it does | Where |
|---|---|---|
| Alibaba Cloud | Hosting for the web application, database and account data | Hong Kong SAR |
| Stripe | Payment processing and billing records | Ireland and United States |
| Resend | Transactional email we send you | United States |
| ImprovMX Inc. | Forwarding email sent to our published addresses | United States |
| Google (Gmail) | The mailbox where that email is read and answered | United States |
We will give you 30 days notice by email before adding or replacing a sub-processor. If you object on reasonable data protection grounds within that period, write to us; if we cannot resolve it, you may terminate the affected subscription and we will refund the unused portion of the period you paid for.
Each sub-processor is under a written contract with data protection obligations no less protective than these. We remain responsible to you for what they do.
The build machines and dedicated Macs are in our own premises in Hong Kong. No third-party data centre operator has access to them. (Version 1.2 listed an unnamed data centre operator; there is none. It also gave ImprovMX's location as the European Union; ImprovMX Inc. is in the United States.)
7Data subject requests
If someone asks you to give them a copy of their data, correct it, delete it, or restrict what you do with it, and answering that request needs data held in our service, we will help you. You can disconnect repositories and revoke tokens and secrets yourself. Deleting artifacts before they expire, or closing an account, we do for you on request, within 30 days.
If a data subject contacts us directly about data we hold on your behalf, we will not answer them ourselves. We will tell them to contact you, and tell you that they tried, unless the law requires otherwise.
8Deletion and return
| What | How long we keep it |
|---|---|
| Your source code | Only during the build. Destroyed with the virtual machine. |
| Build artifacts | 30 days by default, or fewer if the customer sets a shorter period; sooner on request. |
| Build logs | 30 days, or fewer if the customer sets a shorter period. |
| Account data | Until you close the account, then 30 days, then deleted. |
| Billing records | 7 years. We are required to keep these and cannot delete them on request. |
| Backups | Overwritten on their own cycle; deleted data disappears from backups within 90 days. |
On termination you may export your artifacts for 30 days. After that we delete personal data processed on your behalf, except the billing records above and anything a law requires us to keep, which we will keep isolated and stop using.
9Audit
You may ask us, once in any twelve months, for the information you reasonably need to verify that we are meeting this agreement. We will answer in writing within 30 days.
If a written answer is genuinely not enough — for example because your own regulator has told you so — we will accommodate an audit by you or an independent auditor you appoint, at a mutually agreed time, under confidentiality, and in a way that does not compromise other customers' data. You bear the cost unless the audit finds a material breach by us, in which case we do.
We do not currently hold a SOC 2 or ISO 27001 certificate. We are not going to imply that we do. When we obtain one we will publish it here and it will answer most audit requests without either of us spending a day on it.
10Personal data breach
If we become aware of a personal data breach affecting data we process for you, we will tell you without undue delay and in any event within 48 hours, using the contact address on your account. We will tell you what we know, what we do not yet know, what we are doing, and what we suggest you do. We will keep telling you as we learn more rather than waiting until we have a complete picture.
We will not ask you to keep a breach confidential, and we will not delay telling you in order to prepare a statement.
11International transfers
Our service runs in Hong Kong SAR. Hong Kong has not been the subject of an adequacy decision by the European Commission or the UK government. So if you are in the EEA or the UK, sending personal data to us is a restricted international transfer.
For those transfers, the European Commission's Standard Contractual Clauses (Decision 2021/914), Module Two (controller to processor), are incorporated into this agreement and take precedence over it if they conflict. For UK transfers, the UK Addendum issued by the Information Commissioner's Office applies to those clauses. Where those clauses need details filled in: you are the data exporter, we are the data importer, the description of processing is in section 2, the security measures are in section 5, the sub-processors are in section 6, and clause 17 selects the law of Ireland.
We have carried out a transfer impact assessment and will give you a copy on request. The short version: our exposure is limited by the fact that we hold almost no personal data — source code is destroyed with the build virtual machine, and what remains is account and billing data. If we receive a government request for customer data we will challenge it where there are lawful grounds to do so, and tell you unless we are legally prohibited from telling you.
12Liability and precedence
Each party's liability under this agreement is subject to the limitations in the Terms of Service. Nothing in those limitations affects a data subject's rights, or any liability that cannot be limited by law.
If this agreement conflicts with the Terms of Service on a data protection question, this agreement wins. If the Standard Contractual Clauses conflict with either, the Clauses win.