Providers and subprocessors
The providers involved depend on the features and hosting arrangement you use. A service integration is not automatically a subprocessor for every category of customer data.
Cloudflare provides the website runtime and associated network services. Requests can include IP addresses, browser information and enquiry data. Cloudflare operates a global network, so network processing is not limited to the location of a Driftverk compute host.
Resend is the transactional email integration for verification, password reset and team invitations when enabled. Email delivery involves recipient addresses and message content, including account action links. It is not used to send repository contents as part of those account emails.
Stripe handles payment checkout and subscription payment services when you make a purchase. It receives billing and transaction details. Its data protection role depends on the payment activity and applicable agreement; payment providers may also act as independent controllers.
GitHub is involved when you connect an installation or account and access repositories. Your organisation chooses which repositories to authorise. Agents, model providers and other services you configure inside an environment are your chosen integrations, not automatically Driftverk-appointed subprocessors.
Hetzner provides hosting infrastructure for Driftverk. Data processed on that infrastructure depends on the hosted service and can include account and operational data and Cloud environment content. The location of a compute host does not determine where every connected provider processes data. With Hybrid, you select and manage your own compute and storage providers; Driftverk continues to use its providers for control-plane functions.
Email hello@driftverk.com for information about the providers, data locations and transfer safeguards applicable to your service. Changes to authorised subprocessors follow the notification and objection process in the DPA.
