Every control in the technical register carries a build-status label. Legal commitments remain as published: a missing test or an unavailable implementation status does not suspend a contractual commitment.
Terms of Service
The agreement between your organization and KeepState, Inc. (San Francisco, CA) for use of the durable agent session cloud. Written to be read once by a person rather than skimmed by a lawyer.
You keep ownership of everything your agents produce. We run the infrastructure, meter it honestly, and can suspend an account for non-payment or abuse with notice. Neither side promises the other unlimited liability, and either side can leave with your data intact.
A summary is not the agreement. Where the two disagree, the clauses below govern.
1 What we provide
What we provide
KeepState hosts agent sessions in isolated micro-VMs, checkpoints their state, and brokers model calls through a metering gateway. No service level agreement is published yet; when one is, its commitments will be measured by an external probe rather than by our own reporting.
We may change how the service works, including adding, altering, or removing features. Material reductions in functionality are announced 30 days ahead in the changelog and by email to account Owners.
2 Your content and your agents
Your content and your agents
Everything your agents read, write, or produce belongs to you. This includes workspace contents, checkpoints, event ledgers, and any artifact a session generates. We claim no license to it beyond what is technically required to run, store, and restore the sessions you asked us to run.
We will not train models on your content, and we will not permit our subprocessors to.
We will not read your checkpoints except through a break-glass path that notifies your Owners and writes to your audit log; that path is not built yet, and neither is any other access path.
You will be able to export your ledgers and checkpoint manifests at any time, on any plan, including the free tier.
3 Acceptable use, in summary
Acceptable use, in summary
The full list lives in the acceptable use policy. In short: do not use sessions to attack others, to host abuse infrastructure, to mine cryptocurrency, or to run workloads whose purpose is to circumvent a model provider’s own terms. An agent acting on your instructions is your responsibility.
4 Fees, meters, and disputes
Fees, meters, and disputes
You pay for session-minutes, checkpoint storage after deduplication, and, if you use our inference, a spread on brokered tokens. Meter output is authoritative for billing, and your ledgers show the same figures we bill from, line by line.
If you believe a charge is wrong, tell us within 60 days and we will reconcile it against the ledger. Where our meter is at fault we credit the difference and publish the incident.
4a The service today
The service today
The hosted service is self-serve, with billing running today: prepaid credits, three meters, and a $10.00 signup credit for one real plug-pull (a kill-and-resume). There is still no service level agreement: no uptime commitment and no SLA credits. Support is answered within two business days, which is a commitment we state here rather than a measured median. When your credits reach zero, sessions checkpoint and park rather than die. Capacity is finite: signup can pause while we fix what usage surfaces, and the availability matrix and the status page say what works today.
5 Suspension and termination
Suspension and termination
Either side may terminate for convenience with 30 days notice. We may suspend immediately for non-payment after two written reminders, or without notice where a workload is actively harming others or our infrastructure.
On termination your checkpoints remain retrievable for 30 days, then are destroyed.
Checkpoints under a legal hold survive termination until the hold is lifted, and you will be told which ones.
Prepaid unused credits are refunded pro rata unless termination was for abuse.
6 Warranties and liability
Warranties and liability
We provide the service with reasonable skill and care and make the specific commitments a published SLA will state when one exists. Beyond those, the service is provided as it is: we do not warrant that an agent will behave correctly, that a model will return useful output, or that a workload will succeed.
Each side’s aggregate liability is capped at the fees paid in the preceding 12 months, except for death or personal injury caused by negligence, fraud, or a breach of confidentiality obligations, where no cap applies. Neither side is liable for indirect or consequential loss.
7 Governing law
Governing law
These terms are governed by the laws of England and Wales, and the courts of London have exclusive jurisdiction. Enterprise agreements may vary this and frequently do.
Control status register
reg Control status register
technical register, not part of the agreement
Every control this document names, with the deployment state derived from the same capability source /security and /proof render. Implementation evidence is dated separately from the legal commitments above. Missing evidence does not amend those commitments; gaps require remediation and communication of customer impact.
| control | status | evidence |
|---|---|---|
| No model training on session contents The published commitment not to train models on session contents remains as written. Current implementation evidence is not available; provider processing is governed by the applicable provider terms. Evidence register dated 2026-10-23; current implementation not independently verified. The published commitment remains. | production state unavailable | none · plan, not proof |
| Break-glass access path with Owner notification and audit write Built and running in production: opening a customer's session content needs a typed reason, lasts an hour, lands in the customer's own audit trail and sends a security email, and the admin console's gates (ad-1 to ad-4, under ADR-022) proved it on the bench, sabotage runs included. Outside such a window the content is refused. Evidence register dated 2026-10-23; current implementation not independently verified. The published commitment remains. | production state unavailable | /evidence/phase-ad |
| Self-serve export of ledgers and checkpoint manifests A separate hosted self-serve export API is not established by the available evidence. Published data-return and audit rights remain as stated in the legal documents. Evidence register dated 2026-10-23; current implementation not independently verified. The published commitment remains. | production state unavailable | none · plan, not proof |
| Hardware-virtualized single-tenant guests Hardware virtualization isolates each session guest. Historical lifecycle tests cover the tested runtime and architecture; they do not constitute a penetration test or proof against shared-host attacks. Evidence register dated 2026-10-23; current implementation not independently verified. The published commitment remains. | production state unavailable | /proof#gate-1 |
Version history begins at v1.0, effective 2026-09-03; no earlier version exists. Material changes are announced 30 days before they take effect, by email to Owners and in the changelog.
v1.0 · effective 2026-09-03 · no prior versions