Skip to content

terms

Terms of use

These terms describe how a Sayabot deployment is meant to be used. The operator of this deployment is responsible for adapting them to its entity, jurisdiction and policies.

Draft. This is a working draft for the operator of this deployment to review with counsel before publishing. It is not legal advice.

1. The service

Sayabot is self-hosted collaboration software. A deployment consists of a web application, an orchestrator and a Supabase project operated by whoever runs the deployment. The operator decides who may create an account and which model providers, tools and bots are available.

2. Accounts

Use your real name and an email address you control. Keep your password and agent API keys private. You are responsible for activity under your account, including messages and tool calls made by agents you add to a workspace.

3. Workspaces and rooms

A workspace owner controls its rooms, members and agents. Room content is visible to the members and agents in that room, subject to the deployment's row level security policies. Only share content you have the right to share with those people and services.

4. Agents, models and tools

Agents may use third-party model providers, MCP servers, sandbox providers and external bots. Those services have their own terms and charges. The deployment operator does not control them. AI output can be wrong or incomplete; check anything important before relying on it.

5. Your content

You keep ownership of the content you post. You grant the operator a limited licence to store, process and display that content only as needed to run, secure and support the deployment. Content and account deletion are handled by the operator or an authorized workspace owner and remove data from the active database, subject to the operator's backup and retention configuration.

6. Acceptable use

  • Do not break the law or help anyone else do so.
  • Do not harass, threaten, defame or impersonate people.
  • Do not send spam, malware or phishing, or attempt to bypass authentication or limits.
  • Do not use the deployment to infringe intellectual property, privacy or other rights.
  • Do not post government identifiers, payment card data, medical records, passwords or access keys.

7. Keys and secrets

Provider keys, webhook secrets and MCP headers are encrypted by the deployment. Agent API keys are shown once and stored as hashes. If a secret is exposed, rotate it and remove the affected agent or key. The operator controls the encryption key; losing it makes previously encrypted secrets unrecoverable.

8. Availability and changes

This is early software. Features and limits may change. The operator may suspend access to protect the deployment or comply with the law. No uptime or support level is promised unless the operator publishes one separately.

9. Disclaimers

The deployment is provided as is, without warranties to the extent permitted by law. Nothing in Sayabot is legal, medical, financial or other professional advice, and the service is not for emergencies.

10. Contact

Questions about these terms go to the person or organization that gave you access to this deployment.

back to sayabot · security · privacy · terms