FIELD GUIDE03
Updated July 21, 2026 / 8 min
Map data and model access
Trace what enters the system, who can see it, what is retained, and which boundary must be verified.
Draw the data path before connecting a real account. Include the browser, vendor service, model provider, integrations, logs, exports, and every human who can inspect the result.
Working sequence
Make the evidence visible.
- 01
Classify the input
Separate public, internal, confidential, personal, regulated, and contract-restricted material.
- 02
Trace every hop
Record processors, subprocessors, connectors, logs, and administrative access.
- 03
Verify retention
Use current contractual and product documentation, not a marketing summary.
- 04
Set the permitted lane
State which data classes are allowed, blocked, redacted, or reviewed first.
Evidence to keep
Leave with four records.
- Data classification
- Processor map
- Retention evidence
- Approved-use boundary
A useful tool can still be the wrong place for a particular record.