Once a request is verified and scoped, TruePrivacy propagates it simultaneously to all connected systems.
DSR fulfillment view showing per-system execution status

​
Cross-system execution

  • Deletion requests remove data from CRMs, databases, marketing platforms, and data warehouses in parallel.
  • Access requests compile a data export from each in-scope system into a single package.
  • Correction requests apply the confirmed change to each system holding the record.
Each connected system reports its own completion status on the request record. Exceptions or partial failures are flagged for human review — the request cannot close until every in-scope system reports completion.

​
Manual tasks for non-automated systems

If a system cannot be automated — for example, a legacy database without API access — TruePrivacy flags it as a manual task, assigns it to the responsible team member, and tracks completion within the same request thread.
1

Review flagged systems

Systems without automated connectors appear in the request’s execution plan marked “manual”.
2

Complete and confirm

The assignee performs the action in the target system and confirms completion, optionally attaching evidence.
3

Request closes when all systems report done

Automated and manual completions roll up into one overall status.

​
Responding to the data subject

  • Responses are sent through the channel the request arrived on, using configurable templates per request type and language.
  • Access-request exports are delivered as expiring, access-controlled download links — never as plain email attachments.
  • The closing response, together with the full execution log, is stored on the request record and exportable as compliance evidence.
For high request volumes — coordinated erasure campaigns, for instance — use bulk mode to verify a batch, review the combined scope, and execute across systems for all requests in a single operation.