The agreement, in plain sentences.
Written to be read once and understood, rather than skimmed and accepted. Where a term depends on who is running this deployment rather than on the software, the slot is left visible instead of filled with a plausible guess.
Effective
01What this covers
These terms govern your use of this Verity deployment. Your agreement is with the organisation operating it, operatorlegal entity, not with the authors of the software. Using the service means you accept them.
The Verity source code is separately licensed. Running your own instance is governed by that licence, not by this document.
02Your account
You need an account to use the app, you must be old enough to form a contract where you live and at least operatorminimum age, and the details you give must be accurate. You are responsible for what happens under your account, so keep your credentials to yourself and tell the operator promptly if you think they have leaked.
One account is one tenant. Sharing a login to work around per-account limits is a breach of these terms, and it defeats the isolation that makes the product safe to use.
03Acceptable use
Do not use this service to:
- break the law, or help someone else break it
- attack anything, including probing, overwhelming, or circumventing the access controls of this deployment or any system it can reach
- drive automated activity against third parties without their permission, whether through the fetch service, a connector, or contributed SpiderMesh capacity
- generate material that sexualises children, incites violence, or is designed to deceive people about who is speaking
- resell, mirror, or scrape the service, or use it to build a directly competing product from its outputs
Security research is welcome and is not a breach of this section when it stays inside your own account and is reported responsibly. See Privacy §8.
04Your content
What you put in stays yours. Conversations, files, artifacts, knowledge entries, and memory belong to you, and the operator claims no ownership of them.
You grant only the permission needed to run the service: to store your content, to transmit it to the model providers and connectors your use requires, and to display it back to you. That permission ends when you delete the content or close your account. It is not a licence to train on your data, and this deployment does not do so.
You are responsible for having the right to upload what you upload, including anything covered by someone else’s copyright or confidentiality.
05Model output, and what it is worth
Verity orchestrates language models. Language models produce confident text that can be wrong, and no amount of orchestration changes that. Output is generated, not verified.
Do not rely on it as legal, medical, financial, or safety advice, and check anything consequential before acting on it. Confidence readings shown in the interface describe how the system scored its own answer. They are a signal, not a guarantee.
Similar prompts can produce similar output for different people, so nothing here asserts that an output is unique or that it can be protected as such.
06Connectors and code execution
Adding an MCP server is a decision to share with a third party. Tool calls you approve, and the credential you configure, go to that server. The operator does not vet them and is not responsible for what they do with what they receive.
Code the assistant writes runs in a sandbox with no ambient access to your account. The sandbox is a boundary, not a promise of correctness: you remain responsible for reviewing anything you then run yourself, elsewhere.
07Contributed SpiderMesh capacity
Running a SpiderMesh node is voluntary. If you contribute one, you agree that it may execute work units on behalf of other accounts, that you have the right to contribute the machine you are contributing, and that you will not tamper with, inspect, or retain the work it processes.
Contributed capacity is best effort. A node can go offline at any time, and the operator makes no commitment about earnings, credit, or uptime beyond what the plan terms state.
08Plans, metering, and billing
Metered actions are recorded in an append-only ledger with idempotency keys, so a retried request is charged once and a request that fails your entitlement check is not charged at all. Plan limits are enforced by the server against your verified identity on every gated action, and that check reads your entitlement record in the database.
Prices, included quotas, overage handling, currency, taxes, and refund policy for this deployment are as published on the pricing page, and are set by operatorbilling entity and payment processor. Fees are payable in advance and, except where the law says otherwise, are operatorrefund policy.
If you believe you were metered incorrectly, raise it within operatorbilling dispute window and the ledger will be reviewed against your account.
09Availability
The service is provided as it is, when it is. There is no uptime commitment unless one is separately agreed in writing, and the operator may take it down for maintenance. The support commitment for this deployment is operatorsupport channel and response expectation.
10Suspension and closing your account
You can close your account at any time. On closure your content is deleted per Privacy §6, with the usage ledger retained as a billing record.
The operator may suspend an account that breaches section 3, that puts the service or other accounts at risk, or that has unpaid fees. Where the situation allows it, notice comes first and the reason is given.
11Warranties and liability
The service is provided without warranties of any kind, to the fullest extent the law allows. It is not warranted to be uninterrupted, error free, or fit for a particular purpose, and its output is not warranted to be accurate.
Liability is limited to operatorliability cap, and neither party is liable for indirect or consequential loss, lost profits, or lost data beyond that cap. Nothing here excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud.
If you are a consumer, your statutory rights are unaffected by anything in this section.
12Governing law and changes
These terms are governed by the law of operatorgoverning jurisdiction, and disputes go to the courts of operatorvenue.
Changes are published in the changelog with the effective date above updated. Continuing to use the service after a change takes effect means you accept it. If a change is material and you do not accept it, close your account before it takes effect.
If any part of these terms is unenforceable, the rest continues to apply.
These documents describe the software in this repository and the deployment you are reading them on. They are not legal advice. If you run your own instance, read them as a starting template and replace every operator slot before you put them in front of anyone. How the isolation is enforced.