Data Protection

calendar Jan 27, 2023 · 3 min read · Data-Protection  ·
copy

1. Preliminary note

No one would think of handing a lawyer a source code and pointing out to him or her that there may be unpleasant consequences if he or she does not fully understand it. Unfortunately, the other way around this is the case. With this I want to say: I am a computer scientist, not a lawyer. I have compiled the following information to the best of my knowledge. If anything is not legally watertight, please let me know. Thank you very much.

The short version:

  • No cookies
  • No use of tracking or statistical tools (Google Analytics et al.)
  • No inclusion of resources from third-party sources such as advertisements, fonts, social media plugins, etc.
  • No other bullshit you frequently find nowadays on many websites
  • The only thing that is temporarily stored are entries in the log files of the web server, where the IP addresses are anonymized (see section 3)

2. Contact details

Responsible for data processing on this website is:

wohtolF drahreG
62 .rtS-shcaS-snaH
lleznebörG 49128
ynamreG

3. Collection and processing of personal data

Every time content on a website is accessed, various data is sent from the visitor's browser to the provider's web server and back, including personal data such as the visitor's IP address. This is a technical necessity and cannot be prevented, otherwise the World Wide Web would not function in its current form.

The following data is automatically stored in log files of the server each time it is called up:

  • The IP address of the caller in anonymized form. Specifically, everything except the first two blocks is replaced with 0: 146.70.0.0
  • The date and time of access
  • The type of HTTP request, e.g. GET
  • The specific page that is requested, for example in the case of this privacy policy /data-protection/
  • The protocol used with version e.g. HTTP/1.1
  • The HTTP status code that informs whether the request was successful or possibly failed e.g. 200 in case of success.
  • The total number of transmitted bytes of the web server's response to the visitor.
  • The URL of the website from which the visitor came (the so-called referrer).
  • The so-called user agent, a kind of "business card" of the browser, on which, among other things, the browser type including version and the name of the operating system of the visitor is written

These log files allow me to ensure that this website is working technically correctly. In the event of an error, they allow an analysis of the cause of the problem and its prompt resolution. Furthermore, they are relevant to security, as activities of hackers can be identified. In this respect, these data are necessary for the smooth and secure operation of the website, i.e. the data are processed on the basis of Art. 6 (1) (f) GDPR. The log files are kept for 14 days and then automatically deleted. Further use does not take place.

All data that is transferred between you as a visitor and my web server is encrypted using TLS1.2/1.3, recognizable for example by the https:// in the address bar of the browser, often in combination with a lock symbol. On the one hand, this has the advantage that third parties can not read the transmitted information, on the other hand, the browser in conjunction with the certificate stored on the server ensures that you as a visitor are really connected to my web server and not to a malicious server of a potential attacker.