Terms & Policies

Learn more about Chainguard policies and our legal documents.

Last Updated: September 23, 2025


This Cookie Policy explains how Chainguard Inc. ("Company", "we", "us", and "our") uses cookies and similar technologies to recognize you when you visit our websites at https://chainguard.dev, https://edu.chainguard.dev, https://images.chainguard.dev, and https://courses.chainguard.dev ("Websites"). It explains what these technologies are and why we use them, as well as your rights to control our use of them.


In some cases, we may use cookies to collect personal information, or that becomes personal information if we combine it with other information. If we do, any personal information collected will be used in accordance with our Privacy Policy.


1. What are cookies?


Cookies are small data files that uniquely identify your browser or device. The cookies are placed on your browser or device when you visit a website. When you return to that website (or visit websites that use the same cookies) these websites recognize the cookies and your browsing device.


Cookies are widely used by website owners in order to make their websites work, or to work more efficiently, as well as to provide reporting information (for example, whether you have visited the website before).


2. Are there different types of cookies?


There are different types of cookies. Cookies set directly by the website owner (in this case, Chainguard, Inc.) are called "first party cookies". Cookies set by parties other than the website owner are called "third party cookies". Third party cookies enable third party features or functionality to be provided on or through the website (e.g. like advertising, interactive content and analytics). The parties that set these third party cookies can recognize your computer both when it visits the website in question and also when it visits certain other websites.


Cookies can remain on your device for different periods of time. Some cookies are "session cookies", meaning that they exist only while your browser is open and are deleted automatically once you close your browser. Other cookies are "permanent cookies", meaning that they survive after your browser is closed. They can be used to recognize your device when you open your browser and browse the Internet again.


3. Why do we use cookies?


We use first and third party cookies for several reasons:


  • Necessary: Some cookies are required for technical reasons in order for our Websites to operate, and we refer to these as "essential" or "strictly necessary" cookies. Without these cookies, we would not be able to provide you with the Websites and services that you have asked for.

  • Functionality: These cookies record information about choices you have made and allow us to provide relevant content and tailor our Websites for you.

  • Analytics: These cookies help us measure traffic and usage data to analyze how our Websites are used in order to provide you with a better user experience and maintain, operate and improve our Websites. They may also be used together with some of the advertising cookies described below to help show more relevant ads across the web and to measure interactions.

  • Advertising: These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same advertisement from continuously reappearing, ensuring that advertisements are properly displayed and, in some cases, selecting advertisements that are based on your interests.


4. What cookies do we use?


The specific types of first and third party cookies served through our Websites and the purposes they perform are described in the tables below. Please be aware that the cookies we use may depend on the Website you are visiting, the features you are using and the device, browser or operating system you are using.



This Cookie Policy explains how Chainguard Inc. ("Company", "we", "us", and "our") uses cookies and similar technologies to recognize you when you visit our websites at https://chainguard.dev, ("Websites"). It explains what these technologies are and why we use them, as well as your rights to control our use of them.In some cases we may use cookies to collect personal information, or that becomes personal information if we combine it with other information.


4.1. First party cookies (set by Chainguard)


Cookie Name

Purpose

Retention Period

Class

locale

Used to save preferred language and location of the user.

Session

Necessary

theme

Used to store the user's theme preference on the Website.

Session

Functionality

language

Used to store language preferences.

1 day

Functionality

ASP.Net_SessionId_Guest

Used to store by Microsoft .NET Framework identifier to deliver the web pages to visitors.

Session

Functionality

features

Used to enable new features released by Chainguard.

1 month

Functionality

AWSALBTG

Used for Amazon Web Services Elastic Load Balancing functionality for routing requests on the server.

7 days

Analytics


4.2. Cookies set by HubSpot (our Website hosting platform)


Cookie Name

Purpose

Retention Period

Class

_cfuvid

Used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.

Session

Functionality

hubspotutk

Used for user authentication.

6 months

Functionality

cb_user_id

Used to identify the individual user across browsing sessions.

1 year

Functionality

cb_group_id

Used to store the preference settings of a user within a group for Website's content or functionality.

1 year

Functionality

__hssc

Used for website analytics.

30 minutes

Analytics

__hssrc

Used for website analytics.

Session

Analytics

__hstc

Used for website analytics.

6 months

Analytics

cb_anonymous_id

Used to understand logged out user behavior on the website.

1 year

Analytics


4.3. Cookies set by Google Analytics and AdSense


Cookie Name

Purpose

Retention Period

Class

_ga_VSVKH3HF80 and _ga_EPP534WMYM

Used by Google Analytics to persist session state.

1 year 1 month

Analytics

_ga

Used by Google Analytics to distinguish users.

1 year 1 month

Analytics

_gcl_au

Used by Google AdSense for experimenting with advertisement efficiency across websites.

3 months

Advertising


4.4. Cookies set by LinkedIn


Cookie Name

Purpose

Retention Period

Class

li_gc

Used to store guest consent to the use of cookies for non- essential purposes.

6 months

Necessary

_ga

Used for sharing the content of the Websites via social media.

1 year

Advertising

lidc

Used for proper functioning of the Websites.

1 day

Advertising


4.5. Cookies set by Cloudflare


Cookie Name

Purpose

Retention Period

Class

_cf_bm

Used to identify and mitigate automated traffic to protect the Websites from bad bots.

30 minutes

Necessary


4.6. Cookies set by 6Sense


Cookie Name

Purpose

Retention Period

Class

_gd_session

Used to manage user sessions to ensure user interactions are recognized across various web requests.

4 hours

Analytics

_gd_visitor

Used to track visitor interactions with the Website for behavior analytics purposes.

1 year 1 month

Analytics


4.7. Cookies set by Datadog


Cookie Name

Purpose

Retention Period

Class

_dd_s

Used to store session data such as visitor interactions, preferences selected and error management.

15 minutes

Analytics


4.8. Cookies set by Amplitude


Cookie Name

Purpose

Retention Period

Class

AMP_MKTG_fb16da97e5 and AMP_fb16da97e5

Used to identify a user to the Amplitude analytics platform.

1 year

Analytics


4.9. Cookies set by Skilljar on courses.chainguard.dev only


Cookie Name

Purpose

Retention Period

Class

sj_sessionid

Used to maintain logged-in sessions between page views.

2 weeks

Necessary

sj_csrftoken

Used to validate any POST request from the user’s browser.

2 weeks

Necessary

OptanonConsent and OptanonAlertBoxClosed

Used by OneTrust to remember cookie management preferences.

2 weeks

Necessary

auth_xxxx_yyyy

Used to control access to course content.

2 weeks

Necessary

auth_content_wp

Used for authentication.

2 weeks

Necessary

Cloudfront-Policy, Cloudfront-Signature and Cloudfront-Key-Pair-Id

Used by Cloudfront CDN to control access to course content.

2 weeks

Necessary

login-endpoint

Used to store dashboard single sign-on (SSO) configuration used to log in (if you logged in via SSO).

2 weeks

Necessary

cookietest

Used to determine what features are available on Chainguard's training website.

2 weeks

Functionality

sj_lp

Used to store language preferences.

2 weeks

Functionality

dashboardUiState

Used to stores state information about the dashboard (e.g. to show or collapse the navigation bar on subsequent page views).

2 weeks

Functionality

sj_dbgid

Used to store the obfuscated id of the organization under which the user was last logged in.

2 weeks

Functionality

sj_dbu

Used to differentiate between prospects and existing customers for marketing purposes.

2 weeks

Analytics

_gat_skilljarTracker

Used in connection with Google Analytics.

2 weeks

Analytics


4.10. Cookies set by Splash


Cookie Name

Purpose

Retention Period

Class

OptanonAlertBoxClosed and OptanonConsent

Used by OneTrust to remember cookie management preferences.

1 year

Necessary

devspl

Used for tracking platform behavior.

1 year

Analytics

fs_lua

Used by FullStory to store the time of the last user activity.

session based (21 days)

Analytics

fs_uid

FullStory unique user identifier.

1 year

Analytics

iter_id

Used to track user session activity or engagement.

2 years

Analytics


4.11. Cookies set by Unify


Cookie Name

Purpose

Retention Period

Class

__unify

Unique identifier to associate visits with contact profiles.

1 year

Analytics

unify_session

Temporary session- based identifier for visit context.

1 year

Analytics


4.12. Cookies set by Reddit


Cookie Name

Purpose

Retention Period

Class

_rdt_uuid

Unique visitor identifier for Reddit advertising and tracking purposes.

90 days

Advertising


4.13. Cookies set by Qualified


Cookie Name

Purpose

Retention Period

Class

_rdt_uuid

Cloudflare bot management cookie that helps distinguish between humans and bots to protect the site from malicious traffic.

30 minutes

Strictly Necessary

__cflb

Cloudflare load balancing cookie that ensures requests are routed consistently to the same backend server for session continuity.

24 hours

Strictly Necessary

__q_state_h1BO9h0C beFm817m

Qualified session state cookie that tracks visitor identity and chat session progress across pages.

Session (deleted when browser closes)

Functionality

OptanonAlertBoxClos ed

OneTrust cookie that stores whether the user has closed the cookie consent banner so it does not reappear.

1 year

Strictly Necessary

OptanonConsent

OneTrust cookie that stores the user’s consent preferences for cookie categories to ensure compliance with GDPR/CCPA.

1 year

Strictly Necessary

qualified_session

Tracks active Qualified chat sessions with a visitor to maintain continuity during browsing.

Session (deleted when browser closes)

Functionality

team_saml_entity_id

Used in Qualified for SAML- based authentication to remember identity provider configuration.

Session or short- term (until logout)

Strictly Necessary


4.14. Cookies set by Reo.Dev


Cookie Name

Purpose

Retention Period

Class

_reb2bignorerepeats

Used by the RB2B integration in Reo.Dev to prevent duplicating or repeating notifications / visits; e.g. helps ignore repeat events or signals once they’ve been logged.

90 days

Advertising

_reb2bli

Used to store a unique identifier for a visitor (anonymous) for RB2B linkage/integration; helps associate behavior and segmenting.



_reb2bsha

A hashed value (SHA) for a

user or event, for deduplication or matching across sessions in the RB2B integration.



_reb2btd

“Time delta” or “time data” for RB2B; maybe tracks how long between certain events / visits.



_reb2butk

“RB2B user token” — a token to identify the user across different visit interactions once de-anonymized.



cb_anonymous_id

“Customer/consumer/busines s” or “context buffer” etc. Used to store an anonymous identifier for a visitor/user, so that their actions can be tied together across sessions without knowing their identity.

12 months

Analytics

cb_group_id

To group users into cohorts (groups) — used for segmentation, experimentation, tracking behavior of groups.

6 months

Analytics

cb_user_id

Identifies a specific user (once known/authenticated or when an ID is assigned) for personalization, linking activity across sessions.

6 months

Analytics

mp_e54657e02c1d7c 89ed388da56c0f327c _mixpanel

This is a Mixpanel cookie. It stores a “distinct_id” or identifier for a user in Mixpanel, so their behavior can be tracked across time (analytics). Also used to store super properties in some cases (things about the user that persist, like referrer, device type, etc.).

1 year

Analytics


5. What about other tracking technologies, like web beacons?


Cookies are not the only way to recognize or track visitors to a website. We may use other, similar technologies from time to time, like web beacons (sometimes called "tracking pixels" or "clear gifs"). These are tiny graphics files that contain a unique identifier that enable us to recognize when someone has visited our Websites or opened an e-mail including them. This allows us, for example, to monitor the traffic patterns of users from one page within a website to another, to deliver or communicate with cookies, to understand whether you have come to the website from an online advertisement displayed on a third-party website, to improve site performance, and to measure the success of e-mail marketing campaigns. In many instances, these technologies are reliant on cookies to function properly, and so declining cookies will impair their functioning.


6. Do you use Flash cookies or Local Shared Objects?


Websites may also use so-called "Flash Cookies" (also known as Local Shared Objects or "LSOs") to, among other things, collect and store information about your use of our services, fraud prevention and for other site operations. If you do not want Flash Cookies stored on your computer, you can adjust the settings of your Flash player to block Flash Cookies storage using the tools contained in the Website Storage Settings Panel. You can also control Flash Cookies by going to the Global Storage Settings Panel and following the instructions (which may include instructions that explain, for example, how to delete existing Flash Cookies (referred to "information" on the Macromedia site), how to prevent Flash LSOs from being placed on your computer without your being asked, and (for Flash Player 8 and later) how to block Flash Cookies that are not being delivered by the operator of the page you are on at the time). Please note that setting the Flash Player to restrict or limit acceptance of Flash Cookies may reduce or impede the functionality of some Flash applications, including, potentially, Flash applications used in connection with our services or online content.


7. Do you serve targeted advertising?


Third parties may serve cookies on your computer or mobile device to serve advertising through our Websites. These companies may use information about your visits to this and other websites in order to provide relevant advertisements about goods and services that you may be interested in. They may also employ technology that is used to measure the effectiveness of advertisements. This can be accomplished by them using cookies or web beacons to collect information about your visits to our Websites and other sites in order to provide relevant advertisements about goods and services of potential interest to you. The information collected through this process does not enable us or them to identify your name, contact details or other details that directly identify you unless you choose to provide these.


8. Cookie settings


Some of these cookies are essential and we cannot provide our Websites to you without them, but there are others that can be turned off. Please note that turning off certain cookies will disable some of the features available to you through our Websites. We cannot guarantee that your experience on our Websites will be as good as it could otherwise be.


Cookie preferences


To change your cookie preferences, please click the "Cookie Settings" in the cookie banner on our Website or the Cookie icon in the website footer to control the cookies set on our Websites.


Browser settings


You can also change your preferences by changing the settings in your browser. For more information on how to manage the most popular browsers, please see below:



Third party cookies


In addition to managing cookies in your browser settings, you can also opt out of certain third party cookies. For example, we use Google Analytics and Google Tag Manager to help us understand how users engage with our Websites, compile reports and improve our services. The reports disclose website trends without identifying individual users. For more information on Google Tag Manager, see here. For more information on Google Analytics, see here.


You can opt out of Google Analytics without affecting how you visit our Websites. To opt out from being tracked by Google Analytics, see here.


9. How often will you update this Cookie Policy?


We may update this Cookie Policy from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal or regulatory reasons. Please therefore re-visit this Cookie Policy regularly to stay informed about our use of cookies and related technologies. The date at the top of this Cookie Policy indicates when it was last updated.


10. Where can I get further information?


If you have any questions about our use of cookies or other technologies, please email us at privacy-contact@chainguard.dev or by post to:


Chainguard, Inc. 810 7th St S Kirkland, WA 98033 United States