Cookie Policy

The general explanations in this cookie statement were last updated on February 28th, 2022. It applies in addition to our general privacy policy here, which contains basic and further information as to how we use cookies on our website and is to be regarded as incorporated into it. This page you are reading right now primarily contains additions and details. It is applicable to all viewers of this website from any legal order. Together with our privacy policy, it covers the relevant aspects..

Not all cookies listed here will benecessarily always set. In particular, some cookies may be listed which legally do not have to be listed here at all, as they only concern or affect logged-in users. Accordingly, complete information is not required as long as there are no users who are authorised to log in (except for the website owner).

To read more about services and cookies, please click on the name of the service or cookie or the category (“functional”, “preferences”, “statistics” etc.) or on the arrow.

And one preliminary remark as to WordPress: We use WordPress for website development. WordPress itself describes some of its cookies here Below, you can find those cookies we have found that our site sets so far. For even more information on all the cookies WordPress may use, read more here

WordPress

Functional, Preferences

Usage

We use WordPress for website development. Read more

Sharing data

This data is not shared with third parties.

Functional

Name
Expiration
session
Function
Store user preferences
Name
Expiration
session
Function
Helps the website to function
Name
Expiration
persistent
Function
Keep users logged in
Name
Expiration
none
Function
Check if cookies can be placed
Name
wp-saving-post
Expiration
1 day
Function
Saving a post in the editor automatically
Name
wp_lang
Expiration
end of session
Function
Storing language settings
Name
wpEmojiSettingsSupports
Expiration
session
Function
Storing browser details

Preferences

Name
Expiration
1 year
Function
Store user preferences
Name
Expiration
1 year
Function
Store user preferences
Name
comment_author_url_*
Expiration
1 year
Function
Store user preferences

Complianz

Functional

Usage

We use Complianz for cookie consent management. Read more

Sharing data

This data is not shared with third parties. For more information, please read the Complianz Privacy Statement.

Functional

Name
Expiration
365 days
Function
Store accepted cookie policy ID
Name
Expiration
365 days
Function
Store cookie consent preferences
Name
Expiration
365 days
Function
Store cookie consent preferences
Name
Expiration
365 days
Function
Store cookie consent preferences
Name
cmplz_choice
Expiration
365 days
Function
To store if a message has been dismissed
Name
cmplz_policy_id
Expiration
365 days
Function
Registering the ID for the accepted cookie policy
Name
cmplz_functional
Expiration
365 days
Function
To store cookie consent preferences
Name
cmplz_statistics-anonymous
Expiration
365 days
Function
To store cookie consent preferences
Name
cmplz_preferences
Expiration
365 days
Function
To store cookie consent preferences
Name
cmplz_statistics
Expiration
365 days
Function
To store cookie consent preferences
Name
cmplz_consent_status
Expiration
365 days
Function
To store cookie consent preferences
Name
cmplz_banner-status
Expiration
365 days
Function
To store if the cookie banner has been dismissed

Purpose pending investigation

Name
cmplz_consented_services
Expiration
365 days
Function
Functional

WP Do Not Track

Functional

Usage

We use WP Do Not Track for cookie consent management. Read more

Sharing data

This data is not shared with third parties.

Functional

Name
dont_track_me
Expiration
1 year
Function
Helps to respect the user's privacy settings

Cerber Security & Anti-Spam

Functional

Usage

We use Cerber Security & Anti-Spam for security and fraud prevention. Read more

Sharing data

For more information, please read the Cerber Security & Anti-Spam Privacy Statement.

Functional

Name
technicallynecessarybyc
Expiration
Between 1 hour, 1 session and 14 days maximum (see the comments at https://wpcerber.com/browser-cookies-set-by-wp-cerber/ for details).
Function
Any cookie starting with this prefix - the number may vary (normally between two and six, depending on plugin configuration) is set with the sole purpose of securing this website by detecting and mitigating malicious activity. These cookies contain randomly generated values. No personal or sensitive data is stored in them.
Name
technicallynecessarybyccerber_groove
Expiration
1 year
Function
Protect the website from hackers, cyber criminals, spammers and bots.

PHP

Functional

Usage

We use PHP for website development. Read more

Sharing data

This data is not shared with third parties.

Functional

Name
ppwp_wp_session
Expiration
when all browser windows are closed
Function
Belongs to PHP-applications and stores a user's unique session-ID for the purpose of handling his or her session

Feeds & Caching (General)

Preferences

Usage

We use Feeds & Caching (General) for page caching.

Sharing data

This data is not shared with third parties.

Preferences

Name
rss_feed_cache
Expiration
In most cases, the duration is tied to the cache expiration period, which can range from a few minutes to several hours, or even up to a day. This ensures that the cached RSS feed remains valid until the cache expires, and the system regenerates the feed. Typically, the cookie will last for the duration of the cached feed (often up to a few hours) or until the cache is manually cleared (which you can always to at any time).
Function
To help manage the caching of the RSS feed. It indicates that a cached version of the feed is being served, helping to reduce the load on the server by avoiding repeated regeneration of the feed for every visitor. Essentially, it allows the caching system to check whether the cached RSS feed is still valid or whether it needs to be regenerated. The cookie acts as an indicator of whether the RSS feed is coming from the cache and ensures that the feed isn't repeatedly generated from scratch for every user
Name
rss_feed_cache_time
Expiration
Typically lasts for a few hours or until the cache is manually cleared or refreshed. In many cases, the cookie will persist until the cache expires (which you can do anytime), which could range from a few minutes to several hours or even a day
Function
To store the timestamp of when the RSS feed cache was last updated or refreshed. This helps the system decide whether it should serve a cached version of the feed or regenerate the feed. By using a cache, it helps reduce the load on the server by preventing unnecessary regeneration of the feed on each request.

VG Wort

Statistics

Usage

We use VG Wort for Statistics and optimization.

Sharing data

For more information, please read the VG Wort Privacy Statement.

Statistics

Name
srp
Expiration
Session
Function
It helps to determine the copy probability of our texts and ensures the remuneration of legal claims of authors and publishers. IP addresses are only processed in anonymised form.

For questions and/or comments about our cookie policy and this statement, please contact us by using the contact details you can find linked from here.