{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T13:45:35.999Z",
  "record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
  "record_kind": "external_reference",
  "title": "Copilot: Conversation deletion does not delete associated memory",
  "system": "Microsoft 365 Copilot",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does deleting a Copilot conversation through eDiscovery also delete its associated memory?",
  "near_questions": [
    "Which Copilot memories remain after deleting a conversation?",
    "Does an eDiscovery message purge remove inferred memory?",
    "What item class identifies Copilot memories?",
    "How do we scope a deletion review beyond Copilot messages?",
    "Is deleting chat history sufficient for a Copilot memory request?",
    "What evidence shows the associated memory was included?",
    "Can conversation removal be used as proof of memory erasure?",
    "Which retained AI objects need separate identification?",
    "What should a data owner ask about Copilot memory deletion?",
    "Does the Purview conversation search cover memory contacts?",
    "How do holds affect the authorised deletion scope?",
    "What remains unresolved when only message deletion is documented?"
  ],
  "supported_claims": [
    {
      "claim": "Microsoft documents Copilot memories as IPM.Contact items and states that deleting a conversation or message through Purview or eDiscovery does not delete the associated memory. Memories need their own identification and deletion scope. Conversation deletion is therefore insufficient evidence of complete removal of the related AI memory.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration, actual data erasure, effective access or completed business actions",
    "Legal advice, compliance determination, vendor certification or safety assurance",
    "Runtime enforcement, permission to act or expanded licensed-checker coverage"
  ],
  "public_summary": "Microsoft documents Copilot memories as IPM.Contact items and states that deleting a conversation or message through Purview or eDiscovery does not delete the associated memory. Memories need their own identification and deletion scope. Conversation deletion is therefore insufficient evidence of complete removal of the related AI memory.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Microsoft Purview: Search for and delete AI application data",
    "source_url": "https://learn.microsoft.com/en-us/purview/edisc-search-copilot-data",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-COPILOT-MEMORY-DELETE-01-v1",
    "candidate_record_sha256": "1781ee1674acc1da8f100c98c6728028936d59b3750ee000ce4144d5daf11166",
    "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": "Microsoft documents Copilot memories as IPM.Contact items and states that deleting a conversation or message through Purview or eDiscovery does not delete the associated memory. Memories need their own identification and deletion scope. Conversation deletion is therefore insufficient evidence of complete removal of the related AI memory.",
    "required_buyer_context": "The target conversations and associated memory inventory. The memory search scope, item class and authorised deletion evidence. The applicable retention or hold constraints and remaining-data review. 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-18",
    "claim_to_check": "Does deleting a Copilot conversation through eDiscovery also delete its associated memory?",
    "documented_statement": {
      "status": "documented",
      "statement": "Microsoft documents Copilot memories as IPM.Contact items and states that deleting a conversation or message through Purview or eDiscovery does not delete the associated memory. Memories need their own identification and deletion scope. Conversation deletion is therefore insufficient evidence of complete removal of the related AI memory.",
      "source_ids": [
        "copilot-memory"
      ]
    },
    "buyer_evidence_required": [
      "The target conversations and associated memory inventory.",
      "The memory search scope, item class and authorised deletion evidence.",
      "The applicable retention or hold constraints and remaining-data review."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim that associated memories were removed solely because the conversation was deleted; refer unresolved hold obligations to the responsible owner."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "copilot-memory",
        "url": "https://learn.microsoft.com/en-us/purview/edisc-search-copilot-data",
        "final_url": "https://learn.microsoft.com/en-us/purview/edisc-search-copilot-data",
        "title": "Microsoft Purview: Search for and delete AI application data",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T13:33:52.025Z",
        "version_context": "Microsoft Learn page updated 2026-06-29; Copilot memory item classes",
        "sha256": "505644671138235bd3c6205b7323a08e789b880726a5cff0cd3f597effe5460e",
        "bytes": 66979,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does deleting a Copilot conversation through eDiscovery also delete its associated memory?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "An enterprise data owner responding to an AI deletion request needs to identify derived memory as a separate retained item class.",
      "free": "Complete review, practical questions, sources 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": "The target conversations and associated memory inventory. The memory search scope, item class and authorised deletion evidence. The applicable retention or hold constraints and remaining-data review."
    },
    "buyer_relevance": "An enterprise data owner responding to an AI deletion request needs to identify derived memory as a separate retained item class.",
    "refusal_conditions": [
      "Do not claim that associated memories were removed solely because the conversation was deleted; refer unresolved hold obligations to the responsible owner."
    ]
  },
  "niche": {
    "label": "Enterprise AI Data Custody & Exit Assurance",
    "niche_id": "enterprise-ai-data-custody-exit-assurance",
    "topic_id": "enterprise-ai-custody",
    "buyer_intent": "An enterprise data owner responding to an AI deletion request needs to identify derived memory as a separate retained item class."
  },
  "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#copilot-conversation-deletion-memory-separation",
  "machine_readable_record": "/varexis-index/records/copilot-conversation-deletion-memory-separation.json"
}
