KiteHR

Legal

Data processing agreement

This data processing agreement ("DPA") covers the personal data KiteHR processes for your company inside KiteHR. It meets Art. 28 GDPR and is part of our terms: it applies when your company accepts them, so there is nothing to sign. You can print it or save it as a PDF from this page.

Version 1.0 · In effect from November 20, 2026 · Last updated November 20, 2026

1. Who is who

  • Your company, the customer that uses KiteHR, is the controller. It decides which data it keeps in KiteHR, who sees it and how long it is kept.
  • KiteHR, Nicosia, Cyprus, is your processor. Contact: [email protected].

2. Subject matter, duration, nature and purpose

  • Subject matter: providing KiteHR, HR software delivered online, and support for it, under the terms.
  • Duration: as long as your company uses KiteHR, plus the read-only time after it ends, until the data is deleted (see At the end).
  • Nature: storing, organising, showing, changing, exporting, sending (emails and notifications), analysing on your request (reports, AI features) and deleting personal data.
  • Purpose: so your company can run its HR work in KiteHR. We process the data only for that, on your documented instructions.

3. Whose data, and which data

  • People: your employees (current, future and former), candidates, contractors and other people you work with, managers, the members of your company's account, your employees' emergency contacts and dependants, and people named in the documents you upload.
  • Data: identity and contact details; job, contract and employment history; pay, bonuses, expenses and bank details; time off and working time; reviews, goals and feedback; applications and hiring (CVs, interviews, offers); documents and files; ID, tax and social insurance numbers; account, sign-in and activity data; and every field your company adds.
  • Special categories (Art. 9 GDPR): KiteHR can hold health data - sick leave, sick notes, maternity and other leave - and, if your company adds such fields or uploads such documents, other special categories such as trade union membership or religion. Whether you record them, and on what legal basis, is your decision. The annex says how KiteHR protects them.

4. Your instructions

Your instructions are the terms and this DPA, the settings you choose in KiteHR and what your people do in it. If we believe an instruction breaks data protection law, we tell you and may hold it until you confirm or change it. We never use your data for our own purposes, never sell it, and never use it for advertising or to train AI models.

If the law requires us to process your data in another way, for example on an authority's order, we tell you first, unless the law forbids it.

5. Confidentiality and our staff

Only the KiteHR staff who run and support the service can reach your data, each with a personal account, and everyone with access is bound to confidentiality. Staff look into your company only when your company turns on support access, for 1, 7 or 30 days, to look and never to change. Without it, only a KiteHR administrator can look, in an emergency: with a written reason, an email to your owners at once and a line in your activity log.

6. Security

We protect your data with the technical and organisational measures in the annex at the end. We may improve them over time, never below the level described there.

7. Subprocessors

You give us general authorisation to use subprocessors. The current list - who, what for, which data, where and on what safeguard - is public on our subprocessors page, with the date of its last change.

We bind every subprocessor to data protection duties at least as strict as this DPA, and we remain responsible for them.

We announce a new or replaced subprocessor at least 30 days before it starts: on the subprocessors page and to your company's owners in KiteHR. If you have a reasonable data protection objection, tell us within that time; if we can't resolve it, you may cancel before the change takes effect.

Files you export from KiteHR and send elsewhere, for example to your payroll provider, are your responsibility once they leave KiteHR.

8. International transfers

Your data is stored in the EU, in Google Cloud's Frankfurt region in Germany. Where a subprocessor processes it 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. The subprocessors page says which providers that concerns.

9. Helping you

  • Requests from people: KiteHR gives you the tools to answer them yourself - export everything about a person as a ZIP, correct records, erase or anonymise a person with a check first and a certificate at the end, legal holds and retention rules - and candidates can download or delete their own data from their application link. If someone asks us directly, we pass the request on to you and help you answer it.
  • Impact assessments and authorities: we give you the information you reasonably need for a data protection impact assessment, a prior consultation or a request from a supervisory authority.
  • Data breaches: we tell you without undue delay, and at the latest within 48 hours of becoming aware of a personal data breach affecting your data, with what we know at that point, and we keep you updated, so you can meet your own 72-hour duty to report.

10. At the end

When your subscription or your trial ends, your company stays read-only - 90 days after a subscription, 30 days after an unpaid trial - so you can export what you want to keep. Then we delete your company with everything in it, after two warnings to the owner. Deleted files remain in our storage provider's safety copy for up to 30 days; database backups are kept for 30 days, and deleted backups stay recoverable in the backup storage for up to 30 more days. After that the data is gone. Copies of the emails KiteHR sent are deleted 30 days after sending. We keep nothing else, except what the law requires us to keep, such as invoices. Ask us if you want it deleted sooner.

11. Information and audits

We give you the information you need to check that we keep to this DPA. If that isn't enough, you, or an auditor bound to confidentiality who doesn't work for a competitor of ours, may inspect our compliance once a year, after at least 30 days' notice, during business hours and without disrupting the service. Each side carries its own costs, unless the audit finds that we broke this DPA.

12. Everything else

Liability under this DPA follows the terms, except where the GDPR rules otherwise. If this DPA and the terms disagree on data protection, this DPA wins. We change it the same way as the terms. It exists in English only, with no translation.

13. Annex: technical and organisational measures

What protects your data in KiteHR today:

  • Every company walled off in the database itself (row-level security), not only by the application; automatic tests check it against a real database on every change.
  • Encrypted in transit: HTTPS only, browsers told never to connect without it, and encrypted between Cloudflare and our servers too.
  • Hosted in the EU: the database, its backups and the files in Google Cloud's Frankfurt region; files in private storage, downloaded through links that expire within minutes.
  • Roles and scopes decide who sees what, and rights are checked on the server for every page and action. Managers see what their reports' work needs; pay stays with HR and the person.
  • Sensitive data: ID numbers and fields marked sensitive arrive masked, and showing them is recorded; the type of health-related leave is shown only to HR and the approver, colleagues see "Away"; document categories can be kept to HR.
  • An activity log: changes, and looks at pay, documents and ID numbers, with who and when, readable by your company's HR.
  • Four-eyes, on by default: nobody with HR rights changes their own pay, job or balances.
  • No passwords: passkeys, email links and one-time codes, with limits on sign-in attempts.
  • Support access only as described under Confidentiality, every visit in your activity log.
  • Files checked on upload: PDF, Word, Excel, PNG and JPEG only, the content must match its type, and active content such as macros or scripts is refused.
  • AI: only the text a task needs goes to the AI provider; documents are read as data, never as instructions; nothing AI produces is saved without a person; your company can switch AI off.
  • Backups: the database's changes are archived continuously, with a full backup every night, kept for 30 days, so it can be restored to any moment in that time.
  • Protected at the edge: our servers accept traffic only through Cloudflare, which shields them from attacks.
  • Staff: personal accounts, few administrators, bound to confidentiality.
  • No certifications: KiteHR holds no security certification today, and we don't imply one.

Questions about these documents or your data: [email protected]