KiteHR

Legal

Privacy notice

What personal data KiteHR handles for its own purposes - on this website, when you sign in, when your company pays us and when you write to us - and your rights. The HR data your company keeps in KiteHR is your company's: we process it for them under our data processing agreement.

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

1. Who we are

KiteHR, Nicosia, Cyprus, runs this website and the KiteHR product, and is the controller for the personal data this notice describes. Our provider details are in the legal notice.

Questions about your data go to [email protected]. We reply within one working day.

2. Controller and processor

We are the controller for the people who visit this website, the people who sign in to KiteHR (their account and sign-in data), the billing contacts of companies that pay us, the people who write to us, your choices about cookies, and the security records that keep KiteHR safe.

For everything a company keeps in KiteHR about its people - employees, candidates, contractors, managers, emergency contacts, documents - the company is the controller and we are its processor. If you work for a company that uses KiteHR, or applied to one, ask that company first; our GDPR page explains how. If you write to us instead, we pass your request on to the company and help it answer.

3. What we process, why, and on what basis

  • Visiting this website: the pages you ask for, your IP address and browser details, as every web server receives them, to deliver the site and protect it. Basis: our legitimate interest in a working, safe website (Art. 6(1)(f) GDPR).
  • Writing to us: with the contact form, your name, email address, company name and size, what your message is about and the message itself; by email, what you send. To answer you and, if we end up working together, to set that up. Basis: our legitimate interest in answering people who contact us, or steps before a contract (Art. 6(1)(b)).
  • Your KiteHR account: your name, email address and language, when you last signed in, your sessions with the IP address and browser they came from, and, if you add them, your passkeys' public keys. Sign-in is passwordless, so we store no passwords; email links and one-time codes expire. To let you sign in and keep your account safe. Basis: the contract (Art. 6(1)(b)) and our legitimate interest in security.
  • Billing: for a company that pays us, the name, address, VAT number and email on its invoices, its plan, places and payments. Card details go to Stripe directly: we never see or store the card number; KiteHR shows only the card's brand, last four digits and expiry, as Stripe returns them. To bill and to keep the accounting records the law requires. Basis: the contract and our legal obligations (Art. 6(1)(c)).
  • Security records: sign-in attempts and request counts per IP address for our rate limits, and our servers' logs. To stop abuse and find faults. Basis: our legitimate interest in keeping KiteHR safe.
  • Support: what you tell us when you ask for help and, if your company turns on support access, what our staff see while they look. Basis: the contract and our legitimate interest in helping you.
  • Visit statistics, only if you allow them: see Cookies below. Basis: your consent (Art. 6(1)(a)), which you can withdraw at any time.

We don't sell personal data, we don't use it for advertising, and we never use the HR data in KiteHR for our own purposes. We send no marketing emails; if that ever changes, we'll ask for your consent first.

4. Who helps us

We work with a few providers, each bound by data processing terms. For our own purposes: Google Cloud (hosting), Cloudflare (the network and protection), SMTP2GO (sending email), Microsoft 365 (our mailbox), Stripe (payments) and, only with your consent, Google Analytics. What each one does, with which data, where and on what safeguard, is on our subprocessors page.

Stripe processes payment data for us and, for some purposes such as preventing fraud and meeting its own legal duties, as a separate controller, as Stripe's privacy policy explains.

5. Outside the EU

KiteHR's database, its backups and the uploaded files are in Google Cloud's Frankfurt region in Germany. Some providers are based outside the EU or use a worldwide network. Where personal data leaves the EU/EEA, the transfer relies on the EU Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework.

6. Cookies

Without asking, we set only what KiteHR needs to work, and what you choose yourself. Every cookie we set:

  • __Secure-better-auth.session_token

    Keeps you signed in to KiteHR. Scripts in the page can't read it.

    Needed, no consent · KiteHR app · Up to 30 days after your last visit

  • __Secure-better-auth.better-auth-passkey

    Checks a sign-in with a passkey while it happens.

    Needed, no consent · KiteHR app · 5 minutes

  • __Secure-better-auth.admin_session

    Only for KiteHR staff: marks a visit to a company that turned on support access, or an emergency look.

    Needed, no consent · KiteHR app · Until the visit ends, at most an hour

  • NEXT_LOCALE

    Remembers the language you read KiteHR in. It holds nothing else.

    Needed, no consent · Website and app · 1 year

  • kh-bands-…

    Remembers which charts you hid on the work pages, one per person.

    Set when you choose it · KiteHR app · 1 year

  • kitehr-entity-…

    Remembers the legal entity you filter by, in companies with several.

    Set when you choose it · KiteHR app · 1 year

  • kitehr_capacity_hidden

    Hides the line about places nearly used up until next month, when you ask it to.

    Set when you choose it · KiteHR app · 40 days

  • _ga, _ga_…

    Google Analytics: counts visits and tells them apart. Only after you accept, and only on this website.

    Only with your consent · Website · Up to 2 years

Analytics, only with your consent. On your first visit to this website we ask whether we may use Google Analytics. Until you click Accept, nothing is loaded from Google and no analytics cookie is set. If you accept, Google Analytics records the pages you view, how you found us, your device and browser type and your approximate location. We have turned off Google signals and ad personalisation, keep the statistics for 14 months and look at them only in aggregate. Google may process this data in the United States. Analytics runs only on this website, never in the KiteHR app. Your choice is kept in your browser for a year and you can change it at any time: . Withdrawing deletes the analytics cookies.

In your browser's own storage (not cookies) we keep your cookie choice and, in the app, how you left the navigation and the pages and people you opened recently, so they're at hand next time. They stay in your browser.

7. How long we keep it

  • Enquiries that don't lead to work: deleted after 12 months.
  • Your account: while it exists. To have it deleted, write to us; we check that the request comes from you, then delete it. A company's HR records about you stay with that company, which decides about them.
  • Sessions: until you sign out, or 30 days after your last visit; expired sessions and unused sign-in codes are deleted every day.
  • Emails KiteHR sends (sign-in links and codes, invitations, notifications): a copy for 30 days, so a failed email can be sent again and delivery traced, then it is deleted.
  • Billing records: invoices and payments for as long as tax and accounting law requires, also after a company has left.
  • Companies that leave: read-only for a while, then deleted after two warnings, as the terms say. Deleted files stay in our storage provider's safety copy for up to 30 days; database backups are kept for 30 days, and the backup storage keeps deleted backups for up to 30 more days. Then the data is gone for good.
  • Visit statistics: 14 months.
  • Security records: request counts per IP address for our rate limits, for a day; server logs only as long as we need them to keep KiteHR safe and fix faults.

8. Your rights

You can ask for access to your data, its correction or deletion, restriction of processing and data portability, and you can object to processing based on our legitimate interest (Art. 15-21 GDPR). Where we rely on your consent, you can withdraw it at any time. Write to [email protected]; we answer within a month.

You can also complain to a supervisory authority. In Cyprus that is the Commissioner for Personal Data Protection: dataprotection.gov.cy.

We make no decisions about you based solely on automated processing. KiteHR's AI reads, drafts and finds; a person decides.

9. How we protect it

Every company is walled off in the database, every connection to KiteHR is encrypted, and there are no passwords to steal. The full list is in the annex of the DPA; the Trust page sums it up.

10. Changes

We update this notice when KiteHR changes. The version and the dates are at the top of the page; earlier versions are available from us. We announce important changes on this page before they apply.

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