---
title: "Acceptable Use Policy · intentic"
description: "What you may and may not do with the intentic platform and a sandbox we host for you, and how we enforce it."
url: "https://intentic.dev/acceptable-use/"
---

Legal

# Acceptable Use Policy

Effective 2026-08-13. This policy applies to everything you do with the intentic platform, and above all to a sandbox we host for you. It forms part of the Terms of Service.

## Why this exists

A hosted sandbox is a machine we pay for, reachable from the internet, running code we deliberately cannot see, driven by an agent that acts on its own. That arrangement only survives if the rules for using it are clear and the consequences are quick. This document is both.

It applies to you, to anyone you share a sandbox with, and to your agent. An agent acting outside these rules is you acting outside them.

## Do not use the platform to

The prohibitions, in the order they are most likely to come up:

- Mine cryptocurrency, farm tokens or run any workload whose purpose is to convert our compute into value. This is the abuse a free machine attracts most, and it is grounds for immediate destruction with no warning.
- Attack, scan, probe, flood or otherwise interfere with any system: ours, another user's, or anyone else's on the internet.
- Send spam or bulk unsolicited messages, or run automation that violates another service's terms of use.
- Host or distribute malware, ransomware, exploit kits, phishing pages, or infrastructure for fraud.
- Store or transmit material that is unlawful where you are or where the machine runs, and in particular child sexual abuse material, which we report to the authorities.
- Infringe intellectual property or misappropriate someone else's confidential information.
- Circumvent limits: the per-account hosted machine allowance, the trial meter, the credit allowance, or any other quota, whether by extra accounts, automation or otherwise.
- Resell the hosted sandbox, or provide it to third parties as your own service.
- Deploy production services or anything other people depend on. The hosted box is a workspace, not a hosting product, and it is sized and operated accordingly.

## Fair use of a machine we pay for

The hosted sandbox is sized for one person's development work and priced at nothing. Use it that way: interactive work, builds, tests, agents doing your work. Sustained saturation of CPU, disk or network that is not doing your work is not fair use, whether it is deliberate or a runaway process you have not noticed.

If usage patterns make the free offer unsustainable, we will change the offer publicly rather than quietly throttle individuals.

## Credentials in a hosted workspace

You may put credentials in your workspace, most real work needs them. Understand the trade: they sit on a disk at our infrastructure provider, that provider snapshots the disk daily and keeps those snapshots for a few days, and an agent with access to a credential can use it. So a secret you delete from the workspace today still exists in a snapshot for a short while afterwards. Prefer scoped, short-lived credentials, rotate rather than delete when one leaks, and never put in a hosted workspace a credential whose compromise you could not survive.

## How we enforce this

We cannot look inside your machine, so our response to a credible report or a clear signal from our infrastructure provider is to act on the machine itself: stop it, or destroy it.

For anything that is causing active harm: an attack in progress, mining, illegal content reported to us with evidence, we act immediately and tell you afterwards. For anything else, we tell you first and give you a reasonable chance to fix it. Repeated or deliberate breaches end the account.

We do not consider a stopped or destroyed machine a punishment to be appealed at length, but if we got it wrong, say so and we will look again.

## Reporting abuse

Report anything on the platform that breaks these rules to contact@intentic.dev. Include what you saw, where, and why it is a problem, and if you are reporting unlawful content, enough for us to find it and to satisfy ourselves that it is what you say it is.

We acknowledge reports, act on them, and tell the reporter what we did. Where we act against a user's content or machine, we tell that user what happened and why, unless the law forbids it.
