Cookie policy

When you access our website, FERNBACH occasionally uses cookies, i.e. small text files that are stored on your computer and saved by your browser.

They serve the purpose of making our offers user-friendly, effective and secure. Furthermore, they help visitors to the website to navigate efficiently through the pages and to obtain information on the use of the website from the website operator.

Passwords are not stored in cookies. Most of the cookies we use are absolutely necessary session cookies, performance cookies and functionality cookies. They are automatically reset at the end of your visit. If you end the session by closing your browser, the cookie remains stored for a certain time and is then overwritten or deleted by the customer (e.g. your PC, your tablet). Cookies cannot contain viruses or other data that harm your computer.

What do we use cookies for?

We use cookies to track what you have done on our website, but we cannot access personal information such as your name or address. We will only see such information if you provide it to us or if you have set your browser to automatically provide this information.

We use the information collected to analyse trends and optimise our site for our customers. Cookies enable us to provide customers with individual offers based on their use of the website.

Can I disable cookies?

Yes, you can deactivate cookies in your browser. Further information can be found in the “Help” function for your browser. However, deactivating cookies can have an influence on the quality of the visit to the site.

Category 1: Strictly necessary cookies

Cookie Name	Purpose
ASP.NET_SessionId	Each time a user calls such an application, a unique session ID will be affiliated to the user. If the application chooses to store such session data, this will be stored via the cookie. Such cookies will expire immediately once a session ends (i.e. when you close a browser).
ASPXAUTH	Authorisation cookies by ASP. Net web applications when users log into an application using the .Net Framework. Information stored here is encrypted and again only valid for the lifetime of a session, so again when you close the browser the cookie will be removed.
PortalRoles	When logged into the website, the PortalRoles cookie is used to maintain the security roles which the user is within for the CMS.
Edit Mode	The Edit Mode cookie is used to handle the edit view in which the user is. If Edit mode is selected, the cookie is populated and the edit icons are visible.
Move Mode	When CMS parts are moved between the web page columns and applied, the cookie is used to maintain the state.
CartID	The CartID cookie is used with the eCommerce engine to store information about products stored inside the shopping basket.

Category 2: Performance cookies

Cookie Name	Purpose
mf_[session]	This Mouseflow cookie identifies the browser session while it happens. The cookie is deleted as soon as the session ends, meaning when the user leaves the website.
mf_user	This Mouseflow cookie establishes whether the user is a returning or first time visitor. This is done simply by a yes/no toggle – no further information about the user is stored. This cookie has a lifetime of 90 days.
_otui	Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing _otui cookies exists. The cookie is updated every time data is sent to Opentracker.
_ots	Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing _ots cookies exists. The cookie is updated every time data is sent to Opentracker.
_otpe	Used to store the previous event before landing on the current page.
_otor	Used to store the original referrer/event that that explains how the user reached your site. The cookie is created when the javascript library is executes for the first time.
machine-id	Deprecated: was used to store the original country from which the user reached your site. The cookie is created when the javascript library is executes for the first time.
utm_*	Optional: Used to store the original utm_/event that that explains which campaign the user reached your site with. The cookie is created when the javascript library is executes with an optional utm_* parameter in the query portion of the url.

Category 3: Functionality cookies

Cookie Name	Purpose
userFullName	When the log-in has been completed, this cookie stores the display name of the registered user in order to give the user an individual welcome.

We also occasionally use cookies to measure the success of our advertising measures and optimise these. We use the conversion tracking of Opentracker and Mouseflow. There are no features (e.g. complete IP address, first or last name, address, e-mail address) contained, by means of which you could be personally identified.

Useful Sites

Information Commissioner’s Off

Aboutcookies.org

Wikipedia