{"id":4315,"date":"2026-01-13T10:58:17","date_gmt":"2026-01-13T10:58:17","guid":{"rendered":"https:\/\/www.signumvarainhoito.fi\/evastekaytanto-eu\/"},"modified":"2026-01-13T10:58:17","modified_gmt":"2026-01-13T10:58:17","slug":"im-ready-to-eat","status":"publish","type":"page","link":"https:\/\/www.signumvarainhoito.fi\/en\/evastekaytanto-eu\/","title":{"rendered":"Cookie Policy (EU)"},"content":{"rendered":"\n

This Cookie Policy was last updated on January 13, 2026 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.<\/i>
<\/p>

1. Introduction<\/h2>

Our website, https:\/\/www.signumvarainhoito.fi\/en<\/a> (hereinafter: \"the website\") uses cookies and other similar technologies (for the sake of simplicity, all such technologies are referred to as \"cookies\"). Cookies are also placed by third parties with whom we work. In the document below, we inform you about the use of cookies on our website.<\/p>

2. What are cookies?<\/h2>

A cookie is a small, simple file that is sent along with pages of this website and stored by your browser on your computer's hard drive or another device. The information stored within may be returned to our servers or the servers of relevant third parties on a subsequent visit.<\/p>

3. What are scripts?<\/h2>

A script is a piece of program code used to make our website function properly and interactively. This code is executed on our server or on your device.<\/p>

4. What is a web beacon?<\/h2>

A web beacon (or pixel tag) is a small, invisible piece of text or image on a website used to monitor traffic. Web beacons store various data about you to do this.<\/p>

5. Cookies<\/h2>

5.1 Technical or functional cookies<\/p>

Some cookies ensure that certain parts of the website function correctly and that your user preferences remain known. By placing functional cookies, we make your visit to our website easier. This way, you will not have to repeatedly enter the same information when visiting our website, and, for example, items will remain in your shopping cart until you have paid. We may place these cookies without your consent.<\/p>

5.2 Statistics cookies<\/p>

We use statistics cookies to optimize the website experience for our users. With these statistics cookies, we gain insights into the usage of our website. We request your permission to place statistics cookies.<\/p>

5.3 Marketing\/Tracking Cookies<\/p>

Marketing\/Tracking cookies are cookies or any other form of local storage used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.<\/p>

6. Placed cookies<\/h2>
\n\t
\n\t\t

Google reCAPTCHA<\/h3>\n\t\t

Functional, Marketing<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Google reCAPTCHA for spam prevention. Read more about Google reCAPTCHA<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

For more information, please read the Google reCAPTCHA Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_grecaptcha<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
6 months<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Provide spam protection<\/div>\n\n<\/div>
\n

Marketing<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
rc::c<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Read and filter requests from bots<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
rc::b<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Read and filter requests from bots<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
rc::a<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
Persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Read and filter requests from bots<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Elementor<\/h3>\n\t\t

Statistics (anonymous)<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Elementor for content creation. Read more about Elementor<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Statistics (anonymous)<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
Elementor<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
Persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store performed actions on the website<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

WordPress<\/h3>\n\t\t

Functional<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use WordPress for website development. Read more about WordPress<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wp-settings-*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
Persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store user preferences<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wordpress_test_cookie<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Read if cookies can be placed<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wordpress_logged_in_*<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
Persistent<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store logged in users<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wpEmojiSettingsSupports<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
session<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Store browser details<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

LiteSpeed<\/h3>\n\t\t

Functional<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use LiteSpeed for website hosting. Read more about LiteSpeed<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

This data is not shared with third parties.<\/p>\n\t<\/div>\n\t

\n

Functional<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_lscache_vary<\/a><\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
Two days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
Preventing cached pages involves disabling caching mechanisms or controlling how and when cache is updated. Here are several methods:\n\n1. **Controlling HTTP Headers:**\n * **`Cache-Control` Header:** This is the primary header for controlling caching.\n * `no-store`: The most restrictive. No caching is allowed at all, neither by the browser nor by intermediate caches.\n * `no-cache`: The resource can be cached, but the cache must revalidate with the origin server before using the cached version. This is often confused with `no-store`, but it *does* allow storing the resource.\n * `max-age=0`: Similar to `no-cache`, it sets the maximum age of the resource to zero, meaning it's considered stale immediately.\n * `s-maxage=0`: Similar to `max-age`, but specifically for shared caches (like CDNs).\n * `must-revalidate`: The cache must revalidate the resource with the origin server when it becomes stale.\n * `proxy-revalidate`: Similar to `must-revalidate` but applies only to shared caches.\n * **`Expires` Header:** An older header that specifies an absolute expiration date\/time. If `Cache-Control` is present, it generally takes precedence. Setting `Expires` to a date in the past effectively disables caching.\n * **`Pragma: no-cache`:** An even older HTTP\/1.0 header, often used as a fallback for older clients.\n\n2. **Using Query String Parameters (Cache Busting):**\n * Append a unique parameter to the URL path. When the parameter changes, the URL is considered new by the browser, forcing a fresh download.\n * Example: `styles.css?v=1.2.3` or `script.js?t=1678886400` (using a timestamp).\n * This is particularly useful for static assets like CSS, JavaScript, and images.\n\n3. **Using Versioned File Names:**\n * Incorporate a version number or hash into the filename itself.\n * Example: `styles.12345abc.css` or `app.cb456def.js`.\n * This is a very common practice, especially in modern web development workflows. When the file content changes, the filename changes, invalidating any previous cache.\n\n4. **Server-Side Configuration:**\n * **Web Server Settings:** Configure your web server (Apache, Nginx, IIS) to send appropriate cache-control headers for specific file types or URL patterns.\n * **Content Delivery Network (CDN) Settings:** If you use a CDN, configure its caching rules. You can set aggressive caching for some assets and prevent caching for others.\n\n5. **Browser-Specific Mechanisms:**\n * **Developer Tools:** Browsers often have options within their developer tools to disable the cache temporarily while the tools are open.\n * **Hard Refresh:** Users can force a hard refresh (e.g., `Ctrl+Shift+R` or `Cmd+Shift+R`) to bypass the cache for a single page load. This is a user action, not a prevention method for all users.\n\n6. **Content Updates and Versioning:**\n * Ensure that whenever content changes, its cache-busting mechanism (query string or versioned filename) is updated.\n * This requires a process or build tool that automatically handles versioning of assets.\n\n7. **Important Considerations:**\n * **Performance:** Aggressively preventing caching on all resources can significantly degrade website performance as the browser and intermediate caches will not be able to store and serve assets quickly. Use these methods judiciously.\n * **Scope:** Understand whether you want to prevent caching on the client-side (browser), server-side (proxies, CDNs), or both.\n * **Dynamic vs. Static Content:** Typically, dynamic content that changes frequently should not be cached, or cached for very short durations with robust revalidation. Static assets (like CSS, JS, images) can and should be cached for performance, but with effective cache-busting strategies.\n\n**When to prevent caching:**\n\n* Pages with sensitive, user-specific information that changes frequently (e.g., account dashboards).\n* Pages that require the absolute latest data, and even a few minutes' lag is unacceptable.\n* During development and testing to ensure you're always seeing the latest version.\n\nBy combining these techniques, you can effectively manage how and when your web content is cached, ensuring users always see the most up-to-date information when necessary, without sacrificing performance unnecessarily.<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Google Fonts<\/h3>\n\t\t

Purpose pending investigation<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

We use Google Fonts for display of webfonts. Read more about Google Fonts<\/a><\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

For more information, please read the Google Fonts Privacy Statement<\/a>.<\/p>\n\t<\/div>\n\t

\n

Purpose pending investigation<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
Google Fonts API<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n\n<\/div>\n<\/details>\n
\n\t
\n\t\t

Miscellaneous<\/h3>\n\t\t

Purpose pending investigation<\/p>\n\t\t

\n\t\t

Usage<\/h4>\n\t\t

<\/p>\n\t<\/div>\n\t

\n\t\t

Sharing data<\/h4>\n\t\t

Sharing of data is pending investigation<\/p>\n\t<\/div>\n\t

\n

Purpose pending investigation<\/h4><\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
e_my_templates_source<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
e_kit-elements-defaults<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
wp-settings-time-1<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
CookieYes consent<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
WP_PREFERENCES_USER_1<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_ga_PZMZPF2075<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
_ga<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_consented_services<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_policy_id<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_marketing<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_statistics<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_preferences<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_functional<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
cmplz_banner-status<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
2000 days<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
__mp_opt_in_out_150605b3b9f979922f2ac5a52e2dcfe9<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
elementor_sidebar_menu_expanded_v2_elementor-templates<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
trp_language<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Name<\/h5>\n<\/div>\n
llar_login_flow<\/div>\n
\n\t
Expiration<\/h5>\n<\/div>\n
<\/div>\n
\n\t
Function<\/h5>\n<\/div>\n
<\/div>\n\n<\/div>\n<\/details>\n<\/div>

7. Consent<\/h2>

When you visit our website for the first time, we will present you with a pop-up explaining cookies. By clicking \"Save settings\" (Tallenna asetukset), you consent to our use of the cookie and plug-in categories you selected in the pop-up, as detailed in this Cookie Policy. You can disable cookies through your browser settings, but please be aware that this may affect the proper functioning of our website.<\/p>

7.1 Manage your consent settings<\/p>