Chrome can briefly hold unsent text in memory for crash recovery or session restore. That is not the same as chat history saved to an account, and it happens whether or not Docognito is installed. Docognito changes how the page looks, not what Chrome itself caches locally as you type.
What Chrome actually keeps while a tab is open
Modern browsers try not to lose your work when something goes wrong. If a tab crashes, or Chrome itself closes unexpectedly, a feature usually called session restore can bring your open tabs back, and in some cases restore text you had typed into a form field but never submitted. That behaviour is built into the browser engine, not into any particular website, and it predates chat assistants by well over a decade.
This is a short-lived, local mechanism. It exists to survive a crash, not to build a permanent record, and it lives in memory or in a temporary local store tied to your browser profile on that one device.
Session restore is not the same thing as history
It is worth being precise about the difference, because the two get confused constantly. Browser history is a list of pages you visited, kept deliberately, searchable from the address bar, and something you can clear from Chrome's settings at any time. Session restore is different: it is an attempt to reconstruct what was open, including unsubmitted form text, purely so a crash does not cost you a paragraph you had not finished.
Neither of those is the same as a saved chat conversation. the conversation itself, which OpenAI and Anthropic still receive and store, on a server, tied to your account, and reachable from any device you log into. That record exists regardless of what your browser does locally, and clearing your your browser history or restarting Chrome has no effect on it whatsoever.
Where an unsent draft can actually end up
In practice, the situations where this matters are narrow. Chrome crashing mid-sentence and offering to restore your tabs is the clearest one. A shared or unlocked computer where someone else opens Chrome and finds your session still restorable is another, and it is the one worth taking most seriously, because it does not require a crash at all, only an unlocked browser profile.
| What happened | What Chrome does with the draft |
|---|---|
| You typed a message and sent it | Nothing more to hold locally; the assistant now has it |
| You typed a message and closed the tab normally | Usually discarded, depending on the site's own composer behaviour |
| Chrome or the tab crashed mid-sentence | May offer to restore the tab, unsent text included |
| Someone opens your unlocked browser profile | Can see whatever a restored session still holds |
The bottom row is the one that actually costs you something. Locking your screen when you step away closes that gap without touching any setting in Chrome at all.
A shared device is the one place this stops being theoretical
On a computer more than one person uses, a restorable session can hand an unsent draft to whoever opens the browser next. Locking the screen, or using a separate Chrome profile per person, closes that specific gap.
What this has nothing to do with Docognito
This is the point worth stating plainly rather than skating past. Docognito redraws the visible page, redrawn as a document editor so that a glance reads a document editor instead of a chat window. It does not reach into Chrome's own memory management, and it has no way to change whether the browser engine itself caches an unsent form field for crash recovery. That caching happens on every site built the same way, whether or not the extension is installed, and whether the tab is disguised or not.
What the disguise does control is separate: the shape on your screen, the tab title, and the icon in the tab strip. None of those three touch how Chrome handles a crash.
How to reduce what a restored session could show
Turn off Continue where you left off
In Chrome's settings under On startup, choosing to open a new tab instead removes the most common route back to an old session.
Lock your screen, not just your browser
A locked operating system session is what actually stops someone else from reaching a restorable tab on a shared machine.
Send or discard, rather than leaving a draft mid-sentence
Finishing the thought and sending it, or clearing the field before you close the tab, leaves nothing for a crash to bring back later.
Not the same problem as what your screen shows
Chrome's crash recovery is a browser feature that predates every chat assistant and runs the same way regardless of what page you are on. Turn off automatic session restore if you would rather not rely on it, and lock your screen on any device more than one person can reach. For how the page itself looks while you work, that is a separate question, and it is the one Docognito answers.