HouseCall

Privacy, said plainly.

HouseCall communities run on servers that people host themselves. That is where most of the privacy comes from, and it is also the thing to understand before you trust it.

This website

These pages set no cookies and run no analytics, ads or trackers. The fonts and images are served from this site, so your browser isn't sent anywhere else to load them.

The site runs on one rented server with no outside proxy in front of it. The web server's access log is turned off. New system logs are set to stay in memory for a day at most; logs from the initial server setup remain on disk. The server still sees your IP address and browser details while it answers you, and the companies that provide its hosting, network and DNS may keep records of their own that we don't control.

Logging in here

housecall.chat is a front door. It doesn't host chats and it doesn't sign you in to anyone's community. You type in the address of a server, and that server shows you its own login. You can do that without a HouseCall account.

A HouseCall account is optional. It keeps an encrypted list of the server addresses you add, and it doesn't hold your community passwords or messages. Logging in to it sets one secure session cookie to keep you signed in. The account service sees your connection while you use it, and because your browser gets the login page's code from this site, using an account means trusting this site.

Your community and its host

Each community lives on its host's server: their computer, their database. The host decides who gets in. Your messages and files there stay with that community's host. HouseCall's account service doesn't store them.

That makes the host the person you are trusting. Join communities run by people you'd trust with your group chat, or host your own.

What the host can see

How things stand today.
WhereWhat the host can see
Channels and group chats Everything. These are not end-to-end encrypted.
Calls, including one-to-one calls Calls are relayed through the host's server, which could listen.
One-to-one DMs between the apps, once you both have security keys and your app has saved the other person's key Who you talk to, when, how often, roughly how long each message is, reactions and read state. Not what you say, and not what's in the files you send.
One-to-one DMs in a web browser Encrypted only when you both have security keys. Even then, a browser loads its chat code from the community's host, and a dishonest host could change that code and read the conversation. The installed apps don't load chat code from the host. They still rely on you having a genuine copy on a device nobody else controls.

The limits, so nobody is surprised

The encryption design and the code that implements it are public in the HouseCall repository. To report a security problem privately, use the Security tab there.

Open source

HouseCall is free software under the AGPL-3.0 licence. You don't have to take any of this on faith: the code is on GitHub.