Precision AQ Navigator365 Cookie Policy
Effective Date: 15 March 2022
We use cookies on our Navigator365 products and services 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 Navigator365 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 and the use of our Navigator365 products and services.
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 functionality 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 Websites 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.
How to control 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 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 WITHIN THE NAVIGATOR365 PRODUCTS AND SERVICES
| Name | Provider | Domain | Duration | Type | Category | Description | |
| .AspNetCore.Identity.Application | Across Health Session | across.health | Session | 1st party | Essential | This cookie is part of the authentication system. | |
| .AspNetCore.Antiforgery.XXXXX | Across Health Session | across.health | Session | 1st party | Essential | Determines the settings used to create the antiforgery cookies. | |
| _ga | Google Analytics | across.health | 2 years | 1st party | Analytics and customization | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | |
| _gac_UA-XXXXXXX | Google Analytics | across.health | 1 minute | 1st party | Analytics and customization | 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 | Analytics and customization | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | |
| _hjSessionTooLarge | Hotjar | across.health | Session | Boolean true/false | Analytics and customization | 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 | Analytics and customization | 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) | Analytics and customization | 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 | Analytics and customization | 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 | Analytics and customization | 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 | Analytics and customization | 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. | |
| _hjIncludedInPageviewSample | Hotjar | across.health | 30 minutes | Boolean true/false | Analytics and customization | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit. | |
| _hjAbsoluteSessionInProgress | Hotjar | across.health | 30 minutes | Boolean true/false | Analytics and customization | 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 | Analytics and customization | 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 | Analytics and customization | This stores information about the user viewport such as size and dimensions. | |
| _hjRecordingEnabled | Hotjar | across.health | Session | Boolean true/false | Analytics and customization | 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. | |
| intercom-session-hdie55ah | Intercom | across.health | 7 days | UUID | Analytics and customization | 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 privacy@a-cross.com
Our mailing address is:
Precision AQ (BE) NV
Ottergemsesteenweg 808 – Box 332
9000 Gent - Belgium
