Cookie Policy

A cookie is a small text file a website asks your browser to store, and which your browser then sends back on every later request to that site. Cookies let a site recognise your device and remember something between one page and the next — the language you chose, or the consent choices you made.

Two things sit alongside cookies and do a similar job, so this policy covers them too:

• Local storage and session storage. These also keep information in your browser, but the information is never attached to network requests — it stays on your device until the page reads it. We use these in preference to cookies wherever we can.

• Pixels, tags and embedded frames. A small image, script or embedded player loaded from another company's servers. Loading one lets that company see your IP address and set its own cookies.

Cookies set by this website are first-party cookies. Cookies set by a service embedded in our pages — a video player, an analytics tag, an advertising pixel — are third-party cookies, and they are governed by that company's own privacy policy as well as this one.

We use cookies and similar technologies to:

• keep the website working, secure and protected from automated abuse;

• remember your preferences, including your language and your consent choices;

• understand how visitors find and use the site, and where they get stuck;

• measure the effectiveness of our marketing and advertising campaigns;

• show you content and advertising relevant to your interests, on this site and on other platforms.

Two things we want to be explicit about:

• We do not put your personal details in cookies. Nothing you type into a form is placed in a cookie. Where a form remembers what you entered, it is kept in your browser's own local storage — see the section on local and session storage below.

• Showing prices for your region does not use a cookie. Your approximate country is resolved from your IP address by an offline lookup on our own server. No third party is contacted to do it, and no identifier is stored in your browser.

When you first visit our website, a cookie banner powered by Cookiebot, our consent management platform, asks you to accept or reject each category of non-essential cookie.

• Only strictly necessary cookies are set automatically. Everything else — analytics, advertising, functionality and personalisation — loads only after you have given consent for that category.

• Refusing costs you nothing but personalisation. The site remains fully readable and usable if you reject every optional category.

• You can change your mind at any time. Use the cookie settings icon on the website to reopen the banner and adjust or withdraw any category. Withdrawing consent stops further collection; it does not undo collection that already took place while consent was in force.

• Clearing your browser's cookies also clears your stored consent, so the banner will ask again on your next visit.

Your choices are recorded in a consent cookie so that we do not ask again on every page, and so that we can demonstrate what you agreed to.

Almost every optional technology on this site is delivered through Google Tag Manager, a container that decides which tags are allowed to run. Tag Manager is not itself a tracking tool and sets no cookies of its own — it is the mechanism that holds the others back until you have said yes.

Your banner choices are passed to it as Google Consent Mode signals, and each signal governs a group of tags:

• analytics_storage — allows analytics cookies (Google Analytics 4, Microsoft Clarity, HubSpot) to store and read data

• ad_storage — allows advertising cookies (Google Ads, Meta Pixel, LinkedIn Insight Tag) to store and read data

• ad_user_data — allows user data to be sent to Google for advertising purposes

• ad_personalization — allows personalised and remarketing advertising

• functionality_storage — allows cookies that remember site preferences

• personalization_storage — allows cookies that personalise site content

• security_storage — supports security and fraud prevention. This is always active and is exempt from consent, because without it we cannot tell a genuine visitor from an automated attack

Where a signal is denied, the corresponding tags do not set cookies and the related tracking does not take place. Some Google tags may still send a cookieless, aggregated ping recording that an event occurred, with no identifier attached to you.

These are required for the website to function or to keep it secure. They cannot be switched off through the banner, and they carry no advertising identifier.

Consent preferences — CookieConsent

• Set by: Cookiebot, on our behalf (first-party)

• Purpose: stores which categories you accepted or rejected, so we do not ask again on every page and can evidence your choice

• Expires: after one year

Anti-spam protection — _GRECAPTCHA

• Set by: Google reCAPTCHA v3 (third-party, google.com)

• Purpose: scores how likely it is that a form submission is automated, so spam and abusive submissions are rejected before they reach us. It works by observing how the page is used while it is open, without asking you to solve a puzzle

• Expires: after approximately six months

• This falls under security_storage and is exempt from consent. If you block it, forms on the site may refuse to submit — without a score there is no way to tell your submission from an automated one

Network protection and load balancing — __cf_bm, cfuvid, cfclearance

• Set by: our content delivery provider (third-party)

• Purpose: blocks automated abuse, filters bot traffic and routes your request to the nearest server. These are set at the network layer, before our application sees the request

• Expires: typically within 30 minutes to a few hours; a passed challenge may last longer

• Not used for analytics or advertising

Content preview — __prerender_bypass, __next_preview_data

• Set by: this website (first-party)

• Purpose: lets an authorised member of our content team view a page that has not been published yet. These have no effect for ordinary visitors and are never set for them

• Contains: a random token; no personal information

• Expires: when the preview session ends or the browser is closed

These remember choices you make so the site behaves the way you left it. They are governed by functionality_storage.

Language preference — NEXT_LOCALE

• Set by: this website (first-party)

• Purpose: remembers the language you selected — English, ไทย or Español — so the site opens in it next time

• Contains: a two-letter language code and nothing else

• Expires: after one year, or when you clear your cookies

• We do not guess your language from your browser settings; this cookie is written only when you choose a language yourself

Most of what would traditionally sit in this category — remembering what you typed into a form, or which pricing plan you were reading — is handled on this site with browser storage rather than cookies. Those are listed separately below.

These help us understand how visitors interact with the website — which pages are read, how people navigate, and where they run into difficulty — so we can improve performance and content. They load only with your consent under analytics_storage.

Google Analytics 4 — ga, ga_<container>, _gid

• Set by: Google (third-party)

• Purpose: measures traffic, page views, user journeys and conversion events such as form submissions, button clicks and demo bookings. _ga distinguishes one browser from another; the container-specific cookie holds the session state

• Expires: ga and ga_<container> after two years; _gid after 24 hours

Microsoft Clarity — clck, clsk, CLID, MUID, ANONCHK

• Set by: Microsoft (third-party, clarity.ms), deployed through Tag Manager

• Purpose: records anonymised page interaction — mouse movement, scrolling, clicks and page transitions — and aggregates it into heatmaps and session replays, so we can see where the site is confusing. Text you type into form fields is masked before it leaves your browser, and we do not use Clarity to identify you personally

• Expires: clsk after one day; clck and CLID after up to one year

• Microsoft processes this data as an independent controller

HubSpot — hubspotutk, hstc, hssc, __hssrc

• Set by: HubSpot (third-party)

• Purpose: HubSpot is the platform we use to manage enquiries. hubspotutk is an anonymous visitor identifier: when you submit a form it is sent with the submission so the enquiry attaches to your existing record rather than creating a duplicate, and so we can see which pages you found useful before getting in touch. The __hst* cookies count visits and group page views into sessions

• Expires: hssc after 30 minutes; hssrc when you close your browser; hubspotutk and __hstc after six months

• If you decline this category, your enquiry still reaches us in full — it simply arrives without the browsing history that would otherwise be attached to it

One thing that happens whether or not you accept cookies: when you submit a form, your IP address is sent to HubSpot along with it, so that the enquiry records the approximate location it came from. This is part of handling your enquiry rather than a cookie, and it is covered by our Privacy Policy. If you submit no form, no IP address is sent to HubSpot.

These are used to measure our advertising, to limit how often you see the same ad, and to show you our advertising on other platforms after you have visited us. They may be set by us or by our advertising partners, and they can record your activity across other websites. They load only with your consent under ad_storage, ad_user_data and ad_personalization.

Google Ads — gclaw, gcldc, and cookies on doubleclick.net

• Purpose: records that a visit followed one of our ads, so we can attribute conversions such as form submissions and trial sign-ups, and enables remarketing — meaning you may see our ads on other sites after visiting ours

• Expires: typically 90 days

Conversion Linker — gclau

• Purpose: stores ad-click information in a first-party cookie so that conversions are still measured accurately when browsers restrict third-party cookies. It does not personalise anything by itself

• Expires: 90 days

Google Ads Enhanced Conversions

• Purpose: improves the accuracy of conversion measurement by sending Google hashed customer information — such as an email address you entered on a form — so a conversion can be matched to an ad click. The information is hashed in your browser before it is sent; Google does not receive the plain value

• Runs only where you have consented to ad_user_data

Meta (Facebook) Pixel — fbp, fbc, and cookies on facebook.com

• Purpose: measures conversions from advertising on Facebook and Instagram, builds custom audiences and enables remarketing on Meta platforms

• Expires: typically 90 days

LinkedIn Insight Tag — li_sugr, UserMatchHistory, AnalyticsSyncHistory, and cookies on linkedin.com such as bcookie, lidc, li_gc

• Purpose: measures conversions from LinkedIn advertising and enables retargeting of website visitors on LinkedIn

• Expires: from 24 hours to two years depending on the cookie

Some pages include content served by another company. Nothing is set until that content actually loads, but once it does, the provider can set cookies of its own.

YouTube videos

Videos are embedded in privacy-enhanced mode through youtube-nocookie.com. No cookie is set while a video sits on the page unplayed. When you press play, YouTube may set cookies such as YSC (which ends when you close your browser) and VISITOR_INFO1_LIVE (about six months) to remember playback preferences and measure viewing. These are governed by Google's privacy policy.

Demo scheduling

The calendar used to book a demo is provided by HubSpot and opens inside the page. It may set its own cookies when it loads.

Careers listings

Our open roles are listed through Keka, our recruitment platform. The embedded job board and any application you start there are served by Keka, which may set its own cookies. Keka's privacy policy applies to them.

Several conveniences on this site are built on your browser's own storage rather than on cookies. The distinction matters: a cookie is attached to every request your browser makes to us, so its contents travel across the network and appear in server logs. Local and session storage never leave your device unless the page deliberately reads them and sends them — which, for the items below, only happens when you submit a form.

Saved form answers — ycs_form_… (local storage)

• Purpose: after you successfully submit a form, the values are kept so that the next form you open is already filled in and you do not retype your name, email and phone number. The Book a Demo form also saves each completed step, so leaving halfway does not lose your answers

• Contains: the fields of that form. Uploaded files are never saved — CVs, cover letters and attachments are excluded — and neither is the anti-spam token

• Deleted: automatically 30 days after it was last written, or immediately when you clear your browser's site data

Shared contact details — ycs_form_profile (local storage)

• Purpose: the details common to every form — name, work email, phone, company — so that a form you have never opened before can still be pre-filled

• Deleted: on the same 30-day basis

Where you came from — ycs_page_current, ycs_page_previous (session storage)

• Purpose: records the page you were on before the current one, so that an enquiry reaches us with the context of what you were reading

• Deleted: when you close the tab

Pricing hand-off — ycs_pricing_room_range, ycs_pricing_plan (session storage)

• Purpose: carries the plan and property size you selected on the pricing page into the demo form, so you do not answer the same question twice

• Deleted: when you close the tab

Demo confirmation — demo_booked (session storage)

• Purpose: a single yes/no marker, so that the confirmation page is shown to someone who has just booked rather than to anyone who happens to open the URL

• Deleted: as soon as the confirmation is shown, and in any case when you close the tab

Retired cookies — ycs_form_*. Earlier versions of this site stored saved form values in cookies of the same names. They are no longer used. If your browser still holds one, the site deletes it automatically on your first visit and moves anything it contained into local storage instead.

Analytics and advertising providers may also use their own local storage entries under the consent categories described above.

Some cookies described above are placed by third-party services that appear on our pages. We do not control those cookies directly, and each provider handles what it collects under its own terms. Their privacy notices are the authoritative source:

• Google — covering Google Analytics, Google Ads, reCAPTCHA and YouTube

• Meta — covering the Facebook and Instagram pixel

• LinkedIn — covering the Insight Tag

• Microsoft — covering Clarity and Microsoft advertising identifiers

• HubSpot — covering enquiry management and lead attribution

• Cookiebot (Usercentrics) — covering consent management

• Keka — covering the careers job board

This policy covers the Yanolja Cloud Solution website only. Our pages also link out to partner sites, marketplace listings, app stores and social networks, and our products are served from separate addresses with their own sign-in. Once you follow such a link, the cookie practices of that site apply, and we have no control over them.

Session cookies are deleted automatically when you close your browser. Everything held in session storage goes the same way when you close the tab.

Persistent cookies stay on your device for a set period, or until you delete them. Each entry above states its own lifetime; in summary, consent and preference cookies last about a year, advertising cookies typically 90 days, analytics cookies between 24 hours and two years, and saved form answers are removed 30 days after they were last written whether or not you return.

Retention by the provider is a separate matter from the life of the cookie: once data has been collected, that company's own retention policy governs how long it keeps it.

The always-current list of every cookie on this site, with its exact name, provider, purpose and expiry, is maintained automatically by our consent platform and published in the cookie declaration on this page. Clearing your browser's cookies and site data removes all of it immediately.

Through our cookie settings

Click the cookie settings icon on the website to reopen the consent banner and change or withdraw any category at any time. This is the most direct control, and it applies to every optional technology described in this policy.

In your browser

Every major browser lets you see the cookies a site has set, delete them, and block new ones — either for all sites or for this one alone. The same settings screen clears local and session storage. Look under Privacy and security in Chrome and Edge, Privacy and Security in Firefox, or Privacy in Safari, and use your browser's Help for the exact steps on your version. Private or incognito windows discard everything described in this policy when the window is closed.

Through industry opt-out tools

The Digital Advertising Alliance and, for visitors in Europe, Your Online Choices both operate opt-outs covering many advertising networks at once. Google, Meta, LinkedIn and Microsoft each publish their own advertising and privacy controls.

What stops working if you refuse or block cookies

The site remains fully readable. But your language choice will not be remembered from one visit to the next; forms will no longer pre-fill; our measurement of which content is useful becomes incomplete; and if you block the strictly necessary anti-spam cookie, form submissions may be rejected altogether.

Do Not Track

There is no agreed industry standard for how a site should respond to a browser's Do Not Track signal, and this site does not currently change its behaviour based on one. The consent banner and the browser controls above take effect regardless.

We update this Cookie Policy whenever the technologies on the site change — when a service is added or removed, or when an existing one changes what it stores — and for legal, operational or regulatory reasons. The date at the top of the page always reflects the most recent revision, and a material change will be signposted on the site. Please revisit this page from time to time to stay informed.

If you have a question about this policy, want to know more about a particular cookie, or wish to exercise a right over your personal data, write to us at info@yanoljacloudsolution.com.

Our handling of personal data more broadly — the legal bases, your rights, and how to make a request — is set out in our Privacy Policy. The terms governing use of this site are in our Terms and Conditions.