Cookies used

auth.*

The website allows a private area with user registration, login and associated functions. These cookies ensure the identification of the logged-in user.

refreshToken

AccessTokens have an expiration date for security reasons. With the RefreshToken, the access tokens can be renewed regularly.

i18n*

Website content can be provided in different languages. With i18n (internationalization framework), your language settings are stored in the cookie and sent to the server to load the appropriate language files on request.

cookieconsent

Stores consent to privacy and cookie settings.

If the cookie is set or if the user has given the necessary consents for data storage when registering, the following data is stored on the server in addition to form entries (e-mail, name, address, date of birth, etc.):

• IP address and associated information (date, host, location, time zone), see example

• browser data (see example)

• Language settings (e.g. locale: de for German)

• called APIs (interfaces to the server that provides the website content such as texts, images and videos)

• SID (Session Identification)

This data will be automatically deleted after 6 months.

ARRAffinitySameSite

This cookie is set by websites running on the Windows Azure cloud platform. It is used for load balancing to ensure that visitors' page requests are routed to the same server in each browsing session.

Youtube

We integrate the videos of the platform "YouTube" of the provider Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Privacy Policy: https://www.google.com/policies/privacy/, Opt-Out: https://adssettings.google.com/authenticated.

Data processing by local storage

In addition to cookies, information can also be stored in local storage. Data is stored locally in the cache of the browser, which continues to exist and can be read even after closing the browser window or closing the program - unless the cache is deleted.

acceptInstall

In addition to the information mentioned above, acceptInstall is stored in the local specher.

The web application can also be installed on the desktop or mobile device. If the installation has been rejected once, acceptInstall is intended to prevent it from being asked for again. In this case, it is not a cookie but only on information that is stored in the browser and not sent to the server.

styleOptions

The app also allows anonymous users to change the appearance of the application. However, the corresponding settings are only available in the local browser.

maxScreen

Specifies whether the web page should be displayed in full view on certain pages.

SID

The session identification allows the application to give users concrete concrete recommendations based on the use of the page. Without consent, this information will only be stored locally.

OpenAI

Please be aware that by interacting with this chat service, your data, including any personal information shared during the conversation, may be processed and stored. This data is transmitted to OpenAI for analysis and to improve our services. We are committed to handling your information responsibly and in accordance with data protection laws. For more details on how your data is used and protected, please refer to our privacy policy.

Progressive Web App

This application is a Progressive Web App (PWA). A progressive web app is based on a responsive website and is equipped with new technologies such as the service worker. It is accessible like a website and can be indexed via Google. The website must be transmitted SSL-encrypted via the HTTPS protocol and must have a manifest. The PWA manifesto tells the browser that it is a progressive web app. Properly implemented, a PWA is faster, can be used offline and almost like a native app (similar to the apps from the Google Play Store or Apple Store).

Even though a PWA has the look and feel of a native app, it is part of the website and is subject to this Privacy Notice. An installation of an app on a mobile device is therefore not necessary.

Content Delivery Network (CDN) Service

jsDelivr

is a content delivery network (CDN) service that delivers data to web pages. In order to provide this service, your browser may send personal data to jsdelivr.com . jsDelivr can thus collect and store user data such as IP address, browser type, browser version, which website is loaded or the time and date of the page visit.  jsdelivr.com expressly states that the Company does not use cookies or other tracking services.

This service allows the page to load faster.

If you want to prevent this data transfer, you can install a JavaScript blocker (see, for example, https://noscript.net/). Please note, however, that the website no longer works as usual. Further information on data processing by the software service jsDelivr can be found in the company's privacy policy at https://www.jsdelivr.com/privacy-policy-jsdelivr-net.

Our website uses HTTP cookies to store user-specific data.

In the following, we explain what cookies are and why they are used so that you can better understand the following privacy policy.

What exactly are cookies?

Whenever you browse the Internet, you use a browser. Well-known browsers include Chrome, Safari, Firefox, Internet Explorer and Microsoft Edge. Most websites store small text files in your browser. These files are called cookies.

One thing cannot be denied: cookies are really useful helpers. Almost all websites use cookies. More precisely, they are HTTP cookies, as there are also other cookies for other areas of application. HTTP cookies are small files that are stored on your computer by our website. These cookie files are automatically placed in the cookie folder, the "brain" of your browser. A cookie consists of a name and a value. When defining a cookie, one or more attributes must also be specified.

Cookies store certain user data about you, such as language or personal page settings. When you visit our site again, your browser transmits the "user-related" information back to our site. Thanks to cookies, our website knows who you are and offers you the setting you are used to. In some browsers, each cookie has its own file, in others, such as Firefox, all cookies are stored in a single file.

There are both first-party cookies and third-party cookies. First-party cookies are created directly by our site, third-party cookies are created by partner websites (e.g. Google Analytics). Each cookie must be evaluated individually, as each cookie stores different data. The expiration time of a cookie also varies from a few minutes to a few years. Cookies are not software programs and do not contain viruses, Trojans or other "pests". Cookies also cannot access information from your PC.

For example, this is what cookie data may look like:

Name: _ga

Value: GA1.2.1326744211.152221122443-6

Purpose: Differentiation of website visitors

Expiration date: after 2 years

A browser should be able to support these minimum sizes:

• At least 4096 bytes per cookie
• At least 50 cookies per domain
• At least 3000 cookies Overall

What types of cookies are there?

The question of which cookies we use in particular depends on the services used and is clarified in the following sections of the privacy policy. At this point, we would like to briefly discuss the different types of HTTP cookies.

There are 4 types of cookies:

Essential cookies

These cookies are necessary to ensure basic functions of the website. For example, these cookies are needed when a user places a product in the shopping cart, then continues to surf on other pages and later goes to the checkout. These cookies do not delete the shopping cart, even if the user closes his browser window.

Appropriate cookies

These cookies collect information about user behavior and whether the user receives any error messages. In addition, these cookies are also used to measure the loading time and the behavior of the website on different browsers.

Target-oriented cookies

These cookies ensure a better user experience. For example, entered locations, font sizes, or form data are saved.

Advertising cookies

These cookies are also called targeting cookies. They serve to provide the user with individually adapted advertising. This can be very convenient, but also very annoying.

Usually, when you visit a website for the first time, you will be asked which of these types of cookies you want to allow. And of course, this decision is also stored in a cookie.

How can I delete cookies?

How and whether you want to use cookies is up to you. Regardless of which service or website the cookies originate from, you always have the option of deleting, deactivating or only partially allowing cookies. For example, you can block third-party cookies but allow all other cookies.

If you want to know which cookies have been stored in your browser, if you want to change or delete cookie settings, you can find this in your browser settings:

Chrome: Delete, enable and manage

cookies in Chrome Safari: Managing cookies and website data with Safari

Firefox: Delete cookies to remove data that websites have placed on your computer

Internet Explorer: Delete and manage cookies

Microsoft Edge: Deleting and Managing Cookies

If you do not want cookies in principle, you can set up your browser so that it always informs you when a cookie is to be set. This allows you to decide for each individual cookie whether you allow the cookie or not. The procedure varies depending on the browser. It is best to search for the instructions in Google with the search term "Delete cookies Chrome" or "Disable cookies Chrome" in the case of a Chrome browser.

What about my privacy?

Since 2009, there are the so-called "cookie guidelines". It states that the storage of cookies requires your consent. Within the EU countries, however, there are still very different reactions to these directives. In Austria, however, that directive was transposed into Paragraph 96(3) of the Telecommunications Act (TKG).

If you want to know more about cookies and are not afraid of technical documentation, we recommend https://tools.ietf.org/html/rfc6265, the Request for Comments of the Internet Engineering Task Force (IETF) called "HTTP State Management Mechanism".