data-rights-operations-reviewlisted

# Data Rights Operations Review Produce one **Data Rights Operations Contract** that can accept, authorize, fulfill, prove, communicate, and safely recover each supported request without deleting the wrong person's data or making false promises. ## Atomic boundary Own request intake through verified closure for access, export, correction, deletion, restriction, objection/opt-out, withdrawal, and appeal. Consume the product's data inventory, retention/hold rules, identity authority, contracts, and current jurisdiction-specific requirements. Do not author those upstream facts, give legal advice, or redesign the whole privacy lifecycle. ## When not to use - Use `privacy-data-lifecycle-review` when the primary artifact is proactive purpose, collection, consent/preference, vendor, retention, region, or privacy-impact design. - Use the qualified legal, support, analytics, security, or backup owner when the primary job is legal interpretation, support-organization design, event instrumentation, security engineering, or product backup implementation rather than a rights-request case. ## Resource routing - Read `references/request-control-and-fulfillment.md` for every task. - Read `references/rights-edge-cases-and-proof.md` for shared workspaces, minors/agents, holds, backups, derived data, portability, vendors, appeals, or high-risk deletion. ## Source verification Retrieve current deadlines, identity limits, rights, exceptions, formats, and communication duties from applica