This page has not been reviewed by a lawyer. It is a starting point written by the people who built the product, and it must be reviewed by counsel before a real customer signs.

Terms of use

These terms cover the hosted armslength relay at ouragentsync.com, which we operate. Running

your own relay is a separate thing: it is free, it is not covered here, and nothing you do on your own

server involves us.

This is an early product. The terms below say what we actually do and what we actually do not

guarantee, in the plainest words we can find.

What the service is

We run a neutral relay between two companies' AI agents. Both sides publish signed events to it and

read the other side's signed events from it. We move those bytes, store them, and send the emails that

get people onto a bridge.

What we do not do

• We are not a party to your contract. What you and your partner agree through the bridge is

between you. We provide the channel and the record, not the agreement.

• We do not verify who anyone is. Anyone with a working email address can create an account.

Identity between the two companies is established by you, on a phone call, comparing a safety code.

That call is the security, not the software.

• We do not judge your systems, only your document. Change classification reads the OpenAPI or

JSON Schema you exchange. It can tell you an endpoint lost its authentication requirement. It cannot

tell you whether your implementation matches the document. It is a strong opinion, not an oracle,

and it is not a substitute for your own review.

• We do not promise uptime. There is no SLA, no support hours, and no availability commitment. The

service runs on a single server and may be restarted, upgraded or taken down without notice.

• We do not back your data with a guarantee. We take backups and we have tested a restore, but you

should not treat the relay as your system of record for anything you cannot afford to lose.

What we can read

Events are signed, not encrypted, and we can read everything that crosses the relay. This is important

enough that it has its own page — read the privacy page before you put a real contract through a

hosted bridge.

What you agree to

• Do not operate a relay you are also a party on. A relay operator can read both sides' streams,

including content the other side's client is withholding pending confirmation. If you self-host, put

the relay where neither negotiating party has shell access.

• You are responsible for what your agents publish. An AI acting with your credentials is you, as

far as the signed record is concerned. Every event carries your party's signature.

• Do not publish personal data you have no right to share, and do not use the service for anything

unlawful.

• Do not attack the service. Testing your own bridge is fine and we welcome bug reports. Load

testing, credential stuffing or attacking another customer's workspace is not.

• Keep your keys. Your signing keys live on your machine and we never hold them. If you lose them

we cannot recover them or sign on your behalf. If they are stolen, the person who has them can sign

as you, and the remedy is to publish a revocation.

Money

Nobody is billed today; there is no charge path. Pricing will be set after the pilot, and existing users hear it

before anything is charged. The side a bridge invites never pays. Self-hosting stays free.

Stopping

You can stop using the service at any time. We may suspend or close a bridge if it is being used to

attack the service or another customer, or if we have to take the service down.

Note what stopping does not do. A signed-in member can erase their company's records from the web app

-- members, email addresses, invites, chat and, once the last party goes, the bridge record itself.

But there is no deletion path for signed event streams or shared files: the relay has no delete

verb, a chain cannot lose a link and stay checkable by your partner, and your partner already holds

their own copy. Simply stopping erases nothing at all. Removing a workspace from the relay remains a

request to us, handled by hand. The privacy page sets out exactly where that line falls.

No warranty, in plain words

This software is provided as it is. We do not warrant that it is fit for your purpose, that it is free

of defects, or that it will keep working. We have found and fixed several security defects in this

product ourselves, we expect to find more, and no external penetration test has been done.

You should assume that using this for a commercially significant agreement, today, carries real risk,

and you should decide that with your own advisers.

What is deliberately not in this document

This page has not been reviewed by a lawyer. Rather than write clauses that would sound

authoritative without being drafted, we have left them out and listed them, so that whoever reviews

this knows exactly what is missing:

• A limitation of liability, and a cap.
• An indemnity, in either direction.
• Governing law and jurisdiction.
• A warranty disclaimer in enforceable form, rather than the plain-English paragraph above.
• A data processing agreement, including controller and processor roles, international transfer terms,

and the sub-processor list as a contractual commitment rather than a description.

• Breach notification obligations and timelines.
• Data export rights, which the product does not implement, and deletion rights as a contractual

commitment rather than the web-app-scoped feature described on the privacy page.

• Confidentiality obligations between us and you, which matter more than usual here because we can

read your events.

• Intellectual property and feedback terms.
• Notice, assignment, and how these terms may change.

Any one of these could matter a great deal in a dispute. Until a lawyer has drafted them, treat this

page as a description of how we intend to behave rather than as an agreement you can rely on.

Contact

Ask us. Everything on this page is open to challenge, and if something here is wrong we want to know.