Privacy policy

What QxChat knows about you, what it does with it, and how you stay in control. In plain words.

We cannot read your messages

They are encrypted on your device before they leave it. The server only passes them along.

No phone, no email

A username, a password and 12 recovery words. That is the whole account.

Nothing sold, no trackers

No ads, no analytics, no crash reporting in the app. We never sell data.

Delete it yourself

Settings, Profile, Delete account. It takes effect at once (section 10).

What we see

As little as we can.

1. Who we are and what this covers

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:

  • on your own server, that is you;
  • on a friend's or a community server, that is them;
  • on our public server, 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.

2. How we approach your data

  • We ask for as little as possible. There is no email field, no phone number field and no real-name field anywhere in QxChat.
  • We use data only to run the service. Messages, calls, device sync and keeping the service safe from abuse. Never advertising.
  • We never sell data. We do not sell, rent or trade it. The app contains no advertising, analytics, attribution or crash-reporting kit.
  • You can check all of this. The server, the apps and this website are open source under the MIT licence, and the handbook explains how each part works.

3. What we collect and why

Here, "collect" means sent to the server or stored by the app. The Google Play Data Safety category is in brackets.

WhatDetailsWhy
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.

4. Google Play Data Safety answers

QuestionAnswer
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.

5. Android permissions

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.

PermissionWhat it is used for
INTERNETTalking to your QxChat server, uploading and downloading files, checking for updates.
CAMERAVideo calls and photos that you start. Never used in the background.
RECORD_AUDIO and MODIFY_AUDIO_SETTINGSVoice calls and voice messages that you start, and echo and speaker control during calls.
POST_NOTIFICATIONSMessage and call notifications, created on your phone. QxChat does not use Firebase or Apple push.
FOREGROUND_SERVICE and FOREGROUND_SERVICE_DATA_SYNCKeeping the encrypted connection open in the background, so messages arrive without a push service.
WAKE_LOCKStopping 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 hardwareMarked 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.

What we do with it

We run the service, and nothing else.

6. What we use data for

  • Running accounts, rooms, direct messages, calls, file transfers, device sync, profiles and blocking.
  • Rate limits and anti-abuse checks, with counters that live in memory and build no profile of you.
  • Keeping the service up, with overall load counts kept in memory.

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.

7. What encryption covers

  • Messages in private rooms are encrypted on your device with AES-256-GCM, using a new key for each message, and signed with ECDSA P-256. The server checks where a message goes and how big it is, never what it says.
  • The server keeps about 150 recent messages per room in memory so people can catch up. They are never written to disk and are lost when the server restarts. There is no message history table.
  • Friend requests (QXP-PHANTOM) and device sync (QxCloudSync) go through relays that cannot open what they carry. Friend requests wait in anonymous slots for 24 hours at most.
  • One exception: a server operator can set up an official announcement room. To send it to everyone, the server holds that room's key, so treat that one room as readable by the operator.

8. Who else receives data

WhoWhat they getWhy
The operator of the server you useYour account record, encrypted messages, presence and routing information, uploaded filesRunning the service you connected to
A TURN relay, chosen by the operatorEncrypted call audio and video, and the IP addresses of the callConnecting a call when a direct connection fails
The website of a link you postThe server's IP address and the link (fetched within 4 seconds, cached for 5 minutes)Showing a preview of the link
The update server (github.com/lqxp/app; Google Play for Play installs)The app version, to check for a newer one; updates are verified with minisignSafe updates
Tor directory servers, only if you turn on Tor on desktopThe normal traffic Tor needs to startOptional extra anonymity

Nobody receives data for advertising, analytics or attribution. Discord Rich Presence only talks to the Discord app on your own computer (it shares the app version and your OS) and can be turned off. The app only opens links to qxch.at, github.com, metrics.torproject.org, email and phone links.

9. Where data is kept, and for how long

  • On your device: a local vault with your session, your keys, recent rooms and messages (about 500 per room) and your settings, plus a longer history of about 2,000 items. With Client Lock on, it is sealed with your PIN (PBKDF2 with 250,000 rounds, then AES-GCM), and secrets in memory are wiped when the app locks.
  • On the server, in memory only, gone on restart: recent room messages, friend request envelopes (24 hours at most), anti-abuse counters, link preview cache (5 minutes) and connection counters.
  • On the server, until you delete them: your account record, sessions, public keys, block tags, your encrypted friend list, rooms, and uploaded files (up to about 10 GB per server), in SQLite or PostgreSQL.
  • Sessions end after 7 days without use. Poll votes are stored as hashes that cannot be linked back to you. If an operator makes backups, how long they keep them is up to them: ask them.

What you control

Your account, your data, your call.

10. Deleting your account and data

  • In the app, on any platform including Android: 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.
  • Only on this device: Settings → Clear local data removes the local vault and history and leaves your account as it is.
  • Messages and rooms: deleting a message removes it and its attachment. Room owners can delete a whole room, and a room can be set to remove your messages when you leave.
  • By email: write to [email protected] for accounts on 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.
  • How fast: deletion in the app is immediate. Messages in server memory are gone at the next restart at the latest. Operator backups, if any, expire on their own schedule. Once your account is deleted, your recovery words no longer work.

11. How we protect it

  • In transit: HTTPS and secure WebSockets in production, with end-to-end encryption on top. TURN credentials are never logged.
  • Stored: passwords and recovery words as Argon2id hashes, session tokens as SHA-256 hashes, no secret stored in plain text, and metadata removed from uploaded images.
  • Against abuse: rate limits, quota tokens, a proof-of-time puzzle and a CAPTCHA, sign-in checks that do not reveal whether a username exists, and link previews that cannot be pointed at internal addresses.
  • What no software can do: protect an unlocked device in someone else's hands, or hide metadata from a server that was modified on purpose. Lock your devices, turn on Client Lock, check download signatures, and host your own server for the most control.

12. Children

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.

13. Where your data lives

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.

14. Your rights

  • See your data: the app shows your profile and settings; the server returns your stored profile at GET /api/auth/me.
  • Correct it: change your profile and status in the app, and your username once a week.
  • Delete, restrict, object or take a copy: delete your account, messages and rooms (section 10), turn off optional features, and ask your server operator about restriction. There is no automatic export yet: ask your operator, or [email protected] for qxch.at.
  • Start with the operator of your server, since they hold your account. You can also complain to your data protection authority, such as a national authority in the EU or the ICO in the UK, or report the Play version of the app through Google Play.

15. Changes to this policy

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.

16. Contact

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.