Personal data can spread beyond the recording into transcripts, tool arguments, notifications, and diagnostic traces. Map every processing and storage boundary before deciding which settings make the receptionist appropriate for a pilot.
A data map records movement and purpose
A personal-data flow map identifies what information enters a workflow, which services process it, what artifacts are created, and who can access them. It should cover both routine calls and error paths.
For a proposed inventory, list data categories, source, destination, purpose, storage location, access role, retention owner, and deletion mechanism. Distinguish transient processing from durable storage. A service receiving audio may not retain it in the same way as a recording store, but that difference needs verified evidence.
Include the application’s own observability and support channels. Copying a failed payload into a support ticket creates another data location even if the primary database is carefully controlled.
Map a fictional service enquiry
A caller supplies a name, callback number, address, and fault description. Audio passes through telephone and speech services. The agent creates a summary, the request tool writes selected fields, and staff receive a notification linking to the record.
The map should identify whether the notification contains the full address or only an opaque reference. It should also show whether a failed save logs the raw payload. Those choices materially change where personal information resides.
| Boundary | Inventory question |
|---|---|
| Speech processing | Which content is transmitted and retained? |
| Agent context | Which retrieved or caller fields are included? |
| Business write | Which selected fields become authoritative records? |
| Notification | Does it duplicate details or link securely? |
| Diagnostics | Can errors export raw customer information? |
Use synthetic markers in an isolated test and follow them through exported artifacts. Interviews and diagrams reveal intended flow; runtime evidence reveals hidden copies and error-path differences.
Turn the map into decisions
Assign an owner to every destination and unresolved question. Use the inventory to minimise collection, constrain access, and design deletion tests. A diagram without verified settings is a starting hypothesis rather than evidence of the deployed flow.
The applicable legal and contractual obligations depend on the actual deployment and must be established separately. This article describes an engineering inventory method, not a universal compliance determination. Even a complete inventory can become stale when providers or instrumentation change.
The proposed workflow builds on the kinds of integrations described in the voice platform case study. Continue with trace redaction and cross-integration deletion.
Data mapping FAQ
Should failed calls be included?
Yes. Errors and retries can create copies that the happy path never produces.
Is a vendor list a complete data map?
No. Record the actual categories, purposes, artifacts, controls, and movement between services.
When should the map change?
Review it after material tool, provider, logging, notification, retention, or workflow changes.