privacy/infra: document brief temporary-chat retention and DuckDuckGo + Brave search
This commit is contained in:
1 parent
1ec63c443b
commit
606bfc5660
2 files changed
+31
-4
No files matched your search
@@ -43,7 +43,7 @@ Your **chat history is stored on our server** so you can revisit past conversati
|
||||
|
||||
We commit not to read it. But this is a **policy commitment**, not an architectural guarantee. We're transparent about this distinction because it matters.
|
||||
|
||||
Note the boundary precisely: enclave models protect your conversation **while it is being processed** — the model provider and we cannot read the exchange at inference time. Stored history is a separate leg: once a conversation is saved, it sits on our server in a form we can technically read. So for sensitive material, the strongest combination available today is a **Temporary Chat with an enclave model** — protected in transit and at inference, and never stored afterwards.
|
||||
Note the boundary precisely: enclave models protect your conversation **while it is being processed** — the model provider and we cannot read the exchange at inference time. Stored history is a separate leg: once a conversation is saved, it sits on our server in a form we can technically read. So for sensitive material, the strongest combination available today is a **Temporary Chat with an enclave model** — protected in transit and at inference, and deleted shortly afterwards.
|
||||
|
||||
### If you use the API, nothing you send is stored
|
||||
|
||||
@@ -71,7 +71,7 @@ it is:
|
||||
|
||||
The chat has a **Temporary Chat** mode designed exactly for this:
|
||||
|
||||
- Click the **Temporary Chat** toggle in the chat header, and the conversation is **never saved** — it doesn't appear in your history, it isn't written to our database, and it disappears when you leave the page.
|
||||
- Click the **Temporary Chat** toggle in the chat header, and the conversation is hidden from your history. It still exists on our server while you use it, so the chat can work; we delete it from our database about an hour after it is created. It may remain in encrypted backups until those backups age out.
|
||||
- To make this the default for every new conversation, open **Settings → Conversations** and enable **Default Temporary Chat**. The preference is stored in your browser, so it's yours to change at any time.
|
||||
- The trade-off is that there's nothing to revisit: no history, no search, no sync across devices. Use it whenever that trade is right for you — you can mix saved and temporary conversations freely.
|
||||
|
||||
@@ -83,7 +83,7 @@ Our server software keeps standard operational logs (dates, error messages, and
|
||||
|
||||
## 5. Search
|
||||
|
||||
Web search runs through our self-hosted search instance. Search queries are forwarded to the underlying search engines (e.g. DuckDuckGo), which may see them. This is inherent to how web search works.
|
||||
Web search runs through our self-hosted search instance. For chat searches we use DuckDuckGo and Brave; those services receive your query from our server, and may see it. This is inherent to how web search works. Search queries and results are part of the conversation record, so they follow that conversation's retention: deleted when you delete a saved chat, or about an hour after a Temporary Chat is created. Operational details are in [Infrastructure](../operations/infrastructure.md#chat-retention-and-web-search).
|
||||
|
||||
## 6. What we do NOT do
|
||||
|
||||
@@ -102,7 +102,7 @@ The models we serve are provided by third parties that change over time, each wi
|
||||
## 8. Retention and deletion
|
||||
|
||||
- Chat history is retained until you delete it.
|
||||
- **Temporary chats are never retained** — they are not written to our database at all (see §4).
|
||||
- **Temporary chats are retained only briefly** — hidden from your history and deleted from our database about an hour after creation. Copies may persist in encrypted backups until those backups age out.
|
||||
- On leaving, your account is deactivated (data preserved for reactivation).
|
||||
- You may request full deletion at any time: info@inference.coop.
|
||||
|
||||
|
||||
@@ -172,6 +172,33 @@ The co-op serves models from multiple providers — Tinfoil for architectural
|
||||
privacy, GreenPT and Regolo for renewable energy. See the [model list](../guides/models.md),
|
||||
the single source of truth for which models are available and how they're named.
|
||||
|
||||
## Chat retention and web search
|
||||
|
||||
**Saved chats** live in the chat database and its search index until the member
|
||||
deletes them. Web-search tool calls are part of that record: the query and the
|
||||
results returned are stored with the message.
|
||||
|
||||
**Temporary chats** are server-backed — messages must reach the server while the
|
||||
chat is running — so they are not client-only. The chat is configured to delete
|
||||
them from the database about **one hour after creation** (`interface.temporaryChatRetention: 1`
|
||||
in the chat configuration; one hour is the minimum this LibreChat version
|
||||
accepts). They are hidden from history immediately, and the database enforces the
|
||||
expiry automatically. Temporary chats created before this setting took effect
|
||||
keep their original 30-day expiry until they age out.
|
||||
|
||||
**Backups are a separate layer.** Cloudron backups are whole-app snapshots and
|
||||
cannot exclude individual chats, so a temporary chat present when a backup runs
|
||||
can remain recoverable from that backup until the backup itself expires (see
|
||||
[Backups](#backups)).
|
||||
|
||||
**Web search** in the chat uses **DuckDuckGo and Brave** through the co-op's
|
||||
self-hosted SearXNG instance. Queries are sent from the co-op server, so the
|
||||
upstream engines see the query but not the member's IP or identity. The SearXNG
|
||||
instance is also publicly reachable at search.inference.coop, and its logs can
|
||||
contain query text when an upstream engine request fails; those log lines carry
|
||||
no member identity or IP, and are retained only briefly. The reverse proxy does
|
||||
not log search queries.
|
||||
|
||||
## Security posture (plain language)
|
||||
|
||||
- **Member isolation.** Each API key is scoped to its owner's team and budget; a
|
||||
|
||||
Reference in new issue
Block a user