Contact

Three addresses, each monitored for a different kind of message. Using the right one gets you a faster answer than any of them being a general inbox would.

What to expect

We aim to answer support email within one business day and to acknowledge security and abuse reports faster than that. These are intentions, not commitments. There is no contractual response time and no support SLA — see the Terms of Service. If a response time in writing matters to your organisation, say so in your first email and we will tell you honestly whether we can offer one rather than quietly hoping we hit it.

Support is email only. There is no phone line and no 24/7 rota, and we would rather say that plainly than route you to a chat widget nobody is behind. Reports that involve an active attack, a suspected compromise of an account, or content that has to come down immediately are the ones we pick up outside normal hours; put the word "urgent" in the subject and describe the impact in the first two lines so we can triage it without reading the whole thread.

You will get a better answer faster if you include:

• the request id from the response — every API response carries one in the X-Request-Id header and in the error body, and it takes us straight to your request in the logs;
• the sandbox id (sbx_…) or execution id (exec_…) involved;
• timestamps with a time zone;
• what you expected to happen and what happened instead.

Please do not send API keys, passwords or other secrets by email. If you think a key has been exposed, revoke it in the dashboard first, then tell us.

Before you write

Some questions have faster answers elsewhere:

• Status — whether the API and control plane are healthy right now, checked live rather than cached.
• Documentation and the API reference — endpoints, parameters, error codes.
• Limits — timeouts, concurrency, sizes and measured start-up times.
• Security — the isolation model and what we do and do not claim.
• Privacy — what we store, and how to delete it.

Other enquiries

Anything commercial — higher concurrency limits, sandbox sizes we do not list, questions about whether the service fits a compliance requirement, or an integration you would like to build on the API — goes to info@productivity-boost.com as well. We do not have a separate sales function, so those emails reach the people who build the service. If the honest answer is that we cannot do what you need today, that is the answer you will get; the security page already lists the certifications and guarantees we do not have.

Data protection requests

Access, export, correction and deletion requests go to info@productivity-boost.com from the email address on the account. Account deletion does not need us at all — it is self-service on the account page of the dashboard. The privacy policy explains exactly what deletion removes.

Operator details

Sandbox as a Service is operated by the company named below, which is established in Germany. These are the details required for the German Impressum and the entity you are contracting with under the Terms of Service.

Information in accordance with § 5 DDG (Digitale-Dienste-Gesetz). Responsible for editorial content under § 18 Abs. 2 MStV: Florian Standhartinger, address as above.

Postal mail reaches us, but email is considerably faster for anything operational.