Wise Hustlers — Digital Product & App Development Studio Logo
Get Consultation
By Wise Hustler Admin•11/10/2026•22 min read

Kenya Data Protection Act: Website Compliance Checklist

Kenya Data Protection Act: Website Compliance Checklist

# Kenya Data Protection Act Website Compliance Checklist

Summary: To achieve Kenya Data Protection Act website compliance under the Office of the Data Protection Commissioner (ODPC), Kenyan digital platforms must implement five core architectural controls: a localized privacy policy detailing legal bases, a granular cookie consent banner blocking non-essential trackers prior to consent, encrypted storage for customer PII and M-Pesa phone numbers, structured cross-border transfer documentation, and an active ODPC Data Controller registration certificate. Non-compliance risks statutory penalty notices reaching up to KES 5 million.

---

Regulatory Landscape: The Kenya Data Protection Act and ODPC Mandates

Operating an online business, customer portal, or content platform in Kenya requires strict adherence to statutory privacy legislation. The Kenya Data Protection Act, 2019 (Act No. 24 of 2019) and its accompanying 2021 Regulations—governing general compliance, registration of data controllers and processors, and complaints handling—established an enforceable legal framework for personal data governance.

Overseeing this framework is the Office of the Data Protection Commissioner (ODPC), headed by Data Commissioner Immaculate Kassait. The ODPC investigates data subject grievances, conducts regulatory audits, issues statutory enforcement notices, and serves administrative penalty notices under Section 63 against non-compliant entities.

The ODPC has actively demonstrated regulatory enforcement across multiple business sectors in Kenya:

  • Roma School (Uthiru): In September 2023, the ODPC issued a penalty notice of KES 4,550,000 against the educational institution for publishing photographs of minors on digital platforms without obtaining prior parental consent, in breach of Section 33.
  • Mulla Pride Limited: In September 2023, the ODPC penalized the digital credit provider (operating mobile loan applications KeCredit and Faircash) KES 2,975,000 for harvesting contact lists from third parties without consent to send debt-shaming text messages and conduct harassing calls to borrowers' contacts.
  • Casa Vera Lounge: In September 2023, the ODPC served a penalty notice of KES 1,850,000 against the Nairobi hospitality venue for posting a patron's photograph on social media channels for commercial promotion without obtaining affirmative consent.
  • Oppo Kenya: In October 2022, the ODPC issued a maximum statutory penalty of KES 5,000,000 against mobile phone brand Oppo Kenya for the unauthorized commercial use of a complainant's photograph on its social media platforms without consent.
  • WhitePath Company Limited & Regus Kenya: In November 2023, the ODPC issued penalty notices of KES 5,000,000 each to digital lender WhitePath Company Limited (for unsolicited harassment and non-compliance) and office workspace provider Regus Kenya (for failing to respond to enforcement notices).

Kenya's data protection architecture aligns with continental privacy frameworks, including Nigeria's Data Protection Act (NDPA) enforced by the Nigeria Data Protection Commission (NDPC), South Africa's Protection of Personal Information Act (POPIA) overseen by the Information Regulator, and Ghana's Data Protection Act, 2012 (Act 843). Under Section 3 of the Kenyan Act, statutory obligations apply to both automated and manual data collection. If an online platform collects names, telephone numbers, email addresses, IP addresses, or browser cookies belonging to individuals located within Kenya, that platform falls under direct ODPC regulatory oversight.

---

Organizational Thresholds: Who Must Register with the ODPC?

Many Kenyan enterprises operate under the mistaken belief that only multinational corporations or licensed telecommunication operators must register with the ODPC. Under the Data Protection (Registration of Data Controllers and Data Processors) Regulations, 2021, website operators collecting personal data must evaluate their status against statutory revenue, headcount, and sectoral criteria.

Under Regulation 13(2), an entity is exempt from mandatory registration only if it meets two concurrent conditions:

1. Its annual gross turnover or revenue does not exceed KES 5,000,000, and

2. It employs fewer than 10 employees;

provided that the entity does not process personal data for any designated mandatory sector listed in the Third Schedule. If an entity employs 10 or more people, generates more than KES 5,000,000 in annual revenue, or operates in a sensitive sector, registration is mandatory.

Turnover and Employee Thresholds for Kenyan Enterprises

For standard commercial enterprises, statutory registration fees and renewal terms are governed by the Second Schedule of the Registration Regulations. Fees are paid as a single statutory payment rather than staged application charges:

Entity ClassificationAnnual Turnover / RevenueEmployee HeadcountInitial Registration Fee (2-Year Certificate)Statutory Renewal Fee (Every 24 Months)
Micro and Small EntitiesUp to KES 5,000,0001 to 50 employeesKES 4,000KES 2,000
Medium EntitiesKES 5,000,001 to KES 50,000,00051 to 99 employeesKES 16,000KES 9,000
Large EntitiesExceeding KES 50,000,000100 or more employeesKES 40,000KES 25,000
Public Entities & State OrgansEstablished by lawAny headcountKES 4,000KES 2,000
Community & Civil Society GroupsNon-profit operationAny headcountKES 4,000KES 2,000

Mandatory Registration Categories Regardless of Size

Under the Third Schedule of the Registration Regulations, organizations operating in designated sensitive sectors must register with the ODPC as data controllers or processors regardless of their annual revenue or staff size. Mandatory registration applies if your website belongs to or supports:

1. Financial Services and Fintech: Payment gateways, digital credit providers, remittance networks, insurance brokers, and financial aggregators.

2. Health Service Providers: Telemedicine platforms, digital clinics, pharmacies, diagnostic laboratories, and health data management systems.

3. Educational Institutions: Primary and secondary schools, e-learning platforms, tutoring portals, and universities capturing student or parent records.

4. Hospitality and Tourism: Hotels, safari operators, travel agencies, and event booking portals processing guest identification.

5. Telecommunications and ISPs: Internet service providers, mobile virtual network operators (MVNOs), and value-added telecommunication services.

6. Direct Marketing Agencies: Digital advertising agencies, lead-generation platforms, telemarketing vendors, and automated SMS marketing systems.

7. Political Campaigning: Entities aggregating voter contact details or executing political communications.

8. Transport and Fleet Operations: Ride-hailing applications, courier delivery networks, and logistics platforms handling driver and passenger telemetry.

Operating an unregistered website that collects personal data while meeting these thresholds introduces direct compliance exposure under ODPC enforcement guidelines.

---

The Complete Kenya Data Protection Act Website Compliance Checklist

To align digital products, web portals, and software backends with Kenyan statutory mandates, engineering teams must evaluate their systems across six technical and operational pillars.

Pillar 1: Privacy Policy Kenya Statutory Mandates

A generic privacy policy downloaded from an international template fails ODPC statutory standards. Under Sections 19, 29, and 30 of the Act, your website privacy policy must provide localized disclosures:

  • [ ] Data Controller Identity: Clearly state your registered business entity name, certificate of incorporation or business registration number, physical office address in Kenya, and official data protection contact email (e.g., dpo@company.co.ke).
  • [ ] Specific Data Categories: Itemize all categories of data collected through web forms and tracking tags (e.g., identity data, telephone contacts, device IP addresses, geolocation data, browser user-agents, billing details).
  • [ ] Statutory Legal Bases: Explicitly define the lawful basis for each processing purpose under Section 30 (Consent, Performance of a Contract, Compliance with Legal Obligation, Protection of Vital Interests, Public Interest, or Legitimate Interests).
  • [ ] Third-Party Data Processors: Disclose all external processors handling customer data, including cloud infrastructure providers (e.g., AWS, DigitalOcean, Azure), transactional email delivery networks (e.g., Postmark, SendGrid), and local SMS aggregators (e.g., Africa's Talking).
  • [ ] Data Retention Periods: Document specific retention schedules for each dataset. Balance data minimization against statutory record-keeping rules, such as Section 23(1) of the Kenya Tax Procedures Act, 2015, which mandates that financial and tax-related records be retained for 5 years.
  • [ ] Data Subject Rights Instructions: Provide clear operational guidance on how data subjects can exercise their statutory rights under the Data Protection (General) Regulations, 2021, adhering to statutory response windows: 7 days for access requests (Regulation 9) and 14 days for rectification, erasure, and objection requests (Regulations 10, 11, 13).
  • [ ] ODPC Escalation Channel: Include formal contact details for the Office of the Data Protection Commissioner (email: complaints@odpc.go.ke, website: odpc.go.ke), informing users of their legal right to lodge complaints.

Browser cookies, tracking pixels, and client-side device identifiers represent personal data under Section 2 of the Act whenever they relate to an identified or identifiable individual:

  • [ ] Zero-Cookie Execution Prior to Consent: Ensure non-essential analytics and advertising trackers (such as Google Analytics 4, Meta Pixel, TikTok Pixel, and Hotjar) do not execute before the visitor registers affirmative consent.
  • [ ] Granular Category Opt-Ins: Implement consent mechanisms that separate cookies into distinct functional categories (Strictly Necessary, Performance & Analytics, Functional, and Marketing/Targeting).
  • [ ] Prohibition of Dark Patterns: Avoid pre-ticked checkboxes, obscured decline buttons, and manipulative interface choices. Under Section 32, giving consent must be as straightforward as withholding it.
  • [ ] Persistent Preference Management: Place a persistent link in your website footer (labeled "Cookie Preferences" or "Privacy Center") enabling users to modify or withdraw consent at any point during their session.
  • [ ] Cryptographic Consent Logging: Store a timestamped, tamper-resistant record of each user's consent choice to provide verifiable evidence during ODPC compliance reviews.

Web forms represent the primary mechanism through which commercial web applications capture personal data:

  • [ ] Unbundled Direct Marketing Consent: Keep direct marketing checkboxes unselected by default. Section 37 strictly prohibits sending commercial marketing communications via SMS or email without prior, affirmative opt-in consent.
  • [ ] Informed Form Submissions: Display a clear privacy disclosure statement and a direct link to your localized privacy policy immediately adjacent to submission buttons on contact forms, lead generation funnels, and checkout flows.
  • [ ] Enforced Data Minimization: Remove extraneous input fields under Section 29 principles. If telephone numbers, physical addresses, or job titles are not essential to fulfill the immediate user transaction, make them optional or exclude them entirely.
  • [ ] Minor Verification Workflows: If your platform processes data belonging to individuals under 18 years, implement parental or legal guardian consent verification workflows in accordance with Section 33.

Pillar 4: E-Commerce, MSISDN Handling, and M-Pesa Security

In Kenya, mobile subscriber phone numbers (MSISDNs) function as primary digital identities connected directly to Safaricom M-Pesa, Airtel Money, and national identification registries. Mishandling mobile numbers introduces significant operational and legal vulnerability:

  • [ ] Database Encryption for PII: Encrypt personal phone numbers, physical residential addresses, national identification numbers, and customer names at rest using AES-256 encryption within PostgreSQL, MySQL, or MongoDB storage layers.
  • [ ] Safaricom M-Pesa Daraja API Callback Hygiene: When processing payments via Safaricom Daraja C2B, B2C, or STK Push (Lipa na M-Pesa Online) APIs, process transactional webhooks within an isolated, private network zone. Never expose customer MSISDNs, transaction identifiers, or payment amounts in client-side browser consoles, public URL query strings, or unencrypted web server logs.
  • [ ] Payment Gateway Tokenization: When utilizing payment service providers such as Pesapal, Paystack Kenya, or Flutterwave Kenya, handle payment card inputs through hosted tokenization fields or PCI-DSS compliant iframes so that raw PAN data never touches your core application servers. This mirrors secure debit architectures seen across regional ecosystems like South Africa's PayShap or Ghana's GhIPSS rails.
  • [ ] Internal Staff Access Masking: Restrict administrative dashboard access to customer phone numbers through dynamic data masking (e.g., displaying +254 712 *** *89 to support staff) governed by role-based access control (RBAC).

When engineering transactional customer portals or commissioning app development in Kenya, development teams must build compliance directly into the software architecture—enforcing database field-level encryption, role-based data access (RBAC), and automated retention pruning before going live.

Pillar 5: Cross-Border Cloud Hosting and International Data Transfers

Most Kenyan web applications deploy workloads to international cloud regions, such as AWS Europe (Ireland), AWS South Africa (Cape Town), Microsoft Azure, Google Cloud, or European VPS infrastructure:

  • [ ] Cross-Border Transfer Legal Instruments: Under Sections 48 and 49 of the Act, transferring personal data outside Kenya requires proof of appropriate safeguards or explicit consent. Execute Data Processing Agreements (DPAs) incorporating standard contractual clauses with foreign cloud hosting providers and SaaS vendors.
  • [ ] Cloud Location Inventory: Maintain an up-to-date architecture data map detailing the geographical jurisdiction of every server, managed database instance, CDN edge node, and off-site backup storage bucket.
  • [ ] Data Localization for Critical Infrastructure: If your organization processes strategic national records, financial clearing data, or critical health registers, evaluate Section 50 directives to verify whether primary copies must reside on physical servers within Kenyan borders.
  • [ ] Cryptographic Protection for Backups: Apply encryption to all off-site database backups (in transit using TLS 1.3 and at rest using KMS-managed keys), maintaining strict administrative key rotation policies.

Pillar 6: Data Subject Rights and the 72-Hour Breach Escalation Window

Operational compliance requires engineering workflows to support consumer requests and cybersecurity incidents:

  • [ ] DSAR Fulfillment Protocol: Implement standard operating procedures to identify, verify, and resolve Data Subject Access Requests (DSARs). Under Regulation 9(1) of the Data Protection (General) Regulations, 2021, data access requests must be answered within 7 days. Rectification, erasure, and objection requests must be addressed within 14 days under Regulations 10, 11, and 13.
  • [ ] Automated Data Deletion Pipelines: Establish automated database routines that permanently erase or cryptographically anonymize customer records upon receiving a verified right-to-be-forgotten request, subject to overriding statutory record-keeping rules (e.g., Section 23(1) Tax Procedures Act 5-year retention).
  • [ ] Mandatory 72-Hour ODPC Breach Notification: In the event of a security compromise resulting in unauthorized access, destruction, or alteration of personal data, notify the ODPC within 72 hours of becoming aware of the incident under Section 43 of the Act and Regulation 46 of the General Regulations.
  • [ ] Affected User Communications: Establish notification protocols to alert affected data subjects without undue delay when a security compromise presents a high risk to their rights, detailing remedial steps taken to mitigate harm.

---

To satisfy the affirmative consent requirements of Section 32, websites targeting users in Kenya must not fire tracking cookies or marketing scripts before receiving explicit user consent.

Below is a vanilla JavaScript implementation integrating Google Consent Mode v2. It enforces default-denied states and dynamically updates tracking permissions upon user interaction:

// Step 1: Initialize Google Consent Mode v2 in a default-denied state
window.dataLayer = window.dataLayer || [];
function gtag(){ dataLayer.push(arguments); }

gtag('consent', 'default', {
  'analytics_storage': 'denied',
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'wait_for_update': 500
});

// Step 2: Evaluate stored user consent on DOM load
document.addEventListener('DOMContentLoaded', () => {
  const savedConsent = localStorage.getItem('kdpa_consent_status');
  const banner = document.getElementById('kdpa-consent-banner');

  if (!savedConsent) {
    // Display localized consent banner if no prior selection is recorded
    if (banner) banner.style.display = 'block';
  } else if (savedConsent === 'accepted') {
    applyConsentUpdates('granted');
  } else {
    applyConsentUpdates('denied');
  }
});

// Step 3: Handle affirmative consent actions
function handleAcceptAllCookies() {
  localStorage.setItem('kdpa_consent_status', 'accepted');
  localStorage.setItem('kdpa_consent_timestamp', new Date().toISOString());
  applyConsentUpdates('granted');
  
  const banner = document.getElementById('kdpa-consent-banner');
  if (banner) banner.style.display = 'none';
}

function handleRejectNonEssentialCookies() {
  localStorage.setItem('kdpa_consent_status', 'rejected');
  localStorage.setItem('kdpa_consent_timestamp', new Date().toISOString());
  applyConsentUpdates('denied');
  
  const banner = document.getElementById('kdpa-consent-banner');
  if (banner) banner.style.display = 'none';
}

function applyConsentUpdates(status) {
  gtag('consent', 'update', {
    'analytics_storage': status,
    'ad_storage': status,
    'ad_user_data': status,
    'ad_personalization': status
  });
}

Accompanying accessible HTML structure for the consent banner:

<div id="kdpa-consent-banner" style="display:none; position:fixed; bottom:0; left:0; right:0; background:#111827; color:#f9fafb; padding:1.25rem; z-index:9999; box-shadow:0 -2px 10px rgba(0,0,0,0.2);">
  <div style="max-width:1200px; margin:0 auto; display:flex; flex-wrap:wrap; align-items:center; justify-content:space-between; gap:1rem;">
    <p style="margin:0; font-size:0.875rem; line-height:1.4; flex:1 1 300px;">
      We use cookies and process device telemetry in compliance with the Kenya Data Protection Act, 2019. Essential cookies ensure site operations, while analytics and marketing cookies require your explicit consent. Review our <a href="/privacy-policy" style="color:#60a5fa; text-decoration:underline;">Privacy Policy</a>.
    </p>
    <div style="display:flex; gap:0.75rem; flex-wrap:wrap;">
      <button onclick="handleRejectNonEssentialCookies()" style="background:#374151; color:#fff; border:none; padding:0.5rem 1rem; border-radius:0.375rem; cursor:pointer; font-size:0.875rem;">
        Reject Non-Essential
      </button>
      <button onclick="handleAcceptAllCookies()" style="background:#2563eb; color:#fff; border:none; padding:0.5rem 1rem; border-radius:0.375rem; cursor:pointer; font-size:0.875rem; font-weight:600;">
        Accept All
      </button>
    </div>
  </div>
</div>

This technical pattern prevents non-essential cookies from firing in the browser before affirmative consent is granted, aligning frontend code execution with Section 32 standards.

---

Financial Exposure, ODPC Penalties, and Compliance Architecture

Failing to establish website privacy safeguards introduces quantifiable legal and operational risks to Kenyan businesses.

Statutory Penalty Caps Under Section 63 and Section 73

Under Section 63 of the Act, if a data controller or processor fails to comply with an enforcement notice, the Data Commissioner may issue an administrative penalty notice requiring the organization to pay:

  • A fine of up to KES 5,000,000 (five million Kenyan shillings), or
  • In the case of an undertaking, up to 1% of its annual gross turnover of the preceding financial year, whichever is lower.

In addition to administrative penalties, Section 73 sets out general criminal penalties for offenses where no specific fine is stipulated: a court-ordered fine not exceeding KES 3,000,000, imprisonment for up to 10 years, or both. Under Section 65, aggrieved data subjects also hold the statutory right to institute civil proceedings in court to claim compensation for financial or moral damages resulting from unlawful data processing.

Statutory Fee Schedules and Technical Implementation Scope

Rather than relying on unverified third-party cost estimates, engineering and legal leaders must evaluate compliance planning through statutory fee structures and technical control requirements:

Compliance Control AreaStatutory Mandate / CitationCore Technical & Operational Deliverables
ODPC Controller RegistrationRegulations, 2021 (Second Schedule)Statutory registration fee (KES 4,000 – KES 40,000 based on headcount/turnover); 24-month validity.
Privacy Policy LocalizationSections 19, 29, 30Identification of Kenyan legal entity, DPO contact, lawful bases, third-party sub-processors, and 5-year tax retention alignment.
Consent Management SystemSection 32; Section 37Default-denied tracking script blocking, granular category opt-ins, Consent Mode v2, and immutable consent logs.
PII & Payment Data SecuritySection 41AES-256 field encryption for MSISDNs, private VPC subnet processing for Daraja M-Pesa webhooks, and hosted tokenization.
DSAR Operational WorkflowsGeneral Regulations, 2021 (Regs 9, 10, 11)Automated data discovery workflows to satisfy access requests within 7 days, and rectification/erasure within 14 days.
Cross-Border Transfer ControlsSections 48, 49, 50Execution of standard DPAs with cloud providers, server jurisdiction documentation, and localization evaluation.
Breach Escalation FrameworkSection 43; Reg. 46Incident response runbooks providing 72-hour formal escalation to the ODPC and prompt notification to affected data subjects.

---

Technical Verification: 24-Point Website Compliance Audit Matrix

To assist software architects, security leads, and compliance officers in evaluating their web platforms, this 24-point verification matrix maps technical criteria directly to Kenyan statutory provisions:

#Pillar AreaTechnical Audit ItemVerification StandardStatutory Citation
1Privacy PolicyLegal Entity IdentityRegistered corporate name, incorporation number, physical office address, and DPO email published.Section 19
2Privacy PolicyData CategorizationExhaustive itemization of collected data (MSISDNs, IP addresses, cookies, transaction records).Section 29
3Privacy PolicyLawful Processing BasesExplicit attribution of each processing operation to a Section 30 lawful basis.Section 30
4Privacy PolicySub-Processor InventoryNamed disclosure of cloud vendors, email gateways, analytics tools, and SMS aggregators.Section 29
5Privacy PolicyRetention SchedulesPruning rules harmonized with Section 23(1) of the Tax Procedures Act, 2015 (5-year tax record retention).Section 29
6Privacy PolicyAccess Request SLADocumentation explaining that data access requests are resolved within 7 days.Regulation 9
7Privacy PolicyRectification/Erasure SLADocumentation explaining that correction and deletion requests are resolved within 14 days.Regulations 10, 11
8Privacy PolicyODPC Escalation RouteContact details provided for complaints@odpc.go.ke and odpc.go.ke.Section 56
9Tracking TagsPrior Consent BlockingGoogle Analytics, Meta Pixel, and advertising scripts blocked until user confirms opt-in.Section 32
10Tracking TagsGranular Consent StatesCategorized opt-in toggles (Necessary, Analytics, Functional, Marketing).Section 32
11Tracking TagsDark Pattern PreventionEqual prominence given to "Accept" and "Reject" actions; zero pre-selected options.Section 32
12Tracking TagsPersistent RevocationAccessible footer link allowing modification or withdrawal of consent at any time.Section 32
13Tracking TagsTamper-Resistant LoggingTimestamped client consent choices stored in encrypted or audit-logged formats.Section 32
14Web FormsDirect Marketing Opt-InPromotional checkboxes unselected by default; explicit affirmative consent captured.Section 37
15Web FormsForm-Adjacent DisclosuresPrivacy policy hyperlinks and brief notice displayed adjacent to all submission buttons.Section 29
16Web FormsData MinimizationElimination of unnecessary input fields (e.g., non-essential phone numbers or titles).Section 29
17Web FormsMinor Protection GatesAge verification workflows and guardian consent gates for platforms serving users under 18.Section 33
18Data SecurityPII Database EncryptionAES-256 field-level encryption applied to MSISDNs, national IDs, and customer records at rest.Section 41
19Data SecurityM-Pesa Webhook IsolationDaraja C2B/STK Push callbacks processed in private subnets without public console logging.Section 41
20Data SecurityPayment TokenizationPayment cards processed via PCI-DSS compliant hosted fields or iframes (e.g., Pesapal, Paystack).Section 41
21Data SecurityDashboard Data MaskingSupport views mask customer phone numbers (+254 712 *** *89) using role-based permissions.Section 41
22Cross-BorderTransfer AgreementsExecuted Data Processing Agreements (DPAs) with international cloud hosting vendors.Sections 48, 49
23Cross-BorderServer Jurisdiction MapComprehensive architectural documentation of all physical and virtual server locations.Sections 48, 49
24Incident Response72-Hour Breach RunbookIncident response protocol capable of alerting the ODPC within 72 hours of incident discovery.Section 43; Reg. 46

---

Frequently Asked Questions

Does every commercial website in Kenya require an ODPC registration?

No. Under Regulation 13(2) of the Data Protection (Registration of Data Controllers and Data Processors) Regulations, 2021, an entity is exempt from mandatory registration only if it has an annual turnover below KES 5,000,000 and employs fewer than 10 people, provided it does not process personal data for any designated mandatory sector in the Third Schedule. If a business employs 10 or more people, exceeds KES 5,000,000 in annual turnover, or operates in mandatory sectors—including fintech, health services, education, hospitality, telecommunications, or direct marketing—registration with the ODPC is mandatory.

What specific disclosures must a privacy policy Kenya document include?

A privacy policy compliant with the Kenya Data Protection Act must disclose the registered legal identity and physical address of the data controller, the specific categories of personal data collected, and the explicit lawful bases for processing under Section 30. It must also list all third-party sub-processors, describe data retention timelines (harmonized with the 5-year tax record retention rule under Section 23(1) of the Tax Procedures Act, 2015), state cross-border data transfer safeguards, explain data subject access rights, and provide contact details for the ODPC if a dispute arises.

What are the statutory deadlines for responding to Data Subject Access Requests (DSARs) in Kenya?

Under Kenya's Data Protection (General) Regulations, 2021, data controllers and processors must comply with a data subject access request within 7 days of receipt (Regulation 9(1)). For requests involving rectification, erasure, or objection to processing, the statutory response window is 14 days under Regulations 10, 11, and 13. Kenyan law enforces tighter statutory deadlines than the 30-day window found under the European Union General Data Protection Regulation (GDPR).

Websites targeting users in Kenya must implement a prior-consent banner that blocks non-essential analytics and marketing scripts from firing before the visitor clicks "Accept" or selects granular category preferences. Dark patterns, such as pre-ticked checkboxes or hidden reject buttons, violate Section 32 consent principles. Digital platforms must also provide a persistent footer link allowing users to modify or withdraw consent at any time.

How does the Kenya Data Protection Act impact M-Pesa payments on e-commerce websites?

In Kenya, mobile phone numbers (MSISDNs) are personally identifiable information tied to national identification databases. When integrating Safaricom M-Pesa Daraja APIs (such as STK Push or C2B), websites must never expose customer phone numbers in client-side code, public browser logs, or unencrypted database tables. PII must be encrypted at rest, administrative access restricted to authorized personnel using role-based permissions, and phone numbers must never be repurposed for unsolicited direct marketing without prior affirmative opt-in consent under Section 37.

---

Sources

Related articles