{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihxrnmwi4dkc3s3rijuuxzktgv6istabohw73nepj3o5mtcgvzss4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mjost6ccyke2"
  },
  "path": "/t/feature-request-vault-chats-for-sensitive-retained-conversations/1379173#post_1",
  "publishedAt": "2026-04-17T10:52:10.000Z",
  "site": "https://community.openai.com",
  "textContent": "**Feature request: Vault Chats for sensitive retained conversations**\n\n**Summary**\nAdd a vault-style chat space inside ChatGPT for conversations that users want to keep, but protect separately from normal chat history.\n\n**Problem**\nToday there is a gap between privacy and continuity.\n\nUsers can:\n\n  * keep normal chats with history and continuity, or\n\n  * use Temporary Chat for privacy\n\n\n\n\nBut they cannot keep a long-running sensitive conversation in a protected area with an extra access barrier.\n\nThis matters for topics like:\n\n  * intimate health\n\n  * relationship issues\n\n  * legal or financial planning\n\n  * sensitive business strategy\n\n  * private personal reflection\n\n\n\n\nFor many users, the concern is not account compromise. It is everyday device access: a partner, family member, colleague, or anyone who may temporarily have access to an unlocked phone or computer. In those cases, archived chats are not enough, and Temporary Chat removes the retained history users may need.\n\n**Requested feature**\nCreate **Vault Chats** : an optional protected chat area within the same account for sensitive retained conversations.\n\n**Core behavior**\n\n  * User can mark a chat or folder as **Vault**\n\n  * Vault requires a second unlock step beyond normal app access\n\n  * Vault chats remain saved and searchable inside the vault\n\n  * Vault chats stay separated from normal chat history and memory surfaces\n\n  * Vault can auto-lock after inactivity\n\n  * Vault should be hidden from casual browsing when locked\n\n\n\n\n**Ideal unlock options**\n\n  * device biometrics\n\n  * separate PIN/passcode\n\n  * system secure enclave / private storage integration where available\n\n\n\n\n**Minimum viable version**\n\n  * lock/unlock Vault area with PIN or biometric\n\n  * move chats in and out of Vault\n\n  * keep vault chats retained like normal chats\n\n  * hide previews, snippets, and titles while locked\n\n  * exclude vault chats from standard sidebar/history view until unlocked\n\n\n\n\n**Important privacy expectations**\nUsers should be able to clearly control whether Vault chats:\n\n  * participate in memory\n\n  * appear in search outside vault\n\n  * are used for personalization\n\n  * are included in exports\n\n  * are visible in notifications, previews, widgets, or recent items\n\n\n\n\n**Why this matters**\nThis solves a real user need that is not covered by current controls:\n\n  * Temporary Chat is private but does not preserve continuity\n\n  * Archive reduces clutter but is not a security boundary\n\n  * Logging out and using separate accounts is awkward and not realistic for normal use\n\n\n\n\nA protected retained-chat space would let users continue important sensitive conversations over time without exposing them alongside ordinary chats.\n\n**User value**\n\n  * safer long-term use for sensitive topics\n\n  * less need for account switching or manual deletion\n\n  * stronger trust in ChatGPT as a personal thinking tool\n\n  * better separation between everyday work and private matters\n\n\n\n\n**Example use cases**\n\n  * ongoing private health tracking and questions\n\n  * relationship journaling and decision support\n\n  * sensitive startup, legal, or negotiation strategy\n\n  * confidential self-reflection kept separate from work/project chats\n\n\n\n\n**Design principle**\nUsers should not have to choose between:\n\n  1. privacy with no continuity, or\n\n  2. continuity with weak local privacy\n\n\n\n\nVault Chats should provide both.\n\n**Suggested product framing**\n“Vault Chats: a secure space for sensitive conversations you want to keep.”\n\n**Success criteria**\n\n  * users can keep sensitive chat history without exposing it in normal chat browsing\n\n  * unlocking requires intentional authentication\n\n  * locked vault content does not leak through previews, search, notifications, or sidebar history\n\n  * users understand exactly how vault data behaves for memory, training, export, and retention\n\n\n\n\n**Bottom line**\nPlease add a vault-style protected chat space for sensitive retained conversations. This would close a meaningful product gap for users who need continuity, but do not want certain chats casually accessible on a shared or temporarily accessible device.",
  "title": "Feature request: Vault Chats for sensitive retained conversations"
}