This Cookie Policy was last updated on 5 May 2026 and applies to citizens and people with legal permanent residency in the European Economic Area and Switzerland.
1. Introduction
Our website, https://villa-sancarlo.it/en (hereinafter: "the website") uses cookies and similar technologies (for simplicity, all such technologies are referred to as "cookies"). Cookies are also placed by third parties with whom we cooperate. In the document below, we will inform you about the use of cookies on our website.
2. What are cookies?
A cookie is a small, simple file that is sent with the pages of this website and stored by your browser on your computer's hard drive or another device. The information stored in it may be sent back to our servers or to the servers of relevant third parties during a subsequent visit.
3. What are scripts?
A script is a piece of program code that is 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 a pixel tag) is a small, invisible piece of text or image on a website that is used to monitor traffic on a website. In order to do this, various data about you is stored using web beacons.
5. Cookies
5.1 Technical or functional cookies
Some cookies ensure that certain parts of the website function properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need 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 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
Sharing data
This data is not shared with third parties.
Functional
Persistent
Store user preferences
session
Store browser details
Persistent
Store logged-in users
session
Read if cookies can be placed
session
Store language preferences
Sharing data
This data is not shared with third parties.
Marketing
Persistent
Store and track conversions
Sharing data
This data is not shared with third parties.
Statistics
1 year
Store and count page views
2 years
Store and count page views
1 year
Store and count page views
Functional
365 days
Save accepted cookie policy ID
365 days
Save cookie agreement preferences
365 days
Store whether the cookie banner has been dismissed
365 days
Save cookie agreement preferences
365 days
Save cookie agreement preferences
365 days
Save cookie agreement preferences
365 days
Save cookie agreement preferences
Sharing data
This data is not shared with third parties.
Functional
Two days
Here are ways to prevent cached pages:
* **Cache-Control Header:** Use the `Cache-Control` HTTP header with directives like `no-store`, `no-cache`, or `max-age=0`.
* `no-store`: Instructs the browser and any intermediate caches not to store the response at all. This is the strongest directive.
* `no-cache`: Allows the response to be stored, but it must be revalidated with the origin server before being used. This means the browser will check if the cached version is still valid.
* `max-age=0`: Sets the cache’s maximum age to zero seconds, effectively telling the cache that the content is immediately stale.
* **Expires Header:** Set the `Expires` HTTP header to a date in the past. This tells caches that the content has already expired. While `Cache-Control` is generally preferred, `Expires` is still supported by older clients.
* **ETag and Last-Modified Headers (for revalidation):** While not strictly *preventing* caching, these headers are crucial for ensuring the cached version is up-to-date. When you set `no-cache` or `max-age=0`, the browser will often use `If-None-Match` (with ETag) or `If-Modified-Since` (with Last-Modified) requests. If the server finds that the resource hasn't changed, it can respond with a `304 Not Modified` status, saving bandwidth.
* **Vary Header:** If your page content can change based on certain request headers (e.g., `User-Agent`, `Accept-Encoding`), use the `Vary` header. For example, `Vary: Accept-Encoding` tells caches that responses vary based on the `Accept-Encoding` header, ensuring different compressed versions are cached separately. Without it, a cache might serve the wrong encoding to a client.
* **URLs with Query Parameters:** Dynamic or frequently updated content can be served by appending unique query parameters to the URL. For example, `script.js?v=1.2.3` or `style.css?t=1678886400`. Caches typically treat URLs with different query parameters as distinct resources, thus preventing them from serving stale versions. However, be mindful that this can increase the number of requests and potentially impact performance if not managed carefully.
* **Browser-Specific Cache Busting:** Client-side JavaScript can sometimes be used to dynamically update URLs or add cache-busting parameters, but relying solely on client-side methods is less robust than server-side configuration.
* **Server-Side Configuration:** The most reliable way to control caching is through your web server's configuration (e.g., Apache, Nginx) or your application framework's settings. You can define default caching policies and override them on a per-page or per-file basis.
**When to Prevent Caching:**
* **Highly dynamic content:** Pages that change frequently or display personalised information that should always be fresh.
* **Sensitive information:** Pages containing user-specific or sensitive data that should not be stored in a cache.
* **Development and testing:** To ensure you're always seeing the latest deployed version of your code.
Sharing data
Data sharing is pending investigation
Purpose to be confirmed upon investigation
settings store
hst_ai_blocks_added
breakdance-twig-macros
greeting_screen_visited_v1
Onboarding - Set Up Store
breakdance-twig-macros-hash
general-data-store
breakdance_clipboard
chatbot_input_message
cmplzSelectedRegion
365 days
cookieyes-consent
wp-settings-time-3
wp-settings-3
breakdance_view_count
breakdance session count
breakdance_last_session_id
trp_language
WP_DATA_USER_3
_iub_cs-23956533
_iub_cs-91195098
_iub_previous_preference_id
wp-settings-1
wp-settings-time-1
7. Consent
When you first visit our website, a pop-up will appear explaining our use of cookies. By clicking "Save preferences," you consent to us using the categories of cookies and plug-ins you have selected in the pop-up, as detailed in this Cookie Policy. You can disable cookies through your browser settings, but please be aware that our website may then not function correctly.
7.1 Manage your consent settings
You have loaded the Cookie Policy without JavaScript support. On AMP, you can use the manage consent button at 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 the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not function properly if all cookies are disabled. Should you delete the cookies in your browser, they will be placed again after your consent upon your subsequent visit to our website.
9. Your rights concerning personal data
You have the following rights with respect to 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 for.
- 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, have deleted or blocked your personal data whenever you wish.
- If you give your consent for us 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 your personal data from the controller and transfer it in its entirety to another controller.
- Right to object: You may object to the processing of your data. We will comply with this, unless there are justified 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 any questions or comments regarding our Cookie Policy and this statement, please contact us using the following details:
INTERIOR TECH S.R.L.
VIA MAGENTA, 53 - 20017 RHO (MI)
Italy
Website https://villa-sancarlo.it/en
Email: info@ex.comvilla-sancarlo.it
Phone number: +393880514086
This Cookie Policy was synchronised with cookiedatabase.org on 6 May 2026.
Italian 
English