1. Who we are
KUBEBRIDGE TECHNOLOGIES INC. (“Kubebridge”, “we”, “us”, “our”) operates BridgeMCP at bridgemcp.io. This Privacy Policy explains what personal data we collect when you use the Service, why we collect it, who we share it with and what choices you have.
For personal data about account holders and organization members, Kubebridge is the controller. Where you use the Service to process data about your own users or customers, you are the controller of that data and we act as your processor.
2. Information we collect
Account information
When you sign in with Google or GitHub we receive your name, email address, profile image and the provider’s user identifier. We do not receive or store your password for those providers.
Organization information
The name, slug and settings of the organizations you create or join, the members of those organizations and their roles, and invitations you send.
Connector configuration
The connectors you configure, including their names, endpoints, transport settings and scopes. All connectors are bring your own key: the API keys, tokens and OAuth grants you supply belong to your own upstream accounts. These credentials are encrypted at rest, are never shown back to you in full after they are saved, and are used only to make the calls you request.
Activity and usage data
Records of tool calls made through the gateway, including the connector and tool involved, timing, outcome and the organization and user that initiated the call. We also record aggregate usage counts for billing and capacity planning.
Agent job data
Inputs, prompts, outputs, logs and artifacts produced by agent runs in your organization. Agent runs send prompt content to the large language model provider selected for the run.
Billing data
Plan, billing period, subscription status and invoice history. Card details are entered directly with Stripe and are processed by Stripe; we never receive or store full card numbers.
Technical data
Server and application logs including IP address, user agent, request paths, timestamps and error traces, used to operate and secure the Service.
3. How we use information
We use personal data to:
- provide, operate and maintain the Service;
- authenticate you and keep accounts and organizations secure;
- execute the connector calls and agent runs you request;
- meter usage, bill subscriptions and manage plans;
- diagnose faults, monitor performance and prevent abuse;
- respond to support requests and send service notices;
- comply with legal obligations.
We do not sell personal data, and we do not use your content to train our own models.
Where the GDPR or a similar law applies, we rely on: performance of a contract with you, our legitimate interests in securing and improving the Service, compliance with legal obligations, and consent where consent is required.
4. Sub-processors and disclosure
We share personal data with the service providers below, only as needed to run the Service:
| Sub-processor | Purpose |
|---|---|
| Stripe | Subscription billing and payment processing |
| Postmark | Transactional email |
| Datadog | Application monitoring and log management |
| Hetzner | Hosting and object storage |
| Cloudflare | DNS and reverse proxy |
| Authentication for Google sign-in | |
| GitHub | Authentication for GitHub sign-in |
| OpenAI, Anthropic, Google, Ollama Cloud | Large language model inference for agent runs |
Connector calls also send data to the upstream services you choose to connect. Those services act as independent controllers under their own privacy terms.
We may also disclose data when required by law or valid legal process, to protect our rights or the safety of others, or as part of a merger, acquisition or sale of assets, in which case we will give notice before your data becomes subject to a different policy.
5. International transfers
Our infrastructure and sub-processors may process data outside your country, including in the European Economic Area, the United Kingdom and the United States. Where required, transfers rely on appropriate safeguards such as the European Commission’s standard contractual clauses.
6. Retention
- Artifacts produced by agent runs are retained for the period set in your organization’s artifact retention setting, which defaults to 90 days.
- Activity logs are retained for as long as your organization is active, and are deleted when the organization is deleted.
- Account, organization and connector configuration is retained while the account or organization exists.
- Billing records are retained for as long as required by tax and accounting law.
- Technical logs are retained for a limited operational period and then deleted or aggregated.
7. Security
We use encryption in transit, encryption at rest for connector credentials, role-based access control scoped to each organization, and least-privilege access for our own staff. No system is perfectly secure, so we cannot guarantee absolute security, but we will notify affected users and regulators of a personal data breach where the law requires it.
8. Deletion and your choices
You can:
- email [email protected] to ask us to delete your account or any personal data we hold about you. The console does not currently offer self-serve account deletion, so this is the route for erasing an account;
- delete an organization you own from the console. Deletion is restricted to organization owners, and the console requires the organization to be emptied first: it refuses while the organization still holds virtual MCPs, connectors, API keys or agents, and tells you what remains so you can remove those resources and retry. Once the deletion goes through, the organization’s activity logs and artifacts are removed with it;
- revoke a connector’s credentials at any time by deleting the connector or revoking the grant with the upstream provider.
Some records, such as billing history, are kept where the law requires it. Backups are purged on their normal rotation.
9. Cookies
The Service sets only strictly necessary cookies: the session cookies used by our authentication layer to keep you signed in and to protect against request forgery. We run no advertising cookies, no third-party analytics and no cross-site tracking, so there is no cookie consent banner. If we ever add analytics or product telemetry, we will update this policy and disclose it before it is enabled.
10. Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, to restrict or object to processing, and to withdraw consent. Send requests to [email protected]. We will respond within the period the applicable law requires and may need to verify your identity first. You also have the right to complain to your local data protection authority.
11. Children
The Service is not directed to children and is not intended for anyone under 18. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we will delete it.
12. Changes to this policy
We may update this Privacy Policy. If a change is material we will give reasonable notice before it takes effect. The “Last updated” date at the top of this page shows when the current version was published.
13. Contact
KUBEBRIDGE TECHNOLOGIES INC.
- Privacy and general enquiries: [email protected]
- Support: [email protected]