Which AI chat apps keep your chat history on your device, and who can still read it
The Morse teamPublished 9 min read
The AI chat apps that keep your chat history on your device are Morse and a few other cloud apps that store history in your browser, Duck.ai and Venice, plus the local apps, LM Studio, Jan, GPT4All, and Ollama. Proton's Lumo, Maple, and Confer take a third route and keep history on their servers, encrypted so that only your keys open it. In every cloud app the model still has to read your message somewhere to answer it, so "on your device" tells you where the history lives, not who reads each message on its way to the model.
We read each app's own privacy page, documentation, or FAQ on November 20, 2026, and quote them below, with every page listed under Sources at the end. Several of these companies are more exact than most: LM Studio publishes the folder your chats sit in, Confer explains how its app checks the server before sending anything, and Maple lists each check its app runs.
Morse is a private AI chat app with GPT, Claude, Gemini, DeepSeek, and uncensored models, encrypted so even Morse can't read your chats. Your history is stored in your browser, encrypted, and Morse's servers keep no log of your messages. Every message goes through the Morse Enclave, open-source code running in AWS Nitro hardware, and anyone can check it with npx @askmorse/verify inference.trymorse.ai (Verify).
What does it mean when an AI chat app stores history on your device?
It means the record of your past conversations sits in a file or a browser database on your own computer, not in an account on the company's servers. Three things it doesn't mean are worth knowing before you trust the label.
The model still reads your message. A local app runs the model on your machine, so your words never leave it. A cloud app has to send each message to a server where a model reads it. Proton is plain about this for Lumo: "we need to provide the LLM with cleartext messages." On-device history protects the archive, and the mode or architecture an app uses decides what happens to each message.
A local file isn't always an encrypted one. LM Studio says "Conversations are stored in JSON format" in ~/.lmstudio/conversations/ on Mac and Linux, and its page doesn't mention encryption. Jan's privacy page doesn't either. In July 2024, MacRumors reported that ChatGPT's Mac app was "locally storing users' conversations with the chatbot in plain text," until OpenAI shipped a version that "encrypts these conversations."
Browser storage belongs to the browser. Duck.ai says Safari deletes its saved chats "if you go more than 7 days without visiting duck.ai," while other browsers keep them "indefinitely, unless you explicitly clear your browser data." Venice says that on another device or browser "your previous conversations won't be available because they were never stored centrally." A browser-stored history moves only by backup or sync.
What AI chat apps keep your chat history only on your device?
Of the ten apps we checked, the four local apps keep everything on your computer and three cloud apps keep your history in your browser. The other three store it on their servers under encryption they say they can't open. The table sets them side by side, read November 20, 2026, from each company's own pages, with Morse listed first.
| App | Where your history lives | Who can open the stored history | Who reads each message | How to check |
|---|---|---|---|---|
| Morse | Your browser (IndexedDB), encrypted, and never on Morse's servers in a form Morse can read | You, with two keys: one your browser never lets out, and one Morse's server sends only while you're signed in | Depends on the mode you pick. In E2EE, only a verified enclave can decrypt it, not Morse | npx @askmorse/verify inference.trymorse.ai, and the lock on any E2EE reply |
| LM Studio | JSON files in ~/.lmstudio/conversations/ | Anyone with access to your computer. Encryption isn't mentioned | Your computer: "Nothing you enter into LM Studio when chatting with LLMs leaves your device" | Right-click a chat and choose "Reveal in Finder" |
| Jan | Your computer: history and usage logs "are stored locally and never leave your computer" | Anyone with access to your computer. Encryption isn't mentioned | Your computer, or a remote API's servers if you pick one, under that provider's policy | Use local models only |
| GPT4All | Your computer: Nomic says "no data leaves your machine". Its docs don't name the chat folder | Anyone with access to your computer | Your computer. Sharing chats with the GPT4All community is opt-in and off by default | Leave the Data Lake setting off |
| Ollama | Its FAQ doesn't say where chat history is kept | Anyone with access to your computer | Your computer: "We don't see your prompts or data when you run locally." Cloud models run on Ollama's servers | Set OLLAMA_NO_CLOUD=1 |
| Duck.ai | Your browser, by default. Optional Sync & Backup on DuckDuckGo's server | You. The Sync & Backup key "is only stored on your devices" | The model provider, with your IP address removed, which deletes it "at most within 30 days, with limited exceptions" | Turn off recent chats, or use the Fire Button inside Duck.ai |
| Venice | "Stored locally within your browser and is not uploaded or saved on Venice's servers" | You | Depends on the mode. Anonymous: "Provider sees and likely saves your prompt." E2EE (Pro): "only decrypted inside a verified TEE" | Choose the mode for each chat |
| Proton Lumo | "Stored on your device and synced to Proton servers using zero-access encryption" | You: "only the user's device can decrypt the stored data" | Lumo's servers, in cleartext. Proton says it keeps "no logs" of what you ask | Read Proton's security model post |
| Maple | "Your chat history is stored encrypted" | You: "no one at Maple can read them" | Only an enclave the app checks first. If a check fails, "nothing is sent" | Run Maple's check in your browser, or rebuild and compare PCR values |
| Confer | "Stored encrypted on our servers, but only you hold the keys to decrypt it" | You: keys are "generated and stored on your device" | A confidential VM: prompts are "encrypted from your device directly into the TEE" | Rebuild the image and match its measurements to the transparency log |
The local apps answer the history question and the message question at once, because nothing leaves your computer. For the cloud apps, read the last two columns together. Our guide to AI that doesn't save your data covers what ChatGPT, Claude, and Gemini keep on their own servers, and what deleting does there.
Is there an AI chat app where even the company can't read my conversations?
Yes, for your stored history in several apps, and for the messages themselves in apps that run the model inside a hardware enclave your device checks first. Those are two separate promises, so check which one an app is making.
For stored history, Duck.ai says it "never has access to your decryption key and cannot read your chats" in Sync & Backup. Proton says "Proton does not have access to your chat history." Confer's policy says "Confer cannot decrypt or otherwise access the content of your messages," and Maple says no one at Maple can read your chats.
For the message on its way to the model, a server has to read it unless the model runs in an enclave. Lumo's server decrypts each message to run the model, as Proton's post says. Venice's E2EE mode, on its Pro plan, decrypts the prompt only inside a verified enclave, and Venice describes its default Private mode as "Trust-based." Confer's client checks that the server's quote came from genuine hardware and that its measurements "match a release in the transparency log" before it sends. Maple's app asks the enclave for a signed fingerprint of its software and checks it against the ones Maple approved before sending anything. We explain what those checks prove, and who should run them, in how to verify AI enclave attestation.
How can you check where an AI app keeps your chat history?
You can check where history lives in a few minutes with tools you already have, and check who reads each message wherever the company publishes something you can verify.
- Sign in somewhere new. Open the app in a second browser or on another computer. If your old chats appear without a backup or sync step you set up, they're kept on a server.
- Look in the browser's storage. In Chrome, open developer tools, then Application, then IndexedDB and Local Storage. Chats stored as readable text are readable by anyone who copies that profile. Chats stored as scrambled bytes are encrypted.
- Open the folder. For a local app, find its chat files (LM Studio's path is in the table) and open one in a text editor.
- Watch the network. Keep the Network tab open while you send a message, and note every address the app contacts.
- Run the published check. Maple and Confer publish how their apps verify the server. For Morse, run
npx @askmorse/verify inference.trymorse.ai, and add--rebuildto build the enclave image yourself. - Read the exact words. "Stored locally," "zero-access encryption," and "we don't store your prompts" are three different promises. The table above quotes which one each company makes.
Is a local AI app more private than a cloud app that keeps history on your device?
For the message itself, yes. A model on your own computer reads your words there and nowhere else. The trade is the model: GPT, Claude, and Gemini don't run on a laptop, and a model that does needs memory and a graphics card to match. The saved chats also sit on your disk as ordinary files unless you encrypt the drive. Our comparison of local AI vs cloud AI goes through the hardware and what each local app still sends online.
How Morse keeps your chat history on your device
Every app above answers two questions in its own way: where your history sits, and who reads each message on its way to a model. Morse answers both by design, and lets you check the answer.
Your chat history is stored in your browser (IndexedDB), encrypted with a key of its own. That key is locked with two others: your browser's key, which no script can read out, and Morse's key, which Morse's server sends only while you're signed in and your browser never writes down. A copy of your browser's data opens nothing without both. Morse's servers keep no log of your messages, and a temporary chat is kept in memory only, never stored.
Every message goes through the Morse Enclave, open-source code running in AWS Nitro hardware that walls it off from everyone, Morse included. The enclave never receives your account, email, or IP address, so the model provider never learns who you are. npx @askmorse/verify inference.trymorse.ai checks that it runs genuine AWS Nitro hardware, an image on Morse's signed list, and the code at github.com/trymorse/morse-enclave. No AI provider trains on what you send through Morse. You choose what the model provider can see, chat by chat:
- E2EE, so even the company can't read your conversation. Your browser checks the remote enclave's hardware attestation, then encrypts your message so only that verified enclave can decrypt it. Morse's servers and the Morse Enclave relay it without being able to decrypt it, and every E2EE reply has a lock you can open to see each check your browser ran.
- Private, so the model's host keeps nothing. Private-mode hosts are bound by contract to keep nothing they're sent, and read your message only to answer it.
- Anonymous, for GPT, Claude, and Gemini without your name on it. The provider reads your message without knowing it's you, and may keep it for a limited time to check for abuse.
To keep your history safe from a cleared browser, save an encrypted backup to a file from Settings > Data and keep its recovery key apart from the file. With sync on Pro and Max, your devices send each other their changes through Morse's server, encrypted under keys only your devices hold. Because your chats are stored on your devices, Morse has no copy of them to give authorities (privacy policy).
Try a chat from the Morse home page without an account, or start free. E2EE chats come with Pro, at $19 a month, on the plans page.
Sources
All read November 20, 2026.
- LM Studio, chat docs and offline docs
- Jan, privacy
- Nomic, GPT4All and GPT4All settings
- Ollama, FAQ
- DuckDuckGo, Duck.ai recent chats and Duck.ai privacy terms
- Venice, privacy and FAQ
- Proton, Lumo privacy and Lumo security model
- Maple, proof
- Confer, privacy policy, passkey encryption, and private inference
- MacRumors, ChatGPT Mac app stored chats in plain text (July 4, 2024)
Common questions
If an app keeps my chat history on my device, does the AI company never see my messages?
No. On-device history covers the copy you scroll back through. Unless the model runs on your own computer, each message still reaches a server where a model reads it, and that server's own rules decide what it keeps.
Are the chats saved by local AI apps encrypted?
Their own pages don't say so. LM Studio says conversations are stored in JSON format, and Jan's privacy page says history is stored locally without mentioning encryption, so turn on full-disk encryption such as FileVault or BitLocker if others can reach your computer.
What happens to my AI chat history if I clear my browser?
In apps that keep history in the browser, such as Morse, Duck.ai, and Venice, clearing the site's data deletes it from that browser. Save a backup first if you want to keep it: Morse saves an encrypted backup file from Settings > Data, and Venice has encrypted backups.
Does Safari delete AI chats stored in the browser?
DuckDuckGo says Safari deletes Duck.ai's saved chats if you go more than 7 days without visiting duck.ai. Other browsers can keep them indefinitely until you clear your browser data.
Can I move chat history that lives on my device to a new computer?
Usually through an encrypted backup or sync. Duck.ai's Sync & Backup keeps its decryption key only on your devices, Venice's encrypted backups expire after 90 days, and Morse restores a backup file you lock with a recovery key or a passkey.
Is ChatGPT history stored on my device?
ChatGPT keeps your history in your account on OpenAI's servers. Its Mac app also kept a local copy, which in July 2024 was found stored in plain text until OpenAI shipped an update that encrypts it.
Does a private or incognito browser window keep AI chats off the company's servers?
No. A private window only stops your browser from keeping its own copy. An app that stores history in your account on its servers still stores it there.
What is zero-access encryption for AI chats?
It means the company stores your history on its servers in a form only your keys can open. Proton uses the term for Lumo's history, and says the files sit on its servers but zero-access encryption keeps Proton from opening them.
Can Morse read my chat history?
No. Morse's privacy policy says your chat history is stored on your devices, encrypted, and never on Morse's servers in a form Morse can read, and Morse's servers keep no log of your messages.
How can I check that Morse's enclave runs the code it publishes?
Run npx @askmorse/verify inference.trymorse.ai. It checks that the Morse Enclave runs on genuine AWS Nitro hardware, runs an image on Morse's signed list, and runs the open-source code at github.com/trymorse/morse-enclave, and --rebuild rebuilds it for you to compare.