This is Suntera Global's website cookie policy.
This policy was last updated on 25th June 2020.
A 'cookie' is a small piece of data sent from a website and stored on your computer by your web browser. Cookies are designed to help websites remember useful information, such as previously entered form data or your preferences, or to record your browsing activity on that site, such as clicking particular buttons, logging in, or recording page visits.
This website stores cookies on your computer. These cookies collect information about how you interact with our website and allow us to remember you. We use this information to improve and customise your browsing experience and for analytics and metrics about our visitors both on this website and other media. We strongly believe in balancing the need to provide a useful browsing experience with protecting your privacy. You can read more about our wider approach to privacy in our Privacy Notice.
This page explains several types of cookies that are on this site, as well as how to turn them on or off:
You can revoke your cookie consent for this website only at any time.
If you have any questions or concerns about our cookie policy please contact dataprotection@suntera.com.
__hs_opt_out
hs_ab_test
<id>_key
hs-messages-is-open
hs-messages-hide-welcome-message
__hsmem
hs-membership-csrf
hs_langswitcher_choice
__cfduid
__cfruid
__hstc
hubspotutk
__hssc
__hssrc
messagesUtk
.AspNetCore.Antiforgery
Prevents Cross-Site Request Forgery (XSRF/CSRF) attacks in ASP.NET Core
.AspNetCore.Cookies
When a user authenticates using their username and password (and 2FA), they're issued a token, containing an authentication ticket that can be used for authentication and authorization. The token is stored as a cookie that accompanies every request the client makes. Generating and validating this cookie is performed by the ASP.NET Core Cookie Authentication Middleware.
.AspNetCore.Session
ASP.NET Core maintains session state by giving the client a cookie that contains the session ID, which is sent to the server with each request. The server uses the session ID to fetch the session data. Because the session cookie is specific to the browser, you cannot share sessions across browsers. Session cookies are deleted only when the browser session ends. If a cookie is received for an expired session, a new session that uses the same session cookie is created.