Privacy & Cookie Policy
This policy describes what MacBuildCloud collects, why, where it is kept, who else sees it, and what you can ask us to do about it. It reflects what the service does today, not what we plan to build.
1Who is responsible
HONGKONG HDTP SOFTWARE LIMITED, a company incorporated in Hong Kong SAR, of Flat/Rm 1911, Lee Garden One, 33 Hysan Avenue, Causeway Bay, Hong Kong, is the data controller. Write to privacy@macbuildcloud.com about anything on this page.
2What we collect
| Data | Where it comes from | Why |
|---|---|---|
| Email address | You, or your verified GitHub address | To identify your account and send service messages |
| Password | You, if you set one | Stored only as a scrypt hash. We cannot read it. |
| GitHub username and numeric ID | GitHub, if you sign in with it | To link the sign-in to your account. We do not request repository access at sign-in. |
| Two-factor secret and recovery codes | Generated by us | To verify sign-in. Recovery codes are stored only as hashes. |
| API tokens | Generated by us | Stored as a hash plus a short non-secret prefix, so you can tell tokens apart. |
| Sign-in records: time, IP address, browser string | Your browser | To show you your own sign-in history and to alert you to a new device |
| Server access logs | Your browser | Operating and securing the service |
| Build inputs, artifacts and logs | You | To run the build you asked for and return the result |
How you found us: a channel tag from the link you followed (for example ?src=newsletter) and the hostname of the site that linked to us | Your browser, when you open the sign-up page | To learn which channels bring people to us. We keep the hostname only, never the page address, and we do not use it to follow you across pages or sites. |
| Waitlist request: how long you want a machine for, how many, your country, and any note you add | You, if you join the waitlist for a dedicated machine | To email you when a machine is free and to plan how many machines to add |
We do not collect payment card numbers. Card details go directly to our payment processor, Stripe. We see only the card brand, the last four digits, the country that issued it, a fingerprint Stripe gives us to recognise the same card again, and the outcome.
We do not buy personal data, we do not sell it, and we run no advertising or analytics trackers.
3Why we are allowed to (legal bases)
- Performing our contract with you — running builds, managing your account, billing.
- Our legitimate interests — keeping the service secure, detecting abuse, and preventing account takeover. We limit this to what is necessary; the device fingerprint used for new-device alerts, for example, is a keyed hash of a coarse network range and browser string, not a stored profile of you.
- Legal obligation — accounting records, sanctions screening.
- Consent — we do not currently send marketing email. If we ever do, it will be opt-in and separately unsubscribable.
4Where it is kept
Account data, build artifacts and logs are stored on infrastructure in Hong Kong SAR. Backups are encrypted in transit and an off-site copy is held in mainland China on hardware we own. We do not move customer data elsewhere to process it.
If you are in the European Economic Area or the United Kingdom, note that Hong Kong is not the subject of an adequacy decision. Transfers therefore rely on appropriate safeguards; contact us for the current arrangement and we will provide it.
5How long we keep it
| Data | Retention |
|---|---|
| Account record | Until you ask us to close the account (email support@macbuildcloud.com from the address on it), then removed within 30 days |
| Build artifacts and logs | 30 days by default, or fewer if you set a shorter period in your account; then deleted automatically. Ask us and we will delete them sooner still |
| Your source tree | Destroyed with the virtual machine when the build ends |
| Sign-in records | 12 months |
| How you found us, and waitlist requests | Kept with the account record and removed with it |
| Server access logs | 14 days |
| Backups | 14 daily and 8 weekly copies, so deleted data may persist in a backup for up to about two months |
| Invoices and accounting records | 7 years, as required by Hong Kong law |
6Who else sees it (sub-processors)
These are the third parties involved today. We update this list before adding anyone new.
| Provider | Purpose | Location | Status |
|---|---|---|---|
| Alibaba Cloud | Hosting the website and account database | Hong Kong SAR | In use |
| GitHub, Inc. | Sign-in with GitHub, if you choose it | United States | In use |
| Google (Gmail) | The mailbox where email you send to our published addresses (support@, billing@ and so on) is read and answered | United States | In use |
| ImprovMX Inc. | Forwarding email you send to our published addresses to that mailbox | United States | In use |
| Let's Encrypt (ISRG) | TLS certificates | United States | In use |
| Resend | Sending account and alert emails | United States | In use since 7 Sep 2026 |
| Stripe | Card payments, invoicing and fraud checks. Card numbers go to Stripe directly and never reach our servers. | United States, with an Irish entity for EEA customers | In use |
| Bark (api.day.app) | Push notifications for our own operational alerts. These carry internal identifiers such as a lease or machine number — never your name, email, files or build output. | China | In use for operations only |
7Cookies and third-party requests
7.1 Cookies we set
One: a session cookie, set when you open the sign-in or sign-up page and kept while you are signed in. It is HttpOnly, Secure and SameSite=Lax, lasts 14 days, and carries your session and the token that protects forms against cross-site request forgery. It is strictly necessary, so we do not ask for consent to set it. If the link that brought you to the sign-up page carried a channel tag, the tag and the referring hostname are held in that same cookie until your account is created.
We set no analytics, advertising or tracking cookies, and we show no cookie banner because there is nothing to consent to.
7.2 No third-party requests
Our pages load their typefaces, styles and scripts from our own server. Viewing them makes no request to Google or to any other third party. (Earlier versions of this policy said the typefaces came from Google Fonts; they no longer do.) The one exception is when you choose to pay: checkout and the billing portal are pages on Stripe's own site. A small script of our own carries a channel tag along links within our site; it stores nothing on your device and sends nothing to anyone else.
8Your rights
Subject to local law — including the EU/UK GDPR and the Hong Kong Personal Data (Privacy) Ordinance — you may ask us to:
- give you a copy of the personal data we hold about you;
- correct data that is wrong;
- delete your data (we will explain if a legal obligation prevents it);
- restrict or object to particular processing;
- provide your data in a portable format.
Write to privacy@macbuildcloud.com. We respond within 30 days and we do not charge for a reasonable request.
You may also complain to your data protection authority. In Hong Kong that is the Office of the Privacy Commissioner for Personal Data.
9Security
What we do to protect this data — encryption of secrets at rest, destruction of build machines, staff access limits, backup and restore testing — is described in detail on our Security page, including what we have not built yet.
If a breach affects your personal data and is likely to result in a risk to you, we will notify you and the relevant authority within the time the law requires, and we will tell you what actually happened rather than what is comfortable.
10Children
The Service is not for anyone under 18 and we do not knowingly collect their data. If you believe a minor has registered, tell us and we will remove the account.
11Changes
We will post any change here with a new version number and date. For material changes we will email account holders at least 30 days in advance.
Version 1.5, 12 November 2026. We now record how a new account found us (a channel tag and the referring hostname) and waitlist requests for dedicated machines. Corrected two statements: the session cookie is set on the sign-in and sign-up pages, not only after sign-in; and card payments are live, handled by Stripe.
HONGKONG HDTP SOFTWARE LIMITED · privacy@macbuildcloud.com · English is the authoritative language.