Sub-processors.
A sub-processor is a third party we engage to process personal data on your behalf. You give a general authorisation to the sub-processors below; we propose to notify you at least 30 days before adding or replacing one, giving you the chance to object on reasonable data-protection grounds. This list is a draft, proposed alongside the Data Processing Agreement.
DRAFT — not legal advice — pending attorney review. These drafts are not execution-ready. They exist to cut attorney time, not to replace review, and must be confirmed by a qualified attorney before anyone relies on them in a signed contract.
Who processes what depends on how you deploy.
Self-hosted / customer-operated (default). The suite runs on your own infrastructure. Code and model prompts never transit us; model calls go from your own gateway directly to the EU endpoints of the providers you choose, under your own contracts and keys, with no TensorPlane server in that path. The only personal data we receive is licensing telemetry, processed by our control plane (hosted on OVHcloud). In this mode your source-control and model-provider suppliers are yours, not ours.
Vendor-hosted (EU). Your code is processed on infrastructure we operate in the EU (OVHcloud), EU-resident from day one. Model calls still travel through your own keys. In this mode we are the processor of your application data and our infrastructure/source-control suppliers are our sub-processors.
A DPA accompanies every contract in both models.
Our role follows the actual processing.
| Processing activity | Allocation |
|---|---|
| Vendor-hosted processing of customer application data | Customer = controller; we = processor |
| Self-hosted: our processing of licensing telemetry | We = processor of that telemetry under the DPA (customer = controller of the underlying identities) |
| Our sales, invoicing, CRM | We = controller |
| Support involving application personal data | We = processor for that support processing |
| Product / security telemetry we self-operate | Collector is self-run — not a third party |
The current list.
| Sub-processor | Purpose | Data | Location | Safeguard |
|---|---|---|---|---|
| OVHcloud | Hosting the control plane and, in vendor-hosted mode, the platform and data-export object store | Control-plane database, credential ciphertext, account and billing metadata, logs, backups; in vendor-hosted mode, application data | EU (Gravelines / GRA) | EU-resident for our selected services; Standard Contractual Clauses where a service transfers outside the EEA |
| Stripe | Billing, subscriptions, invoices, and checkout for our fees | Billing personal data (also an independent controller for payment, fraud, and regulatory purposes) | Ireland / US | Data Privacy Framework, then EU Standard Contractual Clauses (Data Transfers Addendum) |
| GitHub (vendor-hosted only) | Source-control integration where TensorPlane holds the installation | Repository content, user and organisation identity, installation and repository metadata, webhook payloads | US (EU under Irish law) | Data Privacy Framework and/or EU Standard Contractual Clauses |
| Cloudflare | Transactional email: our operator-owned email Worker runs on Cloudflare Workers and sends via Cloudflare Email Sending | Recipient and sender addresses and message content (verification codes, reset links, support content) | US | Data Privacy Framework, then EU Standard Contractual Clauses |
Who is not a sub-processor.
- Our self-operated telemetry collector. We run it ourselves; it is not a third party, so it is not a sub-processor.
- Your model providers. Model calls travel under your own keys and contracts, customer-directed. Those providers are not our sub-processors; we disclose the flow as a customer-directed transfer, not a sub-processing arrangement.
How long the data is kept.
Retention periods for the data these services hold on our behalf follow our published data-retention classification, and the processing terms follow the Data Processing Agreement.
Questions about these documents?
These pages are the published rendering of our internal drafts and will change as attorney review completes. If your legal or procurement team needs a specific point clarified, contact us.