Skip to main content
이 문서는 영어 원문으로만 제공돼요.
Effective date: August 6, 2026 · Last updated: August 6, 2026
This page identifies the individual cookies and similar technologies used on the VESSL websites and the VESSL Cloud service. It is the Cookie List referred to in our Cookie Policy, which defines the categories used below. Providers that process personal data on VESSL’s behalf are listed in the Sub-processor list. Scope. vessl.ai (including vessl.ai/blog), cloud.vessl.ai, and docs.cloud.vessl.ai. Consent. Only the strictly necessary technologies are used without your consent. Everything in the Functional, Performance, and Targeting categories is set only after you accept that category in our cookie banner or cookie settings, and stops being written when you withdraw that consent. See Section 8. Sharing across sites. Most cookies below are set on the parent domain .vessl.ai, so the same cookie is readable on all three sites and a single consent choice applies to all of them. Cookies whose host is shown without a leading dot are scoped to that one site.

​
1. Strictly necessary

Signing in with Google also causes Google to set its own account and security cookies on accounts.google.com and other Google domains. Those cookies are set by Google as an independent controller of your Google account, not by VESSL, and are governed by the Google Privacy Policy. The in-app support chat (Pylon) is also treated as strictly necessary: it is a support channel you have asked us to provide when signed in. It sets no cookie; its browser-storage keys are listed in Section 6.

​
2. Functional

​
3. Performance

​
4. Targeting

​
5. Cookies set on providers’ own domains

The technologies below run on VESSL sites but write their cookies to the provider’s own domain, so they are not visible under vessl.ai. They follow the same consent categories as the sections above.

​
6. Local and session storage

The Cookie Policy also covers browser storage. The keys below are written to localStorage or sessionStorage; they are not transmitted with HTTP requests and are removed when you clear site data. They follow the same consent categories as the cookies above. The first-party interface-state keys below are implementation details and their names may change between releases.

​
7. Notes on providers

Cloudflare. No Cloudflare cookie is set on any vessl.ai domain. The __cf_bm cookies in Section 5 are set on HubSpot’s and LinkedIn’s own domains by those providers’ bot protection. Our hosting providers serve some of our sites through Cloudflare’s network, which sets no cookie on our domains. Pylon. The in-app support chat loads only for signed-in users of VESSL Cloud. It sets no cookie; it writes the browser-storage keys listed in Section 6 and holds the chat conversation inside its own widget on widget.usepylon.com. Arcade. Some documentation pages embed an interactive product demo provided by Arcade. The demo runs from demo.arcade.software and sets its own anonymous visitor identifier there; it loads only on the pages that contain a demo. Stripe. The two __stripe_* cookies in Section 1 are set on cloud.vessl.ai by Stripe’s payment library when a payment form loads, and are used for fraud prevention. Where a payment is completed on Stripe’s own hosted checkout pages, any further cookies are set by Stripe on Stripe’s domains and are governed by the Stripe Privacy Policy. Each provider publishes its own description of the cookies it sets, and some offer their own opt-out. Those pages are maintained by the provider, not by VESSL.

​
8. Managing your choices

  • Cookie banner. On your first visit you can choose Accept all, Essential only, or Settings. Nothing outside Section 1 is set until you choose.
  • Cookie settings. The Settings view lets you accept or reject Functional, Performance, and Targeting individually. Strictly necessary technologies cannot be switched off.
  • Manage cookies. You can reopen the settings at any time from the Manage cookies link on each site, and withdraw a consent you gave earlier. When you withdraw consent we stop setting cookies in that category and delete the ones we can reach from the browser.
  • Re-asking. Your choices are remembered for 6 months, after which we ask again. We also ask again if we materially change the categories or this notice.
  • Global Privacy Control. If your browser sends a recognized GPC signal, we treat it as an opt-out and leave the optional categories off unless you turn them on yourself.
  • Browser settings and provider opt-outs. See Cookie Policy, Section 4.

​
9. Change log

Questions about this list: privacy@vessl.ai.