# Data and SDK map

UK cookie and marketing rules | Blank worksheet

Step: Find what runs in a clean session
Owner: Web engineering + privacy lead
When: Before adding or changing tags

## 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.

## Fill in

### Source
[Add details here]

### Destination
[Add details here]

### Data and purpose
[Add details here]

### Protocol and boundary
[Add details here]

### Owner and validation
[Add details here]

## 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.

Use the current rules and any prescribed forms for your engagement.
