Privacy Policy

I don’t want my channel to be listed here!

Please refer to the documentation for owners.

Data Processing

search.jabber.network collects and stores information about public channels and domains in the Jabber/XMPP network. Technically, those channels are implemented on servers using so-called Multi-User Chats (MUCs). We only consider MUCs which are persistent, public and open (i.e. not password-protected and not members-only) as channels. Other MUCs may be queried by the crawler if they are somehow encountered, but are otherwise ignored.

Data associated with Channels

The following data is collected and stored about a channel:

  • Its identifying address (Jabber ID, JID).
  • The number of users last seen online in the MUC, as well as a moving average over this number.
  • The timestamp of the last time search.jabber.network successfully made contact with the MUC
  • Whether the MUC exposes the addresses of users (muc_semianonymous and muc_nonanonymous flags).
  • The channel description (if available).
  • The channel name (if available).
  • The current channel subject (if available).
  • The channel language (if available).
  • The URL to an anonymous web chat (if available).
  • The URL to web logs of the channel (if available).
  • A (potentially downscaled) version of the avatar (if available and allowlisted).
  • Any administrative records about the channel necessary for listing management and moderation (so-called "flags").
  • Tags extracted from the channel's description.

If a channel was delisted at our discretion, as described in the documentation for owners, or due to other reasons, we store its address as well as the necessary background information to remind ourselves about why we did this (legitimate interest under Art 6.1f). That background information generally includes a snapshot of the last state the channel had when it was listed.

Data associated with domains

For domains / services, search.jabber.network collects and stores:

  • The domain name.
  • The timestamp of last successful contact and the timestamp of the next planned contact.
  • The XEP-0030 identities advertised by the domain.
  • The XEP-0092 software version information advertised by the domain.
  • The XEP-0157 abuse contacts published by the domain.
  • A counter of errors during connection attempts to delay future connection attempts (exponential back-off).

If a domain was delisted on our discretion, as described in the documentation for operators, or due to other reasons, we store its address as well as the necessary background information to remind ourselves about why we did this (legitimate interest under Art 6.1f). That background information generally includes a snapshot of the domain information we had at the time it was delisted.

Data obtained on the website

To ensure the correct operation of our services, we log requests made to the web service. This information is stored for up to 7 days. This is in line with Art. 6.1f with Recital 49 of the EU General Data Protection Regulation (EU-GDPR). The information we collect under these terms is:

  • Time of request
  • Which resource was requested (e.g. listing, search (including search terms), API request)
  • Full IP address of requester
  • Browser and OS version as reported by the browser
  • Size of the response
  • Status code (indication of success, failure and special conditions)
  • The amount of time it took to process the request

We delete this data after at most 7 days. We generally do not process this data further unless we have an additional legitimate reason (such as suspicion of an attack on our services).

Search terms sent to the search API using the HTTP POST method or via XMPP are not stored.

Data Sharing

search.jabber.network allows anyone to query all information it has stored about channels. This is the information seen on this website.

This is merely a convenience service, since Jabber services already expose channels in directories central to their domain.

Your rights

This service does not store personal data, except such data which may have been made public in places and which cannot be determined to be personal data (for example, if you put your full address into a channel's description).

We will gladly assist you to prevent such data from leaking into the open web. In such cases, simply contact us (see below).

Representative

Please see the legal contact information.