Employee Data Protection Kenya: ODPC Rules
Kenyan employer guide to ODPC registration, employee privacy notices, HR records, access deadlines, biometrics, vendor contracts and breach reporting.
By Cazini Editorial · Updated
Kenyan employers must protect employee and job-applicant data under the Data Protection Act, 2019, including recruitment records, attendance information and personnel files. An employer deciding why and how staff data is used is a data controller, and may need ODPC registration even if it only processes internal HR records. Compliance requires a lawful basis for each purpose, privacy notices, controlled retention, secure processing and timely responses to rights requests and breaches.
Decide Whether You Must Register With ODPC
The ODPC registration guidance specifically treats internal HR and payroll processing as controller activity. An HR employee is not a separate data processor merely because they handle records for their employer.
Apply the guidance as follows:
- Private-sector entities generally must register if annual turnover or revenue is at least KSh 5 million or they have more than 10 employees, unless an exemption applies.
- The small-entity exemption described in the guidance requires turnover or revenue below KSh 5 million and fewer than 10 employees, and no prescribed non-exempt activity or sector.
- If your headcount is exactly 10, confirm your position with ODPC rather than assuming these differently worded thresholds establish an exemption.
- A business acting as both controller and processor must submit separate applications and pay separate fees.
Registration exemption is not exemption from employee-data protection obligations.
Registration and Renewal Fees
The official guidance gives these category fees. Renewal is after every 2 years; confirm your category against the guidance rather than selecting it from its label alone.
| Entity category | Registration | Renewal |
|---|---|---|
| Micro and small | KSh 4,000 | KSh 2,000 |
| Medium | KSh 16,000 | KSh 9,000 |
| Large | KSh 40,000 | KSh 25,000 |
Map HR Data Before Choosing a Lawful Basis
Create a processing register showing the purpose, data fields, lawful basis, recipients, storage location, owner and retention rule. Use it across recruitment, employment and exit, not just for the main personnel file.
The following are practical review prompts, not automatic legal conclusions:
| HR stage | Records to map | Decision to document |
|---|---|---|
| Recruitment | CVs, interview notes, references, screening results | What is necessary before appointment, and why? |
| Onboarding and administration | Identity, contracts, bank and statutory details | Which fields support the contract or a legal obligation? |
| Benefits and health | Dependants, medical and insurance information | Which sensitive-data conditions apply? |
| Performance and discipline | Appraisals, warnings, investigation evidence | Who needs access, and for what purpose? |
| Monitoring | Attendance, CCTV, location and communications | Is the collection necessary, proportionate and high risk? |
| Exit and alumni | Clearance records, disputes and future-contact lists | What continuing purpose justifies retention? |
Consent is not the default answer. Section 30 permits processing necessary for a contract or pre-contract steps, legal obligations and other specified grounds, including legitimate interests. Establish and document the basis before processing; do not use a blanket consent clause to justify unrelated future uses.
Give Applicants and Staff a Privacy Notice
Under section 29, before collection, so far as practicable, explain the purpose, rights, recipients and safeguards, controller or processor contacts, security measures, whether supply is legally mandatory and the consequences of withholding information.
Use an applicant notice at recruitment and an employee notice covering employment processing. Identify actual recipients, such as a screening provider, rather than describing every disclosure as sharing with “partners”.
For indirectly collected information, including references and background checks, regulation 6 requires informing the individual within 14 days. A new incompatible purpose requires fresh consent. Build this notification into the screening workflow instead of leaving it until an offer is issued.
Assess Biometrics, Monitoring and Health Records Separately
A DPIA is required before processing likely to create high risk. Regulation 49 includes biometric or genetic data, sensitive data, significant automated decisions, large-scale processing, linked datasets and innovative technology among its examples.
Treat fingerprint clock-in as a DPIA issue before buying or activating the system. For CCTV, GPS, email monitoring and call recording, document the purpose, necessity, scope, access controls and retention, then assess whether the proposed processing is high risk. Do not treat ownership of workplace equipment as a substitute for a lawful basis and transparency.
AI candidate ranking also needs scrutiny where automated decisions have significant effects. Keep the assessment with the procurement decision, not merely with the vendor's marketing material.
Sensitive-data rules need separate analysis. Sections 44-46 allow processing necessary for specified employment rights and obligations, among other grounds, but health data has additional healthcare-provider, professional-secrecy and confidentiality conditions. A general employee consent form does not settle those conditions.
Set a Defensible Retention Schedule
Section 39 and regulation 19 require purpose-based retention, subject to lawful-retention exceptions. Your schedule must state the purpose, retention period, periodic-audit provision and post-audit action.
Do not assign every HR record the same lifespan. Use this working matrix to determine and document the appropriate period:
| Record group | Retention decision |
|---|---|
| Employment, payroll and tax records | Identify applicable record-keeping obligations before setting the period. |
| Immigration and right-to-work evidence | Document the continuing verification purpose and applicable obligations. |
| Benefits and medical information | Separate benefit-administration needs from restricted health information. |
| Disciplinary and dispute records | Record the continuing purpose and any lawful-retention exception. |
| Unsuccessful applicant CVs and notes | Set a recruitment-purpose period; assess future talent-pool use separately. |
| CCTV, GPS and access logs | Set a purpose-specific period rather than retaining by storage capacity. |
These data-protection provisions do not establish a universal HR-file or unsuccessful-CV retention period. Once the purpose expires, implement deletion, erasure, anonymisation or pseudonymisation as appropriate. Include exports, shared drives and vendor-held copies in the review.
Operate an Employee Rights Request Log
Employees have rights to information, access, objection, correction and deletion of false or misleading data. The General Regulations provide these operational deadlines:
| Request | Deadline or requirement |
|---|---|
| Access | Comply within 7 days, free of charge; commonly used electronic form where requested electronically. |
| Erasure or restriction | 14 days. |
| Justified objection | 14 days. |
| Accepted rectification | 14 days. |
| Refusal to rectify | Written notification within 7 days. |
Log receipt, scope, responsible owner, deadline, decision and evidence of response. Assess deletion requests against continuing lawful-retention grounds rather than promising automatic destruction of the entire file. Keep employee records retrievable in your employee-management process, including records held outside the core HR system.
Control Vendors and Overseas Storage
A processor arrangement requires a written contract under section 42 and regulation 24. For an HRIS, recruitment platform or payroll bureau, check that it covers:
- Processing details and the employer's instructions.
- Confidentiality and security measures.
- Return or deletion at contract end.
- Audit and inspection provisions.
Ask where records are hosted and accessed. Before an overseas transfer, establish an appropriate lawful route: safeguards, an ODPC adequacy decision, necessity or consent. Document safeguard-based transfers and keep the record available to the Commissioner on request. A signed vendor contract alone does not answer the transfer question.
Prepare for an Employee-Data Breach
For unauthorised access or acquisition creating a real risk of harm, the controller must notify ODPC within 72 hours of awareness. Affected employees must receive written communication within a reasonably practicable period. A processor must notify its controller without delay and, where reasonably practicable, within 48 hours.
Regulation 37 includes specified combinations of identity information and other data, and account identifiers combined with passwords, security codes or biometric data, among notifiable cases.
As an operational response, contain access, preserve evidence, identify affected records, record awareness time and assess notification immediately. Keep the notification decision and reasoning in an incident log.
The maximum administrative penalty is KSh 5 million or, for an undertaking, 1% of the preceding financial year's annual turnover, whichever is lower. Individuals suffering damage may also seek compensation, including for distress.
Assign Accountability
Name an internal owner for notices, requests, vendors, retention and incidents. Section 24 provides for appointment of a DPO in specified circumstances, including regular systematic monitoring or sensitive-data processing as core activities. Where appointed, the DPO advises staff, supports compliance and DPIAs, and cooperates with ODPC; published contact details must be sent to the Commissioner.
Sources
Kenya Law, Data Protection Act, 2019 - Principles, lawful bases, notices, rights, DPOs, sensitive data, breaches, transfers and penalties. Kenya Law, Data Protection (General) Regulations, 2021 - Indirect collection, request deadlines, retention schedules, processor contracts, DPIAs and transfer safeguards. ODPC, Guidance Note on Registration of Data Controllers and Data Processors - Employer controller status, registration thresholds, exemptions, fees and renewals.
Frequently asked questions
Does the Data Protection Act apply to employee and applicant records?+
Yes. Kenyan employers must apply data-protection principles to both employee records and candidate information. The employer is a controller where it determines why and how that information is processed.
Do employees have to consent to payroll processing?+
Not necessarily. Necessary processing may rely on the employment contract or a legal obligation rather than consent. Document the lawful basis for each purpose instead of treating a signed consent form as permission for all HR processing.
Is a small employer automatically exempt from ODPC registration?+
No. ODPC guidance describes an exemption for entities below KSh 5 million in annual turnover or revenue and with fewer than 10 employees, provided they do not undertake a prescribed non-exempt activity. Registration exemption does not remove the obligation to protect employee data.
How quickly must HR respond to an employee data-access request?+
The employer must comply within 7 days, and access is free. Where the request is electronic, provide the information in a commonly used electronic form. Keep a record of the request, deadline and response.
Can a Kenyan employer store employee records outside Kenya?+
Yes, but the employer must first establish a lawful transfer route, such as appropriate safeguards, an ODPC adequacy decision, necessity or consent. Safeguard-based transfers must be documented, with the record available to the Commissioner on request. Check sensitive-data requirements separately where relevant.
Hire, manage and pay your team in one place
Post jobs free, run background checks with consent, and run compliant payroll.
Start free