Map personal information and define program scope
6 min read
Lesson objectives
- Apply the decision in map personal information and define program scope, recording assumptions, evidence and scope limits.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
The scope of a privacy program begins with what the organization actually does with personal information. The skill in this lesson is to produce an initial map connecting source, purpose, decision owner, processor, retention point and onward flow. Domain I.A of the current CIPM Body of Knowledge calls for identifying sources, types and uses of personal information; understanding the business model, operating environment and risk appetite; and choosing a governance model, team structure and internal partners. These tasks depend on one another. Accountability for an undiscovered flow is unlikely to work.
Use a unit of analysis smaller than “customer data.” A useful record answers six questions: Where did the information originate? Which fields are present? Why is it used? Which system or third party receives it? Who decides the purpose and who operates the processing? When is continued retention reconsidered? Distinguish information supplied by a person from information inferred from behavior. Separate use needed to deliver a service from marketing or secondary analytics. The same identifier can pass through several systems while the decisions governing its use differ.
Build the map from process interviews, system settings, supplier agreements, samples of records and an actual request path. A questionnaire answered by one department is insufficient. Mark each flow as evidenced, reported but unverified, or unknown. Suppose marketing says an analytics tool does not receive phone numbers, while the integration configuration sends a phone number in a conversion event. The technical evidence calls for correcting the inventory and examining purpose and supplier controls. It does not, by itself, settle which law applies. That depends on locations, roles, transactions and contractual facts still to be established.
Define program boundaries by processes, systems, sites and counterparties rather than department names alone. A central privacy team might set policy and risk criteria while product, human resources, procurement and operations own the evidence of daily execution. Compare this structure with a distributed arrangement using the organization's size, business lines, pace of change and central review capacity. Record a provisional decision: what enters scope now, what remains under investigation, who escalates exceptions and who approves a change of purpose. An explicit provisional boundary is safer than an implicit claim that every system was inventoried.
Determine legal scope after recording where people and operations are located, which parties act in which roles and what activity occurs. The country of the company's headquarters alone does not establish the applicable rule for every flow. This lesson does not issue a compliance determination. It creates questions for qualified review: Where are the people? Who determines purposes? Is information transferred or disclosed across borders? Does the activity involve a regulated sector or children? Later answers can be connected to policy, retention and contracts.
The useful result is an inventory with an owner, date and evidence grade, followed by a decision; an attractive diagram without those fields is insufficient.
Lesson summary
Map flows and assign verification owners to unknowns.