docs: gather privacy posture in one member-facing page
Adds guides/what-happens-with-your-data.md covering what the gateway, chat server and each provider keep, why the routing path differs from a marketplace router, and what the co-op does not claim. Links it from Models, API access, Getting started, Guest access, Infrastructure, the docs index, README and privacy policy. Fixes Getting started's temporary-chat claim: temporary chats are server-backed and deleted about an hour after creation, not never stored.
This commit is contained in:
1 parent
8d002bf5bc
commit
be0ca6c53b
10 files changed
+178
-18
No files matched your search
@@ -199,6 +199,9 @@ 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)).
|
||||
|
||||
The member-facing summary across all three layers — gateway, chat server and
|
||||
providers — is [What happens with your data](../guides/what-happens-with-your-data.md).
|
||||
|
||||
**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
|
||||
|
||||
Reference in new issue
Block a user