Cookie Policy
Effective Date: 24 June 2022
We use cookies on our website www.across.health in order to improve and personalize the user experience. This policy explains what cookies are and which cookies are used for which purpose. This Cookie Policy is part of our Across Health Website Privacy Policy.
What are cookies?
A cookie is a small file that is installed in the browser of your computer or mobile device by a website's server when you consult a website or make use of specific applications. It enables the website to recognize your browser and capture and remember certain information. Cookies can be installed by our website or by one of our service providers.
We use cookies to make the interaction between a visitor and our website faster and easier, help the visitor navigate between the different parts of our website and to make a user's experience more efficient and secure. We also use cookies to personalize content and promotional messages, to provide social media features and to analyze the traffic on our website.
Categories of cookies
We categorize our cookies as follows:
Essential Cookies:
We use essential cookies to make our products and services work. These cookies are strictly necessary to enable core functionality such as security, network management, your cookie preferences and accessibility. Without them you wouldn't be able to use basic services. You may disable these by changing your browser settings, but this may affect how the products and services function.
Performance and functionality cookies:
These cookies are used to enhance the performance and functionality of our products and services but are non-essential to their use. However, without these cookies, certain functionalities like videos may become unavailable or you would be required to enter your login details every time you visit as we would not be able to remember that you had logged in previously.
Analytics and customization cookies:
These cookies collect information that is used to help us understand how our products and services are being used or how effective our marketing campaigns are, or to help us customize our products and services for you.
- We use cookies served by Google Analytics to collect limited data directly from end-user browsers to enable us to better understand your use of our products and services. Further information on how Google collects and uses this data can be found at: https://www.google.com/policies/privacy/partners/. You can opt-out of all Google supported analytics on our Website by visiting: https://tools.google.com/dlpage/gaoptout.
- We use Hotjar in order to better understand your use of our products and services, to optimize our products and services and to improve your experience. For further details, please see Hotjar’s privacy policy which can be found here: https://www.hotjar.com/legal/policies/privacy. You can opt-out of all Hotjar supported analytics and data collection on our products and services by visiting: https://www.hotjar.com/legal/compliance/opt-out.
- We use conversion tracking on our website with LinkedIn Insights Tags in order to statistically evaluate the use of our website in order to optimize it. For more information on conversion tracking, see the website of LinkedIn: https://www.linkedin.com.
- We use Leadfeeder to gather insights on the background of end-users based on their LinkedIn profile. For more information on how Leadfeeder collects and uses this data, please go to https://www.leadfeeder.com/privacy/.
- We use Intercom to give every customer a personalized experience on our website across sales, marketing and support. For more information on how Intercom collects and uses this data, please go to https://www.intercom.com/legal/privacy
How to manage cookies?
Browser controls: most browsers will allow you to see what cookies you have and delete them on an individual basis or block cookies from particular or all websites. Be aware that any preference you have set will be lost if you delete all cookies. Please bear in mind that removing or blocking cookies can have an impact on your user experience and parts of this website may no longer be fully accessible.
External web services: we sometimes use external web services on this website to display content within the web pages of this website, for example to display images, show videos or run polls. We cannot prevent these sites, or external domains, from collecting information on your use of this embedded content.
A DETAILED LIST OF COOKIES USED ON THE ACROSS HEALTH WEBSITE
| Name | Provider | Domain | Duration | Type | Category | Description |
| ASP.NET_SessionId | Across Health Session | across.health | Session | 1st party | Necessary | Identity Management Service. Preserves the visitor’s session state across page requests. |
| Cookie-functional | Across Health consent | across.health | 1 year | 1st party | Necessary | To know visitor’s functional cookie preference |
| Cookie-performance | Across Health consent | across.health | 1 year | 1st party | Necessary | To know visitor’s performance cookie preference |
| Cookie-advertisement | Across Health consent | across.health | 1 year | 1st party | Necessary | To know visitor’s advertisement cookie preference |
| __zlcmid | Zendesk Chat | across.health | 1 year | 1st party | Functional | Zopim Live Chat ID, mainly used for Across Health products |
| _uuid | Survey Anyplace | surveyanyplace.com | / | 3rd party | Functional | Survey Anyplace improves data collection with surveys. |
| survey_referrer | Survey Anyplace | surveyanyplace.com | / | 3rd party | Functional | Survey Anyplace improves data collection with surveys. |
| _s | Shopify | across.health | 30 minutes | 1st party | Functional | Shopify is a Canadian e-commerce company headquartered in Ottawa, Ontario. This cookie is associated with Shopify's analytics suite. |
| _shopify_s | Shopify | across.health | 30 minutes | 1st party | Functional | Shopify is a Canadian e-commerce company headquartered in Ottawa, Ontario. This cookie is associated with Shopify's analytics suite. |
| _shopify_y | Shopify | across.health | 7 days | 1st party | Functional | Shopify is a Canadian e-commerce company headquartered in Ottawa, Ontario. This cookie is associated with Shopify's analytics suite. |
| _y | Shopify | across.health | 7 days | 1st party | Functional | Shopify is a Canadian e-commerce company headquartered in Ottawa, Ontario. This cookie is associated with Shopify's analytics suite. |
| facebook.com | Maximum of 2 years | 3rd party | Functional | Enables the Facebook widget and/or button on our website (Facebook Connect, Facebook Social Plugins). Enables online behavioral remarketing advertising campaigns. | ||
| linkedin.com | Maximum of 2 years | 3rd party | Functional | LinkedIn is a business- and employment-oriented social networking service that operates via websites and mobile apps. | ||
| twitter.com | Maximum of 2 years | 3rd party | Functional | Twitter is a real-time information network that connects you to the latest stories, ideas, opinions and news about what you find interesting. Simply find the accounts you find most compelling and follow the conversations. | ||
| _ga | Google Analytics | across.health | 2 years | 1st party | Performance | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
| _gat_UA-29278782-3 | Google Analytics | across.health | 1 minute | 1st party | Performance | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_ |
| _gid | Google Analytics | across.health | 24 hours | 1st party | Performance | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. |
| Collect | Google Analytics | across.health | 24 hours | 1st party | Performance | Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. |
| rc::c | Google recaptcha | google.com | Session | 3rd party | Performance |
This cookie is used to distinguish between humans and bots. |
| _fbp | across.health | Session | 3rd party | Advertisement | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers | |
| Pardot | Pardot | info.across.health | Session | 1st party | Advertisement | A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking. |
| pi_opt_in |
Pardot | across.health | 570 months | 1st party | Advertisement | If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a true or false value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to true, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to false. The visitor cookie is disabled, and the visitor is not tracked. |
| visitor_id |
Pardot | pardot.com | Maximum of 10 years | 3rd party | Advertisement | The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code. |
| visitor_id |
Pardot | pardot.com | Maximum of 10 years | 3rd party | Advertisement | The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information. |
| __gads | DoubleClick | doubleclick.net | Max 18 months | 3rd party | Advertisement | Provides and displays advertising through Google’s Doubleclick service. |
| utma, utmb, utmc, utmv en utmz | Google Analytics Remarketing | across.health | 2 years | 1st party | Advertisement | Websites that are still using the classic Google Analytics tracking code write the __utma, __utmb, __utmc, and __utmz cookies to your browser. If classic GA is configured for user-scope custom variables, the __utmv cookie is also written. Universal Analytics, on the other hand, drops only the _ga cookie into your browser. |
| _hjClosedSurveyInvites | Hotjar | across.health | 365 days | Boolean true/false | Performance | Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. |
| _hjDonePolls | Hotjar | across.health | 365 days | Boolean true/false | Performance | Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. |
| _hjMinimizedPolls | Hotjar | across.health | 365 days | Boolean true/false | Performance | Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. |
| _hjShownFeedbackMessage | Hotjar | across.health | 365 days | Boolean true/false | Performance | Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. |
| _hjSessionTooLarge | Hotjar | across.health | Session | Boolean true/false | Performance | Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. |
| _hjid | Hotjar | across.health | 365 days | UUID | Performance | Hotjar cookie that 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 on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjRecordingLastActivity | Hotjar | across.health | Session | Numerical Value (Timestamp) | Performance | This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records). |
| _hjTLDTest | Hotjar | across.health | Session | Boolean true/false | Performance | When the Hotjar script executes we try to determine the most generic cookie path we should 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 alternatives until it fails. After this check, the cookie is removed. |
| _hjUserAttributesHash | Hotjar | across.health | Session | Hash | Performance | User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. |
| _hjCachedUserAttributes | Hotjar | across.health | Session | JSON | Performance | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. |
| _hjLocalStorageTest | Hotjar | across.health | Under 100ms | Boolean true/false | Performance | This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. |
| _hjIncludedInPageviewSample | Hotjar | across.health | 30 minutes | Boolean true/false | Performance | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit. |
| _hjIncludedInSessionSample | Hotjar | across.health | 30 minutes | Boolean true/false | Performance | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit. |
| _hjAbsoluteSessionInProgress | Hotjar | across.health | 30 minutes | Boolean true/false | Performance | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjFirstSeen | Hotjar | across.health | Session | Boolean true/false | Performance | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
| _hjViewportId | Hotjar | across.health | Session | UUID | Performance | This stores information about the user viewport such as size and dimensions. |
| _hjRecordingEnabled | Hotjar | across.health | Session | Boolean true/false | Performance | This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. |
| _lfa | leadfeeder | across.health | 2 years | 1st party | Performance | Used to collect the behavioral data of all website visitors. This includes; pages viewed, visitor source and time spent on the site. |
| __RequestVerificationToken | Across Health Session | across.health | Session | UUID | Performance | anti-forgery tokens, to make sure that data submitted through form scan be sent, but in such a way that abuse of this data by external people with bad intentions is not possible. In this was only data that comes via this website is added in the database, and not data coming from other sources. |
| _gcl_au | Google Adsense | across.health | Session | UUID | Performance | This cookie is used to store and track conversions. |
| _hjSession | Hotjar | across.health | Session | UUID | Performance | This cookie is used to provide functions across pages. |
| _hjSessionUser | Hotjar | across.health | Session | UUID | Performance | This cookie is used to store a unique user ID. |
| intercom-session-hdie55ah | Intercom | across.health | 7 days | UUID | Performance | Allows users to access their conversations and have data communicated on logged out pages for 1 week. |
Changes to this Cookie Policy
We may update this Cookie Policy from time to time in response to changing legal, technical or business developments. When we update it, we will take appropriate measures to inform you, consistent with the significance of the changes we make.
Contacting us
If you have any questions, comments or concerns about this Cookie Policy, please contact our Data Protection Officer at privacy@a-cross.com.
Our mailing address is:
Across Health NV
Ottergemsesteenweg 808 – Box 332
9000 Gent - Belgium
