Trust
Sub-processors
The companies that process customer data for Tempa on Devleaps' behalf. This list is for information; the binding list is part of the data processing agreement, which is available on request.
In use
| Sub-processor | Service | Data | Location |
|---|---|---|---|
| Scaleway SAS (France) | Hosting: Kubernetes, managed PostgreSQL and its backups, secret manager, block storage, networking | All customer data: configuration, accounts and roles, devices, audit log, encrypted secrets, pseudonymised telemetry | EU |
Identity providers
They sign people in when your organisation offers them and a person chooses them, and send Tempa only what sign-in needs: an identifier, the e-mail address and whether it is verified, the name, and for Microsoft the groups.
- Microsoft (Microsoft Entra ID): Microsoft sign-in
- Google: when Google sign-in is offered and chosen
- GitHub: when GitHub sign-in is offered and chosen
Planned
Each is added to the list above, with notice to customers, before it processes customer data.
- E-mail delivery: for invitations and sign-in links; the provider is not chosen yet
- Payments (Stripe): for billing paid plans
Not sub-processors
Your own integrations
The Git host Tempa reads your configuration from and the MCP servers you configure: you choose and contract them, and Tempa connects with your credentials.
Your coding agents' model providers
Tempa calls no model provider. Prompts go from the developer's agent to the provider you chose.
Questions, or the data processing agreement? Contact Devleaps.