Try live
Schedule a retention expiry for a resource, list due schedules, then dispose. Not DLP, no remote delete, not a legal hold engine.
Not DLP, no remote delete, not a legal hold engine. The demo host runs in isolation — nothing is stored.
Demo host: isolated demo host set by your deployment
Retention Expiry Clock · Agents & policy
Schedule → list due → dispose
Schedule a resource for expiry, see what is due now, and dispose a single schedule one-shot with an audit note. Status transitions active → disposed.
Not DLP, no remote delete, not a legal hold engine. The demo host runs in isolation — nothing is stored.
Schedule
01Inspect & dispose
02The schedule ID from the last create is held client-side. Inspect a single record, list what is due as of a timestamp, or dispose one-shot with an audit note.
Result
03Details
- Schedule ID
- —
- Resource
- —
- Expires at
- —
- Content hash
- —
- Policy ID
- —
- Meta
- —
- Created at
- —
- Disposed at
- —
- Disposal note
- —
- As of
- —
- Due count
- —
- Total active
- —
Raw response
—
Operator and workspace consoles are separate applications (pilot).