Legal: Privacy DSR Response Preparation with Codex: Sandbox Policy
A production playbook for privacy DSR response preparation in legal operations using Codex: sandbox policy, run-scoped inputs, logs, typed results, and artifacts.
Audience: Privacy legal teams handling data subject requests
The problem
Privacy legal teams handling data subject requests need privacy DSR response preparation to run repeatedly against identity evidence, data maps, request forms, and response templates. In legal operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Run privacy DSR response preparation in an ephemeral sandbox, keep provider credentials in the broker, expose narrow tools, and store logs outside the workspace for review.
Tradeoffs and failure modes
A narrower runtime blocks ambient machine behavior, but it gives security reviewers a concrete boundary. For privacy DSR response preparation, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Runtime boundary
filesystem: /skill and /skill/.argo/inputs only
network: deny by default
artifacts: /skill/output/artifacts
logs: retained outside sandbox
provider: Codex
Run this on Argo