1. Acceptance and scope
By using bridgesllm.ai, downloading a release, or operating BridgesLLM Portal, you agree to these terms. If you do not agree, do not use the site or software.
These terms apply to the BridgesLLM website and distribution of BridgesLLM Portal. They do not replace the license or terms of OpenClaw, an AI provider, a package repository, an operating system, a hosting company, a mail service, or any other third-party component or service.
2. Free and open-source software
BridgesLLM Portal is distributed under the MIT License. The license controls your rights to use, copy, modify, merge, publish, distribute, sublicense, or sell copies of the software.
Third-party dependencies and bundled components can use different licenses. Their notices and license terms continue to apply. BridgesLLM names, logos, domains, and visual identity are not automatically licensed as trademarks by the MIT software license.
3. Operating a Portal
Portal is self-hosted. The operator is responsible for:
- choosing a supported host and maintaining its operating system, access controls, firewall, DNS, TLS, storage, and backups;
- creating and managing Portal accounts, roles, credentials, projects, apps, files, public links, mailboxes, and retention;
- reviewing agent actions, terminal commands, code, tool calls, generated output, and changes before relying on them;
- obtaining rights to process, store, transmit, publish, or share the data placed on the host;
- complying with laws, contracts, and policies that apply to the operator and its users; and
- monitoring resource use and exposure created by optional services.
The supported production profile is a compatible Ubuntu or Debian VPS with the documented memory, disk, and host capabilities. Windows through WSL 2 is experimental. Nested virtualization, unusual kernels, custom service layouts, or modified system components can fall outside the tested profile.
4. AI providers and third-party services
Portal does not include a universal AI subscription or guarantee access to any particular provider, model, authentication method, or usage limit. You bring the provider account, API key, command-line subscription, local model, or remote runtime you choose. Authentication methods vary.
Provider availability, pricing, quotas, model behavior, data practices, and terms can change without a Portal release. You are responsible for the charges and obligations created by accounts, hosting, domains, mail, storage, packages, remote compute, and other connected services.
AI and automation outputs can be incorrect, incomplete, insecure, offensive, or unsuitable. Review important output and obtain qualified professional advice where the stakes require it. Do not rely on an agent as the sole decision-maker for safety-critical, legal, medical, financial, or similarly consequential work.
5. Updates, rollback, and backups
Portal updates are operator-triggered. The signed update flow includes backup preflight, migration, health checks, and rollback behavior, but no mechanism can guarantee recovery from every host failure, provider outage, disk error, operator modification, or external dependency change.
Keep independent, tested backups outside the failure domain of the primary server. Before a major update, review release notes, confirm available disk space, verify critical data, and understand any host-specific services or custom reverse-proxy configuration.
A Complete wipe confirms removal from recorded managed paths. It cannot find a copy that was moved or created elsewhere before uninstall. Operators handling sensitive data should inspect the host and external backups directly.
6. Acceptable use
Do not use the website, download infrastructure, or software to violate law, infringe rights, distribute malware, gain unauthorized access, interfere with another system, evade security controls, abuse public services, or misrepresent your identity or authority.
You may test and modify your own installation. You may not attack BridgesLLM infrastructure or another person’s Portal. Good-faith vulnerability research must follow the security policy and avoid privacy violations, destructive actions, persistence, or service disruption.
7. Security boundaries
Portal includes controls such as role-based access, signed releases, path containment, project-bound runtimes on compatible hosts, controlled public egress, and guarded maintenance actions. These controls reduce risk; they do not remove it.
- Container isolation is not a guarantee that arbitrary untrusted code is safe.
- Public app and share links are public surfaces when enabled.
- Mail and Remote Desktop add services and exposure that require maintenance.
- External agents and tools can act with the permissions the operator grants.
- Unsupported hosts or operator changes can invalidate tested assumptions.
8. No warranty; limitation of liability
To the maximum extent permitted by law, the website, downloads, and software are provided “as is” and “as available,” without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, non-infringement, availability, security, accuracy, compatibility, or uninterrupted operation.
To the maximum extent permitted by law, BridgesLLM and its contributors will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost data, revenue, profits, goodwill, business opportunity, or service availability arising from the website, software, an update, an agent, a connected provider, or operation of a host.
Where liability cannot be excluded, it is limited to the greater of the amount you paid directly to BridgesLLM for the relevant service during the twelve months before the claim or one hundred US dollars. Portal software itself is offered without charge. Some jurisdictions do not permit every exclusion or limitation, so portions of this section may not apply.
9. Indemnity
You agree to defend, indemnify, and hold harmless BridgesLLM and its developers, contributors, and operators from claims, losses, liabilities, damages, judgments, costs, and expenses, including reasonable attorneys’ fees, arising from or related to:
- your deployment, operation, or use of BridgesLLM Portal
- your violation of these terms or applicable law
- your users, data, content, infrastructure, or third-party integrations
10. Governing law and venue
These terms are governed by the laws of the Commonwealth of Virginia, United States, without regard to conflict-of-law rules. Unless applicable law requires otherwise, disputes arising from these terms will be resolved in the state or federal courts located in Virginia, and you consent to that venue and jurisdiction.
11. Privacy
The privacy notice explains standard website request records, the Portal operational report, installer lifecycle events, version checks, external provider requests, and the distinction between BridgesLLM and a self-hosted Portal operator.
Fresh 4.0 setup enables the limited Portal operational report by default, and the Owner can turn it off during setup or later in Portal settings. Existing installations retain their saved choice. When enabled, Portal reports shortly after startup and then about every 24 hours while it remains running. Turning the report off stops that operational payload only. The separate Owner-Dashboard version lookup and manual refresh remain available and create normal request metadata at the version endpoint. The installer independently sends limited install and update lifecycle events regardless of the Portal telemetry setting. Normal requests to downloads, providers, package repositories, websites, mail systems, and other enabled services still create request metadata at those destinations.
12. Changes, continuity, and contact
BridgesLLM may change the website, distribution infrastructure, documentation, or these terms. Material software behavior changes belong in release notes and public documentation. If a term is unenforceable, the remaining terms continue to apply. A failure to enforce one term is not a waiver of it.
For questions, use the official repository. Do not place credentials, personal information, private host details, or vulnerabilities in a public issue. Report security concerns through the repository’s private reporting instructions.