Conversation history is a service-managed record of prior AI prompts, responses, and sometimes generated items or metadata. In consumer and enterprise AI platforms, it helps users resume work, recover context, and review what the model produced. Because the history lives inside the service, not as a simple local file, it is governed by the provider’s retention, sharing, and access-control rules.
In cyber security, conversation history matters because it can contain secrets, internal plans, customer data, or other sensitive material. If an account is compromised, an attacker may read past chats to collect credentials or operational details. Defenders use conversation history for auditing, incident review, and policy enforcement, but they also limit exposure with strong authentication, least-privilege access, encryption, export controls, and retention policies. If AI outputs are important, teams should not assume the history will remain available forever or be recoverable after a service change.