Cookie Policy
Effective date: January 1, 2026
1. Who we are
Yampa ("Yampa", "we", "us") operates the Yampa website and the Yampa platform, an AI agent management platform used by our customers to build, deploy and supervise customer-care agents.
This notice explains which cookies and similar technologies we use, why we use them, how long they last and how you can control them. For how we handle personal data more generally, see our Privacy Policy. Questions go to security@yampa.ai.
2. What cookies are
Cookies are small text files that a website stores on your device through your browser. They let a site remember you between page loads or visits: whether you are signed in, which preferences you set, or how the site is performing.
We also use browser storage (localStorage, sessionStorage) for some preferences. It behaves like a cookie in that it is stored on your device, but it is never sent to our servers automatically. Where it matters, we list it below.
3. How we classify cookies
| Category | Purpose | Consent |
|---|---|---|
| Strictly necessary | Required to sign you in, keep your session secure and deliver the page you asked for. The service does not work without them. | Not required |
| Functional | Remember interface preferences you set (panel sizes, table columns, sidebar state). | Not required; you can clear them at any time |
| Performance and monitoring | Measure whether the console loads and behaves correctly, and detect errors. Used for service quality and security, not for advertising. | See section 7 |
| Analytics (website only) | Understand how visitors find and use yampa.ai. | Required; managed through the website consent banner |
| Marketing and advertising (website only) | Attribute visits and form submissions to our campaigns, identify the companies visiting our website so our sales team can follow up, and measure the performance of our ads on Meta and LinkedIn. Never used on the console, the API or the widget. | Required; managed through the website consent banner |
4. Cookies on the Yampa console (console.yampa.ai, api.yampa.ai)
The console is an authenticated business application. All cookies below are first-party cookies set by Yampa. The console itself sets no analytics, marketing or advertising cookies. If you have accepted marketing cookies on yampa.ai, some of them (section 5) are set on the parent domain .yampa.ai and your browser will also send them to console.yampa.ai and api.yampa.ai; the console does not read or use them.
4.1 Strictly necessary
| Cookie | Set by | Purpose | Lifetime | Attributes |
|---|---|---|---|---|
wos_session | api.yampa.ai | Sealed authentication session issued after you sign in through WorkOS. Identifies your account and organization on each request. | 30 days, refreshed while you use the console; removed on sign-out or when the refresh token is rejected | HttpOnly, Secure, SameSite=Lax, domain .yampa.ai |
en_post_login_redirect | console server | Remembers the page you were trying to open so we can send you back there after sign-in. | 10 minutes | HttpOnly, Secure, SameSite=Lax |
en_toast | console server | Carries a one-time status message (for example "Saved") across a redirect. | Browser session | HttpOnly, Secure, SameSite=Lax |
en_role_preview | console server | Lets Yampa staff preview the console as a given customer role for support purposes. Only set for Yampa staff accounts. | 1 day | HttpOnly, Secure, SameSite=Lax |
4.2 Functional (interface preferences)
These are written by the console in your browser and are not read by our servers. They contain interface state only, no personal data.
| Cookie | Purpose | Lifetime |
|---|---|---|
sidebar_main | Whether the main sidebar is expanded or collapsed | 7 days |
en_panel_layouts, en_panel_states | Sizes and open/closed state of resizable panels | 30 days |
en_visual_builder_node_display_mode | Display mode of nodes in the agent builder | 30 days |
en_datatable_view_state, en_datatable_column_state (and per-table variants en_datatable_column_state.*) | Column visibility, order and saved view of data tables | 30 days |
en_download_conversations_columns, en_download_task_run_columns | Columns selected for CSV exports | 30 days |
en_last_ipa_session | Identifier of your last in-platform assistant session so it can be resumed | 90 days |
en_role_preview_widget | Position and state of the role-preview widget (Yampa staff only) | 365 days |
4.3 Performance and monitoring
| Technology | Provider | Purpose | Lifetime | Notes |
|---|---|---|---|---|
_dd_s cookie | Datadog (EU region, datadoghq.eu) | Groups page views into a session so we can measure load times and detect front-end faults. | Session: expires after 15 minutes of inactivity, 4 hours maximum | Session replay is disabled. Form inputs are masked before any data leaves the browser (mask-user-input). Data is stored in the EU. |
sentryReplaySession (sessionStorage) | Sentry (EU ingest) | Capture the sequence of interface events leading up to an error so we can fix it. | Browser tab session | Recorded for 10% of sessions and for sessions where an error occurs. Associated with your user id and email so we can follow up on account-specific faults. |
5. Cookies on the Yampa website (yampa.ai) and documentation (docs.yampa.ai)
When you first visit yampa.ai, a consent banner (Consent Pro by Finsweet) asks you to choose between Essential, Analytics, Marketing and Personalization cookies. Only essential cookies are set until you make a choice. Analytics and marketing tags are loaded after you accept them; Google tags run in Google Consent Mode and remain cookieless until you accept.
5.1 Essential and functional
| Cookie or storage | Provider | Purpose | Lifetime |
|---|---|---|---|
| Consent preference cookie | Consent Pro (Finsweet) | Store the choices you made in the consent banner so we do not ask again and only load what you accepted | Up to 13 months |
wglang | Weglot | Remember the language you selected (English or French) | 1 year |
__hs_opt_out, __hs_do_not_track | HubSpot | Remember that you declined HubSpot tracking | 6 months |
| Cloudflare Turnstile | Cloudflare | Protect our forms against bots. Runs a challenge in the page and sets no persistent cookie. | n/a |
5.2 Analytics (after consent)
| Cookie or storage | Provider | Purpose | Lifetime |
|---|---|---|---|
__hstc, hubspotutk | HubSpot (EU data centre) | Recognise returning visitors and attribute form submissions to a visitor record in our CRM | 6 months |
__hssc, __hssrc | HubSpot (EU data centre) | Session tracking for the visit | 30 minutes / browser session |
lastExternalReferrer, lastExternalReferrerTime (localStorage) | HubSpot (EU data centre) | Remember which external site sent you to us, for attribution | Until cleared |
_ga, _ga_* | Google Analytics (via Google Tag Manager) | Measure page views and usage of the website | 13 months |
5.3 Marketing and advertising (after consent)
| Cookie or storage | Provider | Purpose | Lifetime |
|---|---|---|---|
_fbp, _fbc | Meta Pixel | Measure the performance of our campaigns on Facebook and Instagram and reach visitors of our website on those platforms | 90 days |
li_fat_id (first-party) and LinkedIn's own cookies on linkedin.com (bcookie, lidc, li_gc, UserMatchHistory, AnalyticsSyncHistory) | LinkedIn Insight Tag | Measure the performance of our LinkedIn campaigns and reach visitors of our website on LinkedIn | 30 days (li_fat_id); up to 2 years for LinkedIn's own cookies, per LinkedIn's cookie policy |
_gcl_au | Google Ads (via Google Tag Manager) | Attribute conversions to Google Ads campaigns | 90 days |
claydar_device_id, claydar_session, radar_sn_* (sessionStorage) | Clay | Identify the company a visitor belongs to, from network and browsing signals, so our sales team can prioritise follow-up. No personal identification of the individual. | Browser tab session |
The Yampa chat widget is also embedded on yampa.ai; the storage it uses is described in section 6.
5.4 Documentation (docs.yampa.ai)
The documentation site is hosted by Mintlify and uses Cloudflare Web Analytics, which measures page views without cookies or any identifier stored on your device. It sets no cookies of its own.
6. Embedded chat widget (widget.yampa.ai)
When one of our customers embeds a Yampa agent on their own website or app (and on yampa.ai itself), the widget runs in an iframe served from widget.yampa.ai. It sets no cookies and loads no analytics or advertising tag. To let a conversation continue across page loads, it keeps the following entries in the browser's localStorage, scoped to the widget.yampa.ai origin:
| Key | Purpose | Lifetime |
|---|---|---|
yampa_widget_conversation_id | Identifier of the current conversation, generated by Yampa | 24 hours from the last save; older entries are deleted and not restored |
yampa_widget_conversation_timestamp | Time of the last save, used to enforce the 24-hour limit | 24 hours |
yampa_widget_pending_agent_message | A message the host page asked the agent to display before the conversation existed, so it can be shown after a reload | 24 hours, and only while it matches the current conversation |
All three entries are removed when the conversation is ended or refreshed, or when the conversation no longer exists on our servers. In the iOS and Android SDKs the same values are kept in the app's local storage on the device. These entries are strictly necessary for the widget to work and are not shared with third parties.
Our customer is the controller of the data collected through the widget and is responsible for the cookie notice on their own site.
7. Legal basis and consent
- Strictly necessary and functional cookies are exempt from consent under the ePrivacy rules because they are needed to deliver the service you requested or to store preferences you set.
- Performance and monitoring on the console is used only to operate, secure and improve the service you contracted for. It does not track you across other sites. You can opt out at any time (section 8).
- Analytics, marketing and advertising cookies on the website are only set after you accept the corresponding category in the consent banner. You can withdraw consent at any time from the same banner (section 8).
8. How to control cookies
- Website: use the "Cookie settings" link in the footer to reopen the consent banner and change your choices by category at any time. Declining a category stops the corresponding tags from loading on the next page view; cookies already set can be deleted from your browser.
- Console: functional cookies can be deleted from your browser without affecting your ability to sign in. To opt out of performance monitoring for your account, contact support@yampa.ai.
- Browser: all major browsers let you block or delete cookies. Blocking strictly necessary cookies will prevent you from signing in to the console.
9. Changes to this notice
We update this notice when we add, remove or change cookies. The version and effective date at the top tell you when it was last changed. Material changes are announced on the website or in the console.
10. Contact
- Data Protection Officer: Baptiste Saintot, security@yampa.ai
- Support: support@yampa.ai