This Cookie Policy was last updated on tammikuu 13, 2026 and applies to citizens and legal permanent residents of the European Economic Area and Switzerland.
1. Introduction
Our website, https://www.signumvarainhoito.fi/en (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.
2. What are cookies?
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.
3. What are scripts?
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.
4. What is a web beacon?
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.
5. Cookies
5.1 Technical or functional cookies
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.
5.2 Statistics cookies
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.
5.3 Marketing/Tracking Cookies
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.
6. Placed cookies
Functional
6 months
Provide spam protection
Marketing
session
Read and filter requests from bots
session
Read and filter requests from bots
Persistent
Read and filter requests from bots
Sharing data
This data is not shared with third parties.
Statistics (anonymous)
Persistent
Store performed actions on the website
Sharing data
This data is not shared with third parties.
Functional
Persistent
Store user preferences
session
Read if cookies can be placed
Persistent
Store logged in users
session
Store browser details
Sharing data
This data is not shared with third parties.
Functional
Two days
Preventing cached pages involves disabling caching mechanisms or controlling how and when cache is updated. Here are several methods:
1. **Controlling HTTP Headers:**
* **`Cache-Control` Header:** This is the primary header for controlling caching.
* `no-store`: The most restrictive. No caching is allowed at all, neither by the browser nor by intermediate caches.
* `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.
* `max-age=0`: Similar to `no-cache`, it sets the maximum age of the resource to zero, meaning it's considered stale immediately.
* `s-maxage=0`: Similar to `max-age`, but specifically for shared caches (like CDNs).
* `must-revalidate`: The cache must revalidate the resource with the origin server when it becomes stale.
* `proxy-revalidate`: Similar to `must-revalidate` but applies only to shared caches.
* **`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.
* **`Pragma: no-cache`:** An even older HTTP/1.0 header, often used as a fallback for older clients.
2. **Using Query String Parameters (Cache Busting):**
* Append a unique parameter to the URL path. When the parameter changes, the URL is considered new by the browser, forcing a fresh download.
* Example: `styles.css?v=1.2.3` or `script.js?t=1678886400` (using a timestamp).
* This is particularly useful for static assets like CSS, JavaScript, and images.
3. **Using Versioned File Names:**
* Incorporate a version number or hash into the filename itself.
* Example: `styles.12345abc.css` or `app.cb456def.js`.
* This is a very common practice, especially in modern web development workflows. When the file content changes, the filename changes, invalidating any previous cache.
4. **Server-Side Configuration:**
* **Web Server Settings:** Configure your web server (Apache, Nginx, IIS) to send appropriate cache-control headers for specific file types or URL patterns.
* **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.
5. **Browser-Specific Mechanisms:**
* **Developer Tools:** Browsers often have options within their developer tools to disable the cache temporarily while the tools are open.
* **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.
6. **Content Updates and Versioning:**
* Ensure that whenever content changes, its cache-busting mechanism (query string or versioned filename) is updated.
* This requires a process or build tool that automatically handles versioning of assets.
7. **Important Considerations:**
* **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.
* **Scope:** Understand whether you want to prevent caching on the client-side (browser), server-side (proxies, CDNs), or both.
* **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.
**When to prevent caching:**
* Pages with sensitive, user-specific information that changes frequently (e.g., account dashboards).
* Pages that require the absolute latest data, and even a few minutes' lag is unacceptable.
* During development and testing to ensure you're always seeing the latest version.
By 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.
Purpose pending investigation
Google Fonts API
Sharing data
Sharing of data is pending investigation
Purpose pending investigation
e_my_templates_source
e_kit-elements-defaults
wp-settings-time-1
CookieYes consent
WP_PREFERENCES_USER_1
_ga_PZMZPF2075
_ga
cmplz_consented_services
2000 days
cmplz_policy_id
2000 days
cmplz_marketing
2000 days
cmplz_statistics
2000 days
cmplz_preferences
2000 days
cmplz_functional
2000 days
cmplz_banner-status
2000 days
__mp_opt_in_out_150605b3b9f979922f2ac5a52e2dcfe9
elementor_sidebar_menu_expanded_v2_elementor-templates
trp_language
llar_login_flow
7. Consent
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.
7.1 Manage your consent settings
You have loaded the Cookie Policy without javascript support. On AMP, you can use the manage consent button on the bottom of the page.
8. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change your internet browser's settings so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in your browser's Help section.
Please note that our website may not function correctly if all cookies are disabled. If you do delete cookies in your browser, they will be re-added after your consent when you visit our website again.
9. Your rights regarding personal data
You have the following rights regarding your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained.
- Right of access: You have the right to access your personal data that we hold.
- Right to rectification: You have the right to supplement, correct, delete, or block your personal data at any time.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to data portability: You have the right to request all of your personal data from the data controller and transfer it in its entirety to another data controller.
- Right to object: You may object to the processing of your data. We will comply with your objection, unless there are compelling legitimate grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).
10. Contact Details
For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:
Signum Wealth Management Ltd
Fabianinkatu 14 B, 2nd floor.
00100 Helsinki
Finland
Website https://www.signumvarainhoito.fi/en
Email: info@ex.comsignumvarainhoito.fi
This Cookie Policy was synchronized with cookiedatabase.org On helmikuu 22, 2026.