Cookie Policy

Effective Date: 07.11.2026

1. What cookies are

Cookies are small files a website stores in your browser. In this policy we also call similar technologies (localStorage, sessionStorage, pixels, third-party scripts) “cookies”.

2. How we use them

Necessary cookies are always on — without them the site cannot remember your choice or stay secure. All others (functional, analytics, marketing) are enabled only after you consent in the banner. Scripts of Google, Meta, Microsoft, LinkedIn and the chat are not loaded until you agree, and not loaded after you refuse. We apply Google Consent Mode v2: all advertising and analytics signals are “denied” by default and consent is passed to Google only after your choice.

3. List of cookies and trackers

Name	Provider	Purpose	Duration	Category
`cookie_consent`	bimpsoft.com	Stores your cookie choice (also in localStorage).	6 months	Necessary
`bimp_utm_*, bimp_referrer (sessionStorage)`	bimpsoft.com	Temporarily keeps UTM tags and the traffic source so they can be attached to your request.	session	Necessary
`bimpLeadSubmitted (localStorage)`	bimpsoft.com	Remembers that a request was already sent, to avoid repeated prompts.	until cleared	Functional
`Krokul (app.krokul.com)`	Krokul	Request form; loaded only after you click “Schedule a demo”. The data you enter is passed to Krokul.	per provider policy	Necessary
`hc_*, helpcrunch (cookies / localStorage)`	HelpCrunch	Support chat: visitor recognition and conversation history.	per provider policy	Functional
`Phonet call-catcher (bimp.phonet.com.ua)`	Phonet	Call-back widget.	per provider policy	Functional
`SmartPopups (static.sppopups.com)`	SmartPopups	Pop-up hints and chat widget.	per provider policy	Functional
`_ga, _ga_*, _gid`	Google (Analytics via Tag Manager)	Visit statistics (pseudonymous identifiers).	up to 2 years	Analytics
`sbjs_*, device-source, device-referrer, sessionExpirationDate`	Google Tag Manager (custom tag)	Traffic-source attribution (where the visitor came from).	up to 1 year	Analytics
`_clck, _clsk, MUID`	Microsoft (Clarity)	Heatmaps and session recordings to improve usability.	up to 1 year	Analytics
`_gcl_au, _gcl_aw, _gac_*`	Google (Ads, Tag Manager)	Measuring Google Ads performance.	up to 90 days	Marketing
`_fbp`	Meta (Pixel)	Ad measurement and remarketing on Meta.	up to 90 days	Marketing
`bcookie, lidc, UserMatchHistory, li_*`	LinkedIn (Insight Tag)	Ad measurement and remarketing on LinkedIn.	up to 1 year	Marketing
`YouTube (youtube-nocookie.com)`	Google (YouTube)	Embedded videos; YouTube cookies appear only after playback starts.	per provider policy	Functional

Durations are indicative, based on providers’ documentation, and may change.

4. How to change or withdraw consent

Click “Cookie settings” at the bottom of any page of the site, knowledge base or blog and change your choice at any time. Withdrawing consent is as easy as giving it; after withdrawal the page reloads and previously set analytics and advertising cookies are deleted. You can also delete or block cookies in your browser settings. Consent is valid for 6 months, after which we ask again. The choice is shared between bimpsoft.com, the knowledge base (/help) and the blog (/blog).

5. Transfers outside the EU / Ukraine

Google, Meta, Microsoft and LinkedIn may process data on servers in the USA and other countries under standard contractual clauses or an adequacy decision. See those companies’ policies for details.

6. Contact

Questions about cookies and personal data: support@bimpsoft.com. General rules of personal data processing are in our Privacy Policy.