Cookies

1. What are cookies?

A cookie is a small data set that is saved on your device. It contains data such as personal page settings and logon information. This data set is created by the web server that your web browser has established a connection to, and this data set is then sent to you. In general, we use cookies to analyse the interest in our websites as well as to improve the user-friendliness of our websites. You can also access our websites without cookies as a matter of principle. If you would like to conveniently use our websites to their full extent, you should, however, accept the cookies which enable the use of certain functions, or which make use more convenient. TB Digital Services GmbH (TBDS) uses cookies to make its website more user-friendly, effective and secure. Our cookies contain no information specific to a person. 

If your browser settings are set to accept cookies, with the use of our websites you consent to the use of these cookies. Most browsers are set to accept all cookies by default. You have the option, however, of configuring your browser so that cookies are displayed before they are saved, or so that only certain cookies are accepted or rejected, or so that cookies are rejected in general.

We would like to point out that changes to settings only ever apply to the respective browser. If you use different browsers or change to a different device, the settings must be configured again. You can also delete the cookies from your storage medium at any time. Please refer to your web browser’s help function for information regarding cookie settings and how to change them, and also regarding the deletion of cookies.

2. Types of cookies and their purpose

2.1. Session cookies

Whilst you are active on a website, a session cookie is temporarily stored in the memory of your computer. Here, a session ID is saved so that, for example, you do not have to log in again each time you change webpage. Session cookies are deleted when you log out or their validity expires as soon as your session has automatically expired.

2.2. Persistent or protocol cookies

A persistent or protocol cookie stores a file on your computer for the duration defined by the file's expiration date. Due to these cookies, websites remember your information and settings for your next visit. This results in faster and more convenient access as you do not need to configure your language settings for our portal again, for example. Once the expiry date has elapsed, the cookie is automatically deleted when you visit the website that created it.

2.3. First-party cookies

These are set by the website itself (same domain as in the address bar of the browser) and can only be read by this website. These cookies are generally used to save information (e.g. your settings) which is then used when you next visit the website. 

2.4. Third-party cookies

Third-party cookies come from other providers than the operator of the website. They can be used, for example, to gather information for advertising, user-defined content and web statistics.

3. Cookies used

The following cookies are used on this website:

3.1 Google Analytics

Name of the cookie: _gat_XX-00000000-0

Storage duration: 1 minute

Description: Reduces the number of requests

Name of the cookie: _ga

Storage duration: 2 years

Description: To distinguish between users

Name of the cookie: _gid

Storage duration: 24 hours

Description: To distinguish between users

Name of the cookie: NID

Storage duration: 6 months

Description: This cookie is set by DoubleClick (owned by Google) to create a profile of your interests and to place relevant ads on other websites.

Name of the cookie: CONSENT

Storage duration: 18 years

Description: A discussion on Heise Forum explains that the Google homepage CONSENT cookie stores information about whether the user has read the data protection policies from Google and consented to them. 

Name of the cookie: ga-disable-***

Storage duration: 30 days

Description: If this cookie is set to true, there is a user opt-out for Google's performance tracking. 

3.1 Cookies of the provider: RIO

Name of the cookie: fe_typo_user

Storage duration: session

Description: This cookie is a TYPO3 standard session cookie. When a user logs in, it saves the session ID, which is used to recognise the user logged into the front-end and to grant them access to protected areas. Information is also obtained when forms are submitted.

Name of the cookie: c_bar

Storage duration: 1 day

Description: Is interpreted as consenting to the cookies.

Name of the cookie: be_lastLoginProvider

Storage duration: 90 days

Description: Contains the key of the Typo3 back-end login provider used

Name of the cookie: be_typo_user

Storage duration: session

Description: This cookie tells Typo3 whether the visitor has logged into the Typo3 back-end and which back-end user it concerns.

Name of the cookie: PHPSESSID

Storage duration: session

Description: PHP’s standard session identification