Cookie policy
This policy explains which cookies and similar technologies (such as the browser's local storage) fibady.com uses, what for, and how you can manage them. For how we handle personal data in general, see the Privacy Policy.
1. What cookies are
Cookies are small files (or browser storage entries) that a website stores on your device to remember information across visits or during a single session. Some are essential for the site to work; others are only used if you give us your consent.
2. How you manage your consent
Non-essential cookies are grouped into three independent categories — analytics & attribution, advertising & remarketing and meeting scheduling — which you can accept or reject separately. The first time you visit the site, we show a banner where you can accept all, reject all, or tap "Customize" to choose category by category.
You can change your decision at any time from the link at the bottom of any page, or by clearing your browser's site data to see the banner again. You can also block cookies from your browser settings, though this may affect some parts of the site (for example, meeting scheduling, if you reject that category).
3. Fibady's own cookies and storage (necessary)
These don't require consent because they are essential for the site to work or to remember your own consent decision.
| Name | Type | Purpose | Duration |
|---|---|---|---|
fibady_consent_v4 | Local storage (localStorage) | Remembers whether you accepted or rejected non-essential cookies, so we don't ask again on every visit. | Until you clear this site's data in your browser |
fibady_lang | First-party cookie | Remembers your chosen language so you don't have to select it again. | 1 year |
fibady_chat_session, fibady_chat_agent, fibady_chat_lead | Session storage (sessionStorage) | Keep the chat widget's state (conversation id, the name of the agent assisting you, your contact details) while the tab is open. | Cleared when you close the tab |
fibady_utms | Session storage (sessionStorage) | Stores the campaign parameters you arrived with (utm_* and, if you came from a Google ad, the gclid click identifier) to attribute your demo request to that campaign. The gclid is only sent to HubSpot if you accept marketing cookies. | Deleted when you close the tab |
fibady_booking | Session storage (sessionStorage) | Temporarily stores your scheduled meeting details to show the confirmation page. | Cleared when you close the tab |
fibady_booking_tracked | Session storage (sessionStorage) | Marks that your booking has already been counted as a conversion, so it isn't counted again if you reload the confirmation page. Stores no personal data. | Cleared when you close the tab |
4. Analytics cookies and storage ("Analytics & attribution" category — require your consent)
These activate if you accept the "Analytics & attribution" category. They are set by HubSpot when we load its attribution script, which we use to measure where visits come from and associate contact-form submissions. Here are the main cookies, per HubSpot's official documentation:
| Name | Purpose (per HubSpot) | Duration |
|---|---|---|
hubspotutk | Identifies your visit so a form submission can be attributed and to avoid duplicating your contact in the CRM. | 6 months |
__hstc | HubSpot's main visitor-tracking cookie (domain, identifier, timestamps and session number). | 6 months |
__hssc | Controls when a new session starts for __hstc purposes. | 30 minutes |
__hssrc | Detects whether you restarted your browser. | End of session |
The same category also loads Apollo.io's website visitor tracker, which tells us which companies visit the site (based on the IP address) for our sales work. It sets no cookies on fibady.com: it stores an anonymous identifier and a queue of browsing events in your browser's local storage.
| Name | Purpose | Duration |
|---|---|---|
apolloAnonId | Anonymous browser identifier used to group your visits. | Until you clear site data |
…_canTrack, …_eventQueue | Whether tracking is allowed, and browsing events waiting to be sent to Apollo. | Until you clear site data |
The same category also enables Google Analytics 4, which tells us in aggregate how the site is used (pages viewed, approximate traffic source, device type). It runs on the same Google tag (gtag.js) as Google Ads, in Google Consent Mode v2: until you accept this category, analytics storage stays denied, Google Analytics sets no cookies and only sends Google cookieless pings without identifiers. According to Google's documentation, Google Analytics 4 does not store or log IP addresses. For Google Analytics, Google acts as our data processor (Google Ads Data Processing Terms). These are its cookies, per Google's documentation:
| Name | Purpose (per Google) | Duration |
|---|---|---|
_ga | Distinguishes users (first-party cookie on fibady.com). | 2 years |
_ga_<container-id> | Keeps session state (first-party cookie on fibady.com). | 2 years |
5. Advertising and remarketing cookies ("Advertising & remarketing" category — require your consent)
On every page we load Google's tag (gtag.js) for Google Ads in Google Consent Mode v2. Until you accept the "Advertising & remarketing (Google Ads, LinkedIn)" category, the tag runs with ad storage, ad user data and ad personalization denied: it sets no advertising cookies and only sends Google cookieless pings without identifiers, which Google uses to model our campaigns' conversions in aggregate. If you accept it, Google sets the cookies below to measure which Google ads lead to a demo booking and to show ads to people who have already visited the site (remarketing). Google decides how it uses that data as an independent controller (Google Ads Controller-Controller Data Protection Terms), under its privacy policy and its advertising page. Here are the main cookies, per Google's documentation (the list may not be exhaustive):
| Name | Domain | Purpose (per Google) | Duration |
|---|---|---|---|
_gcl_au | fibady.com | Stores click and conversion information to measure Google Ads conversions. | 90 days |
_gcl_aw | fibady.com | Stores the ad click identifier (gclid) when you arrive from a Google ad. | 90 days |
_gcl_gs | fibady.com | Ad click information used for conversion measurement. | 90 days |
IDE | doubleclick.net | Google advertising and remarketing. | 13 months |
test_cookie | doubleclick.net | Checks whether your browser accepts cookies. | 15 minutes |
The same category also loads the LinkedIn Insight Tag, LinkedIn's script that we use to measure the results of our LinkedIn campaigns (conversions), to show ads to people who have already visited the site, and to see aggregated, anonymous data about the professional profile of our visitors. The script is only requested from LinkedIn once you accept this category; if you later withdraw consent, the already-loaded script stays active until you reload the page. LinkedIn sets these cookies on its own domain and decides how it uses that data, under its privacy policy and its cookie policy. Here are the Insight Tag's main cookies, per LinkedIn's official cookie table:
| Name | Purpose (per LinkedIn) | Duration |
|---|---|---|
li_sugr | Makes a probabilistic match of a user's identity. | 90 days |
bcookie | Browser identifier used to detect abuse on the platform and for diagnostic purposes. | 1 year |
lidc | Data center selection. | 24 hours |
UserMatchHistory | LinkedIn Ads ID syncing. | 30 days |
AnalyticsSyncHistory | Stores when a sync with the lms_analytics cookie took place. | 30 days |
lms_ads, lms_analytics | Identify LinkedIn members off LinkedIn, for advertising and for analytics. | 30 days |
li_fat_id | Indirect member identifier for conversion tracking, retargeting and analytics. | 30 days |
li_giant | Indirect identifier for groups of members, used for conversion tracking. | 7 days |
6. Meeting-scheduling cookies ("Scheduling" category — require your consent)
These activate if you accept the "Scheduling" category, only on the demo-booking page, when we show HubSpot Meetings' embedded calendar. HubSpot doesn't publish a separate list of cookies specific to that widget (beyond the analytics ones in section 4, which it may reuse), so we don't assert a closed list here.
HubSpot may set additional technical cookies of its own (for example, for anti-bot protection or infrastructure) as part of either of these two components. For the full, always up-to-date list of HubSpot cookies, see their official article .
7. More about these providers
You can see which providers process data on Fibady's behalf, and under which agreement, on the Subprocessors page, which lists Google for Google Analytics, where it acts as our processor. For Google Ads, by contrast, Google is an independent controller, as is LinkedIn: that's why they aren't listed there for advertising, and their role is explained in the Privacy Policy.
8. Changes to this policy
We may update this page if we change providers or if HubSpot, Apollo, Google or LinkedIn change what they store. The last-updated date is shown above.