PRIVACY

Customer support ticket data flow.

This GDPR data flow diagram maps a support request from a customer to an application and an external support platform. The support service looks up the account, logs the ticket event and sends the ticket content to the processor that hosts or manages the case. The response returns through the same service, making the processor’s role and the boundary crossings clear. Privacy and support teams can use this as a compact starting point for reviewing which customer details appear in tickets, who can access them and whether attachments require a separate store. Replace the generic labels with the organization’s systems and actual data categories. The diagram is a process map, not proof that a support operation meets GDPR requirements.

UPDATED 2026-09-24
EXAMPLECustomer support ticket data flow.
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Privacy review

Key decisions

  • Customer contact: Ticket and contact details enter from the public internet.
  • Processor use: Ticket content crosses to an external support platform.
  • Access context: The service performs an account lookup before handling the case.

When to reuse this

Use this DFD to map a customer-support process before reviewing access and vendor handling.

FAQ

Frequently asked questions

Why include an account lookup?01
It shows that support handling may access account information in addition to the ticket itself.
What is a support processor?02
It is an external service that processes ticket content on behalf of the organization.
Should attachments be shown separately?03
Yes, if attachments go to a different store or are handled under different access or retention rules.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.