Terms of service
# Terms of service for the hosted Dispatch team server
> **Draft for review.** Written from the server's code and design documents on
> 2026-11-12 for Wyat and a lawyer to review. It is not legal advice and is not
> in force. Every "Decide:" note marks a business or legal choice that is still
> open; `docs/legal/README.md` lists them all.
- **Provider:** [LEGAL ENTITY NAME], [ADDRESS] ("we", "us").
- **Effective date:** [EFFECTIVE DATE]
- **Contact:** [CONTACT EMAIL]
> Decide: the legal entity name, its address, the contact email and the
> effective date.
These terms are an agreement between you and us for the hosted Dispatch team
server at app.dispatch.foo (the "service"). If you use the service for an
organization, you accept them for that organization and confirm you may do so.
Our privacy policy (`privacy.md`) says what we collect and what we cannot see.
The sign-in page links these terms and the privacy policy and says that
signing in accepts them.
> Decide: whether that line is enough, or whether to add a checkbox when a
> team is created.
## 1. The service
The service is a team's always-on home for Dispatch. It:
- signs people in, and lets them make teams, invite members and sign in
devices;
- stores what the team's devices share and passes it between them, in order;
- notes when a device connects and goes quiet, so its work can be handed on;
- counts seats and takes payment.
It does not run agents. Your agents run on your own machines, with your own
accounts and subscriptions with model providers such as Anthropic or OpenAI.
Those providers' terms apply to that use, and you pay them directly.
Everything your team shares is sealed on your devices with a key we never
have. We cannot read it, search it, or recover it for you.
## 2. Accounts and devices
- You sign in with a GitHub or Linear account. You must keep that account
secure; anyone who controls it can use the service as you.
- Your handle comes from that account the first time you sign in. Handles are
not reused for anyone else.
- Each device you sign in to a team gets its own token. Keep the token file
private. You and your team's admins can sign out any device from the team's
page, which cuts it off at once.
- You are responsible for what happens under your account and your devices.
- You must be at least [MINIMUM AGE] to use the service.
> Decide: the minimum age, and whether the service is for business use only.
## 3. Teams, seats and billing
- **Roles.** A team has admins and members, and always keeps at least one
admin. Admins invite and remove members, make other members admins, sign
out devices, export the team, delete it and manage payment. Any member may
leave a team on their own, unless they are its only admin.
- **Seats.** Each member of a team is a seat. A team pays per seat through a
Stripe subscription. When members join or leave, the subscription's seat
count follows, and Stripe prorates the charge. [FREE SEATS]
- **Price.** [PRICE PER SEAT, CURRENCY, BILLING PERIOD, TAXES]
- **Payment.** Stripe takes payment and holds your payment details under its
own terms. Admins manage payment through Stripe's billing portal.
- **Notice, then a pause, never deletion.** If a team has more members than
seats, if a payment fails, or if a new team has more members than its free
seats and no subscription, we tell the team on its page and through the
service. After 14 days the team is paused: its devices can still read,
export, and sign devices in and out, but cannot add new content (new
projects, changes, snapshots, run logs or device invites) until the team
pays or drops below its seats. Nothing is deleted because a team has not
paid.
- **Cancelling.** An admin can cancel the subscription in Stripe's billing
portal. The team then has no paid seats and is treated as above.
> Decide: the price per seat, currency, monthly or yearly billing, and who
> handles sales tax or VAT.
> Decide: how many free seats a team gets, if any (the server's
> `DISPATCH_FREE_SEATS`, default 0), and whether there is a free trial.
> Decide: refunds, including for prorated seats and for a team deleted
> mid-period.
> Decide: how long a paused team's data is kept before we may delete it.
> The server today keeps it indefinitely.
- **Deleting a team** cancels its subscription at once. If the subscription
cannot be cancelled, the team is not deleted and the admin can try again.
## 4. Acceptable use
Do not use the service to:
- break the law, or store or pass on content you have no right to;
- get into accounts, teams or devices that are not yours, or test the
service's security without our written permission;
- send more than the service's limits allow, or try to get around them (for
example, a device may send at most 50 messages a second and one message may
be at most 8 MiB);
- disrupt the service or other teams;
- resell the hosted service to others.
Because we cannot read team content, we cannot check it. You are responsible
for what your team stores.
> Decide: whether to add more prohibited uses (for example malware
> distribution or sanctions-related restrictions), and the process for
> reports of abuse.
## 5. Your content
What your team shares through the service is yours. You give us only the right
to store it, copy it as needed to run and back up the service, and send it to
your team's devices. We cannot read it, because it is sealed with a key only
your devices hold.
This means:
- if your team loses every device and its recovery phrase, nobody, including
us, can recover the team's content;
- a person removed from a team keeps whatever their devices already had;
- we cannot take content down by reading it; we can only act on what we can
see, such as accounts and teams.
Account, team, device and billing data are described in the privacy policy.
> Decide: what we may do with a team or account we believe breaks these terms,
> given that we cannot inspect content (for example suspend the team, or keep
> its sealed data for a set time before deletion).
## 6. Export and self-hosting
A team admin can export the team's sealed data at any time, including while the
team is paused, and import it into another Dispatch server.
The server software is source-available under the Elastic License 2.0. You may
run it for your own team, at any size, without paying us and without a license
key. Under that license you may not offer it to others as a hosted or managed
service, and you may not remove its licensing notices. A server you run
yourself is not covered by these terms or by any promise in them; the Elastic
License 2.0 applies to the software.
The `dispatch-core` program on your devices is under its own license (Apache
License 2.0 today), not these terms.
> Decide: confirm `dispatch-core`'s license (its repository says Apache-2.0)
> and whether the desktop app needs its own terms.
## 7. Availability and no warranty
We try to keep the service running but do not promise that it will be
available, fast or free of errors. It is a single point of coordination for
your team: while it is down, devices cannot take claims or hand work to each
other, though they keep working and queue what they send. We may change or
stop parts of the service.
THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY
KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT, TO THE EXTENT THE LAW ALLOWS.
> Decide: whether to offer any uptime commitment, backups commitment or
> support terms, for example for paying teams or a dedicated instance.
> Decide: how much notice we give before shutting the service down, and
> that export stays available during that time.
## 8. Limits of liability
TO THE EXTENT THE LAW ALLOWS, WE ARE NOT LIABLE FOR ANY INDIRECT, INCIDENTAL,
SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, DATA OR
GOODWILL. OUR TOTAL LIABILITY FOR ANY CLAIM ABOUT THE SERVICE IS LIMITED TO
THE GREATER OF WHAT YOUR TEAM PAID US IN THE [12] MONTHS BEFORE THE CLAIM AND
[AMOUNT].
We are not responsible for what your agents do on your machines, for your use
of model providers, or for data lost because keys or recovery phrases were
lost.
> Decide: the liability cap, whether to include an indemnity from customers,
> and how consumer law in your markets limits these clauses.
## 9. Termination
- You may stop using the service at any time. An admin may delete a team from
its page, which deletes everything the team stored on the service and
cancels its subscription. You may delete your own account from the
website, unless you are a team's only admin.
- We may suspend or end your access if you break these terms, if the law
requires it, or if your use puts the service or other teams at risk. Where
we can, we will tell you first and give the team time to export.
- Sections 5, 8 and 10 survive termination.
> Decide: the notice and export window we give before ending a team's access,
> and what happens to the team's data afterwards.
## 10. Governing law and disputes
These terms are governed by the laws of [GOVERNING LAW]. Disputes go to the
courts of [VENUE].
> Decide: governing law, venue, and whether to use arbitration or a class
> action waiver.
## 11. Changes to these terms
We may change these terms. We will post the new version with a new effective
date and tell team admins [HOW AND HOW FAR IN ADVANCE] before a change that
reduces your rights takes effect. If you keep using the service after that, the
new terms apply.
> Decide: how we notify (we keep no email address, so the team page and what a
> core shows from the server are the channels today) and how much notice.
## 12. Contact
[LEGAL ENTITY NAME], [ADDRESS], [CONTACT EMAIL].