We use cookies and similar technologies on floe.so and our marketing properties for:
- Essential cookies: required for website functionality and security, including remembering your cookie choices.
- Analytics and session replay: set by PostHog, our product analytics provider, to identify a returning browser across pages and to link the events and session replay described in Section 2 into a single session.
- Company identification: set by Factors (Slashbit Inc., doing business as Factors.ai, which processes data mainly in the United States) on our behalf, to see which companies visit floe.so as described in Section 2. It sets a first-party cookie on floe.so,
_fuid, which recognises a returning browser for two years from its last visit, and keeps related entries in your browser’s local storage. Like the LinkedIn Insight Tag, it never runs on the demo links we send to prospects. - Marketing: set by HubSpot (HubSpot, Inc., which stores this data in the United States) on our behalf, as described in Section 2. It sets first-party cookies on floe.so:
hubspotutk, which recognises a returning browser for six months and is what links your visits to you once you click a link in one of our emails or give us your email address in a form; __hstc, which records your visits for six months; and __hssc and __hssrc, which mark the current session. While a form you submitted is waiting to be sent, HubSpot keeps a copy in your browser’s local storage. Like the LinkedIn Insight Tag and Factors, HubSpot never runs on the demo links we send to prospects. Our website agent also reads hubspotutk, as described in Section 2. - Advertising: the LinkedIn Insight Tag, provided by LinkedIn (part of Microsoft). It tells LinkedIn which pages of floe.so you visit and when you book a call through our booking calendar, so that we can measure our LinkedIn campaigns, see aggregated reports about the professions and industries of our visitors, and show our ads on LinkedIn to people who have visited floe.so. LinkedIn recognises its members through its own cookies. It sets a first-party cookie on floe.so, such as
li_fat_id, which records the LinkedIn ad you clicked to reach us, and uses cookies on linkedin.com, such as bcookie, lidc, UserMatchHistory and AnalyticsSyncHistory. We never load the tag on demo links we send to prospects (addresses under floe.so/d/ and floe.so/demo/), because those addresses identify a specific demo.
Consent. Analytics, company identification, marketing and advertising are separate choices in our cookie banner. Where we detect that you are in the EEA, the UK, or Switzerland, we set none of them until you allow it, and declining leaves only essential cookies in place. Elsewhere, all four run by default and the same banner lets you switch off any of them; if your browser sends a Global Privacy Control signal, company identification, marketing and advertising stay off unless you switch them on. You can change your choices at any time using the Cookie preferences link in the footer of our website; withdrawing is as easy as consenting, and takes effect immediately.
Switching off company identification stops Factors and deletes the cookie and stored data it set on floe.so.
Switching off marketing stops HubSpot and deletes the HubSpot cookies set on floe.so, and any form copy it was still waiting to send. Visits HubSpot has already linked to you stay with your contact record until you ask us to delete them or we delete that contact, and what our website agent already looked up stays with your conversation for the period in Section 10.
Switching off advertising stops the LinkedIn Insight Tag and deletes the LinkedIn cookies set on floe.so. Cookies that LinkedIn sets on its own domain, linkedin.com, can only be removed through your browser settings or LinkedIn’s own settings; you can also opt out of LinkedIn’s ad targeting in your LinkedIn advertising preferences.
Region detection uses your browser’s time zone, which is an approximation — a VPN or travel can place you in the wrong group. Whichever group you are placed in, the banner always offers a decline for each category, and declining always stops the cookies in that category.
Booking calendar. The calendar on floe.so/book-demo is provided by Cal.com. When you book a call, Cal.com receives the details you enter and the campaign information that brought you to our site (for example UTM parameters), so that we know which campaign led to the call.
The Floe agent widget deployed on customer websites may use essential session identifiers to maintain conversation state, and analytics identifiers to generate engagement reports for the customer. The widget does not set third-party advertising cookies. Customers control deployment and configuration on their websites.
You can also block or delete cookies through your browser settings. Blocking cookies may affect site functionality.