Cookie policy
Last updated:
About this policy
This policy explains how Jagelski & Partners OÜ uses cookies and similar technologies on this website, what categories are used, how long they last, who sets them, and how you can change your choices at any time. It applies to every visitor to this website. It supplements the Privacy policy, which explains how the firm processes personal data more generally, and the Terms of service, which govern your use of this site.
What cookies are
A cookie is a small text file that a website places on your device when you visit. Cookies allow the site to recognise your device on later visits, remember basic choices, and gather statistics about how the site is used. Similar technologies, such as pixels, local storage, and tags, work in comparable ways and are treated as cookies for the purposes of this policy.
Cookies set by this website are first-party cookies. Cookies set by a third party whose content or service is loaded on this site are third-party cookies. Cookies that expire when the browser is closed are session cookies. Cookies that remain on the device for a defined period are persistent cookies.
Why we use cookies
We use cookies to run this site and to measure how it is used. We do not use cookies to build behavioural profiles for selling to third parties, and we do not run advertising on this website. The preference centre carries a marketing category, and where marketing cookies are used they serve only to measure the performance of our own advertising and to support audience matching with the platforms we advertise on.
Your choices, and the legal basis
Strictly necessary storage supports the service you request and is exempt from consent only where the law provides that exemption. Related personal-data processing relies on our legitimate interest in operating and securing the service, or another applicable basis described in the Privacy policy. Necessary functions cannot be switched off in our preference centre.
In every region, the consent settings initially deny analytics and marketing cookies until you make a choice. A Global Privacy Control signal refuses marketing storage. Cookieless requests and the separate browser-storage entries described below may still occur.
You can change or withdraw your consent at any time by clicking the Cookie preferences link in the site footer, which re-opens the preference centre. Withdrawing consent is as easy as giving it. Withdrawal does not affect the lawfulness of any processing carried out before withdrawal.
Where you have a Global Privacy Control signal enabled in your browser, we treat that signal as a refusal of marketing cookies. You can still grant analytics cookies if you choose to.
Categories of cookies we use
This site uses three categories of cookies. The exact cookies in each category, including names and durations, are listed in the table further below.
Necessary cookies and storage support page delivery, security, cookie choices, and requested interactive features such as Emma. They may contain preference, session, or security identifiers and can involve personal data. The chat history kept in your browser holds whatever you choose to write, including any name or contact details you give; its storage is described in the table below and its use and retention in the Privacy policy. They are not switched off by the optional-cookie controls.
Analytics cookies help us measure visits and interactions and improve content and usability. Google Analytics uses visitor and session identifiers. Microsoft Clarity records page interactions, including clicks, scrolling, navigation, and session replays, and can group activity by visitor or session. Analytics cookies are placed only after you allow them. Google Analytics event and user data is configured for 14-month retention; aggregate reports may be retained longer. Microsoft describes 30-day retention for ordinary playback data and nine months for heatmaps and labelled or favourited sessions. These periods are separate from cookie lifetimes.
Marketing cookies measure advertising and support audience matching. Our jag_attr_first and jag_attr_last cookies record first and recent referral or campaign details, including advertising click identifiers. Microsoft Advertising receives visit, device, identifier, and interaction data through its conversion tag and processes it under its own privacy statement. Our custom measurement events send selected categories and counts rather than enquiry text or contact fields. Page and referral URLs may also be processed, so do not put personal information into URL parameters. Your choice also controls the advertising-consent signals sent to Google. Marketing settings and Global Privacy Control operate as described above.
Refusing or withdrawing marketing consent stops our marketing-cookie writes, removes accessible marketing cookies on this site’s domain, and signals the Microsoft tag to stop tracking. The firm cannot directly remove cookies on another provider’s domain. Current-visit source, campaign, or referral details may still accompany a submitted enquiry or a Telegram referral link. Data kept with a lead follows the Privacy policy’s retention criteria; the 90-day attribution-cookie lifetime is not a deletion deadline for the lead.
Specific cookies and storage entries
The table below lists the main cookies set on this site. The list is updated when cookies, providers, or durations change. The names of cookies set by third-party processors are provided for transparency, in line with Article 5(3) of the ePrivacy Directive (2002/58/EC) and the EDPB’s cookie-consent guidance.
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
jagelski_consent (cookie and local storage) | Jagelski & Partners OÜ | Stores your category choices, policy version, and choice time | Cookie: 180 days; the browser-storage copy may remain until cleared, but an expired choice is not reused | Necessary |
_ga | Google Analytics (Google Ireland Limited / Google LLC) | Distinguishes unique users for aggregated analytics | 2 years | Analytics |
_ga_<measurement-ID> | Google Analytics (Google Ireland Limited / Google LLC) | Maintains session state for GA4 | 2 years | Analytics |
_clck | Microsoft Clarity (Microsoft Ireland Operations Limited / Microsoft Corporation) | Keeps a Clarity visitor identifier so that page interactions can be grouped by visitor | 1 year | Analytics |
_clsk | Microsoft Clarity (Microsoft Ireland Operations Limited / Microsoft Corporation) | Groups page views into a single Clarity session | 1 day | Analytics |
CLID and related cookies (third-party, on Microsoft domains) | Microsoft Clarity (Microsoft Ireland Operations Limited / Microsoft Corporation) | Set by Microsoft on its own domains when the Clarity tag loads, under Microsoft’s privacy statement | Up to 1 year | Analytics |
jag_attr_first | Jagelski & Partners (first-party) | Records the campaign, advertising click identifier, or external referrer that brought you to the site the first time, together with the page you landed on, so that an enquiry can be attributed to it | 90 days | Marketing |
jag_attr_last | Jagelski & Partners (first-party) | The same record for your most recent arrival, so that a first and a last touch can be told apart | 90 days | Marketing |
_uetsid | Microsoft Advertising (Microsoft Ireland Operations Limited / Microsoft Corporation) | Identifies your current visit for advertising measurement; a copy is kept in local storage | 1 day | Marketing |
_uetvid | Microsoft Advertising (Microsoft Ireland Operations Limited / Microsoft Corporation) | Distinguishes returning visitors for advertising measurement; a copy is kept in local storage | Up to 13 months | Marketing |
_uetmsclkid | Microsoft Advertising (Microsoft Ireland Operations Limited / Microsoft Corporation) | Holds the Microsoft advertising click identifier when you arrive from one of our advertisements | 90 days | Marketing |
MUID (third-party, on Microsoft domains) | Microsoft Advertising (Microsoft Ireland Operations Limited / Microsoft Corporation) | Identifies your browser to Microsoft when its advertising tag loads | Up to 13 months | Marketing |
_uetmsdns | Jagelski & Partners (first-party) | Records that marketing tracking is refused or withdrawn, so that the Microsoft advertising tag sends nothing. Contains no identifier | Session | Necessary |
emma_* (local and session storage) | Jagelski & Partners OÜ | Maintains chat history, search-to-chat handoffs, language labels, panel state, availability, and usage controls. Conversation identifiers and start times support service-outcome measurement; history and identifiers are sent to our service when Emma is used | Browser-tab session, except the local-storage cooldown entry, which may remain until browser storage is cleared | Requested chat functions and service measurement; not governed by the optional-cookie switches |
jg_lead_fired, jg_emma_engaged (session storage) | Jagelski & Partners OÜ | Prevents repeated counting of a lead or an engaged chat across pages in a tab when analytics consent is granted. Without that consent, deduplication uses page memory without writing these flags to browser storage | Browser-tab session | Analytics |
Google Tag Manager loads measurement tags after the initial consent settings. It does not itself set a tracking cookie, but loading it sends a request to Google. Some tags can send cookieless requests even where analytics or marketing storage is denied. Third-party cookie names and lifetimes depend on the provider and browser settings; blocking or clearing browser storage can shorten them.
Separately, when you chat with the Emma AI assistant, the content of your conversation is stored on our server (a server-side record rather than a cookie) for quality, safety, and follow-up. Retention is described in the Privacy policy.
Plausible Analytics measures page views and selected interactions without cookies or persistent device storage. Requests include page and referral information, event categories, IP address, and browser information. Plausible uses technical data to distinguish visits within a day and stores event and session records to produce aggregate statistics; it does not use a persistent cross-day visitor identifier. It runs regardless of the optional-cookie choice. The first-party jg_internal and plausible_ignore local-storage flags exclude internal visits and remain until cleared.
Cloudflare provides website delivery and security processing, including technical request data and security logs. Cloudflare Web Analytics provides cookieless traffic and performance measurement. Cloudflare Turnstile checks contact-form and Emma requests for automated abuse; its script may load while you prepare a submission. These functions can process IP, browser, device, and challenge information independently of optional-cookie choices. Security storage may be used where needed to deliver or protect the requested service.
Third-party processors and international data transfers
Google, Microsoft, Cloudflare, and Plausible process data for the functions described above. Their roles depend on the service and purpose: a provider may act on our instructions or as a separate controller for its own processing. Some providers process data outside the European Economic Area, including in the United States. Plausible states that its visitor-data processing and storage take place in the European Union. Serving a measurement request through our domain does not mean that the data stays with us.
Such transfers rely on the European Commission’s Standard Contractual Clauses, on the EU–US Data Privacy Framework where applicable to the receiving entity, or on other safeguards permitted under Chapter V GDPR. Further information on transfer safeguards is set out in the Privacy policy.
How to change your choices on this site
On your first visit, in every region, the cookie banner appears and offers three choices, of which Accept all and Reject all are the same size and one click each:
- Accept all enables the optional cookie categories, subject to any overriding Global Privacy Control signal.
- Reject all declines both optional cookie categories in one click. The separately disclosed storage and cookieless processing can still occur.
- Preferences lets you change analytics and marketing choices separately. The current choice and any Global Privacy Control signal determine the initial settings; without a choice, both are off.
Use Cookie preferences in the footer to change the optional categories. Switching a category off updates the consent signals and removes the matching cookies and storage entries that our controls can access. Providers’ own cookies or previously collected records may remain subject to their retention rules. Cookieless processing and the separate entries expressly identified above can continue.
The stored choice expires after 180 days. Where the banner applies, we request a new choice after expiry or a relevant consent-policy change. Clearing storage or changing browsers can make the banner appear earlier.
Browser-level controls
Most browsers also let you view, block, or delete cookies through the browser’s own settings. Instructions vary by browser; the major browsers’ help pages explain the steps. Setting your browser to block all cookies, including necessary cookies, may prevent parts of this site from functioning.
What happens if you refuse
You can browse the site without accepting optional cookies. Rejection denies the analytics and marketing cookie categories controlled by the preference centre. It does not prevent the technical, security, cookieless measurement, or separate browser-storage processing described on this page.
Necessary preference and security data still support the site. If you use Emma, submit an enquiry, or follow a contact link, the associated data is processed as described in the Privacy policy, independently of consent to unrelated advertising.
Google tags may send cookieless consent and event requests when storage is denied. These requests can carry technical data such as timestamps, browser information, page and referral URLs, consent state, and IP address, and support measurement and modelling. Plausible and Cloudflare measurement also continue as described above. Cookieless does not mean that no data reaches a provider.
Updates to this policy
We may update this policy as the technologies, providers, purposes, or applicable rules change. The current version is published with the date above. Where a change requires fresh consent, that consent is required before the relevant processing.
Contact
Questions about this policy can be sent to:
Jagelski & Partners OÜ
Email: privacy@jagelski.com
Telephone: +372 669 2066
Registered office and registry details: see Legal Notice on the Disclaimer page.
This policy is published in English and translated for convenience into the other languages offered on this site. In the event of any discrepancy between the English text and a translation, the English text prevails.