Chrome Session Restore Doesn't Leak Open WebUI Chats

Hot take: the browser is usually the weakest link in a "local AI" setup, but Chrome's "Continue where you left off" prompt is not evidence that your Open WebUI conversation is being uploaded to Google.

• –Chrome documents startup restore as reopening the pages you were viewing, while Chrome sync is a separate opt-in that can sync history, bookmarks, passwords, and settings. [Chrome help](https://support.google.com/a/users/answer/9296686?hl=en-IS)
• –Open WebUI is built as a self-hosted, offline-capable AI UI, and its docs say chats live in the internal `webui.db`, with chat history and temporary chat controls available for lower-persistence workflows. [Open WebUI](https://docs.openwebui.com/) [History & Search](https://docs.openwebui.com/features/chat-features/history-search/) [Features](https://docs.openwebui.com/features/)
• –Inference: the bigger privacy leak is often metadata, not raw prompts, because Open WebUI auto-generates chat titles and browser history can outlive the conversation itself. [History & Search](https://docs.openwebui.com/features/chat-features/history-search/)
• –If privacy matters more than convenience, a dedicated browser profile with sync off plus Open WebUI's temporary chat/history controls is a cleaner boundary than assuming "local model" automatically means "private." [Features](https://docs.openwebui.com/features/)