Why do we use cookies?
- To ensure that the website works properly and you have an optimal user experience.
- To understand the number of visitors who visit our site and the pages they view.
- To make it possible to integrate social media on the website.
- To generate advertising tailored to your needs.
What is a cookie?
A cookie is a simple small file that is sent with pages from this website and stored by the browser on your computer's hard drive. The information stored therein can be sent back to our servers on your next visit. A cookie is a file containing an ID (a string of letters and numbers) that is sent by a web server to a web browser and stored by the browser. The ID is then sent back to the server each time the browser requests a page from the server. Cookies are small pieces of data stored in a visitor's browser. They are typically used to track which settings users have selected and the actions they have taken on a site.
Cookies cannot be used to identify individuals; a cookie can only identify a machine. Cookies generally do not contain information that personally identifies a user, but personal information that we store about you can be linked to the information stored in and obtained through cookies.
Use of permanent cookies
With the help of a permanent cookie, we can recognise you when you visit our website again. The website can therefore be adjusted to your preferences. Also when you have given permission for placing cookies, we can remember this by means of a cookie. This saves you having to repeat your preferences over and over again, which in turn saves you time and makes it easier for you to use our website. Permanent cookies are stored by a web browser and remain valid until the set expiry date, unless they are deleted by the user before the expiry date via the settings of your browser.
Use of session cookies
A session cookie expires at the end of the user session when the web browser is closed. They typically store information in the form of a session identifier that does not personally identify the user. A session cookie enables us to see which parts of the website you have viewed during this visit. This enables us to adapt our service as much as possible to the surfing behaviour of our visitors. These cookies are automatically deleted as soon as you close your web browser.
Google Analytics
Through our website, a cookie is placed by the company Google, as part of the 'Analytics' service. We use this service to track and get reports about how visitors use the website. Google may provide this information to third parties if Google is legally obliged to do so, or insofar as third parties process the information on Google's behalf. We have no influence on this. We have not authorised Google to use the analytics information obtained for other Google services.
The information Google collects is anonymised as far as possible. Your IP address is expressly not provided. The information is transferred to and stored by Google on servers in the United States. Google states it will adhere to the Safe Harbor principles and is affiliated to the Safe Harbor program of the U.S. Department of Commerce. This means that there is an adequate level of protection for the processing of any personal data.
Right to access and correct or delete your data
You have the right to request access to and correction or deletion of your data. In order to prevent abuse, we may ask you to provide adequate identification. When it comes to access to personal data linked to a cookie, you must send a copy of the cookie in question. You can find this in the settings of your browser.
You can send your question using the contact details found in our Privacy Statement.
The cookies we use
|
Name |
Lifetime |
Purpose |
|
DFTT_END_USER_PREV_BOOTSTRAPPED |
Two years |
It tells Immotokens that we have already created a record for this site visitor, so there is no need to work and it saves us some loading time. Immotokens classifies these cookies as Functionality type. |
|
XSRF-TOKEN |
Session |
This cookie contains a unique ID which is a link to the user's session information in your database. The browser provides this cookie on future requests and the server knows who you are. |
|
__gads |
< 2 years |
The purpose of this cookie is to measure interactions with the ads on that domain and to prevent the same ads from being shown to you too often. These cookies cannot be read by Google when you are on a site other than the one on which they are placed. |
|
__hssc |
1 year |
This cookie keeps track of sessions. It is used to determine whether we should increase the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each page in a session) and session start timestamp. |
|
__hssrc |
Session |
When HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine whether the visitor has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. |
|
__hstc |
2 years |
The main cookie for visitor tracking. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit) and session number (in increments for each subsequent session). |
|
__utma |
1 year 6 months |
This cookie keeps track of how many times a visitor has been on the site in relation to the cookie, when their first visit was and when their last visit took place. Google Analytics uses the information from this cookie to calculate things like Days and Visits to buy. |
|
_ga |
2 years |
The customer ID is stored in the Google Analytics cookie. The GA cookie is set when a person visits your website for the first time. Google Analytics sends the Client ID with each hit to associate hits with a user. The GA cookie can only exist on the device and browser where it is set. |
|
__utmx |
18 months |
These Google Analytics cookies are used to engage users in Content Experimentation. |
|
hubspotutk |
10 years |
This cookie is used to track the identity of a visitor. This cookie is passed to HubSpot when forms are submitted and is used in the deduplication of contacts. |
|
_fbc |
3 months |
This Facebook cookie is only set if the user has landed on our page with a fbclid URL parameter. It will contain a click ID to be used to track Facebook Pixel events back to the Facebook click. |
|
_fbp |
3 months |
Used by Facebook to deliver a range of advertising products, such as real-time bidding from third-party advertisers. The main purpose of this cookie is: Targeting/Advertising |
|
_gcl_au |
1 month |
Used by Google AdSense to experiment with advertising effectiveness on websites that use their services. |
|
_gid |
1 day |
Records a unique ID that is used to generate statistical data on how the visitor uses the website. |
|
_hjid |
6 months |
Hotjar cookie: This cookie is set when the customer first arrives at a page with the Hotjar script. It is used to maintain the Hotjar User ID, unique to that site on the browser. This ensures that behaviour on subsequent visits to the same site is attributed to the same User ID. |
|
_hjptid |
Session |
Hotjar cookie: This cookie is set when the customer first arrives at a page with the Hotjar script. It is used to maintain the Hotjar User ID, unique to that site on the browser. This ensures that behaviour on subsequent visits to the same site is attributed to the same User ID. |
|
ajs_anonymous_id |
1 year |
These cookies are generally used for Analytics and help count the number of people visiting a particular site by tracking whether you have been there before. This cookie has a lifetime of 1 year. |
|
ajs_group_id |
1 year |
This Analytics cookie gives you a unique group ID. |
|
Ajs_user_id |
1 year |
This Analytics cookie gives you a unique user ID. |
|
c_user |
3 months |
The c_user cookie contains the user ID of the currently logged in user. ... If the 'keep me logged in' checkbox is ticked, the cookie will expire after 90 days of inactivity. If the 'keep me logged in' checkbox is not checked, the cookie is a session cookie and thus deleted when the browser is closed. |
|
datr |
1 year 6 months |
The purpose of this cookie is to identify the web browser used to connect to Facebook, regardless of the logged-in user. This cookie plays an important role in Facebook's security and integrity functions. |
|
fr |
3 months |
Used by Facebook to deliver a range of advertising products, such as real-time bidding from third-party advertisers. |
|
intercom-session |
6 days |
This cookie is used to show the user more relevant advertisements. Purpose: Targeting/Advertising |
|
laravel_cookie_consent |
20 years |
This cookie is used to track the user's consent to cookies. |
|
laravel_session |
Session |
These cookies are used to store file - sessions in storage/framework/sessions.These files are stored in secure, encrypted cookies. |
|
mp_hj_mixpanel |
4 months |
This cookie is used to apply Analytics. |
|
optimizelyBuckets |
8 years |
This cookie is used to apply Analytics. |
|
optimizelyEndUserId |
7 years |
This cookie is used to apply Analytics. |
|
optimizelySegments |
Session |
This cookie is used to apply Analytics. |
|
sb |
2 years |
Allows logging in and signing up via Facebook |
|
wd |
3 months |
Allows logging in and signing up via Facebook |
|
wp-settings-4 |
1 year |
WordPress cookie for a logged in user. WordPress also sets a few wp-settings-[UID] cookies. The number at the end is your individual user ID from the user database table. This is used to customise your view of the admin interface, and possibly also the main site interface. |
|
wp-settings-time-4 |
1 year |
WordPress cookie for a logged in user. WordPress also sets a few wp-settings-[UID] cookies. The number at the end is your individual user ID from the user database table. This is used to customise your view of the admin interface, and possibly also the main site interface. |
Enabling and disabling cookies
You can set your Internet browser in such a way that cookies are not accepted, that you receive a warning when a cookie is installed or that the cookies are subsequently removed from your hard disk. More information on enabling, disabling and deleting cookies can be found in the instructions and/or by using the Help function of your browser.
Most browsers allow you to refuse cookies and delete existing cookies as well. The methods for doing this vary from browser to browser and from version to version. Please note, however, that certain graphic elements may not appear correctly or you may not be able to use certain applications.
You can obtain up-to-date information on blocking and deleting cookies via these links:
(a) https://support.google.com/chrome/answer/95647?hl=en (Chrome);
(b) https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences (Firefox);
(c) http://www.opera.com/help/tutorials/security/cookies/ (Opera);
(d) https://support.microsoft.com/en-gb/help/17442/windows-internet-explorer-delete-manage-cookies (Internet Explorer);
(e) https://support.apple.com/kb/PH21411 (Safari); and
(f) https://privacy.microsoft.com/en-us/windows-10-microsoft-edge-and-privacy (Edge).