Services

Services

Sectors

Home

Cookies Policy

This cookie policy contains important information on our use of cookies or similar technologies on our website. This policy should be read together with our Privacy Policy which sets out how and why we collect, store, use and share personal information generally, as well as your rights in relation to your personal information and details of how to contact us and supervisory authorities in the event you have a complaint.

Our website

This cookie policy only relates to your use of our website, www.thrings.com.

Throughout our website we may link to other websites owned and operated by certain trusted third parties. These other third party websites may also use cookies or similar technologies in accordance with their own separate cookie policies. For privacy information relating to these other third party websites, please consult their cookie policies as appropriate.

Cookies

A cookie is a small text file which is placed on your device (e.g computer, smartphone or other electronic device) when you use our website. We use cookies on our website. These help us recognise you and your device and store some device and store some information about your preferences or past actions.

For example, we may monitor how many times you visit the website, which pages you go to, traffic data, location data and the originating domain name of a user’s internet service provider. This information helps us to build of our users. Some of this data will be aggregated or statistical, which means that we will not be able to identify you individually.

You can set your browser not to accept cookies and the websites below tell you how to remove cookies from your browser. However, some of our website features may not function as a result.

Our use of cookies

We use cookies on this website to;

  • Recognise you whenever you visit this website
  • Obtain information about your preferences and use of our website
  • Carry out research and statistical analysis to help improve our content
  • Make your online experience more efficient and enjoyable.

For further information on cookies generally visit www.aboutcookies.org or www.allaboutcookies.org.

Types of cookies

Broadly there are four types of cookie:

Strictly necessary cookies – these are cookies that are essential to make a website work and enable features that users have specifically asked for. Without use of cookies, these features of the website could not operate.

Performance cookies – these cookies collect anonymous information about users for the purpose of assessing the performance of a website. Common uses include well-known analytics tools such as ‘Google Analytics.’

Functionality cookies – These are cookies that automatically remember choices that users have previously made in order to improve their experience next time they visit a website. For example, where users select their preferred settings and layout.

Targeting and Advertising cookies – These cookies are similar to performance cookies, in that they collect information about users’ behaviour. However, this information is used at individual user level to advertise products and services to users on the basis of the behavioural information collected.

How do we use cookies?

The below table shows what cookies we use and why.

Service Cookie Name Description Expiration Time
Google Analytics gtag.js and analytics.js _ga Used to distinguish users. 2 years
_gid Used to distinguish users. 24 hours
_gat Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. 1 minute
AMP_TOKEN Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. 30 seconds to 1 year
_gac_<property-id> Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out. 90 days
Google Analytics ga.js __utma Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. 2 years from set/update
__utmt Used to throttle request rate. 10 minutes
__utmb Used to determine new sessions/visits. The cookie is created when the javascriptlibrary executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. 30 mins from set/update
__utmc Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmbcookie to determine whether the user was in a new session/visit. End of browser session
__utmz Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. 6 months from set/update
__utmv Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. 2 years from set/update
Google Maps NID, OGPC, APISID These cookies are used by Google to store user preferences and information when viewing pages with Google maps on them. From 1 month to 6 months
Google 1P_JAR, CONSENT, APISD, HSID, S, SIDCC, NID, SID Google uses these cookies, based on recent searches and interactions, to customise ads on Google websites. From 1 month to 20 years
DV, UULE These cookies are used by Google to collect information about how visitors use our site. 1 day
OTZ A cookie used by Google Analytics that provides an aggregate analysis of Website visitors 1 week
PHP System PHPSESSID This cookie contains information that identifies the user and is destroyed when the session expires. Session
Hotjar hjClosedSurveyInvites This cookie is set once a visitor interacts with a Survey invitation modal pop-up. It is used to ensure that the same invite does not re-appear if it has already been shown. 1 Year
_hjDonePolls This cookie is set once a visitor completes a Poll using the Feedback Poll widget. It is used to ensure that the same Poll does not re-appear if it has already been filled in. 1 Year
_hjMinimizedPolls This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. 1 Year
_hjDoneTestersWidgets This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. 1 Year
_hjMinimizedTestersWidgets This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. 1 Year
_hjDoneSurveys This cookie is set once a visitor completes a survey. It is used to only load the survey content if the visitor hasn’t completed the survey yet. 1 Year
_hjIncludedInSample This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate Heatmaps, Funnels, Recordings, etc. 1 Year
_hjShownFeedbackMessage This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show. 1 Year
LinkedIn li_oatml, lidc, bcookie, __utma, VID, ELOQUA, _ga, liap, _guid, _lipt Used by the social networking service, LinkedIn, for tracking the use of embedded services. From Session to 2 years
LinkedIn Ads lang Remembers the user’s selected language version of a website Session
BizoID The BizoID cookie stores a unique LinkedIn user ID.
Note: The LinkedIn user ID does not contain personally identifiable information.
90 days
BizoUserMatchHistory This cookie stores the last time cookie IDs were synced with a given authorized network partner and is part of LinkedIn’s server-to-server data integration solution. 90 days
BizoData The BizoData cookie stores anonymous business demographic profile data for the user. Business demographic data may include anonymous codes for business demographics such as company size, industry, job function, or seniority level, but will not include any personally identifiable information. 90 days
BizographicsOptOut The BizographicsOptOut cookie tracks if the user has opted out of LinkedIn tracking. 90 days
BizoNetworkPartnerIndex Bizographic information generated from authorized LinkedIn Data Provider accounts is shared with authorized third party network partners. This cookie tracks which network partners have received data for a given user. 90 days
UserMatchHistory unclassified 179 days
Facebook pl, c_user, act, fr, wd, xs, presence, sb, lu, spin, dpr These cookies are used for re-targeting, optimisation, reporting and attribution of online adverts From session to 10 years
datr A Facebook cookie that monitors your Facebook account for suspicious behaviour such as failed login attempts or attempts to create spam accounts
Shareaholic c_id, e, lrc_e, lrc_t, p_locc_h, p_locc_user_id_expiry, p_orc_2, shr_br Cookies used to share content and connect with social networks. From session to 2 years
DoubleClick DSID, IDE, _drt_, id, __sonar, _dpm_id.5467 These cookies are used for re-targeting, optimisation, reporting and attribution of online adverts From 2 days to 2 months
Sharethis.com __stid Registers a unique ID that identifies the user’s device for return visits 1 year
pxcelBcnLcy Unclassified Session
pxcelPage_c010 Unclassified 6 days
cookie_notice_accepted This cookie enables you to accept our cookie statement once every year. 1 year
WordPress wp-settings-, wp-settings-time
Used to customize the view of admin interface/main site interface for logged in users.
2 weeks
wordpress_test_cookie Checks if cookies are enabled to provide appropriate user experience. Session
wordpress_logged_in_ Checks whether or not the current visitor is a logged in WordPress.com user. Session
wordpress_sec_ Essential WordPress session management cookies for logged in users. Session
itsec-hb-login-* Set by WP Security Plugin to change the backend login URL for additional security. Session
Adform.net TPC, cid, __qca, adtrc, uid, token These cookies are used to track your usage of the site and ensure that the target adverts you see are relevant to you and your interest From 2 days to 3 months
AppNexus anj, usersync These cookies contain data denoting whether a cookie ID is synced with AppNexus partners. Read more information. 90 days
icu The icu cookie is used to select ads and limit the number of times a user sees a particular ad. 90 days
uuid2 This cookie is used to help deliver ads to people who have previously visited our websites, purchased our products or used our apps and to recommend products and services based on that activity. 90 days
sess It is used by the Platform to test whether a browser is configured to accept cookies from AppNexus. Session
areyouahuman.com ayah_distiltag_sync Unclassified Session
aoc Unclassified 1 year
cpx.to cpSess Unclassified 1 year
Eyeota.net mako_uid, ONPLFTRH Collects data on user visits to the website, such as what pages have been accessed. The registered data is used to categorise the user’s interest and demographic profiles in terms of resales for targeted marketing. 1 year and
Session (ONPLFTRH)
ml314.com tp, u, pi Unclassified From Session to 1 year
owneriq.net lc, bkc, adpq, bsc, nsc, pmc, apq, tapq, oath, cwc, lrc, tpq, rc gguuid, oxc, p2, si, roc, kc, rmuuid, cc Collects anonymous information about products and services that people own, use or have shown interest in. That information is used to provide relevant advertising and content to in ads. From session to 5 years
scorecardresearch.com UID, UIDR The UID cookie is associated with comScore; these are used to get 3rd party measurement of audience size. 2 years
Simpli.fi uid Registers a unique ID that identifies a returning user’s device. The ID is used for targeted ads 1 year
tynt.com pids Unclassified 3 months
__cfduid Used by the content network, Cloudflare, to identify trusted web traffic. 1 year
uid Assigns a user ID that is connected to a registration of the user’s IP address, browser type, browser language, date and time for visiting the website and what search query that took the user to the page. 1 year
Albacross nQ_cookieId, nQ_visitId, _ga, intercom-id-ez7jrn1f Tracking for business IP address lock-up provided by 3rd-party called Albacross for lead classification 2 years to 70 years
HubSpot __hs_opt_out
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies.
2 years
__hs_do_not_track
This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, which still allows anonymized information to be sent to HubSpot.
2 years
__hs_testcookie This cookie is used to test whether the visitor has support for cookies enabled. Session
hs_ab_test This cookie is used to consistently serve visitors the same version of an A/B test page that they’ve seen before. Session
hs_lang_switcher_choice This cookie is used to consistently redirect visitors to the language version of a page in the language they’ve selected on this top-level private domain in the past (if such a language version exists).
<id>_key When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login. The cookie name is unique for each password-protected page.
hs-messages-is-open (TTL 30 minutes) This cookie is used on the visitor UI side so HubSpot can determine/save whether the chat widget is open for future visits. It resets after 30 minutes to re-close the widget after 30 minutes of inactivity 30 minutes
hs-messages-hide-welcome-message (TTL 1 day) When you dismiss the welcome message in your messages tool, a cookie is set to prevent it from appearing again for one day.
__hstc The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). 2 years
hubspotutk This cookie is used for to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts. 10 years
__hssc This cookie keeps track of sessions. This is used to determine if we 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 minutes
__hssrc Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the visitor has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. Session
messagesUtk This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they’re added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookied browser, the messages tool will load your conversation history with that visitor.

Consent

If you continue to use our website, we will assume that you are happy to receive all cookies from our website.

If you would prefer to change your cookie settings, you can do so at any time –see below ‘How to turn off cookies’

How to turn off cookies

If you do not want to accept cookies you can change your browser settings so that cookies are not accepted. If you do this, please be aware that you may lose some of the functionality of this website.

For further information about cookies and how to disable them please go to the Information Commissioner’s webpage on cookies: http://ico.org.uk/for-the-public/online/cookies/.

Changes to this policy

This policy was published on 15.08.2018 and last updated on 15.08.2018.

Latest