ProductsData PrivacyConfigurable SLA Engine
Kenya DPA 2019 - ss.26, 43 - DPA Compliance Timelines

Every compliance deadline, configurable. Every breach, prevented.

Set, track, and enforce SLAs on every DPA obligation - from the 72-hour breach timer to statutory DSR deadlines. Always-on automated tracking, escalation alerts, and a real-time deadline dashboard.

Why this matters

Built for your compliance outcomes

Fully configurable

Set any deadline, any unit

  • Hours, days, or business days
  • Per obligation, per entity
  • Sector-specific presets
  • Override DPA defaults where permitted

Always-on automation

Background tracking at scale

  • Timers run even when nobody is logged in
  • Handles thousands of concurrent SLAs
  • Automatic retries for notification failures
  • No spreadsheets or manual reminders

Escalation alerts

Never surprised by a deadline

  • Configurable alert thresholds
  • Email and in-app notifications
  • Escalate to manager at X% elapsed
  • Final warning before breach

Deadline dashboard

Every obligation, one view

  • Real-time deadline status board
  • RAG status across all obligations
  • Historical breach rate tracking
  • Team-level SLA performance

Features

Everything you need, nothing you don't

SLA Configuration

Configure deadlines in hours, calendar days, or business days. Set per obligation, per entity, or per request type.

Resilient Tracking

All SLA tracking runs in the background around the clock. Handles thousands of concurrent deadlines without performance impact.

Escalation Alerts

Define alert thresholds (e.g. 50%, 75%, 90% elapsed). Email and in-app notifications fire automatically. Escalate to managers.

Deadline Dashboard

Real-time RAG status board for all active obligations. Filter by type, team, status. Historical performance analytics.

Clock Pausing

Pause SLA clocks for identity verification periods, ODPC consultation windows, or other permitted interruptions.

SLA Analytics

Track SLA compliance rates over time. Identify chronic bottlenecks by team, obligation type, or request volume.

DPA alignment

Every feature maps to a DPA section

Dira is built from the Act, not retrofitted to it. Here's exactly how each capability addresses your Kenya DPA 2019 obligations.

Product FeatureDPA 2019 SectionWhat it fulfils
DSR 7-day countdowns.26(5)Enforces the response timeline for data subject access and other rights requests
72-hour breach timers.43(1)Enforces ODPC notification within 72 hours of breach discovery
60-day DPIA consultation windows.31(3)Tracks the ODPC prior consultation response period
Retention period enforcements.25(1)(f)Triggers deletion reminders when data reaches its retention limit
Clock pausing for verifications.26(2)Pauses DSR timer during the identity verification period as permitted
SLA compliance reportings.25Generates evidence of deadline management for ODPC accountability requirements

How it works

Step-by-step workflow

01

Review default SLAs

Dira pre-loads all Kenya DPA 2019 deadlines: 72h breach, 7-day DSR, 30-day DSR extension, and 60-day ODPC consultation.

02

Customise per obligation

Adjust deadlines where your internal policy is stricter than the statutory minimum. Configure business-day vs calendar-day calculations.

03

Set alert thresholds

Define when escalation emails fire: at 50% elapsed, 75%, and 90%. Assign escalation targets per obligation type.

04

Monitor the dashboard

Review your real-time deadline board daily. Track SLA compliance rates. Identify and resolve bottlenecks before they cause breaches.

FAQ

Common questions

What DPA 2019 deadlines does the SLA engine cover?
Out of the box, Dira covers: 72-hour ODPC breach notification (s.43), 7-day DSR response (ODPC guidance / s.26), 30-day DSR response (s.26(5)), 60-day ODPC prior consultation (s.31), and data retention period enforcement. You can configure custom SLAs for any internal obligation.
How reliable is the SLA tracking?
SLA timers run continuously in the background - they do not depend on anyone being logged in or on your browser staying open. The system recovers from failures automatically, retries missed notifications, and scales to thousands of concurrent deadlines, so your tracking stays dependable even under load.
Can I pause the DSR clock during identity verification?
Yes. Section 26(2) allows you to request additional information for identity verification. Dira's clock-pausing feature stops the SLA timer during the verification window. The pause is logged with timestamp and reason, creating a compliant audit trail.
What counts as a "business day" for DSR purposes?
The DPA 2019 specifies response "without undue delay" and "in any event within 30 days" - it does not distinguish between calendar and business days. However, ODPC guidance aligns with a 7-business-day operational target. Dira lets you configure calendar or business-day calculation per obligation.

Start using Configurable SLA Engine today

30-day free trial. No credit card required. Full access to all Data Privacy products from day one.

30-day free trial No credit card Cancel anytime