Aragon Photonics Labs. uses cookies on their web sites in order to collect statistical information on the browsing effected or to know user preferences. 

The cookie policy of Aragon Photonics Labs. is subject to current community and Spanish regulations concerning the treatment of personal data and the protection of privacy in the sector of electronic communications. 

What are cookies? 

A cookie is a small text file which is sent to your computer by the web server so that the website can remember some information about your browsing activity on the website. The cookie will collect information relating to your use of our sites, anonymously. 

What kind of cookies does Aragon Photonics Labs. use? 

Statistical analysis cookiesthat allow us to quantify the number of visitors and a statistical analysis about users of our services. This enables us to study the web site navigation and improve the supply of products or services we offer 

Which cookies are we using? 

CookieDescriptionDurationType
_gaThis cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site’s analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.2 yearsAnalytics
_gidThis cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form.1 dayAnalytics
_gatThis cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites.1 minutePerformance
__cfduidThe cookie is set by CloudFare. The cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.4 weeksNecessary
__cfduidThe cookie is set by CloudFare. The cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.4 weeksNecessary
__hstcThis cookie is set by Hubspot and is used for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).1 yearAnalytics
hubspotutkThis cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts.1 yearAnalytics
__hssrcThis cookie is set by Hubspot. According to their documentation, whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.Necessary
__hsscThis cookie is set by HubSpot. The purpose of the cookie is to keep track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.30 minutesFunctional
__cfduidThe cookie is set by CloudFare. The cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.4 weeksNecessary
_gat_UA-38609494-1This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.1 minutePerformance
NIDThis cookie is used to a profile based on user’s interest and display personalized ads to the users.6 monthsAdvertisement
__cfduidThe cookie is set by CloudFare. The cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.4 weeksNecessary
_hjClosedSurveyInvitesHotjar cookie that is set once a visitor 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.365 days
_hjDonePollsHotjar cookie that is set once a visitor 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.365 days
_hjMinimizedPollsHotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.365 days
_hjShownFeedbackMessageHotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.365 days
_hjidHotjar 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.365 days
_hjRecordingLastActivityThis should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).Session
_hjTLDTestWhen 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.Session
_hjUserAttributesHashUser 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.Session
_hjCachedUserAttributesThis 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.Session
_hjLocalStorageTestThis 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.Under 100ms
_hjIncludedInPageviewSampleThis cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s pageview limit.30 minutes
_hjIncludedInSessionSampleThis cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site’s daily session limit.30 minutes
_hjAbsoluteSessionInProgressThis cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.30 Minutes

 

Disabling and removing “cookies” 

You can deactivate the use of cookies at any time by changing your browser’s configuration parameters: 

For theconfiguration of Internet Explorer cookies 

For theconfiguration of Firefox cookies 

For theconfiguration of Google Chrome cookies 

For theconfiguration of Safari cookies 

 

Please note that disabling “cookies” does not prevent the display of the pages of this website or interfere with navigation.