Methodology

How we map the PDPA

A compliance tool is only as trustworthy as the mapping behind it. This page explains exactly how DataGuard turns the Tanzania Personal Data Protection Act, 2022 into the control matrix you work through — what we include, what we leave out and why, and where we mark our own judgment. Nothing is hidden behind a black box.

9
Parts of the Act (plus the Schedule)
66
Sections reviewed
96
Statutory requirements
123
Practical controls
The source of truth

We start from the Act itself

The matrix is built from the primary legislation, not a secondary summary:

Instrument
Personal Data Protection Act — Act No. 11 of 2022 (Chapter 44)
English text
GN. No. 395B, published 13 June 2023 (Special Supplement No. 21 to Special Gazette No. 15 Vol. 104)
Commencement
1 May 2023 (GN. No. 326 of 2023)
Language note
The English version is a translation published pursuant to section 84(4) of the Interpretation of Laws Act, Cap. 1. Where meaning turns on wording, the authoritative text of the Act prevails.
From Act to controls

One clear chain, top to bottom

Every control can be traced back to the words of the Act. The matrix is a versioned chain:

Parts

The 9 Parts of the Act (plus the Schedule) — its top-level structure.

Sections

All 66 sections, each read in turn.

Requirements

The duties the obligation-creating sections place on organisations — 96 in all.

Controls

123 practical, testable questions you can actually answer and evidence.

Because the chain is preserved, every question you answer in DataGuard shows the section it comes from — so a reviewer, an auditor or the Commission can follow it straight back to the law.

Every section accounted for

We read all 66 sections — not a selection. Sections that create a duty for organisations become requirements and controls.

Sections that don't — the short title, the definitions, provisions addressed to the Commission or the State — are recorded together with the reason they create no organisational obligation. Nothing is silently dropped, so you can see the whole Act was considered.

Each control shows its working

Every control carries its legal reference, the evidence it expects, and the risk it addresses — and a label for how firmly it sits in the law (see below).

A gap you find becomes an owned, dated remediation task, tied back to the same section.

Versioned as the law moves

The matrix is released as a version (currently v1.0.0). When the Act is amended or subsidiary regulations arrive, we publish a new version.

Your answers are preserved across an update, except where a requirement itself has genuinely moved.

We label our judgment

You can tell the law from our interpretation

Not every control is a direct quote of the Act — some follow by implication, and some fill in where the Act leaves detail to practice. We never blur the two. Every control is tagged with its source type:

Explicit

The Act states the duty in so many words. The control restates it and points to the exact section.

Derived

The duty follows by necessary implication from what the Act says — the control makes the implicit requirement testable.

Interpretation

Where the Act leaves detail to practice or to subsidiary regulations, we apply professional judgment and label it as such — never dressed up as black-letter law.

Honest about scope

What this mapping is — and isn't

It is
  • A product implementation mapping of the Act into practical controls.
  • A way to assess, remediate and evidence your compliance work.
  • Transparent about its sources and its own judgment.
  • Kept current and versioned as the law develops.
It is not
  • Legal advice, or a substitute for a qualified adviser.
  • Legal certification that your organisation is compliant.
  • An authoritative interpretation of Tanzanian law.
  • A guarantee against regulatory action.

Found something you'd map differently?

The matrix is maintained by the DataGuard team in Tanzania, and it gets better when practitioners challenge it. If you think a control misreads a section, or a section deserves a control it doesn't have, tell us — we review every mapping question.

solutions@dataguard.co.tz