This Subprocessor List identifies subprocessors and integration recipients used or expected for C4CI Arch. It supports the C4CI Data Processing Addendum and Privacy Policy.
For questions or objections, contact support@c4ci.io.
1. Scope
This list covers providers that may process personal data or Customer Content for hosting, identity, billing, support, monitoring, source-control integration, design operations, AI-assisted features, and related service delivery.
Some providers are optional, customer-selected, environment-specific, or used only when a feature is enabled. Customer-managed providers connected by Customer are not C4CI subprocessors for the customer's own provider relationship, but they may receive data when Customer configures the integration.
2. Subprocessor Table
| Provider | Purpose | Data categories | Location / transfer posture | Status |
|---|---|---|---|---|
| Microsoft Azure | Hosting, compute, storage, database, networking, Key Vault, Kubernetes, monitoring, backup, and Azure Resource Graph integration | Account data, Customer Content, connected-system metadata, logs, support diagnostics, billing and operational records | Primary platform posture targets EU/EEA hosting, including Belgium Central where configured; Microsoft transfer terms and safeguards apply where processing occurs outside the EEA | Core |
| C4CI-operated Keycloak | Identity broker and session authority operated by C4CI on C4CI infrastructure | Identity data, email, name, roles, organisation context, login and session metadata | Hosted within C4CI's platform environment; underlying infrastructure provider is Microsoft Azure | Core |
| GitHub | Source-control integration, repository metadata, branch/file reads, pull-request and draft workflow support where configured | Repository metadata, branch names, file paths, selected file content, pull-request metadata, user identifiers associated with connected repositories | Customer-selected integration; GitHub transfer and processing terms apply to Customer's GitHub account | Optional customer integration |
| Mollie | Payment processing, checkout, subscription billing, payment webhooks, mandate and payment status | Billing contact data, payment metadata, subscription state, invoice/payment references, limited transaction details | Mollie processes payment data under its own terms and applicable payment regulation | Billing |
| Customer-selected identity providers | Federated sign-in through providers such as Microsoft Entra, Google, or GitHub where configured | Identity-provider subject, email, profile claims, authentication metadata | Customer-selected provider; provider terms and transfer safeguards apply | Optional customer integration |
| Azure AI Foundry | AI-assisted admin chat, agent workflows, summaries, and model-backed product assistance where configured | Prompts, instructions, selected context, generated outputs, admin/user identifiers, operational diagnostics | Optional provider; region and transfer posture depend on Customer or C4CI configuration | Optional AI provider |
| C4CI self-hosted LLM serving | Internal OpenAI-compatible inference endpoint for AI-assisted features where enabled | Prompts, selected context, generated outputs, operational diagnostics | C4CI-operated service intended for internal cluster access; region follows deployed C4CI environment | Optional AI provider |
| Figma | Optional HTML-to-design capture for authorised design-source reconciliation | Browser page structure, design-capture metadata, limited user/session context needed for capture | Enabled only when runtime is configured and consent allows third-party design capture | Optional design operations |
| Google Workspace / Gmail SMTP | Support mailbox, legal notices, inbound support messages, and environment SMTP relay where configured | Contact details, support content, operational diagnostics, account metadata, legal-notice metadata | C4CI's public mail exchange currently routes through Google-hosted mail. Environment-specific SMTP use is confirmed in the order form or trust-center response where needed | Operational email |
| Resend | Contact-form delivery and organisation invitation emails where RESEND_API_KEY is configured |
Contact-form content, inviter/invitee email, organisation invitation metadata, delivery diagnostics | Optional email provider; used only when configured for the relevant environment | Optional operational email |
| Twilio SendGrid | SMTP relay for operational, billing, alerting, or identity email where SMTP_HOST is configured to SendGrid |
Contact details, support or billing message content, delivery metadata, operational diagnostics | Environment-specific optional SMTP relay; used only when configured for the relevant environment | Optional operational email |
No separate ticketing, chat-support, CRM, or helpdesk provider is included in this list for Customer Personal Data as of this version. If C4CI enables one for customer support, C4CI will add the provider before using it to process Customer Personal Data.
3. Customer-Managed Integrations
Customer may connect cloud providers, repositories, identity providers, billing accounts, clusters, AI providers, or other systems. Those providers may receive data because Customer configures the integration. Customer remains responsible for its own account relationship, permissions, notices, and provider terms.
4. Change Notice
C4CI will provide notice of material Subprocessor additions or replacements through this list, product notice, email, or another reasonable channel. Customer may object on reasonable data-protection grounds within 30 days after notice.
If C4CI cannot reasonably resolve an objection, Customer may stop using the affected feature or terminate the affected order according to the agreement.
5. Data Minimisation
C4CI uses subprocessors only for purposes needed to operate, secure, support, bill, improve, or provide the services. Optional providers remain disabled unless the relevant feature, runtime configuration, or customer integration is enabled.
6. Contact
Subprocessor questions and objection notices should be sent to support@c4ci.io.