Data mapping and records of processing

Nearly every other privacy task starts by asking what data the organization holds and where it goes: a request from a person, an impact assessment, a vendor review, a transfer decision. Without a map each one begins with the same weeks of asking around.

The short version

A data map is a current picture of what personal data an organization holds, why, in which systems, who else receives it and where it goes, and records of processing are the written form of that picture that a regulator can ask to see.

Article 30 of the GDPR requires controllers and processors to keep records of processing activities, and similar record-keeping duties appear in other laws. The text is on EUR-Lex. Whether a given exemption or a local equivalent applies to you is a question for your counsel, not an assumption we make for you.

What you get

  • A systems inventory. Every system that holds personal data, who owns it and what category of person the data is about.
  • Processing activities. For each activity, its purpose, the categories of data, who receives them, how long they are kept and the security measures around them.
  • A data flow map. How data enters, which systems and processors it passes through, and where it leaves the organization or the country.
  • Records of processing. The activities written in the form a regulator can read.
  • A maintenance routine. A map that is only built once starts going stale the day it is finished, so the engagement ends with an owner, a trigger for each update and a review date.

How the work runs

We start from how data actually moves, not from the org chart, and follow it in this order: where it is collected, where it is stored, who else receives it, and where it goes next.

How a data map follows personal data Four steps in order: where data is collected, the systems that store it, the processors and vendors that receive it, and the transfers that carry it out of the organization or the country. 1 Where it is collected Forms, apps, devices, partners. 2 Where it is stored Databases, SaaS, files, backups. 3 Who else receives it Processors and vendors. 4 Where it goes next Transfers out of the country.
The same four questions are asked for every processing activity.

Work is done through short interviews with system owners and a review of the systems themselves. Where a system is large or undocumented, personal-data discovery finds what the interviews miss. The output feeds transfer decisions and vendor review.

Who it is for

Organizations preparing for a regulator or customer question, launching in a new country, replacing a core system, answering their first access request, or inheriting a data estate through an acquisition. It is also the usual first step of a fractional DPO engagement.

Tools or a spreadsheet

A spreadsheet is enough for a small, stable organization; a platform earns its place when systems and teams change faster than a sheet can be kept current by hand. The choice, and how to run it, is covered in privacy tool selection and implementation; the technical side of the same inventory is in cloud security review and database security review.

Under US law

California’s regulations on risk assessments and automated decisionmaking took effect on 1 January 2026, with compliance dates running from 2027, and each depends on knowing which processing continues and which decisions are automated. The dates are set out in California’s 2026 privacy regulations; the map is where that knowledge comes from. HIPAA’s risk analysis starts from the same inventory (HIPAA readiness).

How the work is bounded

The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.

SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.

Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.

Questions we are asked

What is a data map?

A data map is a current picture of what personal data an organization holds, why, in which systems, who else receives it and where it goes, and records of processing are the written form of that picture that a regulator can ask to see.

Does the GDPR require records of processing?

Article 30 of the GDPR requires controllers and processors to keep records of processing activities, and similar record-keeping duties appear in other laws.

Do we need software to keep records of processing?

A spreadsheet is enough for a small, stable organization; a platform earns its place when systems and teams change faster than a sheet can be kept current by hand.

How is the map kept current?

A map that is only built once starts going stale the day it is finished, so the engagement ends with an owner, a trigger for each update and a review date.

Start with the systems you already know about

Background reading: records of processing built from systems. List the systems you know hold personal data and the countries you operate in. The reply says what a mapping scope would cover. See also all privacy services.

Discuss a scope