Legal
Subprocessors
The providers that help us run KiteHR and may process personal data. Your company authorises them through the data processing agreement, and we announce a new one at least 30 days before it starts.
Version 1.0 · In effect from November 20, 2026 · Last updated November 20, 2026
The list
For each provider: what it does for KiteHR, which data, where it is processed, the safeguard for any transfer outside the EU, and whose data it is. Where it says KiteHR's own, the provider works only with data we are the controller for, and your company's HR data never goes there; we list it so the list is complete.
Last changed November 20, 2026.
Google Cloud
- What for
- Hosting: runs KiteHR and this website, and holds the database, its backups and every uploaded file.
- Which data
- Everything KiteHR stores: your company's HR data and files, accounts, the activity log, and KiteHR's own records.
- Where
- EU: Frankfurt, Germany (europe-west3). Google is a US company.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- Your company's data in KiteHR, and KiteHR's own
Cloudflare
- What for
- The network in front of KiteHR: DNS, delivery, encryption to your browser, protection against attacks and, where it is switched on, Turnstile, the bot check on job application forms.
- Which data
- Everything sent to and from KiteHR while it travels (pages, forms, files), with IP addresses and browser details. Cloudflare decrypts the traffic at its edge to protect it and encrypts it again on the way to our servers.
- Where
- Worldwide: Cloudflare's network, usually the data centre nearest the visitor.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- Your company's data in KiteHR, and KiteHR's own
SMTP2GO
- What for
- Sending KiteHR's emails: sign-in links and codes, invitations, notifications, messages to candidates, and the contact form's enquiries to us.
- Which data
- Recipients' email addresses and the emails' content, which can include names and what a notification is about.
- Where
- Outside the EU possible: SMTP2GO's servers.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- Your company's data in KiteHR, and KiteHR's own
- Their terms
- SMTP2GO: privacy
Anthropic
- What for
- The AI features, which are on unless your company switches AI off: Ask KiteHR, drafting, reading the documents you upload, summaries, and public holidays suggested with a web search.
- Which data
- Only the text a task needs: a question with the records the person asking may see, or the document being read. Under Anthropic's commercial terms, Anthropic does not use it to train its models.
- Where
- Outside the EU: Anthropic is a US company.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- Your company's data in KiteHR (we are the processor)
Stripe
- What for
- Billing: checkout, card payments, invoices and VAT for companies that pay us.
- Which data
- The paying company's billing details: name, email, address, VAT number, its plan and payments. Card details go to Stripe directly. For some payment data, for example to prevent fraud and meet its own legal duties, Stripe is a separate controller, as its privacy policy explains.
- Where
- EU and outside the EU: Stripe's global network.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- KiteHR's own: accounts, billing, enquiries and website visits (we are the controller)
- Their terms
- Stripe: privacyStripe: data processing terms
Microsoft 365
- What for
- Our own mailbox: the emails you send to our address and our replies, support conversations included.
- Which data
- What you write and send to us, with your name and email address.
- Where
- Outside the EU possible: Microsoft's data centres.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- Your company's data in KiteHR, and KiteHR's own
Google Analytics
- What for
- Visit statistics for this website, only if you accept analytics cookies. Never in the KiteHR app.
- Which data
- The pages viewed, how you found us, your device and browser type and approximate location, linked to a random identifier in the cookie.
- Where
- Outside the EU possible, including the United States.
- Transfer safeguard
- EU Standard Contractual Clauses and, where certified, the EU-US Data Privacy Framework
- Whose data
- KiteHR's own: accounts, billing, enquiries and website visits (we are the controller)
Coming changes
No changes are announced right now.
Change log
- November 20, 2026: the list published (Google Cloud, Cloudflare, SMTP2GO, Anthropic, Stripe, Microsoft 365, Google Analytics)
How we announce changes
We announce a new or replaced subprocessor at least 30 days before it starts: here, under Coming changes, and to your company's owners in KiteHR. If you have a reasonable data protection objection, write to [email protected] within that time; if we can't resolve it, you may cancel before the change takes effect.
Transfers outside the EU
KiteHR's database, its backups and the files are in Frankfurt, Germany. Where a provider processes data outside the EU/EEA, the transfer relies on the EU Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework.
Not subprocessors
Services we use that aren't subprocessors, so nobody has to wonder:
- GitHub holds KiteHR's code and builds it. No customer data goes there.
- VIES, the European Commission's VAT number check: we send it the VAT number your company gives us for its invoices. It is a public authority's service, not our processor.
- The European Central Bank publishes the euro exchange rates we download for client work paid in another currency. We send it nothing.
Questions about these documents or your data: [email protected]