hackworth :

Website Cookie Policy

Our websites ("our site" or "our sites") sometimes use cookies and similar technologies, such as pixels, tags, and scripts, to help distinguish you from other visitors to our websites, to track which pages on our sites you visit, etc. For our purposes, we generally refer to all of these technologies collectively as cookies, regardless of whether they actually store cookies in your browser. This Cookie Policy applies to any of our websites where we use such cookies. (Note that our applications and services use a different cookie policy than our websites, and you should refer to those specific applications or services for details.)

By continuing to visit or use our websites, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy, though in most cases, you will need to explicitly opt into the setting of cookies in order for them to be stored in your browser. In other words, most of the cookies we use are subject to your explicit consent before they are enabled.

We may update this cookie policy at any time as our needs and our business change.

The policy was last updated on August 30, 2022.

Though we generally refer to both actual cookies and all cookie-related technologies as just cookies, there are some technical differences between the technologies. What follows is a brief discussion of the specific technologies that we use on our websites:

  • Cookies are small pieces of data that are stored by your browser on your device. When you visit or otherwise interact with a website, the website can request that your browser a) create a new cookie or load an existing one, b) read or write data out of or into that cookie, and c) associate the cookie with a domain name. When the cookie's domain name is the same as that of the website that sets it, that is called a first-party cookie. When the cookie's domain name is different from that of the website that sets it, that is called a third-party cookie.

    Note that cookies may be set either just for the current visit or browser session (session cookies), or for a longer period of time (persistent cookies). Despite the name, persistent cookies may have an expiration date (set by the site that created them), after which your browser will delete them.

  • Pixels are very small images that are used by third-party tracking sites to determine when a browser has visited a particular webpage, or when a visitor has activated a script by opting into a particular cookie or related technology. When the browser tries to render the image, the third-party site that hosts the image can determine that the visitor has interacted with the originating site in some way.

  • Tags or scripts are JavaScript programs that run in the browser. These programs can communicate with the originating site, or even a third-party site, to load data from a database, run another script, or even create content in the browser window dynamically (such as in a browser-based game).

    Some third parties that don't technically set cookies or use pixels can use tags to communicate with their servers to collect browsing data (personal or otherwise), so because they can communicate with a third party, we consider these to be cookies for our purposes.

Why we use cookies

We do not rely on selling or showing advertisements on our websites as a source of income for our business. Therefore, none of the cookies we use are designed to track you across the web, or to build a general-purpose advertising profile so that we can show you relevant third-party ads. The cookies we set are generally used for the following purposes:

  • For authentication purposes; for example, so that you can securely log into your account on our webistes.

  • For security purposes; for example, to keep your account safe and to help us detect malicious activity and violations of our Website Terms of Use.

  • For keeping track of your preferences; for example, whether you have opted out of certain types of cookies or direct marketing.

  • For measuring the effectiveness of our advertising campaigns; for example, when we run an ad on a third-party site for our products and services, and you click on that ad, you are taken to our website, and we use these cookies to record that the ad was effective. Note that these campaign-related cookies do not reveal your personal data to us; the ad effectiveness data is aggregated by our third-party advertising partners, and they do not share your personal data with us.

  • For tracking which pages you visit on our websites; for example, to help us determine which of our products and services you may be interested in, if you have opted into marketing communications.

  • For analytics and research; for example, to build anonymized, aggregated profiles of visitors to our websites, such as from which rough geographic locations they visit, how many times a particular page is visited, etc. Note that none of the analytics cookies we use collect any personal data.

The cookie table below lists each specific cookie or similar technology that we currently use on our websites, including its purpose.

Some of the cookies we use on our site are necessary for the site to function (e.g., authentication cookies). We do not provide a way to opt out of these cookies, though you can generally use a content blocker in your browser to do so, if you wish. (Please note that if you do so, the site may not function.)

However, for most of the other cookies we use, you are opted out by default. The first time you visit our site (and anytime thereafter when you clear your browser cookies), you will be prompted by a cookie banner whether you would like to opt into these optional cookies. This ensures that these cookies are not set, and will not collect any data about your use of our site — personal or otherwise — unless you have given your explicit consent for them to do so.

Cookies and third parties

When cookies that we set collect personal data about you, or your use of our site, we do not share that data with any third party, except for with select third-party data processors, who process your data according to our specific instructions, and never for their own benefit. For more information about our commitment to your privacy with respect to third parties, see our Website Privacy Policy.

Also note that, when we do share the data we collect with a third-party data processor, we will call attention to that sharing in the cookie table below, including a link to the specific data processor we use, and how we process that data, in our data processor registry.

Cookie table

Cookies set by LinkedIn

Note that all cookies on our site that are set by LinkedIn are set only through your explicit consent.

LinkedIn's own documentation on these cookies is here.

Cookie name Domain Purpose Expiration
lang .ads.linkedin.com To remember the visitor's language setting on LinkedIn Session
liap .linkedin.com Denotes the logged-in status of a LinkedIn member 1 year
lang .linkedin.com To remember the visitor's language setting on LinkedIn Session
lidc .linkedin.com To facilitate data center selection 24 hours
li_mc .linkedin.com Cache of a LinkedIn member's consent for client-side enforcement 6 months
AnalyticsSyncHistory .linkedin.com Time sync with the lms_analytics cookie 30 days
lms_analytics .linkedin.com Used to identify LinkedIn members for analytics 30 days
UserMatchHistory linkedin.com LinkedIn Ads ID syncing 30 days
bcookie .linkedin.com Uniquely identify devices accessing LinkedIn to detect abuse 1 year
li_gc .linkedin.com Store consent of guests regarding the use of cookies 6 months

Cookies set by HubSpot

Note that all cookies on our site that are set by HubSpot are set only through your explicit consent.

HubSpot's own documentation on these cookies is here.

Cookie name Domain Purpose Expiration
__hssrc hackworth.io Keeps track of browser restarts for HubSpot Session
__hssc hackworth.io Keeps track of sessions for HubSpot 30 minutes
__hstc hackworth.io Main cookie for tracking visitors for HubSpot 6 months
hubspotutk hackworth.io Visitor ID used on form submission and when deduplicating HubSpot contacts 6 months
__cf_bm .hubspot.com Bot detection for HubSpot's CDN 30 minutes