At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Readable page at freeze time | Capture its exact scanned revision and canonical body | Frozen revision with SHA-256 identity | Deletion or source drift before capture blocks the freeze |
| Canonical frozen content | Store it under a content-addressed object key | Retained bytes separate from the live page | The app runs no retention or deletion workflow |
| Revision record | Show Revision, SHA-256, and Availability | Searchable revision evidence | Metadata alone cannot reconstruct missing body bytes |
| Later live-source deletion | Leave the frozen copy untouched | Frozen evidence that outlives the page | The deleted live page does not become available again |
| Run verification | Check each stored object for presence, checksum, root, and owning freeze | Summary with match, missing, corruption, drift, or stale_source counts | No live-page check, so no "source deleted" state |
| Retention class, date, or legal hold | Record them with every frozen chunk | Stored policy metadata | Recorded only; not evaluated or enforced |
How it works
- Before deletion, open Terminology Baseline.
- Use Create enterprise freeze and select Prepare and queue freeze.
- Review Freeze progress and Coverage blockers.
- Select Run verification and keep the summary line.
- After deletion, use Search deposited evidence or the Artifact filter.
- Read Revision, SHA-256, and Availability in Frozen meanings and revisions.
- Record the deletion in your own change log. The app does not report it.
Example
A policy page is captured at revision 12. Its canonical body and hash enter the enterprise freeze. The live page is later deleted. The frozen revision stays searchable while its stored object is present. Run verification still reports a match, because it checks the stored copy. If capture never completed, the app cannot rebuild revision 12.
What this does not mean
Evidence survival is conditional. Capture must finish before source deletion. The stored objects must remain in app storage. The app does not detect or report live-page deletion. It does not restore a deleted Confluence page. It does not provide a backup, legal WORM storage, enforced legal hold, or guaranteed indefinite retention.
Related questions
Next step
Freeze and verify critical revisions before their live sources can be removed.
View on Atlassian Marketplace