Terms of Service

By creating an account or using an instance of Breno, you agree to these terms. If you are accepting them for an organization, you confirm you are authorized to bind that organization, and “you” means it.

Breno is licensed software that can be self-hosted. If your organization operates its own instance, your agreement for that instance is with your organization, and these terms apply to the extent they are not varied by it.

• You must be at least 16 years old, and you must give accurate account details.
• You are responsible for what happens under your account, and for keeping your credentials and any MCP tokens secret.
• A workspace has one or more owners. An owner controls membership, permissions and billing for that workspace; an owner can also transfer ownership and delete the account, which erases it and its content.
• Tell us promptly if you believe an account or token has been compromised.

You keep all rights to the material you put into Breno and to the material Breno ingests from sources you connect. We claim no ownership of it.

You grant the operator of the instance only the permission needed to run the product for you: to store your content, index it, derive searchable and structural data from it, return it to you and the people you have given access, and send it to the configured model provider when a search or an answer requires it. That permission ends when you delete the content or the account, apart from copies still inside a backup, which expire on the backup retention schedule.

You are responsible for having the right to put the content in. If you connect a source, you confirm you are entitled to grant access to what it exposes, and you will not use Breno to ingest material you have no right to hold.

You may not use Breno to:

• break the law, infringe anyone's rights, or process material you are not lawfully entitled to process;
• gain access to a workspace, document or credential you have not been given;
• probe, scan or breach the security or tenancy isolation of an instance, or interfere with anyone else's use of it;
• upload malware, or use the service to distribute it;
• resell or sublicense the software except as its licence permits;
• strip or obscure ownership notices in the software.

Breno generates answers with a language model, over material retrieved from your own knowledge. A generated answer can be incomplete, out of date, or simply wrong, even when it cites a source — and a citation is not a guarantee that the source says what the answer claims.

• Every answer shows the sources it was drawn from. Check them before relying on an answer.
• An answer is not professional advice — not legal, medical, financial or otherwise — and must not be treated as a substitute for a qualified person.
• You are responsible for the decisions you take on the basis of an answer.

Generating an answer consumes credits from the workspace's balance; ingesting material and searching do not. A workspace's balance, what each operation costs, and its history are visible in the product.

Where an instance is sold as a paid service, the price, the billing period and the refund policy are set out in the order or agreement under which you bought it. Credits are consumed by use and are not a stored-value instrument; nothing in these terms converts them into money.

If your instance is configured with its own model provider credentials, your use of that provider is governed by your agreement with them, and their charges are yours.

• Connecting a source grants Breno read access through the credentials you provide. Credentials are encrypted at rest and used only to read from that source.
• The source's own terms continue to apply to your use of it. Some sources rate-limit or restrict what may be read; Breno works within what those APIs allow.
• Disconnecting a source stops future reads. Material already ingested stays until you delete it, so that removing a connection is not a silent way to lose knowledge you meant to keep.

We work to keep the product available and correct, but this instance is provided without a service-level commitment unless one is agreed separately in writing. Features may change, and a feature may be withdrawn; where a change materially reduces what you get, we will give reasonable notice to workspace administrators.

Maintenance, upgrades and any migration of the schema happen as part of running the service. An export of your knowledge is available to you at any time, so leaving is always possible.

You may stop using Breno at any time, and you may delete your account from within the product. We may suspend or end access if these terms are broken in a way that puts the service, another customer, or the law at risk — and, where the situation allows, we will warn you first and give you the chance to put it right.

On termination your access ends and your content is deleted on the schedule described in the Privacy Policy. Export what you need before you go; the product makes that a self-service action.

Breno is provided “as is”. To the extent the law allows, we exclude implied warranties, including fitness for a particular purpose, and we are not liable for indirect or consequential loss, lost profits, or lost data — which is why export and backup exist and why you should use them.

Where liability cannot be excluded, our total liability arising out of the service is limited to the amount paid for it in the twelve months before the claim. Nothing here limits liability that the law does not permit to be limited.

We may update these terms. When a change is material, the date at the top changes and workspace administrators are told before it takes effect. Continuing to use the service afterwards accepts the updated terms; if you do not accept them, stop using it and export your content.

These terms are governed by the laws of [JURISDICTION], and the courts of [JURISDICTION] have exclusive jurisdiction over any dispute — unless a separate written agreement between you and the operator says otherwise.

Questions about these terms: [LEGAL CONTACT EMAIL].