We cannot read your messages
They are encrypted on your device before they leave it. The server only passes them along.
What QxChat knows about you, what it does with it, and how you stay in control. In plain words.
They are encrypted on your device before they leave it. The server only passes them along.
A username, a password and 12 recovery words. That is the whole account.
No ads, no analytics, no crash reporting in the app. We never sell data.
Settings, Profile, Delete account. It takes effect at once (section 10).
As little as we can.
QxChat is made by the QxChat team, the people behind the open-source organisation lqxp. You can reach us at [email protected]. Security reports follow /.well-known/security.txt.
This policy covers the QxChat apps (Android from Google Play or as an APK, iOS, desktop, and the web app) and the server software they connect to, LQXP (lqxp/lqxp).
Who is responsible for your data depends on the server you use. QxChat is software anyone can host. Whoever runs the server you connect to is responsible for what that server stores:
qxch.at, that is us, and this policy applies with the default settings.Because the code is open, someone could run a modified server. Message content stays unreadable even then, because it is encrypted on your device before it is sent. If you want the strongest guarantee, run the server yourself.
Here, "collect" means sent to the server or stored by the app. The Google Play Data Safety category is in brackets.
| What | Details | Why |
|---|---|---|
| Account (Personal info) | Your username, in lower case, 2 to 24 characters. Your password and your 12 recovery words, stored only as Argon2id hashes. Session tokens, stored as SHA-256 hashes and valid for 7 days after your last use. | Signing in, resetting your password, keeping you signed in |
| What you send (Messages; Photos and videos; Audio; Files) | Room messages (up to 2,000 characters), encrypted envelopes, reactions, polls, attachments (up to 25 MB), profile pictures (up to 10 MB) and banners (up to 15 MB). Image metadata is removed on upload. | Delivering what you choose to send, to the server you chose |
| Contacts (Contacts; Social) | The rooms you are in and your role there, friend and block tags, and your friend list as an encrypted blob of up to 64 KiB that the server cannot read. | Your friend list, rooms and blocking |
| Calls and connection (App activity) | Whether you are online or typing, which rooms and calls you are in, call setup messages (relayed, never stored), device sync identifiers, and app settings such as your microphone and camera choice. | Delivering messages, calls and sync; remembering your settings |
| Device (Device IDs; App performance) | A random identifier per install, used to route sync between your devices. The app version when it checks for updates. Abuse counters kept in memory only. | Sync, updates, protection against abuse |
We do not collect an advertising ID or an IMEI, and there are no analytics events.
For people in the EEA and the UK, the legal bases are: the contract (running your account and delivering your messages), our legitimate interest (security and abuse prevention), and your consent for optional features such as Tor, public STUN or Discord Rich Presence. Turn the feature off or delete your account to withdraw consent.
| Question | Answer |
|---|---|
| Does the app collect user data? | Yes: account, content, contacts and connection data, only to run messaging on the server you chose (section 3). |
| Is data shared with third parties? | No selling and no analytics sharing. Data only goes where it must for the feature to work: the server operator you chose, a TURN relay during calls, the website of a link you post (for its preview), and the update server. See section 8. No advertising kit, no Families kit. |
| Is data encrypted in transit? | Yes: HTTPS and secure WebSockets, and message content is also end-to-end encrypted (sections 7 and 11). |
| Can users ask for deletion? | Yes: in the app, or by email (section 10). |
| Has the app had an independent security review? | Not yet. The code is public under the MIT licence so anyone can review it. |
Sensitive permissions are asked for when you first use the feature that needs them, and you can take them back at any time in your phone's settings. Saying no only turns off that feature.
| Permission | What it is used for |
|---|---|
INTERNET | Talking to your QxChat server, uploading and downloading files, checking for updates. |
CAMERA | Video calls and photos that you start. Never used in the background. |
RECORD_AUDIO and MODIFY_AUDIO_SETTINGS | Voice calls and voice messages that you start, and echo and speaker control during calls. |
POST_NOTIFICATIONS | Message and call notifications, created on your phone. QxChat does not use Firebase or Apple push. |
FOREGROUND_SERVICE and FOREGROUND_SERVICE_DATA_SYNC | Keeping the encrypted connection open in the background, so messages arrive without a push service. |
WAKE_LOCK | Stopping the phone from cutting a call or a sync in progress. |
READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO, READ_MEDIA_VISUAL_USER_SELECTED (and READ_EXTERNAL_STORAGE on Android 12 and older) | Opening only the photos, videos or audio files you pick, to send them or use them on your profile. |
| Camera and microphone hardware | Marked as optional: text chat works on devices without them. |
Released builds only use encrypted connections. Unencrypted HTTP is only used when a developer tests a server on their own machine (for example 127.0.0.1:4560). The app never reads your location, your contacts, your SMS or your call log.
We run the service, and nothing else.
We never use your data for advertising, for building a profile of you, to train AI models, or to sell or give to data brokers.
Your account, your data, your call.
Settings → Profile → Delete account, confirm, then enter your password. The server deletes your sessions, public keys, block tags, account record, profile picture and banner, and signs out all your devices. The app then clears its local data.Settings → Clear local data removes the local vault and history and leaves your account as it is.qxch.at, with your username. We will ask you to prove the account is yours before deleting anything. For accounts on other servers, contact that server's operator.QxChat is a general messaging app and is not meant for children under 13, or under 16 where local law sets that age. We do not knowingly collect data from children. If you think a child has given us data, write to [email protected] and to the operator of their server, and we will delete it.
There is no central QxChat cloud. Your data sits where the server you chose is hosted, together with its file storage and TURN relay. Host your own server to choose the country. A call may go through a TURN relay in another region when a direct connection fails, and link previews make the server visit the linked site. For people in the EEA and the UK, transfers rely on encryption, collecting little, and the operator's own safeguards where they apply.
GET /api/auth/me.qxch.at.Every change is public in our repositories (lqxp/lqxp, lqxp/client, lqxp/site). Important changes are mentioned in the release notes and move the effective date at the top of this page. Using QxChat after that date means you accept the new version. Older versions stay in the git history.
You do not have to take our word for it. The code is public.
Visiting getqxchat.com itself: no analytics, no cookies, no accounts, and nothing loaded from other hosts. Only a qx-theme preference in your browser's local storage, never sent anywhere.