Trial environments run code that people wrote. That is the product. It also means the platform can be used for things it should not be, and that both of those facts need a process attached.
Reporting abuse
Email [email protected] with:
- The trial environment URL, or the build ID
- What was observed
- Anything that lets us act without asking you further questions
Environment URLs are the single most useful piece of information you can give us. With it we can identify the tenant, suspend the environment, and preserve the relevant logs, usually within minutes. Without it we are asking you to describe a system you do not have access to.
What we do on receipt:
- We identify the tenant and suspend the environment. This does not wait for a full investigation — a suspended environment costs the tenant nothing if the report was mistaken.
- We preserve the build logs, the environment’s outbound requests, and the container’s filesystem snapshot.
- We notify the tenant that the environment has been suspended and why, unless doing so would compromise an ongoing investigation.
- We investigate, and then either restore the environment or terminate the account.
Response time: we acknowledge within one business day, and we suspend within four hours for reports that name an environment URL.
What we need to keep doing our job: logs. We keep outbound request records for trial environments for 90 days, which is longer than the default build-log retention, precisely so that abuse reports can be investigated after the fact. If you operate a tenant, you can shorten this, and if you do, we will tell you that it reduces our ability to act on abuse reports.
Copyright complaints
Material hosted in a trial environment, or contained in a build artifact, may infringe copyright. We take these seriously and we act on them.
Send a notice to [email protected] that includes all of the following:
- Your physical or electronic signature.
- Identification of the copyrighted work you claim has been infringed.
- Identification of the infringing material, with enough detail for us to locate it — the trial environment URL or the build ID.
- Your name, address, telephone number, and email address.
- A statement that you have a good-faith belief the use is not authorised by the copyright owner, its agent, or the law.
- A statement, under penalty of perjury, that the information in the notice is accurate and that you are authorised to act on the owner’s behalf.
What we do:
- We review the notice for completeness. If it is missing any of the six elements, we tell you which one and what is needed. We do not ignore an incomplete notice; we tell you what to fix.
- We identify the material and, where the complaint is credible, remove or disable access to it promptly. We do not wait for the full process.
- We notify the party responsible for the material, forwarding the notice.
- We inform you of the outcome.
- Where the accused party submits a counter-notice, we forward it to you, and we restore the material only if you do not file a court action within the statutory window.
Response time: we acknowledge within two business days. Where the notice identifies a specific environment URL and the claim appears credible, we act on the material within 24 hours.
Designated agent: [email protected].
Misrepresentation
We will not process a notice that we have good reason to believe is false, particularly one that targets a tenant in order to get it suspended or to divert traffic. A pattern of notices that appear commercially motivated is reviewed before action is taken.
If a notice is rejected, we explain why and what would need to change. We will not simply ignore it.
What we do not do
We do not adjudicate disputes between the complainant and the accused. We remove material on a credible complaint, and we restore it on a compliant counter-notice. We do not decide who owns the copyright — that is for a court, and the process is designed to get it there quickly.
Reporting a security issue
Security vulnerabilities are a different process with a different address: [email protected]. See Security for the disclosure policy and the safe-harbour terms.