SakhaHireby Intellivane
Legal

SakhaHire Data Processing Agreement: European Union

How Intellivane processes candidate data for agencies on the EU service under GDPR (draft).

Draft, 21 November 2026. This document is being reviewed by our lawyers and may change before it is final. Items in [square brackets] are still to be confirmed. Questions: support@sakhahire.com.

Parties: Customer [name, address] ("Controller") and Intellivane Technologies Private Limited, [address, India] ("Processor"). This DPA is part of the SakhaHire Terms of Service.

1. Subject matter and duration

The Processor processes personal data on behalf of the Controller to provide the SakhaHire service for the length of the agreement and until return or deletion under section 12.

2. Nature and purpose

Receiving and storing CVs and candidate details; AI screening calls (speech, transcript, recording); AI summaries and scores; shortlisting, interview scheduling, offers and reports; email notifications; account administration and support.

3. Types of personal data and data subjects

  • Candidates and applicants: name, contact details, CV content (employment and education history, skills, current and expected salary, notice period, location), call audio and transcripts, AI scores and notes, interview feedback, offer details.
  • Controller's users: name, work email, role, login and usage records.
  • Special-category data: not requested. If a candidate volunteers any, it is processed only as part of the record. The Controller must not ask for it through the service.

4. Controller's instructions

The Processor acts only on the Controller's documented instructions (this DPA, the Terms and the Controller's settings and use of the portal). It will tell the Controller if it believes an instruction breaches data-protection law.

5. Confidentiality and staff

The Processor ensures anyone allowed to process the data is bound by confidentiality and has access only as needed (support, operations, security). Access from India is limited to named staff and logged.

6. Security (Article 32)

Measures include: encryption in transit (HTTPS/TLS) and password hashing; role-based access with sign-in logging and a password policy (min 8 characters, capital, number); audit log of changes; automatic daily encrypted-at-rest database backups on EU servers [confirm disk encryption and backup encryption]; firewall limited to required ports, fail2ban, automatic security updates; separate databases per Controller (tenant isolation in the application); recordings and CVs kept only for the retention period; incident logging and monitoring. [Lawyer/DPO to approve the list; add disk encryption, off-site backup and pen-test status before signing.]

7. Sub-processors

7.1 The Controller gives general authorisation for the sub-processors in the current list (Annex 2). The Processor will give [30] days' notice of additions or replacements; the Controller may object on reasonable data-protection grounds and, if not resolved, end the affected service.

7.2 The Processor imposes on each sub-processor obligations no less protective than this DPA and remains liable for them.

8. International transfers

8.1 EU service data is stored in Germany (UpCloud, Frankfurt).

8.2 The Processor is in India, which has no EU adequacy decision. Remote access from India and transfers to any sub-processor outside the EEA rely on the EU Standard Contractual Clauses (Module 2 controller to processor, and Module 3 processor to processor for sub-processors) [to be signed and attached as Annex 3] and a transfer-impact assessment [to be completed].

8.3 Where a sub-processor is certified under the EU-US Data Privacy Framework, that may be used instead for US transfers [confirm per provider].

9. Assisting the Controller

The Processor will, taking account of the nature of processing and at the Controller's cost where significant effort is needed: (a) help respond to data-subject requests (access, correction, erasure, restriction, objection, portability; the portal has erasure and export tools); (b) help with security, breach notification, impact assessments (including for AI screening) and prior consultation; (c) provide information to show compliance and allow audits under section 11.

10. Personal-data breach

The Processor will notify the Controller without undue delay and within [48] hours of becoming aware of a personal-data breach, with the information the Controller needs for its own notice to the supervisory authority (Data Protection Commission, Ireland, within 72 hours) and to data subjects.

11. Audits

The Processor will make available the information needed to show compliance and allow audits by the Controller or an auditor it appoints, on [30] days' notice, during business hours, at the Controller's cost, no more than once a year unless a breach or authority requires otherwise, and subject to confidentiality.

12. Return and deletion

12.1 On the Controller's request, or [30] days after the agreement ends, the Processor returns the data in a standard export (the portal export) and then deletes it, including from backups within [35] days, unless the law requires storage.

12.2 Retention periods follow the Controller's configured settings. Default [call recordings: 90 days; candidate records: per Controller policy, maximum ___ months].

13. Liability

As set out in the Terms of Service (section 13). [Lawyer to confirm the cap applies to this DPA.]

14. Governing law

[EU service: Irish law and courts.]

Annex 1: Processing details

See sections 2 and 3. Frequency: continuous while the agreement is in force. Supervisory authority: [Data Protection Commission, Ireland, if the Controller is established in Ireland].

Annex 2: Sub-processors (current as of 21 Nov 2026)

Sub-processorPurposeDataLocationTransfer safeguard
UpCloud LtdHosting of portal, database, recordings and voice serversAll service dataGermany (Frankfurt)EEA: none needed [confirm entity]
Microsoft (Azure Communication Services, Azure AI Speech)Sending emails (set-up links, notifications); text-to-speech for the AI voiceCandidate name, email address, spoken sentencesEmail service: Europe data location; Speech: North Europe (Ireland)EEA: none needed [confirm entity]
Deepgram, Inc.Speech-to-text for candidate speechCall audio, transcript textEU endpoint (api.eu.deepgram.com), hosted in EU regions of its cloud provider; the country is not fixed by DeepgramProcessor outside the EEA [SCCs / DPF to confirm]; processing stays in the EU
Anthropic PBCAI language model for the conversation, summaries and scoringTranscripts, CV text, job text[confirm: first-party API offers global or US processing; an EU-only option is not confirmed. EU processing is possible via a cloud provider's EU region]SCCs / DPF [confirm]
Plivo Inc.Telephone (SIP) connection for calls to candidatesPhone numbers, call audio in transit[confirm]SCCs [confirm]
Intellivane staff in IndiaOperations and support accessAny data, as neededIndiaSCCs (Annex 3)

Not currently used for the EU service: WhatsApp messaging, India telephony providers. [Update before any are enabled.]

Annex 3: Standard Contractual Clauses

[Attach EU SCC (Commission Decision 2021/914) Modules 2 and 3 with completed annexes. Lawyer to prepare.]