Compliance Glossary for Confluence

Does evidence survive source deletion?

Yes. A completed baseline can preserve evidence after its live Confluence source is deleted. The freeze stores canonical content separately and records the exact revision, hash, usages, and findings. Survival depends on retained frozen content and successful package checks. Archive records alone cannot recreate missing body bytes. Verification reports source deletion as a distinct evidence gap.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Readable page at freeze timeCapture its exact scanned revision and canonical bodyFrozen revision with SHA-256 identityDeletion or source drift before capture blocks the freeze
Canonical frozen contentStore it under a content-addressed object keyRetained bytes separate from the live pageRetention policy still controls deletion
Revision recordStore hash, byte length, media type, and content object keySearchable revision evidenceMetadata alone cannot reconstruct missing body bytes
Later live-source deletionPreserve the deposited baseline and report the source stateFrozen evidence plus a distinct deletion gapThe deleted live page does not become available again
Verifiable archivePreserve ordered artifact, usage, link, meaning, and conformance recordsPortable evidence records with root and content hashesIt is not a full Confluence backup
Retention date or legal holdEvaluate evidence lifecycle policyRetain, expire, or hold dispositionLegal hold blocks deletion; elapsed retention can permit it

How it works

  1. Before deletion, open Terminology Baseline.
  2. Use Create enterprise freeze and select Prepare and queue freeze.
  3. Review Freeze progress and Coverage blockers.
  4. Select Run verification. Use Export archive for portable records.
  5. After deletion, use Search deposited evidence or the Artifact filter.
  6. Select Open evidence for the frozen revision.
  7. Run verification again. Keep the source-deletion finding with the retained evidence.

Example

A policy page is captured at revision 12. Its canonical body and hash enter a completed baseline. The live page is later deleted. The frozen revision remains available while its retained content object is still present. Verification reports the deleted source separately. If capture never completed, the app cannot reconstruct revision 12 from archive metadata alone.

What this does not mean

Evidence survival is conditional. Capture must finish before source deletion. Required frozen objects must remain under the configured retention policy. Archive validation must pass. The app does not restore a deleted Confluence page. It does not provide a tenancy backup, legal WORM storage, or guaranteed indefinite retention.

Related questions

Next step

Freeze and verify critical revisions before their live sources can be removed.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.