Data Flow and Usage Diagrams (DFUDs) are structured visual artifacts that map how personal and sensitive data moves through an organization's systems, processes, and external boundaries — documenting not just the path of data, but the purpose of each movement, the transformations it undergoes, the parties that handle it, and the controls governing its use. A Data Flow Diagram (DFD) charts technical movement: where data originates (sources), how it is processed (transforms), where it persists (data stores), and where it exits (external entities). A Data Usage Diagram extends this by layering in business context: the stated purpose for each flow, applicable retention periods, legal basis for processing, and access control constraints. Together they form the documentary backbone of a privacy governance program — translating invisible data operations into an auditable, shareable artifact. They are NOT: (1) network topology diagrams — they map data movement, not infrastructure; (2) entity-relationship diagrams — they map flows, not schema; (3) standalone process flowcharts — they must include data stores and external entities; (4) one-time compliance deliverables — they are living documents requiring active maintenance.
Where it stops · what it isn't
- —DFDs map data movement and purpose — they do not replace data models, system architecture diagrams, or network maps, though they complement all three
- —Data usage diagrams extend DFDs with business context (purpose, legal basis, retention) — they are not substitutes for full Privacy Impact Assessments or DPIAs, though they serve as their visual foundation
- —Scope is bounded by the data subject population and regulatory perimeter being documented — a DFD scoped for GDPR compliance will differ from one scoped for HIPAA or PCI-DSS
- —DFDs document intended controls, not validated ones — separate assurance activities are required to confirm that documented controls are operating effectively
- —Automated data lineage tools and catalog metadata are inputs that populate or validate DFDs, not substitutes for the diagram itself
Connected concepts in the graph
Every cubelet sits in a knowledge graph. Here's what this one connects to.
PART OFData Lifecycle Management — Data Purpose (ISACA CDPSE Domain 3)
REQUIRESData Classification and Inventory
ENABLESPrivacy Impact Assessment (PIA) / Data Protection Impact Assessment (DPIA)Purpose Limitation Compliance (GDPR Art. 5(1)(b), CCPA)Third-Party and Vendor Risk ManagementIncident Response and Breach Scope Identification
RELATED TOData Retention and Deletion SchedulesData Subject Rights Fulfillment (Access, Erasure, Portability)
CONSTRAINSData Minimization and Purpose Limitation Controls