The agreement, in plain sentences.

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.

03Company work and administrators

If the operator later activates Verity Business for an organization, the organization owner and administrators are responsible for assigning only intended people, handling manually delivered invitation material carefully, reviewing membership and reviewer assignments, and revoking access when it is no longer appropriate. These are operating responsibilities, not a substitute for employment, privacy, records-management, or legal advice.

Company Setup records a company, membership, workspace, and policy intent. It does not activate a provider, connector, schedule, external delivery, automation, personal-data transfer, directory connection, email invitation delivery, compliance programme, or production Business runtime. A policy label or setup-complete state is not a security certification, data-residency statement, retention commitment, or legal determination.

04Acceptable 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 any other product integration
• 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.

05Your 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 a provider model on your raw data. If you separately enable a Universal Brain learning control, the permission is limited to a privacy-screened, generalized lesson or preference pattern as described in the Privacy notice; it does not authorize raw-session sharing.

You are responsible for having the right to upload what you upload, including anything covered by someone else’s copyright or confidentiality.

06Model output, and what it is worth

Verity delivers model output through its Gateway and can make research evidence, sources, and review steps visible when the work calls for them. Language-model output can still be wrong. Evidence and a quality check help you inspect the work; they do not create a guarantee.

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.

07Connectors 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.

08Model delivery, provider keys, and SpiderMesh status

Verity currently delivers model requests through the Verity Gateway using operator-configured providers and, where enabled, approved user-provided provider keys. You are responsible for having authority to use a key you connect and for complying with that provider’s terms. The key is stored encrypted and is not shown back to you.

SpiderMesh contribution and execution are active. Contribution is denominated in node-hours and recorded in the credit ledger. The operator still makes no commitment about node participation, earnings, credit value, or uptime, and may change or suspend the network.

09Plans, 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.

10Availability

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.

11Suspension 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.

12Warranties 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.

13Governing 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.