_Bastler/wikijs
1
0
Fork 0
Code Releases Activity

docs: update privacy

Browse Source
This commit is contained in:
_Bastler 2023-12-21 10:33:32 +01:00 committed by John Smith
parent 67f15eb2fe
commit 1db7955dd3
1 changed files with 37 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

71
en/privacy.md
View File

@ -2,7 +2,7 @@
title: Privacy Policy
description:
published: true
date: 2021-10-06T08:03:52.688Z
date: 2023-12-21T09:33:30.916Z
tags:
editor: markdown
dateCreated: 2021-09-03T07:41:23.648Z
@ -10,105 +10,108 @@ 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/en/privacy-policy/).
Here is a brief overview of our privacy practices and how we understand them. For a full list of how we use your information, please see our [Privacy Policy](https://www.bstly.de/en/privacy-policy/).
# Privacy By Design <a name="privacy" id="privacy"></a>
# Privacy By design <a name="privacy" id="privacy"></a>
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.
Privacy by design means that systems are designed to be data efficient. In general, we always try to collect as little data as possible. The idea is that if you don't have it, you can't lose it. This applies in general to the data we collect, but also to how we link different data together.
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*.
To separate account and payment data, we use the *Pretix* ticketing system with its check-in system. A secret token is generated for each item. This token can then be redeemed in our in-house developed server component *we.bstly* 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.
The link between account/service and token is therefore only temporary for the current browser session and is not stored elsewhere. In other words, there are two databases, one for payment data and tokens (*Pretix*) and one for account and authorisation data (*we.bstly*). The link only takes place in an active browser session and will be forgotten once the token has been redeemed. So there is no link between payment details 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.
We are currently making compromises when it comes to linking accounts for each service. As always, convenience 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 based on your *we.bstly* account. On the one hand, this offers the convenience of *SSO* in that you only have to take 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 are sending an email to the person you have just chatted with.
# Individual services <a name="services" id="services"></a>
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).
Here we summarise the data collection for each service. For full details, please refer to our [Privacy Policy](https://www.bstly.de/privacy-policy?lang=en). For more information or instructions on the features of each service, please see our [Overview of Available Services](/en/services).
## Webserver <a name="webserver" id="webserver"></a>
Almost all services run via a web server, as well as this page. In general, a web server automatically generates a lot of data, such as 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.
Almost all services run through a web server, including this site. In general, a web server automatically generates a lot of data, such as your IP address, the version of your web browser and much more. The transmission of this data is technically necessary and can only be prevented at great expense to you. 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!
The answer is simple: Nothing! In general, this data is not stored at all. It may be written to log files as part of maintenance work so that we can investigate problems more thoroughly. However, these are not linked to any other data and are deleted as soon as the work is finished!
## Pretix <a name="pretix" id="pretix"></a>
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.
In the *Pretix* system, of course, we need to store personal data for payment transactions, as well as an email address for sending emails with confirmations, payment data and tokens. If you are a member of the Association, your membership details and membership fee account will be stored here. As mentioned above, this information is not linked to any other services.
## we.bstly <a name="webstly" id="webstly"></a>
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 *we.bstly* all you need is a username and password (well *salted*, [Argon2](https://en.wikipedia.org/wiki/Argon2) hashed!). It also creates a [PGP](https://en.wikipedia.org/wiki/Pretty_Good_Privacy) key pair, nothing more. Specifying an email address is optional. This is required if you lose your login details 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 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**!
In addition to your central account details, your permissions and the expiry date of your services are also stored here. At the moment it also stores the information that you are a regular club member. This has the advantage that we can contact all club members directly about our services or offer them extended services. Of course, this information is not linked to your membership data or your membership fee account, i.e. we only know **that** you are a member of the club, **not which club**!
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.
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 fields are also visible to other users and public fields are also visible to third parties.
Some settings for additional service like [Jitsi Meet](/en/services/jitsi) rooms, [Partey timeslots](/en/services/partey/stream) or [shortened urls](/de/services/urlshortener) are also stored here.
Some settings for additional services like [Jitsi Meet](/en/services/jitsi) rooms, [Partey timeslots](/en/services/partey/stream) or [shortened urls](/en/services/urlshortener) are also stored here.
## Nextcloud <a name="nextcloud" id="nextcloud"></a>
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.
Of course, the sensitivity of the data in the *Nextcloud* only depends on how you use it. The service itself does not provide any data other than your account data (only username and voluntary profile data). Since only user-generated content is stored here, it depends on what you upload, publish and write. The data is automatically encrypted, but only on the server side, so you can still share it with others.
However, *Nextcloud* also offers its own end-to-end encryption (*E2EE*) in the latest versions. You are of course free to use this for sensitive data, so that no one else can access these files. Note, however, that these files will no longer be accessible in the browser and cannot be shared. Also, the *E2EE* only applies to files and not to other data such as contacts, calendars, etc., so you should always think about what data you are 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.
As *Nextcloud* is also the basis for some community features, your account information will be shared with all other users. However, you are free to share other data such as files, calendars, etc. with other users.
## Email <a name="mail" id="mail"></a>
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.
Currently, emails are stored on the server as they arrive. As this has some disadvantages and requires 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, it also means that you'll have to set up all your email clients to decrypt them. We will, of course, publish detailed instructions in due course and will probably also offer an *opt-out* if you do not wish to use this feature.
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.
Your *we.bstly* account details will be used for authentication. Note that enabling two-factor authentication in your *we.bstly* account will not affect your email login.
## Vaultwarden <a name="vaultwarden" id="vaultwarden"></a>
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.
As a password manager, Vaultwarden stores highly sensitive data. However, it is all encrypted with your Master Password, which is stored on the server in hashed form only. The strength of your master password is also critical to the security of this data. In addition to the actual passwords, data such as the associated username, website URLs, or custom fields and notes are also stored. However, this data can only be decrypted with the master password.
## Partey <a name="partey" id="partey"></a>
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).
No data is stored in our virtual clubhouse. However, the transmission of your video and audio data is a highly sensitive area. As mentioned above, we do not store this data, but it is not technically impossible for other users to make illegal recordings. If you become aware of any infringements, please contact us as a matter of urgency. A good place to start is our [Help] page (/en/help).
## bstlboard <a name="bstlboard" id="bstlboard"></a>
In addition to your user data, all your entries and comments are stored in our message board. Currently, access is only limited to club members. So no outsiders have access to your content.
In addition to your user details, all your posts and comments are stored on our message board. Access is currently restricted to club members only. No outsiders will be able to access your content.
## Matrix <a name="matrix" id="matrix"></a>
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*.
As *Matrix* is a messaging service, sensitive communications may be generated. Fortunately, *Matrix* offers end-to-end encryption. However, as this is optional, we recommend that you always enable *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.
In addition to your chat messages, your room memberships are also stored for the service. If you create public rooms yourself, they will of course be 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.
Please also note that *Matrix* is a decentralised network, similar to email communication. This means that you can communicate with users from other providers, but you also transfer data, including your messages, to these servers.
## Jitsi-Meet <a name="jitsi" id="jitsi"></a>
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.
Our *Jitsi-Meet* rooms are the same as 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 <a name="peertube" id="peertube"></a>
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.
Important note: PeerTube has a P2P function, which means that you automatically share your video files with other users to reduce the load on the server. However, this will reveal your IP address to third parties! You can disable this feature at any time. See [tube.bstly.de/about/peertube#privacy](https://tube.bstly.de/about/peertube#privacy) for more details. We have chosen to leave this feature on because it is very handy and there is very little abuse of an IP address.
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.
The service itself only stores your username and a few personal settings and channels. Otherwise, the videos you upload are stored and, depending on your settings, made available to other users or to the public. The same goes for your livestreams.
## PrivateBin <a name="privatebin" id="privatebin"></a>
Since PrivateBin uses a client-side *end-to-end* encryption NO personal data is stored.
Because PrivateBin uses client-side *end-to-end* encryption, NO personal information is stored.
<!--
## Minetest <a name="minetest" id="minetest"></a>
The only personal data stored ara your username and a password hash. Of course as Minetest is an online-multiplayer game with a persistant world all your in-game changes and actions are stored on the server.
The only personal information stored is your username and a password hash. Of course, as Minetest is an online multiplayer game with a persistent world, all your in-game changes and actions are stored on the server.
-->
## Wiki.js <a name="wiki" id="wiki"></a>
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.
In general, no personal information is collected in our *Wiki*. Only your *we.bstly* username and your email address are stored in your account. In general, any text you write will be public and linked to your username. There is also a comment function. However, this is only available to other users and is not public.
## Urlshortener <a name="urlshortener" id="urlshortener"></a>
Of course every data added to the Urlshortener is stored. If a password is set only the hash of it is stored.
Of course all data added to the urlshortener will be saved. If a password is set, only the hash of the password is saved.
## Gitea <a name="gitea" id="gitea"></a>
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!
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, is entirely up to you. So be careful what files you upload, and whether your repository is publicly accessible. Since repositories often contain source code, including configuration files, we would like to remind you not to accidentally upload sensitive information such as passwords, *API keys* or *private keys* to your repository. Of course, on public repositories, your changes, issues, comments and account are public too!