Vulnerability Disclosure Policy
How to tell us about a security problem, and what we promise in return. The first section is the one that matters: report in good faith and we will not come after you.
1The promise
If you find a security problem in MacBuildCloud and report it to us in good faith under this policy, we will not sue you, we will not report you to law enforcement, and we will not complain to your employer. We will thank you, fix the problem, and credit you if you want to be credited.
We put this first because it is the part that matters. A researcher who is unsure whether reporting will get them in trouble usually stays quiet — and a vulnerability nobody told us about is worth less to us than one someone did.
2How to report
Email security@macbuildcloud.com. Include enough for us to reproduce it: what you did, what happened, what you expected, and any proof-of-concept. Screenshots and request or response captures help.
If the report is sensitive enough that you would rather encrypt it, say so in a first email with no details and we will arrange a channel.
| What | When |
|---|---|
| We acknowledge your report | Within 2 business days |
| We tell you our initial assessment | Within 7 days |
| We fix, or give you a dated plan | Within 90 days |
| We tell you it is fixed | Same day we deploy the fix |
If we are going to miss one of these, we will tell you before the deadline rather than after it.
3What is in scope
macbuildcloud.comand its subdomains- The MacBuildCloud web application and API
- The build execution environment, including isolation between builds and between customers
- Our published build images
Isolation findings are the ones we care about most. If you can see another customer's source, artifacts, secrets or metadata, tell us immediately and we will treat it as our highest severity.
4What is out of scope
- Anything requiring physical access to our hardware, or social engineering of our staff or suppliers
- Denial of service, volumetric or otherwise. Please do not test this — you will affect real builds, and we will learn nothing we did not already know
- Findings from automated scanners with no demonstrated impact
- Missing security headers, cookie flags or TLS configuration with no exploitable consequence
- Vulnerabilities in third-party software we run, unless you can show that our particular configuration makes it exploitable — report those upstream, and tell us so we can patch
- Reports about email configuration (SPF, DKIM, DMARC) unless you can demonstrate a working spoof that would deceive a recipient
- Anything you found by attacking a customer rather than us
5Rules we ask you to follow
- Use your own account and your own test data. Do not access, modify or download anyone else's data. If you accidentally do, stop, tell us, and delete what you have.
- Do not degrade the service for other customers.
- Do not use a finding to gain persistence, install anything, or move further into our systems than you need to demonstrate the issue.
- Give us a reasonable period to fix the problem before telling anyone else.
If you follow these rules, section 1 applies. If you go outside them — exfiltrate customer data, hold a finding to ransom, or attack our customers — it does not, and we will treat it as what it is.
6Disclosure
We support coordinated disclosure and we do not ask for indefinite silence. Our default is that you may publish 90 days after your report, or sooner once we have shipped the fix and told you, whichever comes first.
If we need longer we will ask, explain why, and give you a date. We will not use a request for more time as a way of never disclosing. If we cannot fix something within 90 days, that is worth knowing about and we will say so publicly ourselves.
Where a vulnerability affected customer data, we will tell the affected customers regardless of whether it is publicly disclosed.
7Recognition
We do not currently run a paid bug bounty. We are a small company and we would rather promise something we can keep than advertise a reward and then argue about severity ratings.
What we do offer: public credit on this page if you want it, a written acknowledgement you can show an employer, and a genuine answer about what we changed. If you find something serious, ask us about a bounty and we will have an honest conversation rather than pointing at a policy.
8Our own transparency
Where an incident affected customers, we publish what happened, when, why, and what we changed. We do this whether or not anyone would otherwise have found out. The same standard applies to problems we found ourselves.
Our security page includes a section on what we have deliberately not built yet. We would rather you learn our gaps from us than from an incident.