USE OF COOKIES
Our Website uses cookies and other tracking mechanisms.
Cookies are small files that are stored on your computer and are used to collect information while you are visiting the Website. We use cookies to better understand how you use the Website, collect statistics about the use of our Website and customize advertisements that are shown to you, for example on Facebook. In the long term, we use this knowledge to develop increasingly better and more user-friendly offers and to offer you a better experience when you visit our Website. Examples of what the statistics give us answers to are; how many people visit different pages, how long the visit lasts, which websites the users come from and which browsers are used.
The information we collect using cookies includes IP addresses, operating systems, usage/navigation, device location, etc. The information is processed in de-identified and aggregated form, which means that we cannot trace the information we collect back to the individual user. Your IP address is only stored while you visit the website, after which it is either deleted or anonymized before the information is stored and processed.
At fredensborg.no we use Google Analytics for website analysis. This is done by Google downloading cookies to your browser. Using the cookies, Google Analytics collects information about usage. The information is stored anonymized, without identifying you, and Fredensborg AS only receives summarized statistics for the website. Examples of what such statistics provide answers to are how many people visit the website, which pages they visit and how long they are on the website. User statistics are stored for 14 months.
It is the visitors’ IP addresses that Google Analytics uses in the collection. The IP addresses are anonymized before storage. Here you can read about how Google anonymizes IP addresses.
At fredensborg.no we use Hotjar to improve the user experience for visitors to www.fredensborg.no by analyzing usage patterns and web behavior. To do this, the heatmaps function and polls of the web analysis tool Hotjar are used. No tracking is done outside the website and user patterns are not linked to personally identifiable information. IP addresses are anonymized before storage on the server, thus making all user data anonymous. Here you can read more about how Hotjar anonymizes IP addresses. Data collected in Hotjar will be deleted after 12 months.
If you do not want Google Analytics or Hotjar to store data about you, you can either change the settings in your browser (as described further down the page) or you can download a “google plugin” in your browser or a Hotjar plugin.
Fredensborg AS also uses the following types of cookies:
Use of Google cookies
Google Tag Manager (gtag.js) and Google Analytics (analytics.js) set the following cookies:
| Name | Exp date | Description |
|---|---|---|
_ga | 2 years | Used to distinguish users. |
_gid | 24 hours | Used to distinguish users. |
_gat | 1 minute | Used to interrupt the request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named dc_gtm. <property-id> |
AMP_TOKEN | 30 seconds to 1 year | Contains a token that can be used to retrieve a client ID from the AMP Client ID service. Other possible values indicate opt-out, inflight request, or an error retrieving a client ID from the AMP Client ID service. |
_gac_<property-id> | 90 days | Contains campaign-related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt out. |
Hotjar cookies
Cookies set by the Hotjar script
| Name | Description | Exp date |
| _hjClosedSurveyInvites | Hotjar cookie. This cookie is set when a visitor interacts with a modal pop-up survey. It is used to ensure that the same invitation is not shown again if it has already been shown. | 365 days |
| _hjDonePolls | Hotjar cookie. This cookie is set when a visitor has completed a poll using the feedback poll widget. It is used to ensure that the same poll is not displayed again if it has already been completed. | 365 days |
| _hjMinimizedPolls | Hotjar cookie. This cookie is set when a visitor minimizes a feedback poll widget. It is used to ensure that the widget remains minimized as the visitor navigates through your website. | 365 days |
| _hjDoneTestersWidgets | Hotjar cookie. This cookie is set when a visitor submits their information in the User Tester Recruitment widget. It is used to ensure that the same form is not shown again if it has already been filled out. | 365 days |
| _hjIncludedInSample | Hotjar cookie. This session cookie is set to let Hotjar know if the visitor is included in the sample used to generate funnels. | 365 days |
| _hjShownFeedbackMessage | This cookie is set when a visitor minimizes or completes the incoming feedback. This is done so that the incoming feedback will load minimized immediately if they navigate to another page where it is set to appear. | 365 days |
| _hjid | Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar user ID, unique to that site, in the browser. This ensures that behavior on subsequent visits to the same site is attributed to the same user ID. | 365 days |
| _hjRecordingLastActivity | This should be located in sessionStorage (as opposed to cookies). This is updated when a visitor recording starts and when data is sent through WebSocket (the visitor performs an action that Hotjar records). | Session |
| hjTLDTest | When the Hotjar script is run, we try to determine the most generic cookie path to use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring options until it fails. After this check, the cookie is removed. | Session |
| _hjUserAttributesHash | User attributes sent via the Hotjar Identify API are cached during the session to know when an attribute has changed and needs to be updated. | Session |
| _hjCachedUserAttributes | This cookie stores user attributes that are sent through the Hotjar Identify API whenever the user is not in the sample. These attributes will only be stored if the user interacts with a Hotjar Feedback tool. | Session |
Mailchimp Cookies Served Through Websites
The specific types of first and third party cookies served through our websites and the purposes they serve are described in more detail below:
| Kategorier | Cookies |
|---|---|
| Mailchimp These cookies are strictly necessary to provide you with services available through our websites and to use some of the features, such as access to secure areas. | _mcga _mc PHPSESSID _new-status-app_session JSESSIONID mc_blog_Session _mcid KB_ID _integrations_session _AVESTA_ENVIRONMENT _experts_session PHPSESSDATA whatsNewLastVisited KB_HIS MC_ATPC |
To monitor the use of cookies and other tracking mechanisms, please visit www.ghostery.com or www.disconnect.me.
You can change your browser settings to identify and block the use of cookies. Read more about how to manage cookies at nettvett.no. Please note that if you choose to refuse the use of cookies, it may limit access to some features of the Website.
