ChatCat Privacy Policy
ChatCat is a chat app for the Matrix and XMPP networks, published by LSYS ("we", "us"). This policy explains what ChatCat does with your data, and, just as importantly, what it does not do.
The short version
- We do not run any server that your messages pass through. We have no user database, no analytics, and no crash reporting.
- The one service we run is the link host at cc.lsys.xyz. It is used only when you make a one-time account link, or read or write a one-time note, and it only ever holds account details and notes encrypted with a key it never receives.
- Everything you send in ChatCat goes to the server you chose when you signed in (your Matrix homeserver or XMPP server). That server's operator, not us, holds your account and your messages.
- We cannot see, access, sell, or delete your data, because we never have it in a form we can read.
Who is responsible for your data
ChatCat is a client. When you sign in, you pick a server: the default suggestion is matrix.org, but you can type any Matrix homeserver or XMPP server, including one you run yourself. That server stores your account, your contacts, your rooms, and your message history, and its operator is the data controller for all of it. Please read the privacy policy of the server you use. For matrix.org, that is matrix.org/legal/privacy-notice.
We publish the app and run the link host described below, nothing else. We have no way to look up who uses ChatCat or what they send.
Data the app sends off your device
ChatCat sends data only to servers you choose, and only to make the app work.
To your Matrix or XMPP server
- Your username and password (or a sign-in token) when you sign in.
- Your display name and avatar, if you set them.
- Messages, reactions, and read receipts.
- Photos, videos, voice messages, audio, and files you attach.
- Your location, only when you deliberately share it in a chat, and only for as long as you leave a live location share running.
- Your device's name and the encryption keys needed for end-to-end encryption.
- A push registration so the server can tell your device when a new message arrives.
Rooms and chats that use end-to-end encryption (Matrix Olm/Megolm, XMPP OMEMO) are encrypted on your device before they are sent, and only the participants can read them. Unencrypted rooms, public rooms, and plain XMPP chats are readable by the servers involved.
To our account-link host, only if you use one-time account links
"Copy link" under "Share an account" makes a one-time link (https://cc.lsys.xyz/add#…). ChatCat encrypts the account's server address, username, and password on your device with a fresh key that exists only in the link itself, and leaves the encrypted copy on our link host at cc.lsys.xyz. When someone opens the link in ChatCat and taps Add, their app fetches the encrypted copy once and decrypts it on their device. The host never receives the key, so it cannot read what it keeps.
- The encrypted copy is deleted as soon as the link is used, and after at most 8 days if it never is. For up to 8 days after a link is used, the host remembers only that it was used, so a second tap can say so.
- To stop abuse, the host counts how many links each network address makes. That count is kept only in the host's memory, never on disk, and is cleared at most a day after that address last made a link.
- Requests for links are not written to the host's logs.
- Opening a link in a web browser loads a page from cc.lsys.xyz. The link's secret part, after the #, stays in your browser and is never sent.
To push notification services
To wake your phone when a message arrives, ChatCat by default registers with the UnifiedPush rewrite proxy at unifiedpush.org, which relays through Google's Firebase Cloud Messaging. These services see a push token identifying your device and small notification payloads, which do not contain message content. Builds configured for a self-hosted push proxy do not contact unifiedpush.org.
To Google Play
The Google Play version checks for app updates through Google Play's in-app update service. Google's handling of that request is covered by Google's privacy policy.
ChatCat contacts no other services. There are no advertising networks, trackers, analytics, or crash reporters in the app.
One-time notes
The link host also keeps one-time notes: a short text that someone we have made a writer writes at cc.lsys.xyz/note/new, and that whoever gets the link (https://cc.lsys.xyz/note#…) can read once, in any web browser. The writer's browser encrypts the note with a fresh key that exists only in the link itself, and leaves the encrypted copy on the link host. The reader's browser fetches it only when they click to reveal it, and decrypts it there. The host never receives the key, so it cannot read any note.
- The encrypted note is deleted as soon as it is read, when its writer deletes it unread, or when the time its writer chose (at most 7 days) runs out. For up to 8 days after a note is read or deleted unread, the host remembers only that it was, so the reader and the writer can be told.
- Only writers can leave notes. The host keeps a list of each writer's name and a one-way fingerprint (SHA-256) of their passphrase. Signing in sets a cookie that holds a random token for 12 hours; the host keeps it in memory only, so a restart signs everyone out. The host does not record which writer wrote which note.
- A writer can add passkeys to sign in with. For each, the host keeps the passkey's public key and id, the name the writer gave it, when it was added, and when it was last used, until the writer removes it, or, once they stop being a writer, until the next time anyone signs in. A passkey's private key, and the fingerprint, face or screen lock that unlocks it, never leave the writer's device.
- A writer can send someone an invite link with which they set up a passkey, either to become a writer or to add a passkey on another device. For each invite, the host keeps the name it is for, who made it, a one-way fingerprint (SHA-256) of its secret, when it was made, when it was first opened and when it expires; once it is used, revoked or expired, it keeps only whether it was used or revoked, and when, and forgets it all 30 days after its last change. For a writer who joined by invite, the host keeps their name, who invited them and when they joined, until whoever invited them removes them; if we remove them, or whoever invited them stops being a writer, the host forgets them, with their passkeys, the next time anyone signs in. The part of an invite link after the # is never sent to the host until the link is used.
- A writer can also send a note to one of their contacts. Their browser encrypts it to the recipient's own key for notes, so the host cannot read these notes either. For each writer, the host keeps the public half of that key, and the private half encrypted, once for each of their passkeys, with a secret only that passkey can produce in their browser (the WebAuthn PRF extension); the host never has the private key itself. A link a writer makes for another device of theirs may carry the key, encrypted with a key in the part of the link after the #, until the link is used.
- For each such note, the host keeps the encrypted note, who sent it to whom, when, how long it is to be kept, whether it is to be deleted when first read, and when it was first read. It is deleted when its recipient deletes it, when it is read if it was to be deleted then, when its sender deletes it unread, or when the time its sender chose (at most 30 days, or until its recipient deletes it) runs out. Its sender is shown what became of it for 30 days after. The host also keeps who are whose contacts. When someone stops being a writer, the host forgets all of this about them, and the notes sent to them, the next time anyone signs in.
- To stop abuse, the host counts how many notes each writer leaves in a day, and wrong passphrases from each network address in an hour. Those counts are kept only in the host's memory, never on disk.
- Requests to the link host are not written to its logs, and its error log never records a network address.
- The writing page keeps, in that browser's own storage, the notes written there: for each, only an id, the token that lets its writer delete it unread, and when it expires. It does not keep the link or the text. They are dropped from the list 8 days after the note expires.
- The part of a note's link after the # stays in the browser and is never sent to the host.
Data stored on your device
ChatCat keeps a local copy of your accounts, message history, media cache, and encryption keys on your device so the app works offline and encrypted messages can be decrypted. This data stays in ChatCat's private app storage and is excluded from Android cloud backup. Uninstalling ChatCat deletes it.
Permissions
ChatCat asks for permissions only when you use the related feature, and you can refuse any of them:
- Camera and microphone: taking photos and recording voice messages to send.
- Location: sharing your location in a chat. Location is never read for any other purpose.
- Notifications: showing new-message alerts.
- Photos, media, and files: attaching things you pick.
Children
ChatCat is not directed at children under 13, and we do not knowingly collect any data from them. Since we hold no data we can read, age restrictions are enforced by the server you sign up with.
Deleting your data
- Local data: sign out of an account in ChatCat, or uninstall the app.
- Your account and server-side history: deactivate your account with your Matrix homeserver or XMPP provider. Matrix servers offer account deactivation in their account settings or through their web client; most XMPP servers offer it through their account management page. We cannot delete an account for you, because we do not operate the server that holds it.
Changes to this policy
If this policy changes, the new version will be published at cc.lsys.xyz/privacy.html with an updated effective date.
Contact
Questions about this policy: cc@hooli.email