Start hereMap the entities, roles and purposes
~87 days leftOpen step
Guide library
Regulation Africa

Uganda PDPO registration and reporting

Uganda Data Protection and Privacy Act: PDPO registration, renewal and annual reports

Register with Uganda’s Personal Data Protection Office, check the issued certificate, and keep the renewal and annual compliance report on separate calendars.

Issuing authority
Uganda Personal Data Protection Office (PDPO)
Timing
Regulation 18 gives the PDPO 30 days from receipt of an application or additional information to prepare its report, then 15 days from the report for a decision. Registration is valid for 12 months. The annual compliance report is due within 90 days of the end of the financial year under Regulation 50.
Reviewed
Inside this guide
4 steps · 8 templates

Who it applies to

Covered data collectors, processors and controllers, including organizations outside Uganda that handle the personal data of Ugandan citizens. Check the applicable role, purpose and any gazetted exemption with Legal.

What you’ll produce

An approved processing and role record, the issued Form 4 certificate, evidence for any overseas processing, and dated renewal and annual report receipts.

Regulation 23 sets renewal at least three months before expiry, while older PDPO guidance says within the three months before expiry. The gazetted regulation cites Form 1, but the PDPO lists Form 2 for renewal and Form 1 for objections. Ask the PDPO to confirm the procedure before the statutory cutoff and keep its reply.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which entity is responsible for each service?
Assign a service owner and have Legal verify where the entity acts as collector, processor or controller. Give the DPO authority to hold a new purpose until its registration and overseas processing have been reviewed.
Who checks renewal against the certificate?
Put renewal on the corporate calendar well ahead of the date set in Regulation 23. Assign a backup filer and have the DPO verify the current portal and accepted form with the PDPO.
Can we prove the report is complete?
Require Support and Security to reconcile their complaint and breach logs before the report goes to the signatory. Give the DPO the authority to obtain the supporting records from every service owner.

How to spend the first week

  1. Walk the public sign-up or client workflow with an operator. Compare the live fields and permissions with the intended filing.
  2. Ask Finance to identify the owner of the payment reference and ask the DPO to test access to the registration and reporting service.
  3. Set the financial year end and request sample complaint and breach exports before assigning the final report date.

What to review each week

Show each entity and purpose, application and certificate status, changes awaiting notice, renewal dates, overseas processing decisions and annual report evidence gaps.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Uganda PDPO registration and reporting kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Map the entities, roles and purposes · Executive sponsor + DPO + Legal [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Walk the public sign-up or client workflow with an operator. Compare the live fields and permissions with the intended filing.
2. Ask Finance to identify the owner of the payment reference and ask the DPO to test access to the registration and reporting service.
3. Set the financial year end and request sample complaint and breach exports before assigning the final report date.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which entity and purposes appear on our registration, and does this match what the product collects now?
  • Can our DPO pull a complete complaint and breach history for the financial year before the report is due?

Worked scenario

A Kampala software supplier handles employee data for its own HR and processes billing data for customer clinics. Its DPO verifies how to register these purposes, asks IT to map overseas support and backups, and gathers complaint and incident totals before year-end.

What to read next

FROM THE SOURCE

Cases and numbers

Court conviction · 10 July 2025

UGX 300,000Fine in the first conviction reported by the PDPO

A loan app operator pleaded guilty to failing to register

The Makindye Standards, Wildlife and Utilities Court convicted the director of Nano Loans Microfinance Ltd, operator of Quickloan, after he pleaded guilty to failing to register. The PDPO says it gave him guidance before referring the case for prosecution.

What to check When a regulator contacts you about registration, give one executive ownership of the response and require evidence of each corrective action.

PDPO statement on the conviction and sentence (opens in a new tab)

PDPO reporting notice · August 2026

23 November 2026Deadline announced in the PDPO’s 2026 notice

The 2026 annual report notice names a filing date

The notice calls on registered controllers, processors and collectors to file their reports. Regulation 50 requires a summary of complaints and their statuses, plus breaches and the action taken.

What to check Keep the date from the applicable notice alongside your financial year deadline. Confirm any difference with the PDPO and keep its reply.

PDPO Knowledge Center, annual compliance reporting notice (opens in a new tab)

Published fees · Uganda shillings

UGX 100,000Published fee for a registration or renewal application

Registration and renewal carry the same filing fee

Schedule 2 lists a separate UGX 25,000 fee for a certified copy of a register extract or entry. Ordinary register inspection is free under Regulation 28.

What to check Budget for each filing and save the payment reference and receipt. If you need a certified extract for a contract, order it separately.

Regulation 28 and Schedule 2 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • 30 days from receipt

    Application investigation and report

    Regulation 18 measures from the application or additional information. Keep proof of both receipt dates.

    Official reference (opens in a new tab)
  • 15 days after the PDPO report

    Registration decision

    Track requests for evidence. Ask for the written decision and record the issued Form 4 if approved.

    Official reference (opens in a new tab)
  • At least three months before expiry

    Renewal filing

    Use Regulation 23 to plan the deadline and check the current PDPO form and submission window early.

    Official reference (opens in a new tab)
  • Within 90 days of financial year-end

    Annual compliance report

    Regulation 50 calls for complaint statuses and breach actions. Check the PDPO’s dated notices for your filing.

    Official reference (opens in a new tab)
The whole journeyabout 87 days across 4 steps
  1. 01Map the entities, roles and purposes, Executive sponsor + DPO + Legal, about 7 days
  2. 02Prepare, pay and file the application, DPO + authorized signer + Finance, about 45 days
  3. 03Report changes and renew the certificate, DPO + company secretary + Finance, about 14 days
  4. 04Submit the annual compliance report, DPO + Support + Security + accountable executive, about 21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 8 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map the entities, roles and purposesExecutive sponsor + DPO + LegalBefore covered collection or processing beginsSet a start dateUganda registration scope and DPO review; Processing inventoryOpen
Prepare, pay and file the applicationDPO + authorized signer + FinanceBefore the service relies on registrationSet a start dateUganda application and transfer evidence; Response logOpen
Report changes and renew the certificateDPO + company secretary + FinanceWithin 14 days of a registered change and ahead of expirySet a start dateUganda certificate and renewal register; Evidence inventoryOpen
Submit the annual compliance reportDPO + Support + Security + accountable executiveWithin 90 days of financial year-end under Regulation 50Set a start dateUganda annual compliance report; Rights workflowOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Map the entities, roles and purposes

    Who Executive sponsor + DPO + Legal When Before covered collection or processing begins

    Build a list of entities, purposes, data categories, recipients and retention periods. Decide which party determines purpose and means for each service. Confirm with the PDPO how to file distinct purposes and roles, and identify the local representative required in the application for applicants situated outside Uganda.

    How to do this step

    Before you start

    Service and entity lists, system settings, client instructions and DPO details.

    1. Identify which entity makes the decisions for each purpose and who receives the data. Record all retention periods and identify who can prove them.
    2. Confirm registration scope and any representative with Legal. Ask the PDPO how the portal handles distinct purposes and roles before finalizing the application.

    What a reviewer should see

    A dated scope decision names the roles, purposes, owner and evidence for each filing.

    When to escalate

    Raise an uncovered purpose or disputed role with Legal and the service owner before launch.

    What to produce

    Uganda registration scope and DPO reviewMemo

    Gather first

    • Legal entity list
    • Actual system data flows and forms
    • Client instructions
    • Retention settings
    • DPO appointment and authority

    How to prepare it

    1. Make a row per entity and purpose. Record the data categories, collection channels, recipients, retention periods and role. Ask operators to show the system and contracts that support each answer.
    2. Have Legal review the territorial scope, registration roles, distinct purposes and any claimed exemption. For an applicant outside Uganda, identify the representative and verify what the PDPO requires in the application.
    3. Ask the accountable executive to sign the role decision, confirm the DPO’s mandate and assign a custodian for each draft, approval and regulator response.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Applicant and activities
    Fictional Nakasero Billing Services Ltd in Kampala. The company runs its own employee payroll and supplies a clinic invoicing service under client instructions.
    Role and purpose decision
    Internal payroll uses staff data for employment administration. Clinic invoicing uses billing fields on the clinic’s instructions. Legal checks the registration treatment of each purpose with the PDPO.
    Open question
    A third party provides support. IT must identify what it can see, from where, and which copies it can retain before the DPO signs the filing.

    Check before handing it over

    Every purpose on the application has an owner, a substantiated role, and evidence of the actual data, retention and recipients.

    Give the signed scope decision to the filer and retain each source record used in the review.

    Processing inventorySpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.

    Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.

  2. 02

    Prepare, pay and file the application

    Who DPO + authorized signer + Finance When Before the service relies on registration

    Prepare the Form 2 particulars and Form 3 undertaking using the PDPO’s current forms. Review backups, hosting, supplier access and onward transfers against section 19 and Regulation 30 before signing the undertaking. Generate the Uganda Revenue Authority Payment Registration Number and pay the applicable fee. Save the submission and receipt. Track any requests, the written outcome and the issued Form 4.

    How to do this step

    Before you start

    Form 2 particulars, current Form 3, fee and payment details, and technical evidence for overseas processing.

    1. Match Form 2 answers to the signed role decision and actual processing. Ask Legal to approve the overseas processing evidence and undertaking before the signer submits it.
    2. Save the payment and submission receipts. Track PDPO questions and the formal outcome. Review the certificate against the application and reconcile the public register entry.

    What a reviewer should see

    A second operator can retrieve the filed application and show the fee, correspondence, reviewed certificate and approved scope.

    When to escalate

    Escalate any conditions or gaps before approving the activity.

    What to produce

    Uganda application and transfer evidenceSpreadsheet

    Gather first

    • Approved role decision
    • PDPO application and undertaking
    • Supplier contracts, regions and access settings
    • DPO contact information
    • Uganda Revenue Authority payment records

    How to prepare it

    1. Build an attachment index. For each Form 2 answer, capture the owner, source and approval date. Have the signer and DPO check registration details and supporting documents against each other.
    2. Use the cloud configuration and supplier terms to document storage, processing locations and any onward transfer. Have Legal substantiate the applicable route under the Act and the regulations, and check the current Form 3 language with the PDPO before signing.
    3. Track the payment reference, receipt, application timestamp and requests for further information. When an issued Form 4 arrives, compare its details to the submitted entity, role and purposes the PDPO confirms.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer evidence row
    Fictional EU disaster recovery service. Security supplies a region export, access configuration and subprocessor list. Legal checks the route and evidence for each country before activation.
    Fee and payment
    The published registration application fee is UGX 100,000. Finance matches the Payment Registration Number and receipt to the submitted application.
    Status evidence
    The DPO saves the signed undertaking, exact submitted file, regulator correspondence and the issued certificate. The service owner waits for the verified filing outcome.

    Check before handing it over

    A backup filer can explain each application answer, locate the approved transfer evidence and prove the authority’s outcome.

    Share filing conditions and permitted operating scope with the service owner and secure the supporting records.

    Response logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

  3. 03

    Report changes and renew the certificate

    Who DPO + company secretary + Finance When Within 14 days of a registered change and ahead of expiry

    Verify the issued certificate and reconcile it with the register entry. Assign company changes to the corporate secretary and processing changes to service owners. Notify the PDPO in writing within 14 days of a change to registered particulars. Start renewal preparation early enough to confirm the accepted form and filing date with the PDPO before the three-month statutory cutoff.

    How to do this step

    Before you start

    Issued certificate, registered particulars, changes and current PDPO instructions.

    1. Have the change owner record the effective date and have the DPO send written notice within 14 days when registered details change.
    2. Compute the Regulation 23 date, ask the PDPO to confirm the process early and record the filed renewal and updated certificate.

    What a reviewer should see

    The certificate record shows which changes were reported and the relevant renewal decision and dates.

    When to escalate

    Escalate a missed statutory date or pending renewal to Legal before the current certificate expires.

    What to produce

    Uganda certificate and renewal registerSpreadsheet

    Gather first

    • Issued Form 4
    • Register entry and filed particulars
    • Change notices
    • Corporate and vendor change tickets
    • Current renewal instructions and fee

    How to prepare it

    1. Record the certificate number, entity, role, issue and expiry. Calculate the date three months before expiry and set an earlier internal review.
    2. Get written confirmation of the accepted form and timing where the instructions differ, then save the renewal filing and payment documents. Track the decision and compare its details with the outgoing certificate.
    3. For changes to registered particulars, log the effective date, owner, written notice due date and proof that the notice was sent within 14 days.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Renewal example
    Fictional certificate expires 20 December 2027. Set a review for 20 August and use 20 September as the three-month statutory date. Ask the PDPO to confirm timing and the current form before that date.
    Change example
    The office address changes on 4 May. The corporate secretary gives the DPO the valid date and new address, and the DPO keeps proof of written notice by 18 May.
    Status evidence
    Save the prior certificate, renewal receipt, issued certificate and each accepted change notice with its date.

    Check before handing it over

    The calendar, evidence of each filing and issuer status agree for every registered entity and role.

    Give the DPO and backup filer access to the register. Give Finance the renewal due dates and payment status.

    Evidence inventorySpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  4. 04

    Submit the annual compliance report

    Who DPO + Support + Security + accountable executive When Within 90 days of financial year-end under Regulation 50

    Reconcile every complaint and its status against the case log. Reconcile every data breach and the action taken against Security’s incident log and regulator notices. Have the DPO review the counts and file through the current PDPO channel. Keep the exact filed report, working papers and acknowledgment, and check for current filing notices.

    How to do this step

    Before you start

    Financial year close date, full complaint and breach logs, and the current PDPO reporting notice.

    1. Have each source owner confirm the period and counts. Reconcile pending and resolved complaints and verify the action taken on each breach.
    2. Submit the reviewed report through the current PDPO channel, save the exact version and receipt, and give the executive the list of unresolved actions and due dates.

    What a reviewer should see

    Complaint totals and breach actions tie to source evidence and the submitted report.

    When to escalate

    Escalate an unverified count, missing source system or evidence that an immediate breach notice may have been missed.

    What to produce

    Uganda annual compliance reportReport

    Gather first

    • Financial year dates
    • Complaint and resolution logs
    • Security incident register
    • External notices and corrective actions
    • Current PDPO filing instructions

    How to prepare it

    1. Fix the reporting period and list every system and team that can receive complaints or detect a breach. Have Support and Security export case references, dates, status and response evidence.
    2. Reconcile the totals against the source records. List whether each complaint is resolved or pending and summarize breaches and actions taken. Keep a private evidence index and use the issuer’s current reporting fields.
    3. Have the DPO verify completeness. Have the accountable signatory review open items, record submission and preserve the acknowledgment or receipt.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional complaint counts
    6 complaints received. Five resolved and one pending at year-end. Internal reference CMP-041 is pending with one named case owner.
    Fictional breach entry
    One incident. Evidence references IR-018 and the related notice. Access disabled on discovery, logs preserved and the affected export process amended.
    Submission evidence
    DPO records the financial year, the applicable due date and any current PDPO notice. Keep the filed version, sign-off, receipt and any regulator request together.

    Check before handing it over

    Complaint totals reconcile to resolved and pending cases, each breach has a documented action, and the submission can be reproduced.

    Give the accountable executive the submission receipt and the owners and dates for unresolved actions.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.

    Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes