OpenAI officially rolled out 'Locked Chats' across all ChatGPT subscription tiers, including Free, Plus, Team, Enterprise, and Edu. Users can now safeguard sensitive individual conversation threads behind a device PIN, Face ID, or Touch ID biometric lock. Crucially, locked chats feature strict memory isolation: interactions inside locked sessions are physically barred from updating ChatGPT's persistent user memory bank. Confidential corporate discussions, sensitive health queries, or proprietary code audits remain strictly ephemeral to the local lockbox without contaminating future general chat contexts.

Key Takeaways

  • ✓OpenAI officially released Locked Chats, rolling out globally across Free, Plus, Team, Enterprise, and Edu subscriptions
  • ✓Enables hardware-level protection via device PIN, Face ID, and Touch ID, shielding sensitive threads from physical shoulder surfing
  • ✓Guarantees complete memory isolation: queries, uploaded documents, and confidential context are strictly prohibited from updating user memory
  • ✓Eliminates context contamination risks when conducting proprietary code reviews, compliance audits, or medical inquiries
ChatGPT Officially Rolls Out Locked Chats: Biometric Authentication and Complete Memory Isolation Across All Tiers
🖼️Official Media
Click to view high-res
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Background and the Problem

As frontier AI assistants embed deeply into enterprise workflows, features like persistent cross-session memory introduce significant privacy hazards. Users routinely interleave trivial queries with highly confidential activities—such as proprietary software vulnerability triage, corporate restructuring discussions, and sensitive health evaluations. Previously, without turning off global memory entirely, facts extracted from confidential sessions were automatically indexed into the user's permanent memory bank, periodically bleeding into unrelated subsequent prompts. Furthermore, physical device sharing exposed unlocked conversation histories. Addressing these data governance vulnerabilities, OpenAI officially launched Locked Chats (@ChatGPT, Status #2112597766333673624) on October 21, 2026.

Architecture and How It Works

  1. Native Biometric Gating:
  • Integrates directly with device-level secure hardware enclaves (iOS Face ID, Android Biometrics, Windows Hello, macOS Touch ID);
  • Locked threads are immediately sealed behind a secondary authentication layer, requiring biometric verification to view or search;
  1. Absolute Memory Isolation:
  • Implements strict architectural write-fences: token streams, entity extractions, and behavioral observations generated within locked sessions are blocked from persisting into long-term user memory;
  • Ensures zero cross-context contamination between confidential deliberations and routine everyday prompting;
  1. Stealth UI & Background Protection:
  • Automatically hides locked threads from the sidebar hierarchy and suppresses notifications, blurring window contents immediately upon app switching.

Benchmarks and Measured Results

Disclosed in OpenAI's privacy architecture briefings and community testing:

  • Memory Bleed Zero-Leakage Verification:
  • Across adversarial prompt-injection probes probing cross-session fact recall, information contained within locked chats recorded a 0.00% memory leakage rate;
  • Universal Availability:
  • Accessible without tier restrictions across Free, Plus, Team, Enterprise, and Edu user bases;
  • Local authentication unlock latency clocks under 150 ms, preserving fluent productivity.

Getting Started for Developers

  • Activation: In the ChatGPT mobile app or desktop web interface, right-click or long-press any conversation and select 'Lock Chat';
  • Official Announcement: View verified feature walkthrough via @ChatGPT status https://x.com/ChatGPT/status/2112597766333673624;
  • Operational Recommendation: Engineering and corporate teams utilizing ChatGPT for proprietary code refactoring or security assessments should mandate Locked Chats as standard operating procedure (SOP) to ensure uncompromised IP protection.
Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextPerplexity Computer Launches Natively on macOS: Full On-Device Model and Agent Execution Without Cloud Roundtrips
Read Now→