Privacy request queue
Access, export and erasure requests from data subjects, and the record of how each was decided.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
Each request with the identity verification behind it, the decision and who made it, and the execution record — the evidence that a request was answered within its statutory window.
What has to exist first
- Reads
- staffPrivacyRequestsList
- Actions
- staffPrivacyRequestVerify
- staffPrivacyRequestDecide
- staffPrivacyRequestExecute
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.