Worker.ai
Product
Resources
Company
Get started

Cookie Policy

How Worker uses cookies and similar technologies.

This page is maintained by Worker to explain how we use cookies. It is not independent legal advice or a certification of compliance.

Effective Date: November 9, 2026

What changed: On November 9, 2026, worker.ai added PostHog for analytics and for replays of some visits. Sections 2 to 4 describe it and what it keeps in your browser. On November 6, 2026, Section 3 added what the LinkedIn Insight Tag records on its own and the hashed copy of your email address it sends LinkedIn when you request access, and Section 4 added its li_giant cookie and the two entries it keeps in your browser’s local storage (li_adsId and li_hem). On November 5, 2026, worker.ai added the LinkedIn Insight Tag and LinkedIn’s Conversions API (Sections 2 to 5) and two entries in your browser’s local storage: the sources of your visits, and a hashed copy of your email address after you request access. On November 4, 2026, worker.ai added the Meta Pixel and Meta’s Conversions API, with Meta’s automatic event detection and automatic advanced matching turned on. Sections 2 to 5 describe them, the cookies they set, and how to opt out. Later the same day, worker.ai’s own server began sending these events to Meta as well and setting Meta’s _fbp and _fbc cookies itself. On November 3, 2026, worker.ai added Google Analytics, with Google signals and advertising features turned on.

This Cookie Policy explains how Icos AI Inc., the company behind Worker (“Worker”, “we”, “our”, or “us”), uses cookies and similar technologies on our websites, including worker.ai. Read it together with our Privacy Policy, which explains how we handle personal data more generally.

1. What cookies are

Cookies are small text files placed on your device when you visit a website. They make a site work, remember your choices, and help us understand how the site is used. In this policy we use cookies to refer collectively to cookies and to similar technologies such as pixels, tags, local storage, and software development kits.

2. The categories we use

  1. Strictly necessary cookies. Required for the site and the application to function, including signing you in, keeping your session secure, remembering your privacy choices, and protecting against fraud and abuse. These cannot be switched off in our systems. You can block them in your browser, but parts of the site will stop working.
  2. Functional cookies. Remember choices you make, such as language or region, so the site behaves the way you expect.
  3. Analytics cookies. Let us count visits, see which pages are used, and understand how visitors move through the site, so that we can improve it and measure our marketing.
  4. Advertising cookies. Let Google, Meta and LinkedIn use data about your visit for advertising and ad measurement, on their own services and on other sites.

On worker.ai we use strictly necessary cookies set by our hosting provider, Cloudflare; settings stored in your browser; Google Analytics, which sets analytics cookies and, unless you opt out, supports Google’s advertising features; PostHog, which sets analytics cookies; and, unless you opt out, the Meta Pixel and the LinkedIn Insight Tag, which set advertising cookies. Section 4 lists each one. Visitors in the European Economic Area, the United Kingdom and Switzerland are asked first: until they accept, Google Analytics sets no cookies on their device and Google receives only cookieless signals, which it uses to estimate visits, and PostHog, the Meta Pixel and the LinkedIn Insight Tag do not load at all.

3. Google, PostHog, Meta and LinkedIn

We use Google Analytics to see how people find and use worker.ai: pages viewed, clicks, scrolling, film plays, questions opened, form use, approximate location, device and browser, and the campaign that brought you. We do not send Google your email address or anything you type into a form.

Google signals and Google’s advertising features are turned on. If you are signed in to Google and have allowed ad personalization, Google can link data about your visit to your Google account and use it for advertising and ad measurement, on its own services and on other sites, using its own cookies as well as ours. Under the laws of California and some other states, this can count as selling or sharing personal data, or as targeted advertising. You can opt out at any time: use “Do not sell or share my personal information” at the bottom of every page, or turn on Global Privacy Control in your browser. Google explains how it uses this data at policies.google.com/technologies/partner-sites.

We also use PostHog, from PostHog, Inc., to see how people use worker.ai: pages viewed, clicks, scrolling, film plays, questions opened, form use, approximate location, device and browser, and the campaign that brought you. PostHog also records replays of some visits. A replay shows how the page looked and where you moved, clicked and scrolled. Anything you type is hidden before it leaves your browser, and so is the company name you type into the demo. We do not send PostHog your email address. When you request access, PostHog receives the ID of the request, not your address. PostHog works only for us and does not use this data for advertising. In the European Economic Area, the United Kingdom and Switzerland it loads only after you accept. It never loads after you turn analytics off with “Do not sell or share my personal information” at the bottom of every page, and what it kept in your browser is removed then.

We also use the Meta Pixel and Meta’s Conversions API, from Meta Platforms, Inc. The Conversions API sends Meta a copy of the same events from a server, including worker.ai’s own server, so that Meta receives them even when a browser blocks the Pixel. They tell Meta about your visit so that we can measure our ads on Facebook, Instagram, Messenger, WhatsApp, Threads and Meta’s Audience Network, and show ads to people who have visited worker.ai. Meta receives the pages you view, clicks, scrolling, film plays, form events (such as a request for access, or an address we decline), how long a page stays open, device and browser data, your IP address, a random visitor ID that we create in your browser, and a hashed (scrambled) copy of any email address you enter in our forms, including addresses we decline. We never send Meta your email address in readable form, anything else you type, or the company name you type into the demo.

When worker.ai’s server sends an event to Meta, it adds your IP address, your browser’s user agent and your approximate location (country, region, city and postal code, which our hosting provider, Cloudflare, estimates from your IP address). It sends the location, the visitor ID and any email address only as hashed values. Our server sends nothing where the Pixel would not load.

Meta’s automatic event detection and automatic advanced matching are turned on. That means Meta’s code can also record button clicks and page details on its own, and can read the email field in our forms to send Meta a hashed copy. Meta can match this data to a Facebook or Instagram account and use it for advertising and ad measurement, on its own services and on other sites, under its own privacy policy at facebook.com/privacy/policy. Under the laws of California and some other states, this can count as selling or sharing personal data, or as targeted advertising.

The Meta Pixel loads only where advertising is allowed. In the European Economic Area, the United Kingdom and Switzerland it loads only after you accept. It does not load when your browser sends Global Privacy Control or after you turn advertising off. To opt out, use “Do not sell or share my personal information” at the bottom of every page, or turn on Global Privacy Control in your browser. You can also set how Meta uses data for ads at facebook.com/adpreferences, and opt out of interest-based ads from many companies at optout.aboutads.info.

We also use the LinkedIn Insight Tag and LinkedIn’s Conversions API, from LinkedIn Corporation, to measure our ads on LinkedIn and to show ads to people who have visited worker.ai. The Insight Tag loads under the same rules as the Meta Pixel. It records the address and title of the pages you visit (including any campaign tags and ad click identifiers in the address), how long you stay and what you click on, including the visible text and attributes of the link or button (with any email address or phone number in that text masked), and when you request access it sends LinkedIn a hashed copy of your email address, computed in your browser before it is sent. It does not see your answer to our question about how you heard about Worker. Turning advertising off stops it at once, also on pages you already have open, and removes the identifiers it stored for worker.ai in your browser. When you request access, worker.ai’s server also sends LinkedIn a hashed copy of your email address and, if you arrived from a LinkedIn ad, LinkedIn’s click identifier. LinkedIn can match this data to a LinkedIn member account and use it for advertising and ad measurement under its own privacy policy. LinkedIn also uses its own cookies on LinkedIn’s domains, which LinkedIn’s Cookie Policy describes. Under the laws of California and some other states, this can count as selling or sharing personal data, or as targeted advertising, and the same opt-out applies.

4. The cookies we set

These are the cookies that can be set when you visit worker.ai. We keep this list up to date as the site changes. You can also request a copy at privacy@worker.ai.

Cookie Provider Purpose Duration
__cf_bm Cloudflare Strictly necessary. Helps tell people apart from automated traffic, to protect the site against bots and abuse 30 minutes of inactivity
cf_clearance Cloudflare Strictly necessary. Set only when you pass a security check, so you are not asked again 30 minutes
_ga Google Analytics. Tells visitors apart, so we can count visits and returning visitors 2 years
_ga_29M5QWSXYJ Google Analytics. Keeps track of your current visit for Google Analytics 2 years
_gcl_* Google Advertising. Set only when you arrive from a Google ad and advertising is allowed, to connect your visit to that ad 90 days
ph_phc_*_posthog PostHog Analytics. A random visitor ID and visit ID for PostHog, with the page and the referring site of your first visit, so we can count visits and returning visitors and see how the site is used. Kept as a cookie and in your browser’s local storage. Set only where analytics is allowed, and removed when you turn analytics off 1 year
ph_phc_*_posthog_cpm PostHog Analytics. Lets PostHog keep its cookie and its local storage entry in step. Set and removed with the cookie above 1 year
ph_phc_* (session storage) PostHog Analytics. In your browser’s session storage: keeps the pages of one visit in one tab together, with the campaign tags and the referring site the visit arrived with. Set only where analytics is allowed, and removed when you turn analytics off Until you close the tab
_fbp Meta Platforms Advertising. Set by the Meta Pixel, and by worker.ai’s server, only where advertising is allowed. Tells browsers apart so Meta can measure our ads and show ads to people who have visited worker.ai 90 days
_fbc Meta Platforms Advertising. Set by the Meta Pixel, and by worker.ai’s server, only when you arrive from a link in a Meta ad and advertising is allowed, to connect your visit to that ad 90 days
li_fat_id LinkedIn Advertising. Set by the LinkedIn Insight Tag only when you arrive from a LinkedIn ad and advertising is allowed, to connect your visit to that ad 30 days
li_giant LinkedIn Advertising. Set by the LinkedIn Insight Tag only when you arrive from a LinkedIn ad link that carries this identifier and advertising is allowed, to connect your visit to that ad 7 days
wk-consent Worker Strictly necessary. Remembers your cookie and privacy choices, in your browser’s local storage Until you clear it
wk-film-subtitles Worker Functional. Remembers whether you turned on subtitles for the film, in your browser’s local storage Until you clear it
wk_internal Worker Analytics. Set only in our own team’s browsers, in local storage, so their visits are marked as internal and left out of our reports Until cleared
wk_vid Worker Advertising measurement. A random visitor ID in your browser’s local storage, sent to Meta with each event so Meta can recognize repeat visits. Set only where advertising is allowed, and removed when you turn advertising off Until you clear it
wk_src Worker Analytics and ad measurement. In your browser’s local storage: the campaign tags, referring site and first page of your first and your latest visit that came from a link, sent to our own database only if you request access. Ad click identifiers are kept only where advertising is allowed. Set only where analytics is allowed 90 days
wk_em Worker Advertising measurement. In your browser’s local storage, after you request access: a hashed copy of your email address, sent to Meta with your later events from this browser. Set only where advertising is allowed, and removed when you turn advertising off 90 days
li_adsId LinkedIn Advertising measurement. In your browser’s local storage (or, where local storage is unavailable, a cookie that lasts 180 days): a random ID the LinkedIn Insight Tag uses to recognize this browser’s visits. Set only where advertising is allowed, and removed when you turn advertising off Until you clear it
li_hem LinkedIn Advertising measurement. In your browser’s local storage, after you request access: the hashed copy of your email address that the LinkedIn Insight Tag computed, sent to LinkedIn with the tag’s later signals from this browser. Set only where advertising is allowed, and removed when you turn advertising off 90 days

5. How to control cookies

  1. Your choices. Visitors in the European Economic Area, the United Kingdom and Switzerland see a banner and can accept or decline before any analytics or advertising cookie is set. Everyone can turn analytics and advertising on or off at any time with “Do not sell or share my personal information” at the bottom of every page. Your choice is stored in your browser and applies at once.
  2. Your browser. Most browsers let you refuse or delete cookies. Doing so may affect how the site works.
  3. Global Privacy Control. We honor the Global Privacy Control signal. If your browser or extension sends a GPC signal, we turn off Google’s advertising features, do not load the Meta Pixel or the LinkedIn Insight Tag and do not send your visit to Meta or LinkedIn from our server, which opts you out of the sale or sharing of your personal data and of targeted advertising, and the choices panel shows that the signal was honored. We do this everywhere, not only where the law requires it.
  4. Google. You can also install Google’s opt-out add-on for your browser at tools.google.com/dlpage/gaoptout, and control ad personalization in your Google account.
  5. Meta. You can set how Meta uses data for ads at facebook.com/adpreferences, and opt out of interest-based ads from many companies at optout.aboutads.info.
  6. LinkedIn. You can set how LinkedIn uses data for ads in your LinkedIn account settings, under Advertising data.

6. Do Not Track

There is no common industry standard for how to respond to the browser “Do Not Track” signal, and we do not respond to it. We do honor Global Privacy Control, as stated in Section 5.

We may update this policy to reflect changes in technology, law, or our practices. Material changes will be posted on this page with a new effective date, and where the law requires it we will ask for your consent again.

8. Contact

Questions about our use of cookies: privacy@worker.ai or by phone (415) 907-4709

Icos AI Inc., 757 Third Avenue, 24th Floor, New York, NY 10017, United States