Legal
Subprocessors
(informational list)
This page lists major third-party providers that process personal data on our behalf when we operate Opsphere and opsphere.io. It is published for operational transparency and is not a contractual annex, an exhaustive inventory of every vendor you connect through integrations, or a substitute for a signed data processing agreement.
Enterprise customers may receive a DPA and a subprocessors annex under commercial contract. For questions, contact contact@opsphere.io.
A. Platform subprocessors
The following subprocessors act for Connecting Tech People SL as processors under Article 28 GDPR when providing the Opsphere platform.
Platform subprocessors (Connecting Tech People SL)
| Subprocessor | Processing purpose | Personal data involved (categories) | Location / transfer | More information |
|---|---|---|---|---|
| Amazon Web Services, Inc. | Host and operate the Opsphere platform (compute, databases, logging, object storage, transactional email, admin authentication infrastructure). | Account and identity data, session and security logs, encrypted credential metadata, operational configuration, support communications, and content you submit through the Service. | Primarily European Union (AWS eu-west-1, Ireland). Additional processing may occur under the vendor’s global infrastructure — see vendor documentation. | AWS data privacy |
| Mistral AI | Language-model inference for Opsphere Web Client and related agent flows operated by us. | Conversation text, operational prompts, tool metadata, and context needed to generate responses in Web Client sessions. | May involve transfers outside the EEA — see vendor documentation. | Mistral privacy policy |
| OpenAI, L.L.C. | Fallback language-model inference when the primary Mistral path is unavailable for Web Client flows. | Same categories as Mistral inference for the affected request. | May involve transfers outside the EEA — see vendor documentation. | OpenAI privacy policy |
| Stripe, Inc. | Payment processing for paid subscriptions and checkout. | Billing contact details, payment method metadata, transaction records, and fraud-prevention signals processed by Stripe. | May involve transfers outside the EEA — see vendor documentation. | Stripe privacy policy |
B. Customer-enabled API destinations
When you connect integrations, Opsphere calls third-party APIs using credentials you supply. Those providers process operational data under your instructions and their own terms — they are not listed here as Opsphere subprocessors for that payload. You remain responsible for lawful use of those services.
- Cloud infrastructure and observability (for example AWS, Azure, Datadog, Grafana, Prometheus);
- Deployment and developer platforms (for example Vercel, Railway, GitHub, GitLab, Argo CD);
- Incident, collaboration, and ITSM tools (for example PagerDuty, Slack, Jira); and
- Other vendors you enable through Opsphere MCP tools.
C. Bring Your Own AI (MCP / IDE clients)
When you use Opsphere through MCP or IDE clients with Bring Your Own AI, your chosen model provider (for example the LLM configured in Cursor, Codex, or Claude) may process conversation text outside the subprocessors in Block A. See Privacy Policy — AI inference for how Opsphere-hosted inference differs from MCP-only flows.
Enterprise DPA
A signed DPA and contractual subprocessors annex are available to Enterprise customers. The list on this page remains indicative for transparency and may be updated when we add or replace platform providers.