Terms of Service

These terms govern your use of Sandbox as a Service. By creating an account or calling the API you agree to them. They are meant to be read once, in full, without a lawyer present.

Last updated: 22 August 2026

1. Who you are contracting with

Sandbox as a Service is operated by productivity-boost.com Betriebs UG (haftungsbeschränkt) & Co. KG, Reichenbergerstr. 2, 94036 Passau, Germany, registered at Amtsgericht Passau under HRB 8453, VAT ID DE296812612 — referred to below as "we" or "us". Full details are on the imprint.

2. The service

Sandbox as a Service provides ephemeral, isolated cloud sandboxes. Through a REST API, an MCP server or the dashboard, you can create a sandbox — a dedicated virtual machine — run shell commands inside it, extend its lifetime and destroy it. Sandboxes are intended for running code you would not want to run on your own machines, including code generated by language models.

We may add, change or remove features, sizes and limits. If a change materially reduces what your existing integration can do, we will give notice by email to account holders before it takes effect where that is practical.

3. Accounts

You need a Google account to sign in. You must give accurate information, you must be at least 16 years old, and you must have the authority to accept these terms on behalf of any organisation you sign up for. One human or organisation, one account — creating additional accounts to evade limits, quotas or the free credit grant is a breach of these terms.

You are responsible for your API keys. A key is shown once, at creation time, and anyone holding it can act as you. Keep keys out of client-side code and public repositories, revoke keys you no longer need, and tell us at security@sandbox-as-a-service.com if you believe a key has leaked. Usage incurred with your key is your usage.

4. Acceptable use

Your use of the service is subject to the Acceptable Use Policy, which forms part of these terms. It sets out what you may not run on our infrastructure — mining, spam, attacks on third parties, malware hosting, illegal content and attempts to circumvent resource limits, among others. Read it; it is short and concrete.

You are responsible for the code you run and the data you put into a sandbox, including having the right to process that data. Do not put personal data of others into a sandbox unless you have a lawful basis to do so.

5. Credit and payment

The service runs on prepaid credit. You buy credit through Stripe; runtime is charged against that credit for the time a sandbox runs, to the second, at the rates shown on the pricing page. The specifics:

• Credit does not expire. It stays on your account until it is spent.
• We never charge you automatically. There is no subscription, no stored-card auto top-up and no invoice at the end of the month. When your balance reaches zero, running sandboxes are stopped and new ones cannot be created until you add credit.
• Credit is non-refundable except where refund rights are mandatory under applicable law — including statutory withdrawal rights for consumers in the EU. Where a refund is due, it is issued through Stripe to the original payment method and the corresponding credit is removed from your balance.
• Credit is forfeited if you delete your account. Account deletion is immediate and irreversible; use up or leave behind whatever balance remains.
• Credit has no cash value, cannot be transferred between accounts and cannot be resold.

Prices are stated in US dollars and exclude any taxes that may apply to you. Stripe issues a receipt for every purchase, and invoices are available from the billing section of the dashboard.

6. Sandboxes are ephemeral — there is no durability guarantee

This is the most important operational term in this document.

Everything inside a sandbox is lost when the sandbox is destroyed. Do not store anything in a sandbox that you cannot afford to lose.

A sandbox is destroyed when you delete it, when its timeout expires, when your credit balance reaches zero, when your account is suspended or deleted, when the underlying machine fails, or without notice for operational or security reasons. There is no backup, no snapshot and no recovery path for a sandbox filesystem. Persist anything you need — push it to your repository, upload it to your own storage, or read it out of the command output before the machine goes away.

7. Availability

The service is provided "as is" and "as available", with no service level agreement. We do not commit to an uptime percentage, a provisioning latency, a support response time, or continued availability of any particular sandbox size or capacity. Provisioning can fail, and capacity can be temporarily unavailable. To the maximum extent permitted by law we disclaim all implied warranties, including merchantability, fitness for a particular purpose and non-infringement. Live health is published on the status page.

8. Suspension and termination

We may suspend or terminate your account, destroy your sandboxes and revoke your API keys if you breach these terms or the Acceptable Use Policy, if your usage threatens the stability or security of the platform or third parties, if we receive a credible abuse report we cannot otherwise resolve, or if we are legally required to. Where the circumstances allow it we will warn you first; for active abuse, active attacks or illegal content we will act immediately.

You can stop using the service at any time and delete your account from the dashboard. Sections that by their nature should survive termination — payment obligations already incurred, limitation of liability, governing law — survive it.

9. Limitation of liability

To the maximum extent permitted by law, our total liability for all claims arising out of or relating to the service in any 12-month period is limited to the amount you paid us for the service in that period. We are not liable for indirect or consequential damages, lost profits, lost business, or lost or corrupted data — including data lost when a sandbox is destroyed, which is the expected behaviour of the product.

Nothing in these terms limits liability that cannot be limited by law, including liability for intent and gross negligence, for injury to life, body or health, or under the German Product Liability Act. In cases of ordinary negligence we are liable only for breach of an obligation essential to the purpose of the contract, and then only for the foreseeable damage typical for this kind of contract.

You will indemnify us against third-party claims arising from your use of the service in breach of these terms or the Acceptable Use Policy.

10. Changes to these terms

We may update these terms; the current version always lives at this URL with the date it last changed. We will notify account holders by email of material changes at least 30 days before they take effect, and continuing to use the service after that means you accept them. If you do not, delete your account before the change takes effect.

11. Governing law and jurisdiction

The operator of Sandbox as a Service is a company established in Germany; the operating entity and its registered address are disclosed on the contact page. These terms are governed by German law, excluding its conflict-of-law rules and the UN Convention on Contracts for the International Sale of Goods. If you are a business, the courts at the operator's registered seat have exclusive jurisdiction. If you are a consumer, mandatory consumer protection law in your country of residence continues to apply and you may bring proceedings in the courts available to you there. If any provision of these terms is found unenforceable, the rest remains in force.

12. Contact

Questions about these terms: info@productivity-boost.com. Security reports: security@sandbox-as-a-service.com. Abuse reports: abuse@sandbox-as-a-service.com.