Terms of service

Last updated 25 August 2026

These terms are the agreement between you and [LEGAL ENTITY NAME] for the use of Ondago. They are written to be read: where a clause costs you something, it says so in the same words we would use out loud.

1. Accepting these terms

By creating an Ondago account, installing the Ondago command-line tool, or using the service in any other way, you agree to these terms. If you are agreeing on behalf of a company, you confirm that you may bind it, and “you” means that company. If you do not agree, do not use the service.

You must be at least 16 years old, and legally able to enter into this agreement.

2. Early access

Ondago is early-access software. That is a statement about its maturity and not a disclaimer we hide behind: expect features to change or be withdrawn, expect occasional downtime, and do not make Ondago the only copy of work you cannot afford to lose. Section 5 explains the one failure mode you should plan around specifically.

3. What the service is

Ondago lifts a coding-agent session — the conversation and the state of the working tree — off one machine, stores it encrypted, and lets you resume it on another machine, in a cloud container, or from a browser on your phone. It consists of the command-line tool, the web application, the macOS application, and the hosted service behind them.

Ondago is not the agent. It carries sessions belonging to third-party tools — Claude Code, Codex, OpenCode, Copilot and others — and it does not produce their output, does not review it, and is not responsible for what they write. Whether a given tool can be carried is a property of that tool, and the app names which ones it supports.

4. Your account

Keep your credentials to yourself. You are responsible for what happens under your account and under credentials it issues — workspace tokens, enrolled devices, CLI sign-ins. All of them are listed in the app and every one can be revoked; if you think one has leaked, revoke it there and tell us.

A workspace can have several members. Membership is not the same thing as the ability to read a session: reading requires that somebody who already holds the workspace key has granted it to one of your devices. Adding someone to a workspace does not give them access to its existing sessions, and no action we can take on the server changes that.

5. Keys, and data we cannot recover

Your sessions are encrypted on your machine before they reach us, to a key whose private half exists only on devices you have enrolled. We store ciphertext. This has consequences that are yours to carry:

• We cannot read your sessions, and therefore cannot search them, preview them, summarise them, or produce their contents to anybody who asks us for them.
• We cannot recover them. If you lose every enrolled device, the only remaining way in is your workspace recovery passphrase. If you lose that too, the data is gone — permanently, for everybody, including us. We cannot reset the passphrase, because what we hold is your key encrypted with it.
• You are responsible for keeping the passphrase. Store it in a password manager. It is shown once, by design, and we have no copy.
• Deleting is deleting. Deleting a session destroys its ciphertext. Where that session is the result of a cloud run, the code it produced may exist nowhere else, because the container that made it has been destroyed.
• One thing is unreadable by everybody, on purpose. The copy of a session handed to a cloud container is re-encrypted to a key that container generated for itself and took with it. Nothing opens that row, and no enrolment or recovery ever will.

We think this is the right trade for work that contains your source code. We are stating it here so that it is a choice you made rather than a discovery you make.

6. Your content

Your sessions, code, prompts and everything in them remain yours. We claim no ownership of them and no licence to use them beyond what operating the service requires: storing the encrypted bundle, transmitting it to the clients and containers you direct it to, and holding the index described in our privacy policy.

There is no clause here granting us a broad licence to “use your content to improve our services”, because it would be unperformable. We hold ciphertext; there is nothing for such a licence to reach.

You are responsible for having the right to put what you put into Ondago — including where a session contains somebody else's personal data or an employer's code.

7. Acceptable use

Do not use Ondago to:

• break the law, or help anybody else do so;
• infringe somebody's intellectual property or privacy;
• run malware, mine cryptocurrency, mount denial-of-service attacks, send spam, or use our compute for anything other than the agent session you are carrying;
• attack or probe our infrastructure, other tenants, or the boundaries between workspaces, except where you are reporting a vulnerability to us in good faith — which we welcome;
• circumvent limits, quotas, credentials or metering, or resell access to the service;
• store material that is illegal to possess.

Because we cannot read your sessions, we enforce this on what we can see: resource consumption, credential abuse, traffic patterns, and reports we receive.

8. Agents, providers and their keys

Running an agent requires a credential for its model provider. You may forward the one on your own machine for a single run, or store one for a workspace, in which case it is encrypted to your workspace key before it is sent and we cannot read it.

Your use of those providers is governed by their terms, and their charges are yours. Ondago starts the agent; what the agent then sends to Anthropic, OpenAI, GitHub or anybody else, and what it costs, is between you and them. Keep your provider keys scoped and rotate them. We are not liable for a provider's charges, outages, refusals or output.

9. Cloud runs and limits

A cloud run executes in an isolated container with a time limit and a memory limit, and is given a credential scoped to that one run which is revoked when it ends. Your workspace has limits on how many sessions it may store, how many members it may have, how many runs it may hold and how many may be live at once. Those limits are visible in the app, and we may change them; where a change reduces what an existing account can do, we will tell you first.

An agent running in a container acts with whatever access you gave it. It can change code, run commands and make network requests. That is what you asked it to do, and reviewing its output before you rely on it is yours.

10. Fees

During early access, Ondago is provided at no charge unless we have agreed otherwise with you in writing. We will give reasonable notice before charging for something that is free today, and you will be able to decline and stop using it.

11. Availability and support

There is no service-level commitment during early access. We aim for the service to be up and will tell you about planned interruptions where we can. Support is by email at team@ondago.ai, on a best-effort basis.

If we discontinue the service, we will give you reasonable notice and time to collect your sessions before anything is deleted.

12. No warranty

The service is provided “as is” and “as available”. To the fullest extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted, error-free, or that it will preserve any particular piece of data — see section 5.

Nothing in these terms excludes liability that cannot lawfully be excluded, and if the law where you live gives you rights this section cannot remove, it does not remove them.

13. Limitation of liability

To the fullest extent the law allows, neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, goodwill or data, however caused.

Our total liability arising out of or relating to these terms is limited to the greater of the amounts you paid us in the twelve months before the claim, or [CAP AMOUNT]. During early access, where you pay nothing, this means our liability is limited to that second figure.

14. Suspension and termination

You may stop using Ondago and delete your account at any time. Note what section 5 says about deletion, and collect anything you want first.

We may suspend or terminate your account if you materially breach these terms — in particular section 7 — if we are required to by law, or if your usage threatens the service or other users. Except where the breach is serious or urgent, we will tell you and give you a chance to fix it. On termination we will, where we lawfully can, give you a reasonable window to collect your sessions before deleting them.

15. Changes to the service and these terms

Ondago is under active development and will change. We may update these terms; the date at the top says when we last did. For a material change we will notify account holders by email rather than relying on you noticing. Continuing to use the service after a change takes effect means you accept it; if you do not, stop using it and tell us, and we will help you get your data out.

16. Governing law

These terms are governed by the laws of [JURISDICTION], without regard to its conflict-of-laws rules, and the courts of [VENUE / COURTS] have exclusive jurisdiction over any dispute arising out of them.

If a provision of these terms is unenforceable, the rest stays in force. Our not enforcing a provision is not a waiver of it. You may not assign this agreement without our consent; we may assign it as part of a merger, acquisition or sale of assets. These terms, together with the privacy policy, are the whole agreement between us about the service.

17. Contact

team@ondago.ai, or [LEGAL ENTITY NAME], [REGISTERED ADDRESS].