Cookies

Intrexx generates various cookies while it is in use. These are small text files on the accessing system that can save information about the user or similar. Principally, Intrexx does not store any personal information in its cookies. The type and content of Intrexx cookies are described below. Cookies can have different functions and properties. A cookie can be up to 4093 bytes in size.

General cookies

Session cookies or persistent cookies

A session cookie exists only as long as the browser is left open. This means that the cookie is not stored persistently by the browser. A persistent cookie is stored on the user's hard drive / browser until a date specified by the provider. Session cookies should be HTTP only so that they can be read by the generating server only and not by JavaScript. Websites or portals should generally only be used in encrypted form - in this case, the cookies should also be provided with the secure flag so that they are only sent via an encrypted connection.

First-party or third-party cookies

A first-party cookie is set by the site visited and sent back to the site visited by the browser with each request. Third-party cookies are created in the background by a site other than the one visited, and by the browser when it makes requests to any sites that use the creator. Trackers are a typical example of this type of cookie.

Functional cookies

Functional cookies are used to increase the usability of a website. For example, settings that should be predetermined when you visit a website again are saved here. These can be settings for sorting tables or a specific language or currency, for example. Shopping carts are also often stored in cookies to restore them when you leave the store and reload the shop. Functional cookies usually have a longer lifespan.

Intrexx Cookies

The session cookie (co_SId)

A session ID is assigned to uniquely identify a user's session (guest or authenticated). This is randomly generated on the server side and kept there for the duration of the session. The session ID is stored in a cookie so that this session can also be assigned to the client (browser).

The cookie contains only the session ID and no other personal information. The validity period of the cookie is limited to the session duration meaning it is not stored persistently. Furthermore, the cookie is only sent back to the visited Intrexx page.

The layout cookie (co_Layout)

The layout cookie stores the portal layout set by the user is therefore a first-party cookie. The value of the cookie contains the portal operator but no personal data of the user. The GUID attached to the cookie name serves to identify the layout (each layout in Intrexx has a unique identifier in the form of a GUID).

The language cookie (co_Lang)

The language set by the user in the portal is stored in the language cookie. The ISO key of the selected language is stored as the value (de, en, fr, ...). This first-party cookie does not contain any user-related information.

The locale cookie (co_Locale)

If the user can select a locale, it will be stored in the locale cookie. The ISO key (e.g. EN-en, DE-de) is stored as the value. This first-party cookie also does not contain any user-related information.

Possible "externally generated" cookies in Intrexx portals

Cookies can be generated by additional programming in Intrexx via JavaScript. However, this is done through special customizations as part of the application development, which is in the hands of the customer. In principle, according to the current legal situation, such adjustments should generally be documented so that customer-specific cookie generations are made known.

Cookies are also frequently generated by components integrated in Intrexx portals, such as trackers (GoogleAnalytics, eTracker, ...). Usually, all data that can be determined via the request (including the complete IP address) is stored and transmitted externally to the tracking service provider.

Access from external websites via an Intrexx portal can also produce cookies in the context of a portal. This means that the cookie list in the user's browser can contain many cookies that were not generated by Intrexx or the portal itself.

For all of these "externally generated" cookies, the responsibility for data protection-compliant use or implementation lies with the data controller - i.e. the controller of the Intrexx portal.