Hosted Backend Policy.
This page explains how Qwek's shared hosted backend works, what it is for, and the limits of our responsibility. Please read it before using the shared backend.
Last updated: November 14, 2026
Short version: the shared backend is a free trial service for testing and small-scale use only. We are not responsible for any data stored on it, including loss, leaks, or breaches. Self-host if you care about your data.
Default hosted backend
By default, Qwek provides a shared backend service for users who do not run a self-hosted backend. You do not need to deploy anything to try Qwek: the client can connect to this shared service and start chatting right away.
This service is provided as-is and at no cost. It exists so you can evaluate Qwek and use it with small groups. It is not a production service. Availability, uptime, storage limits, message retention, and feature support may change or be discontinued at any time, without notice.
We are not responsible for your data
We are not responsible or liable for any user data stored on our shared backend. This includes, without limitation, data loss, corruption, deletion, unauthorized access, leaks, breaches, downtime, or any other damage or loss resulting from the use of the service.
Do not store sensitive, confidential, personal, or regulated information on the shared backend. You use the shared backend entirely at your own risk. If your data matters, self-host Qwek Server on infrastructure you control.
Self-hosting is recommended
For production use, larger teams, or any data you care about, self-host Qwek Server and its PostgreSQL database yourself. Self-hosting keeps your messages and attachments on infrastructure that you own and are responsible for.
Setup instructions are available on the installation section of the landing page and in the backend repository.
No warranty, no guarantees
The shared backend is provided "as is" and "as available", without warranties of any kind, whether express or implied, including but not limited to fitness for a particular purpose, reliability, or security. We may suspend, limit, or terminate access to the shared backend at any time to protect the service or other users.
Changes to this policy
We may update this policy from time to time. When we do, we will revise the date at the top of this page. Continued use of the shared backend after changes are published means you accept the updated policy.