Template library
TRUST ATLAS WORKSHEET

Data flows

PIPEDA · Step 1 · Determine federal and provincial scope
Who prepares it
Privacy counsel + operations
When to prepare it
At initiation

Worked example

This example uses fictional details. Use the same fields with evidence from your work.

Source
Web checkout
Destination
Billing API in EU region
Data and purpose
Order reference and billing email to send the receipt
Protocol and boundary
HTTPS, crosses from public network into hosted production
Owner and validation
Billing owner, validated against request logs on 2026-11-12

Gather first

  • System and vendor inventory
  • Examples of live transactions or data events
  • Approved boundaries and information categories

How to prepare it

  1. Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
  2. Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
  3. Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.

Review

An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.

Handoff

Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.

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