The short version
Your portal, your data. BridgesLLM Portal is software you install on your own server. We do not have administrative access to your VPS. We cannot see your chats, your files, your projects, or your users unless you separately choose to show us something.
We do not sell data, run ad tech, or use third-party advertising trackers. We do use a small amount of first-party analytics and product telemetry to understand whether the website is being used, whether downloads are happening, which software versions are deployed, and whether updates are succeeding. That is a common and legitimate practice for operating and improving software, and we keep it limited to what is reasonably necessary for those purposes.
1. Who This Policy Covers
This policy applies to:
- bridgesllm.ai — this marketing website and documentation
- BridgesLLM Portal software — the self-hosted software you install on your own server
It does not govern how the AI providers you connect (Anthropic, OpenAI, Google, etc.) handle your data. Those are separate services with their own privacy policies. We recommend reviewing each provider's policy before connecting them.
2. The Marketing Website (bridgesllm.ai)
What we collect
The marketing site uses lightweight, first-party measurement and standard server logging. It does not use advertising trackers, retargeting networks, or marketing cookies.
- Standard server/network logs such as IP address, timestamp, requested URL, and browser user-agent
- First-party pageview analytics using a simple image request to measure page visits, page path, referring page, IP address, and browser user-agent
- Download logs when someone downloads the installer or release tarball, including IP address, browser user-agent, and referring page
We use this information for ordinary operational reasons: to understand whether the site is being used, to measure which pages and downloads are actually useful, to detect abuse, and to troubleshoot delivery or update issues. This is a common practice for software distribution sites and product websites.
We do not use advertising cookies, cross-site tracking networks, data brokers, or behavioral profiling. The analytics described here are first-party and limited to site operations, product improvement, fraud prevention, and diagnostics.
3. The Portal Software (Running On Your Server)
Your data is on your server
When you install BridgesLLM Portal, it runs entirely on the VPS you control. All of the following exist only on your server:
- Your chat conversations with AI models
- Your project files and agent outputs
- Your user accounts and credentials
- Your connected OAuth tokens for AI providers
- Any data processed by your agents or code execution sandboxes
We cannot access any of this. We don't have the credentials. We don't have a backdoor. If you lose your server, we cannot recover your data.
Telemetry (Opt-In Only)
BridgesLLM Portal may optionally send limited product telemetry to BridgesLLM-operated endpoints. This is opt-in and can be disabled in portal settings. The purpose of this telemetry is to help us understand deployment health, version adoption, and update reliability across self-hosted installations.
When enabled, telemetry may include:
- Installation identifier — a randomly generated installation ID used to distinguish one deployment from another
- Portal version and lifecycle events — for example, the installed version and whether an install or update completed successfully
- System/runtime metadata — such as operating system, CPU architecture, Node.js version, uptime, and active user count
- Dependency/version metadata — such as the detected versions of major platform components used by the portal
This telemetry is intended to answer operational questions such as: which versions are in the field, whether updates are breaking, and whether a problem is isolated to a specific runtime or dependency stack. Collecting this kind of limited operational telemetry is a common practice for modern software products, including self-hosted software.
This telemetry does not intentionally include chat content, project files, prompts, code, API keys, OAuth secrets, usernames, or email addresses. Like any HTTPS request, it also carries network metadata such as the requesting IP address and browser or runtime user-agent to our servers.
Update Checks and Downloads
Your portal may check for the latest available version using BridgesLLM-operated endpoints. In addition, when someone downloads the installer or release archive from bridgesllm.ai, we log standard request metadata such as IP address, browser or runtime user-agent, and referring page. We use this information to understand release adoption, verify that downloads are working, investigate installer/update failures, and protect the service from abuse.
4. AI Provider Connections (OAuth)
When you connect an AI provider (Claude, Codex, Gemini, etc.) via OAuth, the authorization flow happens directly between your browser and the provider. BridgesLLM Portal stores the resulting access token on your server. We never see your OAuth tokens.
Your conversations with those providers are governed by their respective privacy policies:
- Anthropic (Claude): anthropic.com/privacy
- OpenAI (Codex): openai.com/policies/privacy-policy
- Google (Gemini): policies.google.com/privacy
5. Children's Privacy
BridgesLLM Portal is intended for developers and technically capable adults. It is not directed at children under 13. We do not knowingly collect information from children. If you believe a child has used this software inappropriately, please contact us.
6. Retention and Disclosure
We retain operational website logs and telemetry for as long as reasonably necessary for security, diagnostics, analytics, product improvement, and support. Exact retention periods may vary depending on infrastructure, abuse-prevention needs, and future system changes. We may disclose information where required by law, to protect our rights or systems, or in connection with investigating abuse or security incidents.
7. Changes to This Policy
We may update this privacy policy as the software evolves. If we make material changes, we'll update the "Last updated" date at the top of this page. Continued use of the software after changes constitutes acceptance of the updated policy.
8. Contact
Questions about this privacy policy? Reach us at support@bridgesllm.com or open an issue on our GitHub repository.