Privacy

What data is processed when you visit this blog

This is a translation for convenience. The German version is legally binding.

Last updated: October 2026

Controller

The controller for data processing on this website within the meaning of the General Data Protection Regulation (GDPR) is:

Daniel Remmers
Brombeerweg 16
27793 Wildeshausen
Germany
Email: hello@dr365.io

Overview

This blog is a static website. There are no user accounts, contact forms, newsletters, ads or analytics. No cookies are set. Fonts and scripts are served from this server, not from third-party servers (CDNs).

Personal data is essentially only processed in the server log files (see “Server log files”). External services only come into play for comments (see “Comments via Bluesky”), and only on posts where comments are enabled.

Your rights

You have the following rights regarding your personal data:

  • Access (Art. 15 GDPR)
  • Rectification (Art. 16 GDPR)
  • Erasure (Art. 17 GDPR)
  • Restriction of processing (Art. 18 GDPR)
  • Data portability (Art. 20 GDPR)
  • Objection to processing based on Art. 6(1)(f) GDPR, on grounds relating to your particular situation (Art. 21 GDPR)

You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the member state of your habitual residence, place of work or place of the alleged infringement.

An informal email to the address above is all it takes.

Hosting

This website runs on a server operated by:

STRATO GmbH
Otto-Ostrowski-Straße 7
10249 Berlin
Germany

The server is located in a STRATO data centre in Germany. A data processing agreement under Art. 28 GDPR is in place with STRATO; STRATO processes the data only on my instructions. The legal basis for hosting is Art. 6(1)(f) GDPR; the legitimate interest is reliable provision of the website.

The website is built automatically from a Git repository on every change and served as static files by a web server (nginx) behind a reverse proxy.

Server log files

Each time a page is requested, the server automatically processes information transmitted by your browser:

  • IP address
  • date and time of the request
  • requested address (URL) and HTTP status code
  • amount of data transferred
  • referrer URL (the previously visited page), if transmitted
  • browser and operating system (user agent)

This data is required to deliver the website and is stored in log files to detect and fix errors and abuse (e.g. attacks). The legal basis is Art. 6(1)(f) GDPR; the legitimate interest is the secure and stable operation of the website. Log files are deleted after [Speicherdauer, z. B. 14 Tagen] unless they are needed longer to investigate a specific incident. The data is not combined with other data or analysed for statistical purposes.

Encryption

The website is served exclusively over HTTPS (TLS), so data in transit cannot be read by third parties.

Fonts

The “Lato” font is loaded locally from this server. No connection is made to Google Fonts or other font providers.

Local storage, no cookies

This website does not set any cookies.

To keep your colour scheme (light, dark, or automatic based on your system setting) across page views, the website stores the entry StackColorScheme with one of the values light, dark or auto in your browser’s local storage. On your first visit, auto is stored; when you use the light/dark toggle, your choice is stored.

The entry stays in your browser only, is not sent to the server and contains no personal information. It remains stored until you delete it in your browser (e.g. via “clear site data”). Storing it is strictly necessary for the display of the website you are using (§ 25 (2) no. 2 TDDDG, German Telecommunications Digital Services Data Protection Act).

Comments via Bluesky

Comments may be shown below individual posts. These comments are replies to a post on the social network Bluesky. There is no comment form on this website; to comment, you reply on Bluesky.

Only on posts where comments are enabled, your browser loads the comments directly from Bluesky’s public API (public.api.bsky.app) and the commenters’ profile pictures from cdn.bsky.app. In doing so, your IP address, the time of the request and information about your browser are transmitted to Bluesky. The provider is Bluesky Social, PBC, USA. You do not need a Bluesky account to read comments, and no cookies are set.

The legal basis is Art. 6(1)(f) GDPR; the legitimate interest is being able to show the discussion about a post right next to it. This involves a transfer of data to the USA. In its privacy policy, Bluesky does not rely on the EU-U.S. Data Privacy Framework but bases transfers from the EU on the European Commission’s Standard Contractual Clauses. It cannot be ruled out that US authorities access the data and that you have no legal remedies comparable to those in the EU. For more information, see Bluesky’s privacy policy: https://bsky.social/about/support/privacy-policy.

If you comment on Bluesky yourself, your comment is public there and also appears below the post on this website with your display name, handle and profile picture. If you delete your comment on Bluesky, it no longer appears here either.

No analytics

No analytics or tracking tools are used (e.g. no Google Analytics, no Matomo), and no user profiles are created.

Posts contain links to other websites as well as buttons for sharing on LinkedIn, Bluesky and X. These are plain links: the respective site is only contacted, and only receives data from you, when you click on them. The respective provider is responsible for any processing there.

No third-party content (e.g. videos or social media posts) is embedded that would load automatically when you open a page.

Contact by email

If you email me, I process your address and your message in order to respond. The legal basis is Art. 6(1)(f) GDPR (responding to your enquiry), or Art. 6(1)(b) GDPR where a contract is concerned. Emails are deleted when they are no longer needed and no statutory retention obligations apply. I run my mailbox myself on the same STRATO server (see “Hosting”).