Cookie Declaration
Cookies are small text files a website stores in your browser. hypefactors.com uses one that is necessary for the site to work, and others for statistics and marketing only if you allow them. Some of these come from the services we use (Google, HubSpot, Leadfeeder and LinkedIn), which also handle the data under their own privacy policies.
Below are all of them, grouped by purpose, with who sets them and how long they are kept. You can change or withdraw your consent at any time, here or with “Cookie settings” at the bottom of every page. A category you switch off stops loading straight away, and its cookies on hypefactors.com are removed. How we process personal data is described in our privacy policy.
Your choice
Necessary
Make the site work and remember your cookie choice. They can’t be switched off.
| Cookie | Purpose | Duration |
|---|---|---|
| site_ | Remembers your cookie choice (which categories you allowed, and when), so the site doesn’t ask again on every page. | 12 months |
Statistics
Show us how the site is used, so we can improve it (Google Analytics).
| Cookie | Purpose | Duration |
|---|---|---|
| _ | A random ID that tells visitors apart, so we can count visits and see how the site is used. | 2 years |
| _ | Keeps track of the current visit (session). | 2 years |
Marketing
Let us measure our marketing, link visits to enquiries and recognise companies that visit us (HubSpot, Leadfeeder, LinkedIn, Google). Also needed for the chat.
| Cookie | Purpose | Duration |
|---|---|---|
| _ | HubSpot’s main visitor cookie: an ID and the times of your first, last and current visit, so visits can be linked to a contact who fills in a form. | 6 months |
| hubspotutkHubSpot | Your visitor ID. Sent with a form, so the enquiry is linked to your earlier visits. | 6 months |
| _ | Keeps track of the current visit (session). | 30 minutes |
| _ | Tells whether the browser was restarted, to count a new visit. | Session |
| messages | Recognises visitors who use the chat, so a conversation can be continued. | 6 months |
| _ | Details of the tracking events HubSpot collects during your visit. | Until deleted |
| hublytics_ | Holds tracking events until they are sent to HubSpot. | Until deleted |
| _ | A random ID for your browser, so visits from the same company (recognised from its IP address) can be grouped. | 1 year |
| _ | A copy of the same ID. | 1 year |
| _ | When the ID in local storage expires. | 1 year |
| _ | An ID used to measure which Google ads lead to visits and enquiries. | 90 days |
| li_ | An indirect ID of a LinkedIn member who arrived from a LinkedIn ad, to measure conversions and build ad audiences. | 30 days |
| li_ | An indirect ID for groups of LinkedIn members, to measure conversions. | 7 days |
| bcookieLinkedIn, set on linkedin.com | Identifies the browser, to detect abuse of LinkedIn. | 1 year |
| lidcLinkedIn, set on linkedin.com | Chooses the LinkedIn data centre that answers. | 24 hours |
| li_ | Used to make a probable match of a visitor’s identity, for advertising. | 90 days |
| User | Syncs LinkedIn Ads IDs. | 30 days |
| Analytics | When the last sync with LinkedIn’s analytics cookie took place. | 30 days |