Terms and conditions

The terms you agree to when you use Nessie Cloud.

This is a draft. It describes how Nessie actually works today, but it has not been reviewed by a lawyer and Nessie has not launched. Treat it as a statement of intent, not as a finished contract.

1. Who you are agreeing with

Nessie is made by UnlikeOtherAI s.r.o., a company registered in the Czech Republic. In these terms, “we” and “us” mean that company, and “you” means the person or organization using Nessie.

Missing: the company registration number (IČO) and the registered office address.

Missing: the VAT number, if the company is VAT registered.

Missing: the effective date of these terms.

2. Using Nessie Cloud

These terms cover Nessie Cloud: we run Nessie for you, and you pay us a monthly fee.

3. Nessie Cloud: accounts and signing in

Nessie Cloud has no passwords of its own. You sign in through UnlikeOtherAI SSO, which is the authority for who you are, which organization you belong to and which teams you are in. Your account, your profile and your organization’s membership are created and changed there, not in Nessie.

That has three practical consequences. Your administrators in UnlikeOtherAI control who can reach your Nessie tenant. Removing somebody there removes their access here. And if you close your UnlikeOtherAI account, you lose access to Nessie Cloud with it.

You are responsible for what happens under your organization’s accounts. Tell us at hello@nessie.works if you believe an account has been misused.

4. Acceptable use

However you use Nessie, do not:

• break the law with it, or use it to help somebody else break the law;
• use it to harass, defraud, impersonate or harm people — including by having an agent send email that pretends to be somebody it is not;
• attempt to reach another customer’s data, break out of your tenant, or interfere with the isolation between organizations;
• connect a mailbox, a calendar, an MCP server or any other account you are not authorized to connect;
• point an agent’s tools at infrastructure you do not control in order to attack or overload it;
• resell or rebrand Nessie Cloud, or use it as the backend of a competing product.

Nessie tries to keep credentials out of conversations: a scanner refuses messages that look like they contain a secret, and offers to store the value in a vault instead. That is a safety net, not a guarantee. Keeping credentials out of chat is still your responsibility.

5. Fees, billing and tax

Nessie Cloud is billed monthly. The published prices are:

You can bring your own AI accounts. If you connect AI accounts you already pay for — including subscriptions — your agents run on them and we add no charge for that inference. You pay your provider directly, on their terms. If you use the models we provide instead, we bill per token.

Nessie records every model call in a token-cost ledger: the provider, the model, the token counts and an estimated cost, broken down by organization, team, project, channel, agent and person. That ledger is what usage charges are based on, and you can see it.

Billing itself sits in UnlikeOtherAI rather than inside Nessie. Your statement, your subscription and your payment details live there, and card payments are processed by Stripe. Nessie holds no card details, no subscription and no invoice of its own.

Missing: whether prices are stated excluding VAT, how VAT applies to customers inside and outside the Czech Republic, and how the reverse charge is handled for EU business customers.

Missing: payment terms — when an invoice falls due, what happens if it is not paid, whether there is a refund or a pro-rata credit when you remove users mid-month, and how much notice we give before a price change.

6. Your data, and who owns it

Your content stays yours. Messages, files, documents, tasks, agent configuration and everything else you put into Nessie belong to you. We do not claim ownership of it, and we do not sell it.

We process it in order to run the service: to store and deliver it, to send it to the model provider your deployment is configured with when an agent runs, to index it so agents and search can find it, and to keep the audit trail and the cost ledger the product is built around. What happens to personal data, and who else touches it, is set out in the privacy policy.

If you self-host, we hold none of it. It is on your infrastructure and we never see it.

Missing: a data processing agreement (DPA) for Nessie Cloud customers, which EU business customers will ask for before signing. There is no published DPA yet.

7. AI employees, and what you are responsible for

Nessie’s agents are software. They are not people, not employees and not professional advisors. They produce output by asking a language model, which means the output can be wrong, incomplete or invented — and wrong in a way that reads as confident.

You are responsible for what your agents do. You decide which agents exist, what they can reach, which tools they hold, which mailboxes they can use, and what runs without a person looking at it first. Nessie gives you approval gates that hold consequential actions until somebody accepts them, an audit trail of what each agent did and what was refused, and per-agent scoping so an agent sees only the channels, projects and documents you gave it. Whether you switch those protections on, and where you set the line, is your decision.

Agents can send email from a real address, reply in a mailbox you connected, call external tools and act on other systems. When they do, that is your organization acting. Do not use agent output for anything legal, medical, financial or safety-critical without a qualified person checking it.

8. Availability and support

We want Nessie Cloud to be reliable, and we would rather tell you what we do not promise than promise something we cannot keep.

• There is no uptime commitment. We publish no SLA and we owe no service credits.
• We deploy changes to Nessie Cloud continuously. We may change, add or remove features, and something you rely on may work differently after an update.
• Parts of Nessie depend on services we do not run — model providers, mail providers, browser and search providers, identity. When one of those is down or refuses a request, that part of Nessie stops working, and we cannot fix it for you.
• Support is by email at hello@nessie.works.

Missing: support hours, target response times, any maintenance window, and whether a paid support or SLA tier will exist.

9. Warranties

For Nessie Cloud we provide the service with reasonable skill and care. Beyond that, and to the extent the law allows, we give no warranty: not that the service will be uninterrupted or error-free, not that it will meet your requirements, and not that anything an AI model produces through it will be accurate.

10. Liability

Nothing here limits liability that cannot be limited by law — including liability for death or personal injury caused by negligence, and for fraud.

Subject to that, and to the extent the law allows, we are not liable for indirect, special, incidental or consequential loss, for lost profits, lost revenue or lost business, or for loss or corruption of data, even if we were told the loss was possible.

Missing: the cap on our total liability to a Nessie Cloud customer. This needs a specific figure or formula — a common one is the fees paid in the twelve months before the claim — and we will not invent one here.

11. Termination

You can stop using Nessie Cloud at any time by canceling your subscription. We can suspend or end your access if you breach these terms, if fees go unpaid, or if the law requires it. Where it is reasonable to do so, we will tell you first and give you a chance to fix the problem.

If we stop offering Nessie Cloud altogether, we will give you notice and a period in which to get your data out.

Missing: a stated period after termination during which we keep your data available for export, and the point at which it is deleted. There is no self-service export and no self-service deletion in the product today — both are done by hand on request — so no dated contract can honestly be published yet.

12. Changes to these terms

We may update these terms. When a change materially affects Nessie Cloud customers, we will tell you before it takes effect, and the updated version will be published on this page with its date. If you do not accept a change, your remedy is to stop using Nessie Cloud and cancel.

Missing: how much notice we give before a material change takes effect, and whether notice is by email or only by publishing here.

13. Governing law and jurisdiction

These terms are governed by the law of the Czech Republic, and the courts of the Czech Republic have exclusive jurisdiction over any dispute arising from them or from your use of Nessie. If you are a consumer, this does not remove any protection you have under the mandatory law of the country you live in.

If any part of these terms is found unenforceable, the rest stays in force.

14. Contact

Write to hello@nessie.works about anything on this page.