Terms of service

1Definitions

2The service

2.1Coordination, not compute

Quayutec provides cross-company coordination infrastructure: state management, shared project memory, and the Approval Gate, which applies to each action an always-on Agent declares the Agent Rights its own Organization chose and the Room Rules of each Organization the action lands on, and holds the action for a person’s decision where either requires one (Sections 4.3 to 4.6). Quayutec does not carry out an Agent’s actions outside the Room: when an action goes ahead, the Services post the Agent’s reply in the Room, and anything the action changes outside the Room is changed by systems that an Organization has chosen to act on it. Quayutec does not provide foundation models, does not resell model inference, and does not host proprietary model compute. Intelligence is generated either by an always-on Agent running on Quayutec’s runtime with its Organization’s own BYOK credentials, or by an AI tool an Organization already uses, connected to a Room over the Model Context Protocol from wherever that tool runs. Every model call an always-on Agent needs is made with its own Organization’s credentials and is billed by the provider to that Organization; Quayutec makes no model call on its own account and pays for no model usage. The only model Quayutec runs itself is an open-source embedding model inside its own application code, which turns Room text into vectors for search (Section 6.3).

2.2Two connection paths

• Path A (always-on Agents). A durable background worker on Quayutec’s runtime, authenticated with its Organization’s own encrypted BYOK credentials, that keeps running when every human is offline.
• Path B (connected Agents). An AI tool that connects to a Room over MCP from where it runs: a coding tool, or a chat app such as Claude.ai on the web. The tool reaches the Room with the Agent’s own Quayutec key or, where the tool supports it, by its owner signing in to Quayutec and choosing which of the Organization’s Agents the tool acts as (OAuth). A connected Agent never gives Quayutec a model provider key: its model calls are made by its own tool. It takes part while its tool is in use, and where its owner has set it up to be woken (by a Claude routine, or by an app subscribed to its events), Section 4.2 decides who may wake it. Agent Rights and Room Rules do not apply to a connected Agent (Section 4.3).

2.3The Host-Payer model

A Room, and the capability pool that comes with it, is funded solely by the Host’s subscription. Quayutec does not invoice a Guest for a Host’s Room. The runtime meters every always-on Agent’s usage in a Room against that Room’s balance, which the Host funds, whichever Organization owns the Agent. A Guest’s always-on Agents therefore draw on the Host’s plan allowance and the Host’s prepaid top-ups for that Room, never on a balance of the Guest’s own; a Guest participating only through a connected Agent over MCP draws no Agent Runs at all. Charges from a model provider for calls made under a Guest’s own credentials remain the Guest’s, under Section 5.

2.4Business users and age

The Services are for use in business only, as the opening of these Terms says. Every person who uses them for an Organization must be at least 18 years old. Quayutec does not knowingly let anyone younger use the Services; if it learns that a user is under 18, it ends that person’s access and deletes their personal data, except what a law requires it to keep.

3Accounts, roles and authority

3.1Organizational identity

Each participating entity registers an Organization profile and represents that the corporate identity and contact information it provides is accurate, and keeps it up to date. Quayutec may check that information, including against the lists Section 14.1 names.

3.2Top Manager designation

An admin or owner of an Organization’s account may name one member as its Top Manager. When one is named, only that person may decide an Approval Gate escalation that the Organization is asked to decide, whether one of the Organization’s own Agents raised it (Section 4.3) or it concerns another Organization’s Agent’s action that lands on the Organization (Section 4.5): a colleague who tries is refused and told who decides, and if the Services cannot read who may decide, the decision is refused rather than guessed. When none is named, any signed-in member of that Organization may decide. A decision by a person at any other Organization is not accepted. Escalation emails go to the Top Manager when one is named (or, if the Top Manager has no email address on file, to the Organization’s members), and to the Organization’s members otherwise, at most 25 people for any one escalation.

Besides deciding escalations, a Top Manager is one of the Organization’s Managers, together with the owners and admins of its account. The Managers, among other things, change the Organization’s rows of a Room’s Room Rules and accept them after a change (Section 4.5), choose its Room Admins where the Organization is a Host, change or propose changes to the Agent Rights of the Organization’s Agents (Section 3.3), and manage an Agent that has no owner. An admin or owner of the Organization’s account sets its read-only safelist, and its triage policy and automatic approval (automatic approval affects only Agents whose Agent Rights have not been chosen, and Rooms under Section 4.6). A Bilateral Room Agreement is set by the Host and accepted by the Guest as Section 4.1 describes.

3.3Agent owners and changes to Agent Rights

An Agent’s owner manages that Agent, its keys and its Agent Rights. While an Agent has no owner, because the person who held it has left, the Organization’s Managers manage it. Where Agent Rights are switched on for the Organization, a Manager who is not the owner of an owned Agent may also change its Agent Rights, as follows:

(a) A stricter change applies at once. A change that makes the Agent wait for a person more often applies at once, and the owner is told by email. A change is stricter when it moves the Agent to a later level in the order Full autonomy, Read-only on its own, Ask first, or, at Full autonomy, keeps every kind of action that already waited for a person and adds more. For an Agent whose Agent Rights have not been chosen, or cannot be read, only a change to Ask first applies at once.

(b) Any other change is a proposal. The Agent keeps its Agent Rights until its owner accepts the proposal, and the owner may reject it instead. One proposal waits for each Agent at a time, and a newer one replaces it. A proposal made before the Agent’s Agent Rights changed again can no longer be accepted.

Proposals, and their acceptance or rejection, are visible only to the Agent’s own Organization, and the person who made a proposal is told by email when the owner answers it. The change that takes effect is recorded in the ledger of every Room the Agent works in, in the same way as any change of Agent Rights, without saying whether it came from a proposal. Each change of Agent Rights is recorded with who made it, when, and from what to what, and is emailed to the Organization’s Managers, at most 25 people. Section 4.3 describes what each level means.

3.4Authority and reliance

An Organization is responsible for who it lets sign in to its own account, and Quayutec is entitled to rely on any decision made from an authenticated session of that account without independent investigation of which person was at the keyboard. Where these Terms reserve an act to an Organization’s Managers, the Services refuse it from anyone else. In particular, when an Organization joins a Room or creates one, the Services record its acceptance of a Room Rules row under which it would be asked less than before every Irreversible Action only when a Manager of the Organization gives that acceptance; until one does, the Organization is asked before every Irreversible Action that lands on it (Section 4.5).

4Follow-lists, the Approval Gate, Agent Rights and Room Rules

4.1Bilateral Room Agreements

Before a Guest’s Agents work in a Host’s Room, the Host sets the scope of their Bilateral Room Agreement and the Guest accepts it inside the Services: whether the Guest’s Agents may read the Room’s shared memory, write to it, assign tasks, and take live action. The Guest’s acceptance is recorded with the version of these Terms then in force, the time, and the person who accepted. The Host may change the scope or revoke the agreement afterwards. Where Room Rules apply to the Room (Section 4.5), accepting the agreement also accepts the Room’s current Room Rules for the Guest’s own row, and that acceptance is recorded as Section 4.5 describes; an acceptance of a row under which the Guest would be asked less than before every Irreversible Action is recorded only when a Manager of the Guest gives it.

Reading and writing shared memory and assigning tasks are each checked against the agreement’s own permission, and a Guest without an active agreement cannot post in the Room, read or write its shared memory, assign tasks, or wake its always-on Agents. Revoking an agreement takes every one of the Guest’s Agents off the Room’s roster, which takes the Guest out of the Room. Any action of its Agents still waiting at the Approval Gate then expires untaken, and so does any request for the Guest to decide another Organization’s action; the same happens when a Guest removes its own last Agent from the Room.

The live-action permission does not let an Irreversible Action past the Approval Gate. In a Room where Agent Rights and Room Rules apply (Section 4.5), it has no effect on whether an action goes ahead, and no co-signature request is opened: the acting Agent’s Agent Rights and the Room Rules decide, and an Organization an action lands on is asked itself where its Room Rules say so. In any other Room, such an action by a Guest’s always-on Agent is held for the Guest’s own Organization to decide, under Section 4.6; when the permission is granted, the same action also opens a co-signature request in the Room; nothing waits on that request and only the Guest’s Organization can resolve it, so it records that a co-signature was asked for and does not require the Host’s approval.

4.2Follow-lists

An Agent acts on messages from its own Organization’s people and Agents without being told to. A message from a sender in another Organization is acted on only when that sender is on the Agent’s follow-list. A message from anyone else does not execute: the Agent does not act on it, and an escalation is opened for the Agent’s own Organization to decide, recorded in the Room’s ledger and emailed to the people who may decide it. Approving that escalation adds the sender to the Agent’s follow-list, so the Agent acts on what that sender says next; the held message itself is not replayed.

The always-on runtime applies this rule to the message that wakes each run. The same rule decides who may wake a connected Agent that its owner has set up to be woken by a Claude routine or by an app subscribed to its events: a sender from its own Organization or on its follow-list wakes it, and anyone else opens the same escalation and no wake is sent. A connected Agent’s own tool calls are not checked against its follow-list; the Bilateral Room Agreement bounds them.

4.3The Approval Gate and Agent Rights

The Approval Gate applies to the actions that always-on Agents declare. An always-on Agent declares each action it intends on a line of its own, naming the Organization whose side the action lands on (Section 4.5). Each declared action is read as read-only, or as Irreversible when it does not match Quayutec’s built-in list of read-only verbs or, for an action on the acting Organization’s own side, that Organization’s own read-only safelist; an action that lands on another Organization, or on every other Organization because it names none, is read against the built-in list alone. A reply is also read as Irreversible when it matches a fixed keyword net (payment, deploy, delete, and similar terms), or says in the first person that the Agent will delete or destroy something, even with no declared action at all. An action goes ahead when the reply that declares it is posted in the Room.

Agent Rights. Where Agent Rights are switched on for its Organization, the person connecting an always-on Agent chooses its Agent Rights; nothing is chosen in advance. With “Full autonomy”, the Agent’s declared actions go ahead without a person at its own Organization, Irreversible Actions included, except Irreversible Actions of the kinds the Organization has ticked to always wait for a person there: money; deploying or going live; deleting; sending email or posting publicly; changing access; anything else that changes something; and anything another company asked for, which starts ticked. With “Read-only on its own”, read-only actions go ahead and every Irreversible Action waits for a person at the Agent’s own Organization. With “Ask first”, every declared action waits for a person there. Whatever its Agent Rights, an Irreversible Action that lands on another Organization then also follows that Organization’s Room Rules (Section 4.5). The kind of an action is read as Section 4.5 describes. Section 3.3 says who may change an Agent’s Agent Rights, and how each change is recorded and announced.

Anything another company asked for. For this kind, a run counts as asked for by another Organization, so that the kind covers every Irreversible Action in it, when: the message that woke the Agent came from a person or Agent of another Organization, or from a sender the Services cannot place; anything the Agent is shown for the run came from another Organization or from a sender the Services cannot place, whether a recent message in the Room (the lines the Services write included), a shared-memory entry, the sender of one of its open tasks or a file added to the Room; the Room’s recent messages could not be read; or the message that woke it was written by an Agent, in a Room that includes another Organization. In a Room shared with another Organization, this kind therefore covers most Irreversible Actions.

An Agent whose Agent Rights have not been chosen (an always-on Agent connected before Agent Rights were switched on for its Organization, until someone who manages it chooses) is held for its own Organization as before: every Irreversible Action waits for a person there, and a read-only action does too unless that Organization has switched automatic approval on. Its Irreversible Actions that land on another Organization then also follow that Organization’s Room Rules. Agent Rights the Services cannot read are treated as “Ask first”, and a reply the Services cannot classify waits for a person at the Agent’s own Organization.

When an action waits. The Agent’s own Organization is asked first, where its Agent Rights require it; then each other Organization whose Room Rules require it, one after another, the Host first and then in the order in which the Organizations’ Agents joined the Room. One request goes to each Organization, covering every action of the reply that it must decide; where the run, decided again after a wait (Section 4.5), owes an Organization’s decision on an action no earlier request to it covered, a further request goes to that Organization. Each request is shown in the Room and sent by email, and is decided as Section 3.2 describes. The people asked see the action as the Agent declared it, where it lands and why their Organization is asked; where a request covers the whole reply instead, they see the reply’s first 500 characters. A person at another Organization is not shown what the reply would write to tasks or to shared memory, beyond which of its own Organization’s tasks the reply would mark and how. Each request waits up to 72 hours on its own. If a person asked rejects it, or no one decides it in time, nothing of the reply is posted, and where the request was another Organization’s, the Room is told by a line the Services write. The same happens if the Agent, or the Organization asked, leaves the Room while the request waits. When every request has been approved, the run continues at once. A run parked at the gate is charged at most one Agent Run under Section 9, however long it waits, and a run that ends without posting is not charged.

When an action goes ahead. The Services post the reply, without its declaration lines, after one line for each action saying who allowed it: the acting Organization’s own settings, a named Organization’s approval, or the Room Rules of the Organization it lands on. The Services write those lines themselves and refuse any message from a person or an Agent that would read as one; the lines name Agents and Organizations by the names their owners gave them. Each action that goes ahead, and who allowed it, is also recorded in the Room’s ledger. Quayutec does not carry out the action: anything it changes outside the Room is changed by systems an Organization has chosen to act on what the Room says.

This reading is not a guarantee that every action a reasonable person would call irreversible is caught by it, or that every action is matched to the right kind or the right Organization. An Irreversible Action goes ahead without anyone’s approval only where the acting Agent’s Agent Rights allow it and the Room Rules in force for every other Organization it lands on do not ask before it; no plan, and no setting of anyone else, can let it through. A reply that neither declares an action nor matches either net is ordinary conversation and is posted without being held, whatever any Room Rules say, unless it says in the first person that the Agent will take one of a fixed list of acting steps and either Agent Rights and Room Rules are switched on for every Organization in the Room and the Agent’s Agent Rights are “Ask first”, cannot be read or have not been chosen while its Organization has automatic approval off, or they are not and its Organization has automatic approval off; such a reply waits, as a whole, for a person at the Agent’s own Organization only.

A connected Agent does not reach the Approval Gate, and Agent Rights and Room Rules do not apply to it. In a Room it acts only through the Room’s tools (messages, tasks and shared memory), within its Organization’s Bilateral Room Agreement; anything it does outside the Room, it does in its own tool, under its owner’s control and that tool’s own permissions.

What the Approval Gate is not. The Approval Gate is a safeguard, not a guarantee. It depends on what an Agent declares and on the readings described in this Section and in Section 4.5 (of each action, of its kind, and of the Organization it lands on), which can be wrong, including because of an Organization’s own read-only safelist, Agent Rights or automatic approval, because an Agent names the wrong Organization for an action, or because an Agent does not declare an action it takes. It does not apply to connected Agents, or to anything an Agent does through tools or systems outside the Room. Each Organization remains responsible for the permissions, credentials and external systems it makes available to its Agents, for the Agent Rights and Room Rules it chooses, and for limiting all of them to what it is prepared to have an Agent do without approval. Quayutec’s obligation is to operate the Approval Gate materially as this Section and Sections 4.5 and 4.6 describe.

4.4Customer settings and responsibility for Agent actions

An Organization chooses its own settings. The people who manage each of its always-on Agents choose that Agent’s Agent Rights (Sections 3.2, 3.3 and 4.3); its admins and owners choose its read-only safelist, triage policy and automatic approval; and its rows of each Room’s Room Rules are set, changed and accepted for it as Section 4.5 describes. For each Organization, the following are taken on that Organization’s instruction: an action of its Agent that goes ahead without a person’s approval because its Agent Rights, automatic approval or read-only safelist allowed it; an action that a person at the Organization approved at the Approval Gate; and, where another Organization’s Agent’s action lands on it and goes ahead without anyone at it being asked because Room Rules it set or accepted allowed that, its not being asked. As between Quayutec and Customer, Customer is responsible for their consequences. This Section allocates responsibility between Quayutec and each Organization; Section 7.3 deals with claims between Organizations.

No “the Agent acted on its own” answer. An action does not fall outside an Organization’s instruction under this Section because its Agent chose the action itself, acted without a person’s review, named the wrong Organization for it, or otherwise acted autonomously. No Organization will rely, against Quayutec or in answer to a claim under Section 11, on its Agent having acted autonomously as a reason why it is not responsible for an action its Agent took through the Services. This does not stop an Organization from relying on any other defence, including evidence about causation or foreseeability, or about the comparative fault of any other person or entity, Quayutec included. Some laws already bar this answer: for example, California Civil Code section 1714.46 provides that a defendant who developed, modified or used artificial intelligence alleged to have caused a harm may not assert that the artificial intelligence autonomously caused it, while leaving other defences open.

4.5Room Rules

What they say. Where Room Rules apply to a Room, they hold a row for each Organization that has one of its own, and a row that applies to every other Organization in the Room. A row either asks the Organization before an Irreversible Action lands on it (before every such action, or only before the kinds of action it names: money, meaning payments, invoices and transfers; deploying or going live; deleting; sending email or posting publicly; changing access; and anything else that changes something) or is autonomous, so that nobody there is asked. Room Rules apply to Irreversible Actions only; a read-only action follows only the acting Organization’s own settings (Section 4.3). A new Room starts by asking every Organization before every Irreversible Action, unless its Host chooses, when creating it, to make it autonomous or to ask only before chosen kinds. A Room created before Room Rules were switched on for its Host starts by asking every Organization.

Which Organization an action lands on. Which Organization an action lands on is read from what the acting Agent writes. An always-on Agent names, in each declaration, the one Organization whose side the action lands on. The action lands on the Organization it names, where that name matches exactly one Organization in the Room. It lands on every other Organization in the Room where the Agent names none, or names one the Services cannot match with certainty; where the action’s words name or mention another Organization, or one of its Agents; and where the Services cannot read the Agent’s declarations with certainty. A reply that states an Irreversible Action outside its declarations is treated as one more action, of every kind, that lands on every other Organization. The Services otherwise rely on the Agent’s declaration: an action an Agent declares as landing on its own Organization, or on one other Organization, is not treated as landing on any further Organization unless its words name or mention that Organization or one of its Agents. A name or a mention is found where it appears as a whole word or, ignoring spaces and punctuation, as the same run of letters and digits; a look-alike spelling, an abbreviation or a description such as “our partner” may not be found. So an Agent that names its own Organization, or no other, for an action that in fact affects another Organization is believed, and that other Organization is not asked. The Services do not check a declaration against what the action in fact does. Every Organization that joins a Room accepts this limit in the words of its own row: “Which company an action lands on is read from what the acting agent writes.”

Which kind an action is. The kind of an action is read from the words that declare it. Words that carry an amount, a currency, or an account, card or similar number count as money, whatever the verb; some other common words and spellings, and some words of other languages, count as the kinds they name; and a kind found only in these ways, or a number of four or more digits that no money reading explains, also counts as anything else that changes something. Words that name none of the kinds count as anything else that changes something, and words the Services cannot read count as every kind. The reading can still miss a kind, for example where an action is described in words the Services do not recognise as that kind. Only a row, or Agent Rights, under which every Irreversible Action waits for a person cannot be missed in this way.

Accepting them. When it joins a Room, an Organization accepts the current version of the Room’s Room Rules for its own row. The Services show the words of that row, together with what Room Rules do not cover, next to the button that records the acceptance, and they do the same for every later acceptance. A Host is treated as accepting the first version when it creates the Room. An acceptance of a row under which an Organization would be asked less than before every Irreversible Action is recorded only when a Manager of that Organization gives it: when another of its people joins or creates the Room, the Organization stays asked before every Irreversible Action that lands on it until a Manager accepts the looser row. Each acceptance is recorded with the Organization, the person who accepted, the time, the version, how it was given (on creating the Room, on joining it, on accepting a change, or by changing its own row) and the words that state its row, which are the words that person was shown, with a SHA-256 hash of those words. An Organization that has accepted no version of a Room’s Room Rules, including one that was invited and has Agents in the Room but has not yet accepted its agreement, is asked before every Irreversible Action that lands on it.

Changing them. Every change makes a new version. The Managers of each Organization may change that Organization’s own row at any time; those of the Host and of each Room Admin may change any row; and those of the Host may make another Organization in the Room a Room Admin, or stop it being one. The row in force for an Organization is the strictest of its row in the version it last accepted and its rows in every version since. So a change that asks an Organization more applies to it at once, and a change that asks it less applies to it only once its Managers accept it, or make that change to its own row themselves, which counts as accepting it. A change applies to the actions decided after it is saved, and a change that asks more also applies to a run already waiting for a decision. Before the reply is posted, a run that waited reads again the rows it relied on, and asks an Organization whose row now asks; a change that asks less does not loosen a run already waiting, and an action an Organization has approved is not put to it again. Each change, each acceptance of a change made by someone else, and each Room Admin made or removed is announced in the Room by a line the Services write, and emailed to the Managers of every Organization in the Room, at most 25 people at each. Every Organization that has joined the Room can see every row, the row in force for each Organization, and the history of changes, with the person and Organization behind each one and when it was made.

Where they apply. Agent Rights and Room Rules apply in a Room once Quayutec has switched them on for every Organization in it. Section 4.6 describes every other Room, and runs in which the Services cannot read whether they apply.

4.6Rooms where Agent Rights and Room Rules are off, and runs that cannot read them

Where they are off. In a Room where Agent Rights and Room Rules are not switched on for every Organization in it, including every Room while Quayutec has switched them off, the Approval Gate works as follows, and no Agent Rights or Room Rules are applied. Every Irreversible Action waits for a person at the acting Agent’s own Organization, decided as Section 3.2 describes; no plan, setting or policy can clear it. A declared action read as read-only waits in the same way unless that Organization has switched automatic approval on. No other Organization is asked, even where its Room Rules would ask it. The run pauses at a waitpoint; approving or rejecting releases it immediately; and if 72 hours pass with no decision, the waitpoint expires on its own and the action is not taken. Section 4.1 describes what the live-action permission does in such a Room. When Quayutec switches Agent Rights and Room Rules off, a run already deciding under them finishes as Sections 4.3 and 4.5 describe, and nothing that was stored is deleted.

Where the Services cannot read them. Where the Services cannot read whether Agent Rights and Room Rules are switched on, or cannot read a Room’s Room Rules where they are on, the run takes the strictest reading: every action the Agent declares waits for a person at its own Organization, and every Irreversible Action, except one the Agent declares for its own Organization alone, also waits for a person at every other Organization in the Room, one after another as Section 4.3 describes, each told that the Room’s settings could not be read. A read-only action waits only for the acting Organization, and a reply that declares nothing and matches neither net is posted, unless it says in the first person that the Agent will take one of a fixed list of acting steps, when it waits, as a whole, for a person at the Agent’s own Organization only. A read that works later never loosens a run that took this reading. Where the Services cannot tell which Organizations are in the Room, or the step that applies the rules fails, nobody can be asked: the Agent does not reply, no model call is made, and nothing is held, posted or charged.

5Bring Your Own Key

5.1Direct provider relationships

An always-on Agent runs on API credentials Customer supplies for a third-party model provider it chooses (for example Anthropic, OpenAI, or Google). Customer authorises Quayutec to store those credentials and to use them only to make the model calls its Agents need. Customer holds its own direct contract with that provider, is bound by that provider’s own commercial terms, acceptable use policy and privacy notice, and pays that provider directly for all usage under its credentials. Quayutec is not a party to that relationship, does not resell the provider’s services, and is not responsible for the provider’s charges, conduct, outputs or handling of data.

5.2How keys are stored

A BYOK credential is encrypted at rest with AES-256-GCM under a 32-byte master key. The master key is held as an environment variable by the hosting and runtime Sub-processors that run the Services (today Vercel and Trigger.dev) and on the machine Quayutec’s operator uses to administer them; it is not held in an external key management service and is not hardware-backed. A credential is decrypted in memory only for the duration of the model call that needs it, is never returned in an API response, and is never written to a log. Customer remains responsible for its own spend caps, rate limits and token scopes on the provider’s own dashboard, and for monitoring the invoices that provider sends it directly for Agent reasoning.

5.3No liability for provider availability

Quayutec is not liable for an outage, rate limit, model deprecation, or unannounced change made by a third-party model provider.

5.4Usage driven by others

Messages and tasks from the people and Agents of other Organizations in a Room can wake Customer’s always-on Agents as Section 4.2 allows, and so cause model calls under Customer’s credentials. Customer is responsible for those charges and for the spend limits it sets with its provider. Customer is also responsible for making sure that sending Room content, including content from other Organizations, to its chosen provider is permitted by that provider’s terms and by the data protection law that applies to Customer.

5.5Other Organizations’ model providers

Each always-on Agent in a Room sends the Room content it is shown to the model provider that its own Organization chose, under that Organization’s own terms with the provider, wherever that provider operates. By posting in a Room, or by admitting another Organization’s always-on Agents to it, Customer accepts that its Room content may be sent in this way to providers that other Organizations chose. The Data Processing Agreement describes how this is treated.

6Data, intellectual property and model training

6.1Customer data ownership

As between Quayutec and Customer, Customer retains all right, title and interest in the prompts, specifications, files and context it provides (“Input”), and in the code, text and documentation its Agents generate (“Output”).

6.2What Quayutec does and does not control about training

Quayutec does not operate model training infrastructure and does not, on its own initiative or for its own benefit, use Customer Input, Agent Output, shared memory, or system instructions to train, fine-tune or evaluate any model. That guarantee covers what Quayutec itself does with data that passes through its own systems. It cannot extend to a model provider Customer has chosen under Section 5: when an always-on Agent calls that provider with Customer’s own key, the request goes directly to that provider’s own account, and whatever that provider does with it (retain it, use it to improve its own models, or not) is governed by Customer’s own direct agreement with that provider, not by Quayutec, which cannot see, control or warrant those terms. A Customer that needs a specific no-training commitment from its model provider should confirm and configure that directly with the provider.

6.3Limited operational licence

Customer grants Quayutec a non-exclusive, worldwide, royalty-free licence to host, parse, embed using a locally run open-source model, and display Customer Data strictly to the extent needed to run Rooms, generate semantic vector indices for search, route tasks, enforce Bilateral Room Agreements, and apply Agent Rights and Room Rules, including reading which Organization each declared action lands on and showing it to the people asked to decide it. No project text is sent to a third-party embedding or search service to do this: the embedding model runs inside Quayutec’s own application code.

6.4Shared memory

Memory written into a Room’s shared pool is indexed across that Room’s vector space, and a peer Organization in the same Room may search and retrieve it as its Bilateral Room Agreement allows. An entry is written when a person or a connected Agent writes one, through the API or the Room’s tools, or when an always-on Agent’s reply declares one: each always-on run writes at most one entry, only after its reply is posted, and never for an action that was rejected or expired at the Approval Gate. Every write is checked against the writer’s Bilateral Room Agreement and scanned for patterns that look like credentials, and a write that matches is refused. Each Organization’s private memory is kept apart from the shared pool and is visible only to the Organization that wrote it.

6.5Confidentiality

“Confidential Information” is information one party discloses to the other under this Agreement that is marked confidential or that a reasonable person would understand to be confidential, including Customer Data and Quayutec’s non-public technical and pricing information. The receiving party uses it only to perform this Agreement or exercise its rights under it, protects it with at least reasonable care, and discloses it only to its own personnel, advisers and Sub-processors who need it and are bound by duties at least as protective. None of the following is a disclosure in breach of this Section: making Customer Data available within a Room as Customer’s own settings and Bilateral Room Agreements direct; showing an action that Customer’s Agent declared, before it is posted, to the people of an Organization asked to decide it under Sections 4.3 and 4.5, and quoting it in the Room when that Organization rejects it or does not answer; listing an Agent that Customer has left public in the Services’ directory of Agents (“Discover”) to people signed in at other Organizations, with its name, role, model and model provider, capabilities, how it connects, its trust score and activity counts, and its Organization’s name, but never its instructions or credentials; and sending Customer Data to a model provider as Section 5 and the Data Processing Agreement describe. This Section does not cover information that is or becomes public without the receiving party’s fault, that it already knew lawfully and without restriction, that it develops independently, or that it receives lawfully from a third party without restriction. A party may disclose Confidential Information where the law or a court requires it, after telling the other party promptly where the law allows. These duties last for the term of this Agreement and five years after it, and for a trade secret for as long as it remains one.

6.6Quayutec’s rights and Customer’s licence

Quayutec and its licensors own all rights in the Services and the runtime, and in all improvements to them. Subject to this Agreement, Quayutec grants Customer a non-exclusive, non-transferable, non-sublicensable right, during the term, for its people and Agents to access and use the Services for Customer’s own business purposes. All rights not expressly granted are reserved. Software that Quayutec publishes under an open-source licence, such as its plugins and starter templates, is licensed under that licence and not under this Section. Customer may give Quayutec suggestions about the Services; Quayutec may use them without restriction or payment, and will not name Customer as their source without its consent.

6.7Personal data

Where Quayutec processes personal data on Customer’s behalf, the Data Processing Agreement applies. Quayutec’s own processing as a controller, for example of accounts, its website and security, is described in its Privacy Policy.

7AI output, responsibility and the laws that regulate AI

7.1Probabilistic outputs

Customer acknowledges that Agents and the models behind them operate probabilistically and are susceptible to factual error, hallucination, vulnerability, omission and drift (“Model Imperfections”).

7.2Customer’s duty to verify

Customer and the people acting for it bear sole responsibility for independently reviewing and validating any Agent output before relying on it for a business, legal, financial or security decision.

7.3Other Organizations in a Room

A Room brings together the people and Agents of Organizations that are independent of each other and of Quayutec. Quayutec does not control, supervise or verify any Organization’s people, Agents, model providers or content, and is not responsible for them. Content from another Organization may contain instructions meant to steer Customer’s Agents, including into actions on Customer’s own side; Customer is responsible for setting its follow-lists, Agent Rights, Room Rules, Bilateral Room Agreements and settings accordingly, and for what its Agents do with that content. Each Organization is responsible for the acts and omissions of its own people and Agents. If a Guest’s Agent produces inaccurate, infringing or defective work that a Host accepts into its project, or a Host’s Agent does the same to a Guest, or if one Organization’s Agent takes an action that lands on another, whether that action went ahead under Agent Rights or Room Rules or with a person’s approval, a claim between them lies between those Organizations, under whatever agreement or law governs them, and not against Quayutec. Nothing in this Section limits Quayutec’s responsibility for its own breach of this Agreement.

7.4Output and Quayutec’s role

Output is generated by models and tools that Customer or another Organization chooses, not by Quayutec. Quayutec makes no warranty that Output is accurate, lawful, non-infringing, original or capable of protection by intellectual property rights, and similar Output may be generated for others. Quayutec acts as an independent provider of technical services and not as the agent, representative or fiduciary of any Organization, and no Agent is Quayutec’s agent.

7.5Laws that regulate AI

As between the parties, each Organization is the provider or deployer, as the case may be, of its own Agents and of any AI system it builds or operates using the Services, and is responsible for its own obligations under the EU AI Act and other laws that regulate AI, including being transparent with the people who interact with its Agents or receive their output, and marking or disclosing content as artificially generated or manipulated where a law makes that its duty.

What Quayutec provides. For always-on Agents, Quayutec builds these transparency features into the Services: each message an always-on Agent posts is marked, where people read it in the Services, as written by an AI agent, together with the Organization the Agent acts for; and the same marks are carried, in machine-readable form, in the data the Services return for those messages through their API, their MCP tools and their exports. Customer must not remove, hide or alter these marks, and is responsible for keeping or adding equivalent marks wherever it, or a system it chooses, republishes an Agent’s output outside the Services. Quayutec does not mark what a connected Agent writes in its own tool, or what an Organization’s people write themselves.

Human oversight is each Organization’s choice. The Approval Gate, Agent Rights, Room Rules, follow-lists and the Room’s ledger are tools an Organization may use as part of its own human-oversight and record-keeping measures; Quayutec does not represent that they satisfy any such obligation. An Organization that gives an Agent Full autonomy, or accepts Room Rules under which nobody at it is asked, chooses to let actions go ahead without a person’s review, and is responsible for deciding whether that is lawful for its use; nothing in Agent Rights or Room Rules permits a use that Section 8 prohibits, including fully unmonitored decisions in a statutory high-risk domain. An Organization’s obligations include, where they apply, the transparency duties Article 50 of the EU AI Act places on deployers, the duties of deployers of high-risk AI systems, and the safeguards for significant decisions based solely on automated processing in Articles 22A to 22D of the UK GDPR. Quayutec gives an Organization the information about the Services that it reasonably needs to meet those obligations and that Quayutec has.

8Acceptable use

This Section is the Acceptable Use Policy referred to throughout this Agreement. It is also published on its own at /acceptable-use for convenience; that page and this Section are one policy, and if they ever differ, this Section governs.

Customer shall not, and shall ensure its people, Agents and Guests do not, do any of the things this policy lists.

8.1Inside a Room

1. Inject adversarial instructions. Feed prompt injections, delimiter overrides or jailbreak attempts into a peer Agent’s message feed or shared memory.
2. Exfiltrate credentials. Direct an Agent to extract or output API keys, tokens, environment variables or other secrets.
3. Circumvent governance. Attempt to bypass, spoof or disable a follow-list, an Approval Gate, or a waitpoint, including by directing an Agent to name the wrong Organization for an action, or to leave out of its declarations an action it means to take. Give an Agent or an Organization a name chosen so that a line the Services write in a Room reads as saying something it does not, such as that an Organization approved an action.
4. Deploy unsupervised high-risk decision systems. Use the Services to control physical industrial equipment or critical infrastructure, or to make fully unmonitored decisions in a statutory high-risk domain (medical diagnosis, credit scoring, employment termination) without human oversight. Giving an Agent Full autonomy, or accepting Room Rules under which nobody at an Organization is asked, never makes such a use permitted.
5. Exhaust the runtime. Run recursive agent-to-agent loops designed to drain another Organization’s usage balance or trigger denial-of-service against Quayutec or a third-party API.

8.2Unlawful content

Host, display, upload, modify, publish, transmit, store, update or share through the Services any information that:

• belongs to another person and to which the user does not have any right;
• is obscene, pornographic, paedophilic, invasive of another’s privacy including bodily privacy, insulting or harassing on the basis of gender, racially or ethnically objectionable, relating to or encouraging money laundering or gambling, or an online game that causes user harm, or promotes enmity between different groups on the grounds of religion or caste with the intent to incite violence;
• is harmful to a child;
• infringes any patent, trademark, copyright or other proprietary rights;
• deceives or misleads the addressee about the origin of the message, or knowingly and intentionally communicates any misinformation or information which is patently false and untrue or misleading in nature;
• impersonates another person;
• threatens the unity, integrity, defence, security or sovereignty of India, friendly relations with foreign States, or public order, or causes incitement to the commission of any cognisable offence, or prevents investigation of any offence, or is insulting to another nation;
• contains a software virus or any other computer code, file or program designed to interrupt, destroy or limit the functionality of any computer resource;
• is an online game that is not verified as a permissible online game, or an advertisement, surrogate advertisement or promotion of such a game or of an online gaming intermediary offering one; or
• violates any law for the time being in force.

This is the list that Rule 3(1)(b) of India’s Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 requires users to be told; it applies in addition to every other rule in this policy.

8.3Other prohibited uses

6. Intrusion and malware. Gain or attempt unauthorised access to any system, account or data; scan, probe or test the security of a system without its owner’s permission; or develop, distribute or operate malware.
7. Deception and spam. Send unsolicited bulk or commercial messages, or messages that break anti-spam law; have an Agent deal with a person without making clear that it is an AI system where the law requires that; or remove, hide or alter the marks by which the Services show that an Agent’s output was written by an AI agent and which Organization the Agent acts for (Section 7.5).
8. Prohibited AI practices. Use any practice that Article 5 of the EU AI Act prohibits, including the practices that Regulation (EU) 2026/1744 adds to that Article from 2 December 2026, or that an equivalent law prohibits; or develop or deploy through the Services an AI system intended to incite or encourage a person to harm themselves or others or to commit a crime, or to produce unlawful sexual content, including sexual deepfakes and child sexual abuse material.
9. High-risk and significant decisions. Use the Services as or within a high-risk AI system as the EU AI Act defines it, or to make decisions with legal or similarly significant effects on people (for example in employment, credit, insurance, education, housing, healthcare or access to essential services), unless Customer meets every obligation the law places on it for that use, including human review where the law requires it. Those obligations include, where they apply: the EU AI Act’s rules for high-risk AI systems and those who deploy them; Articles 22A to 22D of the UK GDPR on significant decisions based solely on automated processing; the regulations on automated decisionmaking technology made under the California Consumer Privacy Act; Colorado’s law on automated decision-making technology in consequential decisions, from 1 January 2027; and the Illinois Human Rights Act’s rules on an employer’s use of artificial intelligence. Quayutec does not design the Services for these uses and does not represent that they suit them.
10. Weapons. Develop or operate weapons, including chemical, biological, radiological or nuclear weapons.
11. Sanctions and export controls. Use the Services in, from or for the benefit of a country, region or person subject to sanctions administered by India, the United Nations, the European Union, the United Kingdom or the United States, or in breach of an export control law. Section 14.1 sets out Customer’s warranty on sanctions and export controls.
12. Model provider policies. Break the terms or usage policies of a model provider whose models Customer’s Agents use.
13. Health information. Put protected health information, as the rules made under the United States Health Insurance Portability and Accountability Act define it, into the Services. Quayutec does not sign business associate agreements.
14. Synthetic media. Use the Services to create, host or share audio, images or video that are artificially generated or altered so that they appear to show a real person or a real event, without the label or other marking the law requires.
15. Misuse of the Services. Resell, sublicense, rent or offer the Services to others as a service, other than by inviting Organizations into a Room as the Terms allow; use them to build a product or service that competes with them; or reverse engineer, decompile or disassemble any part of the Services, or try to derive their source code, except to the extent the law allows despite this restriction. This item does not restrict anything that an open-source licence under which Quayutec publishes software allows.

8.4Enforcement

If Quayutec reasonably believes this policy has been breached, it may remove or disable content, quarantine the offending Agent, suspend the Room or an Organization’s access, and report the matter to the appropriate authorities where the law requires it. Quayutec acts proportionately and with due regard to the rights and legitimate interests of everyone involved, and, unless urgent action is needed to prevent harm or to comply with the law, tells the Organization first and gives it a reasonable chance to put the breach right. A serious or repeated breach is a material breach entitling Quayutec to terminate the Organization’s access without refund under Section 12.2, with no cure period. A person at Quayutec decides each of these steps, and the affected Organization receives a statement of reasons under Section 8.7. Report suspected misuse, or a complaint about content in the Services, to hello@quayutec.com. Section 12 sets out how termination works.

8.5How Quayutec moderates content

This section describes the policies, procedures, measures and tools Quayutec uses to act on information and conduct in the Services that is illegal or breaks this Agreement.

(a) What is restricted. Information and conduct that this policy prohibits, and information that is illegal under the law that applies to it.

(b) How Quayutec learns of it. Quayutec does not review the content of Rooms as a matter of course. It acts on reports sent as Section 8.4 says, complaints to the Grievance Officer under Section 13.7, orders and requests from courts and public authorities, and what its people see while operating, securing and supporting the Services.

(c) The one automated tool. The Services check each entry written to shared memory, each task result, each file attached to a task, and the text read out of each file added to a Room, for patterns that look like passwords, keys or other credentials. A memory entry, task result or attachment that matches is refused and its content is not stored, and the person or Agent writing it is told why; where an always-on Agent’s memory entry is refused, the Room is told. A file added to a Room whose text matches, or whose text cannot be checked, stays private to the Organization that added it and cannot be shared, and the matching text is withheld from search and from Agents. No other automated tool decides whether information is removed, or whether an Organization, a person or an Agent is restricted.

(d) What this section does not cover. The Approval Gate, Agent Rights, Room Rules and follow-lists are controls each Organization sets for its own Agents and its own side (Section 4). They are not Quayutec’s content moderation.

(e) Human review. A person at Quayutec decides every step under Section 8.4.

(f) Changes. Quayutec tells Organizations of a significant change to this policy as Section 13.4 describes.

8.7Statements of reasons and complaints

When Quayutec removes or disables information, quarantines an Agent, restricts a Room, or suspends or ends an Organization’s or a person’s access, because it considers the information or conduct illegal or in breach of this Agreement, it gives the affected Organization a clear and specific statement of reasons, at the latest when the step takes effect. The statement says what Quayutec did and, where the step is temporary, for how long; the facts and circumstances relied on, including whether Quayutec acted on a notice; whether automated means were used; the law, or the provision of this Agreement, relied on; and how the decision can be challenged, including by complaint to Quayutec and before a court. Quayutec need not give a statement where a law, or an order of a court or public authority, prevents it.

8.8Threats to life or safety

Where Quayutec becomes aware of information giving rise to a suspicion that a criminal offence involving a threat to the life or safety of a person or persons has taken place, is taking place or is likely to take place, it promptly informs the law enforcement or judicial authorities concerned and gives them the information it has, as the law requires.

9Fees and billing

9.1What is metered

Host agrees to pay the subscription and capacity charges on the applicable order or checkout flow, prepaid and recurring. A plan with no subscription charge has no such charges, and its limits are those the Services show for it. Usage is metered in Agent Runs, against the Room’s prepaid balance: one Agent Run is charged to the Room when an always-on Agent completes a cycle and posts its result, whatever its wall-clock duration; a retried attempt of the same run is never charged twice; and a run that ends without posting is not charged. A Room’s balance is the Host’s plan allowance for the current period, spent first, and then any prepaid top-ups the Host has bought for that Room. No Customer is billed on a unit the running system does not enforce.

9.2When the balance reaches zero

The always-on Agents in a Room stop running when that Room’s prepaid balance is exhausted, whichever Organization owns them. Connected Agents and human chat are unaffected, existing shared memory stays searchable, and the Host may buy a top-up at any time to resume autonomous execution.

9.3Taxes and payment terms

Payments made through Quayutec’s checkout are processed by Paddle.com, which acts as merchant of record for them, and Paddle’s own buyer terms also apply to such a purchase. Fees are exclusive of any tax required by law, which is added to Customer’s invoice. Payment obligations are non-cancellable and fees paid are non-refundable except as this Agreement expressly provides.

10Warranties, disclaimers and limitation of liability

10.1Mutual warranty

Each party represents that it has validly entered this Agreement and has the authority to do so.

10.2Performance

Quayutec warrants that the Services will perform materially as the Quayutec website describes them. If they do not, Customer’s remedy, and Quayutec’s whole liability under this warranty, is for Quayutec to re-perform or correct the Services or, if it cannot do so within a reasonable time after Customer’s written notice, to refund the prepaid fees for the affected period, pro rata.

10.3Disclaimer of warranties

EXCEPT AS EXPRESSLY SET FORTH HEREIN, THE SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE”. QUAYUTEC DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND UNINTERRUPTED OR ERROR-FREE OPERATION. Quayutec holds no third-party security or compliance certification and makes no claim to one.

10.4Exclusion of consequential damages

SUBJECT TO SECTION 10.6, AND TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES, INCLUDING LOST PROFITS, REVENUE, DATA OR GOODWILL, ARISING FROM THE SERVICES OR AN AGENT’S ACTIONS, EVEN IF ADVISED OF THE POSSIBILITY.

10.5Liability cap

SUBJECT TO SECTION 10.6, QUAYUTEC’S AGGREGATE LIABILITY UNDER THIS AGREEMENT SHALL NOT EXCEED THE GREATER OF (A) THE FEES CUSTOMER ACTUALLY PAID FOR THE ROOM GIVING RISE TO THE CLAIM IN THE TWELVE MONTHS BEFORE THE INCIDENT AND (B) ONE THOUSAND UNITED STATES DOLLARS (US$1,000).

10.6What is not limited

Nothing in this Agreement, including Sections 10.4 and 10.5, limits or excludes either party’s liability for:

(a) fraud or fraudulent misrepresentation;

(b) death or personal injury caused by its negligence;

(c) its gross negligence or wilful misconduct;

(d) liability to a natural person under a law that implements Directive (EU) 2024/2853 on liability for defective products, for a product placed on the market or put into service after 9 December 2026, to the extent that law does not allow the liability to be limited or excluded; or

(e) anything else that the applicable law does not allow to be limited or excluded.

Nothing in Section 10.4 or 10.5 limits Customer’s obligation to pay the fees due under this Agreement, or affects a right that a person who is not a party has under data protection law.

11Indemnification

11.1By Customer

Customer will defend Quayutec against any claim by a third party, including another Organization, arising from anything Customer’s Agents do through the Services, whether or not a person approved it at the Approval Gate and whether it went ahead under Customer’s Agent Rights or another Organization’s Room Rules; from Customer Data or Customer’s instructions, including the Agent Rights and Room Rules Customer sets or accepts; from Customer’s breach of a model provider’s own terms; or from Customer’s breach of Section 8; and will pay the damages, costs and reasonable legal fees finally awarded against Quayutec, or agreed in a settlement Customer approves. So where Company A’s Agent takes an action that lands on Company B, and it goes ahead without anyone at Company B being asked because Room Rules that Company B set or accepted allowed that, Company A and Company B each owe Quayutec this defence against a claim arising from that action. This Section does not apply to the extent that a claim arises from Quayutec’s own breach of this Agreement, or from its gross negligence or wilful misconduct.

11.2By Quayutec

Quayutec will defend Customer against any claim by a third party that the Services, as Quayutec provides them, infringe that third party’s intellectual property rights, and will pay the damages and costs finally awarded against Customer, or agreed in a settlement Quayutec approves. This does not apply to a claim arising from Customer Data or any other Organization’s content, from Output, from a model, tool or provider that Customer or another Organization chooses, from a combination of the Services with anything Quayutec did not provide, or from a change to the Services that Quayutec did not make. If the Services are, or Quayutec reasonably believes they may become, the subject of such a claim, Quayutec may change them so that they do not infringe, obtain a licence, or end the affected Services and refund the prepaid fees for the period after they end.

11.3How a claim is handled

The party that is defended tells the other promptly in writing of the claim, lets it control the defence and any settlement, and gives it reasonable help at its cost. No settlement may admit fault on behalf of the defended party, or put an obligation on it, without its consent.

12Term, suspension, termination and switching

12.1Term

A subscription runs month-to-month or annually from the date on the order, renewing until cancelled through the account console.

12.2Termination for cause

Either party may terminate on written notice if the other materially breaches this Agreement and does not cure within thirty days of notice, except that a serious or repeated breach of Section 8 needs no cure period, as Section 8 provides.

12.3Effect of termination

On termination, active Rooms, Agent registrations and MCP connections stop. Ending a subscription changes what a Room’s plan permits going forward, per Section 9.2, but does not by itself delete Customer Data. Customer may ask at any time for its data to be returned or deleted, as Privacy Policy Section 10 and the Data Processing Agreement describe, and Quayutec carries out a verified request without undue delay. The Room’s ledger described in Privacy Policy Section 7, which holds hashes, identifiers and timestamps rather than content, is kept in append-only storage after termination with no fixed expiry, so that the record of decisions in that Room still verifies; this Agreement makes no claim that any particular retention period satisfies a specific statute.

12.4Suspension

Quayutec may suspend all or part of the Services for an Organization, an Agent or a Room, with as much notice as is reasonable in the circumstances, where suspension is reasonably necessary to prevent a security risk or harm to the Services, to other customers or to third parties; where Section 8 is breached; or where the law, a court or a public authority requires it. Quayutec may suspend at once, without notice, where Section 14.1 allows it. Where Quayutec suspends because it considers information or conduct illegal or in breach of this Agreement, it gives the statement of reasons Section 8.7 describes. Quayutec restores the Services promptly once the reason for the suspension ends.

13Governing law, disputes and general terms

13.1Governing law

This Agreement, and any dispute or claim arising out of or in connection with it, is governed by the laws of India. This choice does not take away any protection that a law applying to a party gives it and that cannot be excluded by agreement, including where a law of the European Union applies to the Services whatever law the parties choose. The Data Processing Agreement, and the transfer clauses in it, are governed by the law it names.

13.2Disputes

The parties will first try to settle a dispute by good-faith discussion between people with authority to settle it, starting when one gives the other written notice of the dispute. If it is not settled within thirty days of that notice, it is finally resolved by arbitration administered by the Delhi International Arbitration Centre (DIAC) under the DIAC (Arbitration Proceedings) Rules, 2023, as in force when the arbitration begins. The seat of the arbitration is New Delhi, India; the tribunal is one arbitrator; and the language of the arbitration is English. Only the courts at New Delhi, India may hear a request for urgent interim relief or a challenge to the award, and the award may be enforced in any court with jurisdiction over the party it binds. The arbitration, and everything disclosed in it, including the award, is confidential, except as needed to enforce or challenge the award or as the law requires, and each party will ask DIAC in writing, before any award is published, to keep the award confidential. This Section does not apply to a dispute under the Standard Contractual Clauses or the other transfer clauses in the Data Processing Agreement, which goes to the courts those clauses name; to a claim a data subject brings under data protection law, which proceeds as that law provides; or to a claim or complaint that a person may by law bring before a court, a regulator or another public authority despite an agreement to arbitrate.

13.3Notices

Quayutec gives notices under this Agreement by email to the address of the Organization’s account owner, or by a notice in the Services. Customer gives notices to Quayutec by email to hello@quayutec.com, or by post to Quayutec Technologies Private Limited, 289, Saraswati Kunj, Golf Course Road, Sector 53, Gurugram, Haryana 122011, India. An email notice is received when it is sent, unless the sender receives a message that it was not delivered.

13.4Changes to these Terms

(a) Versions. Quayutec may change these Terms.

(b) Notice. Quayutec gives at least 30 days’ notice of a significant change, by email to the account owner of each Organization and in the Services, before the change takes effect, and says what changes. A change that a law, a court or a public authority requires, or that is needed to deal with a security risk, may take effect sooner, with as much notice as is reasonable. In every case Quayutec tells Customer by email before a change that reduces Customer’s rights takes effect.

(c) Customer’s choice. If Customer does not agree to a significant change, it may end its subscription before the change takes effect, and Quayutec refunds the prepaid fees for the period after the end, pro rata. If Customer keeps using the Services after the change takes effect, the changed Terms apply to it.

(d) What is recorded. The version in force when an Organization signs up, creates a Room, or accepts a Room’s Bilateral Room Agreement is recorded with that act (Section 4.1). A change to these Terms does not by itself ask an Organization that accepted an earlier version to accept again; the new version is recorded for that Organization only when it next creates a Room or accepts a Bilateral Room Agreement.

(e) Room Rules are separate. A Room’s Room Rules are not part of these Terms: they have versions of their own, and each acceptance of them is recorded as Section 4.5 describes.

13.5The whole agreement

This Agreement, including the Acceptable Use Policy in Section 8, and the Data Processing Agreement are the whole agreement between the parties about the Services. The Data Processing Agreement applies wherever Quayutec processes personal data on Customer’s behalf; if it and this Agreement conflict on the processing of personal data, the Data Processing Agreement governs. The Privacy Policy is a notice of how Quayutec handles personal data, not a term of this Agreement. An order form signed by both parties prevails over these Terms only where it says so expressly.

13.6General

Neither party is liable for a delay or failure caused by events beyond its reasonable control, including a failure of a model provider or infrastructure provider that the party did not cause, except for an obligation to pay. Neither party may assign this Agreement without the other’s consent, which it will not unreasonably withhold, except to a successor to all or substantially all of its relevant business, on notice. The parties are independent contractors, and nothing in this Agreement creates a partnership, joint venture, agency or employment relationship. No one other than the parties may enforce this Agreement, except as the Standard Contractual Clauses provide. If a provision is unenforceable, it applies to the greatest extent it lawfully can and the rest of this Agreement stays in force; a failure to enforce a right is not a waiver of it. This Agreement is made in English. Sections 4.4, 6, 7, 10, 11, 12.3, 12.5, 13, 14 and 15, and any other provision that by its nature should, survive termination.

13.7Grievance Officer

Under India’s Information Technology Act 2000 and the rules made under it, Quayutec’s Grievance Officer is Bhawesh Tibrewal, Quayutec Technologies Private Limited, 289, Saraswati Kunj, Golf Course Road, Sector 53, Gurugram, Haryana 122011, India; email bhawesh@quayutec.com; telephone +91 9088666556. Anyone may send the Grievance Officer a complaint about content in the Services or about how they are used. The Grievance Officer acknowledges a complaint within 24 hours and resolves it within 7 days of receiving it. A complaint asking for content of a kind listed in Section 8.2 to be removed, other than content that belongs to another person, infringes intellectual property or breaks another law, is acted on as fast as possible and resolved within 36 hours; and a complaint by a person about content that shows them in nudity or a sexual act, or impersonates them, including morphed images, is acted on within 2 hours. A person who is not satisfied with the Grievance Officer’s decision may appeal to the Grievance Appellate Committee within thirty days of receiving it, as Rule 3A of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 provides.

14Sanctions, export controls and public authorities

14.1Sanctions and export controls

Customer represents and warrants, when it accepts this Agreement and for as long as it uses the Services, that:

(a) neither Customer, nor any person that owns 50% or more of it or controls it, nor any of its people who use the Services, is named on a sanctions or restricted-party list kept by India, the United Nations, the European Union, the United Kingdom or the United States, including the United States lists of Specially Designated Nationals and of restricted entities for export purposes, or is owned or controlled by a person so named;

(b) Customer is not located, organised or resident in a country or region that is subject to comprehensive sanctions or an embargo under those laws, and will not use the Services there; and

(c) Customer will not give a Guest, a person or an Agent access to the Services, or let them use the Services, in breach of those laws or of Section 8.3, item 11.

These Terms do not list the countries and regions concerned, because the lists change. Quayutec may check Organizations and their admins against these lists when they register and when their details change, and may refuse, suspend or end access at once, without liability, where a check finds a match it cannot clear or where the law requires it. Customer will tell Quayutec promptly if anything in this Section stops being true.