{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-22T21:15:08.873Z",
  "record_id": "VXI-EXT-PROCUREMENT-ATLAS-BACKUP-POLICY-CLUSTER-TERMINATION-RESIDUE-01-v1",
  "record_kind": "external_reference",
  "title": "MongoDB Atlas: Cluster termination and protected backup residue",
  "system": "MongoDB Atlas",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does terminating an Atlas cluster remove snapshots governed by a Backup Compliance Policy?",
  "near_questions": [
    "Do Atlas backup snapshots survive cluster termination?",
    "Can extra snapshot retention outlast Atlas backup protection?",
    "Does removing an Atlas cluster complete data offboarding?",
    "What backup evidence remains after terminating a protected Atlas cluster?"
  ],
  "supported_claims": [
    {
      "claim": "Atlas retains existing snapshots after cluster termination according to the backup policy. With Backup Compliance Policy enabled, snapshot deletion and reduced retention are restricted. Extra snapshot retention can extend storage beyond the protected period, when appropriately authorized users can delete snapshots. Cluster removal and backup erasure are therefore separate decisions.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified deletion or compliance certification from a product policy name",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Atlas retains existing snapshots after cluster termination according to the backup policy. With Backup Compliance Policy enabled, snapshot deletion and reduced retention are restricted. Extra snapshot retention can extend storage beyond the protected period, when appropriately authorized users can delete snapshots. Cluster removal and backup erasure are therefore separate decisions.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Backup Compliance Policy",
    "source_url": "https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy/",
    "checked_on": "2026-10-22",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-ATLAS-BACKUP-POLICY-CLUSTER-TERMINATION-RESIDUE-01-v1",
    "candidate_record_sha256": "4449bf4356344f54d2e75c1b1aaa044481786362d0cea08a5d47f3670e9f17d5",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Atlas retains existing snapshots after cluster termination according to the backup policy. With Backup Compliance Policy enabled, snapshot deletion and reduced retention are restricted. Extra snapshot retention can extend storage beyond the protected period, when appropriately authorized users can delete snapshots. Cluster removal and backup erasure are therefore separate decisions.",
    "required_buyer_context": "Terminated cluster and retained snapshot inventory; Backup Compliance Policy and protected retention periods; Extra retention, copy settings and authorized deletion evidence. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-22",
    "claim_to_check": "Does terminating an Atlas cluster remove snapshots governed by a Backup Compliance Policy?",
    "documented_statement": {
      "status": "documented",
      "statement": "Atlas retains existing snapshots after cluster termination according to the backup policy. With Backup Compliance Policy enabled, snapshot deletion and reduced retention are restricted. Extra snapshot retention can extend storage beyond the protected period, when appropriately authorized users can delete snapshots. Cluster removal and backup erasure are therefore separate decisions.",
      "source_ids": [
        "atlas-compliance"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "An exit record should account for retained backups after the primary cluster disappears.",
      "source_ids": [
        "atlas-compliance"
      ]
    },
    "buyer_evidence_required": [
      "Terminated cluster and retained snapshot inventory",
      "Backup Compliance Policy and protected retention periods",
      "Extra retention, copy settings and authorized deletion evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a full-erasure finding while retained snapshots or their retention conditions remain unresolved."
    },
    "unknowns": "Snapshot contents, retention enforcement and actual deletion are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Snapshot contents, retention enforcement and actual deletion are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "atlas-compliance",
        "url": "https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy/",
        "final_url": "https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy/",
        "title": "Backup Compliance Policy",
        "checked_on": "2026-10-22",
        "captured_at_utc": "2026-10-22T21:06:17.726Z",
        "version_context": "Rolling official documentation captured on review date; not a pinned software release.",
        "sha256": "c10b29203b1bb2b41f15e4a61d4ce99586bd786fea117b755c04a7b5a7edb511",
        "bytes": 880395,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Limitations",
          "Retention",
          "Disable policy"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Make residual backup custody visible in enterprise offboarding decisions.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Make residual backup custody visible in enterprise offboarding decisions.",
    "refusal_conditions": [
      "Refuse a full-erasure finding while retained snapshots or their retention conditions remain unresolved."
    ]
  },
  "niche": {
    "niche_id": "enterprise-ai-data-custody-exit-assurance",
    "label": "Enterprise AI Data Custody & Exit Assurance",
    "classification_id": "custody",
    "classification_label": "AI Data Custody, Retention & Exit Assurance",
    "topic_id": "custody",
    "buyer_intent": "Make residual backup custody visible in enterprise offboarding decisions.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#atlas-backup-policy-cluster-termination-residue",
  "machine_readable_record": "/varexis-index/records/atlas-backup-policy-cluster-termination-residue.json"
}
