Improving the privacy of our chat app #57

Open
opened 2026-11-18 05:09:05 +00:00 by ntnsndr · 1 comment

What's the idea?

Currently, our LibreChat app by default stores chat history on the server. This is convenient, but it introduces a major privacy and compliance issue that risks violating our co-op's value of "trustworthiness" to users. It turns our data into a potential honeypot for bad actors.

We should make efforts to improve the privacy of our flagship chat app.

Why does it matter?

Chat is the killer app for LLMs, and especially less-technical users expect it to be provided. We want to provide that accessible UX while also protecting user privacy as much as possible.

Who is it for?

All our members.

How might it work?

There are a range of options we could explore:

  • Improvements to LibreChat
    • Set a default data deletion policy (the relevant fields are all documented under the interface object: temporaryChat, temporaryChatRetention, generalChatRetention, retentionMode, retainAgentFiles, plus visibility toggles like memories, sharedLinks, prompts, bookmarks, schedules. https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/interface)
    • Adding custom changes to LibreChat that would encrypt user data. This is a complex task and would likely introduce UX friction.
  • Switching to an app like LobeChat that stores user data only in the local browser, not on the server. This would mean losing cross-device history.
    • LobeChat has a restrictive license so we could not permissionlessly customize it. This was why we dropped Open WebUI.
  • Integrating chat into encrypted Matrix rooms, essentially bootstrapping Matrix's privacy as our chat apparatus. But this would likely mean losing a lot of features and ease-of-use that users expect.
  • Switch to only supporting our own local app, desktop and mobile, that doesn't store data on our server.

What else?

## What's the idea? Currently, our LibreChat app by default stores chat history on the server. This is convenient, but it introduces a major privacy and compliance issue that risks violating our co-op's value of "trustworthiness" to users. It turns our data into a potential honeypot for bad actors. We should make efforts to improve the privacy of our flagship chat app. ## Why does it matter? Chat is the killer app for LLMs, and especially less-technical users expect it to be provided. We want to provide that accessible UX while also protecting user privacy as much as possible. ## Who is it for? All our members. ## How might it work? There are a range of options we could explore: * Improvements to LibreChat * Set a default data deletion policy (the relevant fields are all documented under the interface object: temporaryChat, temporaryChatRetention, generalChatRetention, retentionMode, retainAgentFiles, plus visibility toggles like memories, sharedLinks, prompts, bookmarks, schedules. https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/interface) * Adding custom changes to LibreChat that would encrypt user data. This is a complex task and would likely introduce UX friction. * Switching to an app like LobeChat that stores user data only in the local browser, not on the server. This would mean losing cross-device history. * LobeChat has a restrictive license so we could not permissionlessly customize it. This was why we dropped Open WebUI. * Integrating chat into encrypted Matrix rooms, essentially bootstrapping Matrix's privacy as our chat apparatus. But this would likely mean losing a lot of features and ease-of-use that users expect. * Switch to only supporting our own local app, desktop and mobile, that doesn't store data on our server. * [Chatbox](https://github.com/ChatBoxAI/ChatBox) is GPL-3.0 **What else?**

To the extent that it’s possible, I think we should go for a solution that allows cross-device chat history. I think that’s pretty important.

To the extent that it’s possible, I think we should go for a solution that allows cross-device chat history. I think that’s pretty important.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: co-op/support#57