Data map

What it is for

The data map shows where personal data travels inside your organization: where it comes from, where it is stored, who receives it, and when it crosses the organization's boundary. It is the visual reading of what the processing activities declare.

File import

You can bring an inventory in from a spreadsheet. Column mapping is suggested automatically from header synonyms in Portuguese, English, and Spanish, but it is a list of known names rather than a model that guesses: an unusual header falls through as ignore.

That is why the import has a review step before anything is written — you see the suggested mapping and a simulation of the result before confirming.

What looks like a defect and is not

A dashed arrow in the diagram means inferred direction: the activity did not declare which processing operation happens there, so direction came from the path. It is a gap the screen admits to, not a drawing error — and it disappears once the operation is declared.

A data store drawn inside the boundary even though it belongs to a supplier means the storage owner was not declared. Without that declaration the map does not invent a boundary crossing — it prefers not to assert. Declare the owner in the storage block and the drawing changes.

Coverage at zero percent with a visibly dense diagram is not a contradiction: the flows are real, what is missing is the origin and storage declaration that coverage measures. The screen explains this in a banner of its own rather than leaving the number to stand alone.

And the first load after an update may be slow: the map re-derives its computed data once per organization when the algorithm changes.