--- title: Privacy Policy description: published: true date: 2021-09-03T07:41:23.648Z tags: editor: markdown dateCreated: 2021-09-03T07:41:23.648Z --- # Privacy Here you will find a small overview of our data protection and our understanding of it. The exact list of the use of your data can be found in our [Privacy Policy](https://www.bstly.de/privacy-policy?lang=en). # Privacy By Design Privacy by Design means that the systems are fundamentally designed for data economy. In general, we always try to collect as little data as possible. Following the idea of 'what you don't have, you can't lose'. First of all, this applies generally to the data we collect, but also to the connection of different data to each other. To separate account and payment data, we use the ticket system *Pretix* with its check-in system. A secret token is generated for each item. In our self-developed server component *we.bstly*, this token can then be redeemed and the corresponding performance stored. The token is then marked as redeemed in *Pretix*. The link between account/service and token is therefore only valid temporarily for the existing browser session and is not stored otherwise. In other words, there are two databases, one for payment data and tokens (*Pretix*) and one with account and authorization data (*we.bstly*). The link only takes place in an active browser session and is also forgotten there after redeeming the token. So there is no link between payment data and account. We are currently making compromises when linking accounts for the individual services. As always, comfort and simplicity come at a price. Through so-called [single sign-on](https://en.wikipedia.org/wiki/Single_Sign-on) (*SSO*) via [OpenID Connect](https://en.wikipedia.org/wiki/OpenID_Connect) (*OIDC*), this means: One account for everything. In other words, the use of the individual services is always due to your *we.bstly* account. On the one hand, this offers the convenience of *SSO*, that you only have to take good care of this one account. On the other hand, of course, you also get the simplicity that everyone has the certainty that the different services are always the same *we.bstly* account. So you know for example, that you also write an e-mail to the exact person you just have chatted with. # Individual services Here we summarize the data collection of the individual services. For the exact details, we refer again to our [Privacy Policy](https://www.bstly.de/privacy-policy?lang=en). More information or instructions on functions of the individual services can be found in our [Overview of available services](/en/services). ## Pretix In the *Pretix* system, we must of course store personal data on payment transactions as well as an e-mail address for sending e-mails with confirmations, payment data and sending the tokens. As a member of the association, your membership data to be collected and your membership fee account are stored here. As mentioned at the beginning, this data is not linked to other services. ## we.bstly In *we.bstly* all you need is a username and password (well *salted*, [Argon2](https://en.wikipedia.org/wiki/Argon2) hashed!). In addition, a [PGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) key pair is created, nothing more. The specification of an e-mail address is optional. This is required if you lose your login data or your *private key*. However, we keep this option optional, so that a completely anonymous use of all services is possible if you do not lose your password or your *private key*! In addition to your central account data, your permissions and the expiration date of your services are also stored here. Currently, the information that you are a regular club member is also stored. This has the advantage that we can also reach all club members directly via our services or offer extended services. Of course, the data will not be linked to your membership data or the membership fee account, i.e. we only know **that** you are a member of the association, **not which one**! Optionally, you can create additional profile data with adjustable visibility (*Private*, *Protected* and *Public*) for your account. Private profile fields are only visible to you, protected ones are also visible to other users and public ones are also visible to third parties. ## Email Currently, the e-mails are stored on the server as they arrive. Since this requires some disadvantages and unnecessary trust, a solution is being worked on to automatically encrypt all emails with your *public key*. This gives you the assurance that only you can decrypt the emails. However, this also means that you'll need to set up all your email clients for decryption. Of course, we will publish detailed instructions when the time comes and probably also offer an *opt-out* if you want to do without this function. Your *we.bstly* account data will be used for authentication. Note that enabling two-factor authentication in your *we.bstly* account will not affect your email login. ## Vaultwarden As a password manager, Vaultwarden stores highly sensitive data. However, these are all encrypted with your master password which is only stored hashed on the server. The strength of your master password is also crucial for the security of this data. In addition to the actual passwords, data such as associated user name, URLs of the websites or user-defined fields and notes are also stored. However, decryption of this data is only possible with the master password. ## Nextcloud Of course, how sensitive the data in the *Nextcloud* is depends only on your use. The service itself does not provide any data other than your account data (only username and voluntary profile data). Since only content created by users is stored here, it depends on what you upload, publish and write. The data is automatically stored encrypted, but it is only server-side encryption, so you can continue to share the data with others. However, *Nextcloud* also offers its own *end-to-end* encryption (*E2EE*) in the current versions. Of course, you are free to use them for sensitive data, so that no one else can access these files. Note however, that these files are then no longer accessible in the browser and cannot be shared. In addition, the *E2EE* only applies to files and not to other data such as contacts, calendars or the like, so the recommendation is to always think about what data you are currently creating and how sensitive it is. Since *Nextcloud* also serves as the basis for some community functions, your account data will be shared with all other users. However, you are also free to share other data such as files, calendars, etc. with other users. ## Matrix Since *Matrix* is a messaging service, sensitive communication data can of course be generated here. Fortunately, *Matrix* offers *end-to-end* encryption. However, since this is optional, we recommend that you always activate *E2EE*. In addition to your chat messages, your room memberships are also stored for the service. If you create public spaces yourself, they are of course also visible to others. Please also note that *Matrix* is a decentralized network similar to e-mail communication. This means that you have the opportunity to communicate with users from other providers, but you also transfer data including your messages to these servers. ## Partey No data is stored in our *virtual clubhouse*. Nevertheless, the transmission of your video and audio data affects a highly sensitive area. As mentioned, this data is not persisted by us, but it is not technically excluded that other users may illegally make recordings. If you are aware of any violations, please contact us urgently. As a first point of contact, there is our page with [help offers](/en/help). ## Jitsi-Meet In our *Jitsi-Meet* rooms, the same applies as for our *virtual clubhouse*. No data is stored about you, but you should be aware that you are transmitting sensitive video and audio data to other users in real time. ## PeerTube Important note: PeerTube has a P2P feature, which means that you automatically make your watched video data available to other users to relieve the server. However, this will pass on your IP address to third parties! You can deactivate this function at any time. For more details, see [tube.bstly.de/about/peertube#privacy](https://tube.bstly.de/about/peertube#privacy). We decided to leave this feature on because it is a very practical function and the misuse of an IP address is very low. The service itself only stores your username and a few personal settings and channels. Otherwise, of course, the videos you upload will be stored and, depending on the settings, made available to other users or to the public. The same goes for your livestreams. ## Wiki.js In general, no personal data is collected in our *Wiki*. Only your *we.bstly* username and e-mail address will be transferred to your account. In general, all texts you write are public and linked to your username. In addition, there is a comment function. However, this is only accessible to other users and not public. ## Gitea Similar to *Nextcloud*, only your username and a few personal settings are stored by the service itself. How sensitive the data in your *Git* repositories is and who can access it depends entirely on you. So pay attention to which files you upload and whether your repository is also publicly accessible. Since repositories often contain source code including configuration files, we would like to remind you not to accidentally load sensitive information such as passwords, *API keys* or *private keys* into your repository. On public repositories, your changes, issues, comments and account are of course also public! ## Webserver All services run via a web server, as well as e.B this page. In general, a web server automatically generates a lot of data, such as.B your IP address, your web browser version and much more. The fact that this data is transmitted is technically conditioned and can only be prevented with effort from your side. So what's important is what we do with this data. The answer is simple: Nothing! In general, this data is not stored at all. In the context of maintenance work, it may happen that this data is written to log files so that we can investigate the problems more deeply. However, these are then not linked to any other data and deleted immediately after completion of the work!