Retention policies and cleanup
How long each class of data is kept, and the proof that expired data was removed.
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
The retention policy per data class, a preview of what publishing a change would delete, and the cleanup runs that carried it out with their certificates.
What has to exist first
- Reads
- staffRetentionGet
- Actions
- staffRetentionPreview
- staffRetentionPublish
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.