Terms of Service
Last updated: 30 July 2026 · Draft for legal review
1. The service
sessiontwin ("Service") lets you ask an AI agent to perform a software task that continues running after you close your browser. A separate process, not the agent that did the work, decides whether the task's frozen contract was met, and every step is recorded in a signed, append-only ledger. The Service is provided by the operator described in the Privacy Policy.
2. Eligibility and accounts
You must be able to form a binding contract and use the Service for lawful, professional software-development purposes. You are responsible for activity under your account and for the security of your login.
3. Acceptable use
- Do not point the Service at repositories or content you are not entitled to access or share.
- Do not submit content that is unlawful, infringing, or that you have no right to process.
- Do not attempt to make the agent perform actions outside the single file and branch a mission declares, or to defeat the verifier or the ledger's integrity for deceptive purposes.
- Do not use the Service to develop or deliver malware, or to violate others' rights or applicable law.
The Service opens work on a non-default branch as a pull request for a human to merge; you remain responsible for reviewing and merging any change.
4. Your content and the ledger
As between you and us, you retain ownership of the task text, the repository contents you supply, and the code the Service generates for you ("Generated Output"), to the extent such rights exist under applicable law. You grant us the limited licence needed to operate the Service — to store, process, transmit to the AI provider and to GitHub, and to record your mission in the ledger.
Note that the platform we run on (Base44) takes its own licence over customer data and generated output under its terms, which we cannot override; see the Privacy Policy, section 3.
5. What a verified ledger does — and does not — attest
This section is central to the Service and to these terms. sessiontwin's ledger and its Merkle/checkpoint chain provide integrity evidence. Read precisely:
A verified chain attests that: the recorded steps of a mission were signed by the runtime's key, have not been altered or deleted since they were recorded, and are consistent with any checkpoint an auditor already holds; and that the pass/fail verdict was produced by a process separate from the one that produced the work.
A verified chain does NOT attest that: the work is correct, safe, fit for any purpose, free of bugs or vulnerabilities, or legally compliant; that the contract's checks were sufficient to catch a given defect; that a passing verdict means the code is good — only that it passed the checks that were frozen; or that any statement inside a step is true. Integrity is not accuracy. The chain proves the record was not tampered with; it does not vouch for what the record says.
You must not represent a verified sessiontwin ledger as a warranty of correctness, security or compliance of the underlying work.
6. AI output
The Service uses AI models. AI output can be wrong, incomplete or unsuitable. You are responsible for reviewing all output before relying on or merging it. The verifier reduces, but does not eliminate, this risk — see section 5.
7. Disclaimers
The Service is provided "as is" and "as available", without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, non-infringement, and any warranty that the Service will be uninterrupted, error-free, or secure. Some jurisdictions do not allow certain exclusions, so parts of this may not apply to you.
8. Limitation of liability
To the maximum extent permitted by law, the operator will not be liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, data or goodwill, arising from your use of the Service; and the operator's total liability will be limited to [amount/formula — TO BE SET WITH COUNSEL]. The specific cap and its enforceability depend on jurisdiction and are an open question.
9. Third-party services
The Service depends on Base44 (hosting, database, auth, AI routing), the AI providers, and GitHub. Your use is also subject to their terms, and their availability and acts are outside our control.
10. Termination
You may stop using the Service at any time. We may suspend or terminate access for breach of these terms or where required by law or by our platform. Because the ledger is append-only, some mission records may persist after account closure; see the Privacy Policy, section 6.
11. Changes
We may update these terms and will revise the "Last updated" date; material changes will be signposted. Continued use after a change means you accept it.
12. Governing law
These terms are governed by the laws of [Israel — TO BE CONFIRMED WITH COUNSEL], without prejudice to mandatory consumer-protection rights you may have where you live.
Open questions for counsel
- Operator legal identity and the notice/contact address for these terms.
- Governing law and forum, and interaction with Base44's US-law terms that flow through.
- The limitation-of-liability cap (section 8) and its enforceability by jurisdiction (Israel/EU consumer law may restrict it).
- Whether any users are "consumers" (vs. professionals), which changes disclaimer/liability enforceability and EAA scope.
- Precise wording of the "verified chain" clause (section 5) so it forecloses a misrepresentation/warranty claim without overclaiming.
- Whether the platform licence flow-through (section 4) needs fuller disclosure to be enforceable/fair.
- Acceptable-use and IP-indemnity provisions appropriate to a code-generation tool.
Evidence map (source in code)
| Claim | Source |
|---|---|
| Work continues after browser close; separate verifier | base44/functions/advance/entry.js; base44/functions/verify/entry.js; base44/agents/worker.jsonc |
| One file / one branch / PR for human merge | base44/entities/Mission.json (path, branch); base44/functions/repo/entry.js |
| Signed, append-only ledger; tamper-evidence vs service-role | base44/functions/advance/shared/sign.js; base44/entities/Step.json; base44/functions/tamper/entry.js |
| Merkle chain / checkpoints attest integrity not accuracy | base44/functions/advance/shared/merkle.js; base44/entities/Checkpoint.json; base44/functions/advance/shared/audit.js |
| Contract frozen, cannot be lowered by the worker | base44/entities/Contract.json (rls update:false); base44/functions/chat/entry.js |