Acceptable Use Policy

Back

This applies to every Lonch workspace — the real execution environment (a Fly.io Machine) Chat's tools run commands and read/write files against on your behalf. Owning real compute means being clear, up front, about what it's for and what happens if it's used for something else.

Not a substitute for technical controls, and not optional because they exist. Lonch restricts workspace egress to HTTPS/HTTP/DNS and sizes every Machine to a fixed, modest resource budget, but no sandbox is ever fully escape-proof, and those controls don't cover everything listed below (most of it is entirely possible over plain HTTPS). This policy is the backstop for the parts a technical control can't reach, not a fallback for the parts it can.

You may not use a Lonch workspace to:

  • Mine cryptocurrency, or run any workload whose primary purpose is extracting the Machine's compute value rather than developing your own project.
  • Attack, scan, or probe systems you don't own or have explicit permission to test — this includes port scanning, DDoS traffic, exploit attempts, and running offensive security tooling against third parties.
  • Send unsolicited bulk messages of any kind (email, SMS, or otherwise), or operate a spam/abuse relay.
  • Host, store, or distribute illegal content, or content that violates someone else's rights (copyright, trademark, privacy, or otherwise).
  • Use the workspace as a proxy, VPN, or general-purpose relay for traffic unrelated to your own development work.
  • Attempt to access another user's workspace, data, or credentials, or probe for ways to do so.
  • Run persistent, long-lived services unrelated to active development — a workspace is for building and testing your own project, not for hosting production traffic or running an unattended bot/service indefinitely.

Enforcement

Lonch may suspend or terminate a workspace or account, without prior notice, on a good-faith belief that it's being used in violation of this policy. Where practical you'll be notified and given a chance to explain — but for anything posing a real risk (active attacks, illegal content, abuse actively in progress), suspension comes first.

This is deliberately short and will get more specific as real cases come up — it isn't meant to be a complete enumeration of everything that counts as misuse, and Lonch reserves judgment on anything not explicitly listed here that shares the spirit of what's prohibited above.