Seat uses different cookies on its websites. Cookies are small files with configuration information which are stored on your terminal. Cookies can generally be broken down into three categories. There are cookies which are essential for the function of the website (referred to as functional cookies), cookies which increase the user-friendliness of a website visit and, for instance, save your language settings (referred to as convenience cookies) and cookies which are used as the basis for a pseudonymised user profile (referred to as tracking cookies).
Functional cookies must be processed in order to make your visit to the website possible (see also Art. 6 Par. 1 lit. GDPR).
The legal basis for convenience cookies is legitimate interest (Art. 6 Par. 1 lit. f GDPR). The legitimate interest is constituted by the provision of convenience during the visit to the website. You can withdraw your consent for data processing for the future at any time. You will find more detailed information in the data protection declaration.
Tracking cookies are only used if consent is provided by the website visitor (Art. 6 Par. 1 lit. a GDPR). Consent is provided using what is referred to as a cookie banner, which has to be actively clicked.
You will find further information on the tracking cookies used in our data protection declaration.
Please note that any changes to settings only affect the respective browser. If you use different browsers or change terminal, the settings will need to be made again. Furthermore, you can delete cookies from your data storage device at any time. Please use the help function of your web browser for information on cookie settings, how to change and delete them.
|Name of the cookie||Purpose||Storage period||Type of cookie|
|erWinUser||A cookie with the user name is placed in the user’s browser. The prerequisite for this is that the browser allows the placement of cookies and saves them permanently. This cannot be influenced by the server. If a cookie exists with the user name, the user name is entered in the "User name" field as a default value. A check is made as to whether the user’s browser already has a cookie in which the user name is stored.||10 years||Stored cookie for authentication|
|JSESSIONID||Cookie, which is generated by servelet containers, such as Tomcat or Jetty, and is used for session management in the J2EE web application for the HTTP protocol.||Session||Stored cookie for authentication|
|eventMessageHiding||Cookie used to display event messages in erWin.||365 days||Stored cookie for personalisation of the operating interface|
|X-Token||Cookie generated automatically by the server with random data for synchronisation of the session between the browser and the application, for prevention of a CSRF attack.||Session||Stored cookie for authentication|