Cookie Policy

 

About cookies

Cookies are small text files that your browser stores when you visit some websites and will be sent back to the website each time you request a page. Most websites use cookies in order to improve a user’s experience by allowing that website to ‘remember’ you. This can be for the duration of your visit (using a ‘session cookie’) or for repeat visits (using a ‘persistent cookie’).

Spoke Technologies Ltd use cookies to help manage our website, make our website easier to use and support the provision of relevant information and functionality. This is done to improve your visitor experience, as well as provide us with information about how our website is used so that we can make sure it is as relevant and as accurate as possible. By opting into using cookies on our website you agree to the use of cookies as described in this Cookie Policy. You can disable cookies and certain cookies may be set as soon as you visit our website. Also you can manage or remove cookies using your internet browser settings – see below.

Cookies in use

Squarespace - Website analytics
Used to measure site performance (over time and by segmentation of users)
Name Description Duration
SS_ANALYTICS_ID To identify unique visitors to our website 3 months
crumb Prevents cross-site request forgery (CSRF). Session duration
ss_cid Identifies unique visitors and tracks a visitor’s sessions on a site 2 years
ss_cpvisit Identifies unique visitors and tracks a visitor’s sessions on a site 2 years
ss_cvisit Identifies unique visitors and tracks a visitor’s sessions on a site 30 minutes
ss_cvr Identifies unique visitors and tracks a visitor’s sessions on a site 2 years
ss_cvt Identifies unique visitors and tracks a visitor’s sessions on a site 30 minutes
ss_cookieAllowed Remembers if a visitor agreed to placing Analytics cookies on their browser if a site is restricting the placement of cookies 30 days
Google Analytics - Website analytics
Used to measure site performance (over time and by segmentation of users)
Name Description Duration
_ga Used to distinguish users. 2 years
_gid Used to distinguish users. 24 hours
_gat Used to throttle request rate. 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 Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more. 90 days
Recruitee - Applicant tracking system
Used to allow candidates to apply to jobs
Name Description Duration
recruitee_careers Store information about the source (For example LinkedIn) through which the candidate came in Session duration
allow_cookies Store whether careers site visitor has clicked "accept" on the cookie notice 1 year
Hotjar - Website analytics
Used to measure the usage of experimental pages
Name Description Duration
_hjClosedSurveyInvites Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. 365 days
_hjDonePolls Hotjar cookie. 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. 365 days
_hjMinimizedPolls Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. 365 days
_hjDoneTestersWidgets Hotjar cookie. 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. 365 days
_hjIncludedInSample Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels. 365 days
_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. 365 days
_hjid Hotjar cookie. This cookie 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
_hjRecordingLastActivity This should be found in sessionStorage (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
hjTLDTest 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. Session
_hjUserAttributesHash 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. Session
_hjCachedUserAttributes 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.

Session
_hjLocalStorageTest 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 immediately after creating it so the expected storage time is under 100ms.

N/A
_hjptid This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.

Session
_hjAbsoluteSessionInProgress The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.

30 minutes

Managing cookies