Center text consent mode
Paragraph 01: What cookies are
When you visit any website, it can store or retrieve information on your browser, mostly in the form of cookies. This information could be about you, your preferences or your device and is used mainly to make the site work according to your expectations. The information does not usually directly identify you, but it can provide a more personalized web experience. We respect your right to privacy, so you can choose not to allow certain types of cookies. Click the headers of the different categories to find out more and change the default settings. However, blocking certain types of cookies may affect your experience of the site and the services we can offer.
Further information
Paragraph 02: Strictly necessary cookies
These cookies are required for the website to work and cannot be disabled on our systems. Usually, they are only set in response to actions you take that constitute a request for services, such as setting privacy preferences, logging in, or filling out forms. You can set your browser to block or issue alerts about these cookies, but as a result some parts of the site will not work. These cookies do not store any personal information.
Paragraph 03: Performance cookies
These cookies enable us to count visits and sources of traffic, so we can measure and improve the performance of our site. They let us know which pages are the most and least popular and see how visitors browse the site. All information collected from the cookies are aggregated and are therefore anonymous.
Paragraph 04: Functionality cookies
These types of cookies are used to remember the choices made by the user (for example, the language or geographical region in which they are located). These choices are reused when you visit the site in the future, to provide improved personalized services (for example, they can be used to provide content similar to your previous requests).
Paragraph 05: Profiling cookies
Profiling cookies analyze how users browse the site and their habits, purchases and behavior, to provide commercial communications in line with their preferences.
COOKIE POLICY
Barilla Foundation, with its registered office in Parma at Via Madre Teresa di Calcutta, 3/a – Tax Code and VAT Number 02716600347, acting as the Data Controller, info@fondazionebarilla.com, (hereinafter “Fondazione”) informs users, in accordance with Regulation (EU) 679/2016 (hereinafter “GDPR”) and the legislation, including Italian legislation, on the protection of personal data applicable at the time (hereinafter “Privacy Legislation”), that the personal data (hereinafter “Data”) relating to users (hereinafter, “Data Subjects”) of the website (hereinafter “Site”), collected using cookies will be processed in the manner and for the purposes indicated in this policy.
1. DATA CONTROLLERS AND JOINT CONTROLLERS
Fondazione is the controller of the Data collected using cookies via this Site. Exclusively in relation to Facebook Business Tools, including but not limited to the Insight button on the page to redirect to the Facebook page, Barilla and Facebook Ireland Limited, with its registered office at 4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Ireland, act as joint controllers, on the basis of a specific Joint Ownership Agreement, in order to measure the level of interaction between the websites visited based on the preferences of the data subjects and to provide targeted advertising.
Further information on how Facebook Ireland processes the Data, including the legal basis to which Facebook Ireland refers and how data subjects can exercise their rights vis-à-vis Facebook Ireland can be found in the Facebook Ireland Data Policy at https://www.facebook.com/about/privacy.
2. DATA: COOKIES
Cookies are small text files that are saved on the Data Subject’s electronic device (PC, tablet, etc.) while browsing a website, which provide certain information. Cookies are then sent back to the website of origin each time the site is browsed in the future, or are sent to a different website that can recognize that specific cookie. Cookies act as a memory for a website, enabling it to recognize the Data Subject’s device each time the same site is browsed in the future. Cookies also enable the saving of Data Subjects’ browsing preferences, offering them a more functional experience of the Site, and making the content on the Site as personalized as possible.
TYPES OF COOKIES
Our Site uses the following categories of cookies, which may pertain to Fondazione or to third parties.
2.1 TECHNICAL COOKIES
These strictly necessary cookies are used to improve your browsing of the Site and your use of its the features and services offered by the website. In particular, they enable functions without which it would not be possible to use the Site fully, given that their presence enables basic functions such as page navigation and access to protected areas of the Site.
Technical cookies operate by default and you do not need to accept them, as they are necessary for the Site to work properly. In particular, the Site uses “session” and persistent technical cookies, such as:
| Cookies | Expiration | Description and provider |
|---|---|---|
| _iub_cs-70853207 | 12 months | Third-party technical cookie generated by Iubenda to save the cookie preferences expressed by the user in the Cookie Banner |
2.2 PERFORMANCE COOKIES
These types of cookies are used so we can analyze the way you browse the Site, to help us improve your browsing experience. These cookies are anonymized and only identify you to a limited extent (e.g., parts of your IP address are masked).
| Cookies | Expiration | Description and provider |
|---|---|---|
| _ga | 2 years | Used to distinguish users. |
| _gid | 24 hours | Used to distinguish users. |
| _ga_ | 2 years | Used to persist session state. |
| _gac_gb_ | 90 days | Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more. – Google |
| _gat | 1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property- id> . |
| AMP_TOKEN | 30 seconds to 1 year | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. |
| _gac_ | 90 days | Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more. – Google |
| __utma | 2 years from set/update | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmt | 10 minutes | Used to throttle request rate. |
| __utmb | 30 mins from set/update | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmc | End of browser session | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. |
| __utmz | 6 months from set/update | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
| __utmv | 2 years from set/update | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. – Google |
| __utmx | 18 months | Used to determine a user’s inclusion in an experiment. |
| __utmxx | 18 months | Used to determine the expiry of experiments a user has been included in. |
2.3 FUNCTIONALITY COOKIES
These types of cookies are used to remember the choices you make (for example, the language or geographical region in which you are located). These choices are reused when you visit the site in the future, to provide improved personalized services (for example, they can be used to provide content similar to your previous requests).
2.4 PROFILING COOKIES
Profiling cookies analyze how you browse the site and your habits, purchases and behavior, to provide commercial communications in line with your preferences. In particular, the Site uses the following proprietary and third-party profiling cookies:
| Cookies | Expiration | Description and provider |
|---|---|---|
| t | 30 days | Stores informtion on the advertisement seen by the user is order to provide a correct conversion report – Datafront |
| e | 12 months | Backup cookie to store User-ID for a longer time period – Datafront |
| o | 60 days | Stores the user optout status – Datafront |
| p | 15 days | Stores User-ID – Datafront |
| tui | 30 days | Stores information on the user (Dynamic Creative Engine) – Datafront |
| tev | 30 days | Stores information on the products seen (Dynamic Creative Engine) – Datafront |
| uuid2 | Persistent / 90 days | This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices. It is matched against information – such as advertising interest segments and histories of ads shown in the browser or device – provided by clients or other third parties and stored on the Platform. This information is used by clients to select advertisements for delivery by the Platform, and to measure the performance of, and attribute payment for, those advertisements. In addition, we use this cookie to enable clients to use data which does not reveal or use an Internet user’s real-world identity or data they collect outside of the Platform or acquire from other third parties. This cookie is also sometimes matched to clients’ or other third parties’ cookies so that they can use data they collect outside of the Platform to serve more relevant advertisements to Internet users. When a user opts out of having the Platform used to select ads based on online behavior, the unique value in uuid2 is deleted and replaced with the non-unique value “-1”. – Xandr |
| uids | Persistent / 90 days | This cookie contains a base 64 encoded JSON object which contains external unique randomly-generated values that enable other Prebid Server demand partners to distinguish browsers and mobile devices. This information is used by our Prebid Server demand partners to select advertisements for delivery by the Platform and to measure the performance of, and attribute payment for, those advertisements. Note the cookie is a cookie used by prebid.org, the open source heading bidding project and is not our proprietary cookie. We run an instance of prebid.org software on our infrastructure. – Xandr |
| usersync | Persistent / 90 days | The usersync cookie contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside the Platform on the Platform. – Xandr |
| icu | Persistent / 90 days | The icu cookie is used to select ads and limit the number of times a user sees a particular ad. It contains information such as the number of times an ad has been shown, how recently an ad has been shown, or how many total ads have been shown. – Xandr |
| anj | Persistent / 90 days | The anj cookie contains data denoting whether a cookie ID is synced with our partners. ID syncing enables our partners to use their data from outside the Platform on the Platform. – Xandr |
| UserMatchHistory | 30 days | LinkedIn Ads ID syncing – Linkedin |
| AnalyticsSyncHistory | 30 days | Used to store information about when a synchronization with the lms_analytics cookies occurred for users in designated countries – LinkedIn |
| li_oatml | 30 days | Used to identify LinkedIn users outside of LinkedIn for advertising and analytics purposes outside designated countries and, for a limited time, for advertising purposes in designated countries – LinkedIn |
| lms_ads | 30 days | Used to identify LinkedIn Users in designated countries for advertising purposes |
| lms_analytics | 30 days | Used to identify LinkedIn Users in designated countries for analytics purposes – LinkedIn |
| li_fat_id | 30 days | Indirect user identifier for Users for conversion tracking, retargeting and analytics purposes – LinkedIn |
| li_sugr | 30 days | Used to make a probabilistic association of the user’s identity outside the designated countries – LinkedIn |
| U | 3 months | Browser identifier for users outside the designated countries – LinkedIn |
| _guid | 90 days | Used to identify a LinkedIn User for advertising purposes via Google Ads – LinkedIn |
| BizographicsOptOut | 10 years | To determine opt-out status for third-party tracking – LinkedIn |
| li_giant | 7 days | Indirect identifier for LinkedIn user groups used for conversion tracking – LinkedIn |
| UserMatchHistory | 30 days | LinkedIn Ads ID syncing – Linkedin |
| li_oatml | 30 days | Used to identify LinkedIn users outside of LinkedIn for advertising and analytics purposes outside designated countries and, for a limited time, for advertising purposes in designated countries – LinkedIn |
| lms_ads | 30 days | Used to identify LinkedIn Users in designated countries for advertising purposes – LinkedIn |
| li_fat_id | 30 days | Indirect user identifier for Users for conversion tracking, retargeting and analytics purposes – LinkedIn |
| li_sugr | 90 days | Used to make a probabilistic association of the user’s identity outside the designated countries – LinkedIn |
| U | 3 months | Browser identifier for users outside the designated countries – LinkedIn |
| _guid | 90 days | Used to identify a LinkedIn User for advertising purposes via Google Ads – LinkedIn |
| A3 | 1 year | Advertising/targeting cookies for Yahoo – LinkedIn |
| anj | 3 months | Advertising/targeting cookies for AppNexus – LinkedIn |
| uuids | 3 months | Used by AppNexus ad nexus analytics – LinkedIn |
| ELOQUA | 2 years | Used for ELOQUA tracking – LinkedIn |
| ELQSTATUS | 2 years | Used for ELOQUA tracking – LinkedIn |
| dpm | 6 months | Sends events to Adobe Audience Manager – LinkedIn |
| dextp | 6 months | Logs the last time a data sync call was made – LinkedIn |
| demdex | 6 months | Visitor identification – LinkedIn |
| dst | 6 months | Logs when an error occurs sending data to its destination. Used as part of Adobe Audience Manager – LinkedIn |
| lnkd | 6 months | Sends events to Adobe Audience Manager – LinkedIn |
| aam_uuid | 30 days | Set to sync ID for Adobe Audience Manager – LinkedIn |
| MUID | 1 year | Bing tracking – LinkedIn |
| MR | 6 months | Bing tracking – LinkedIn |
| MR2 | 6 months | Bing tracking – LinkedIn |
| IDE | 2 years | Advertising/targeting cookies for DoubleClick – LinkedIn |
| fr | 3 months | Advertising/targeting cookies for Facebook – LinkedIn |
| personalization_id | 2 years | Advertising/targeting cookies for Twitter – LinkedIn |
| GUC | 5 months | Yahoo conversion tracking – LinkedIn |
| B | 1 year | Yahoo conversion tracking – LinkedIn |
| test_cookie | 1 day | Testing for cookie installation permissions in the user’s browser – LinkedIn |
| _gcl_au | 3 months | Used via Google Analytics to understand user interactions with the site and advertising – LinkedIn |
| _gcl_aw | 3 months | Used via Google Ads to understand user interactions with the site and advertising – LinkedIn |
| _gcl_dc | 3 months | Used via Google Campaign Manager and DV 360 to understand user interactions with the site and advertising – LinkedIn |
| brwsr | 2 years | Affiliate Marketing Cookies for LinkedIn – LinkedIn |
| ABSELB | 2 years | Load balancing cookies for Affiliate Marketing – LinkedIn |
| IRLD | 2 years | Affiliate Marketing Cookies for LinkedIn – LinkedIn |
| barometric[cuid] | 1 year | Used for conversion tracking on the Veritone/Barometric podcast on both linkedin.com (product) and microsites (business.linkedin.com) – LinkedIn |
| tluid | 90 days | Used for unique user identification on web pages for advertising purposes – LinkedIn |
| oribi_cookie_test | Session | To determine whether tracking can be enabled in a current domain – LinkedIn |
| oribi_session | 2 hours | Used to identify a visitor’s session time in a specific domain – LinkedIn |
| oribi_user_guid | 6 months | Used to identify a visitor’s events in different sessions in a specific domain – LinkedIn |
| m_session | 1 day | This cookie is for video functionality for live events by geolocation – Twitter |
| lang | Maximum 30 days | This cookie is for language functionality – Twitter |
| Authorization | Maximum 30 days | This cookie is for video functionality for live events – Twitter |
| fontsLoaded | Maximum 30 days | This cookie is for fonts functionality – Twitter |
| form-lead-gen | Maximum 30 days | This cookie is for Business account functionality – Twitter |
| ssa-calendar- signup | Maximum 30 days | This cookie is for Business account functionality – Twitter |
| mp_ | Maximum 30 days | This cookie analyzes your user interaction on Twitter for product research – Twitter |
| eu_cn | Maximum 30 days | This cookie is for cookie notices – Twitter |
| kampyleInvitePres ented | Maximum 30 days | This cookie is for help center functionality on help.twitter.com – Twitter |
| md_isSurveySubm ittedInSession | Maximum 30 days | This cookie is for help center functionality on help.twitter.com – Twitter |
| aem-lang- preference | Maximum 30 days | This cookie is for language functionality – Twitter |
| lang-preference | Maximum 30 days | This cookie is for language functionality – Twitter |
| csrf_same_site | Maximum 30 days | This cookie is for security – Twitter |
| csrftoken | Maximum 30 days | This cookie is for MoPub authentication – https://www.mopub.com/en/legal/privacy |
| csrftoken | Maximum 30 days | This cookie is for MoPub authentication – https://www.mopub.com/en/legal/privacy |
| ads_prefs | Maximum 30 days | This cookie is to opt-out of ads tracking – Twitter |
| auth_token | Maximum 30 days | This cookie is for account login and authentication – Twitter |
| twid | Maximum 30 days | This cookie is for authentication – Twitter |
| co | Maximum 30 days | This cookie is for testing functionality – Twitter |
| night_mode | Maximum 30 days | This cookie is for night mode functionality – Twitter |
| mbox | Maximum 30 days | This cookie is for marketing on developer.twitter.com – Twitter |
| studio_account | Maximum 30 days | This cookie is for authentication for Twitter Media Studio – Twitter |
| email_uid | Maximum 30 days | This cookie is for authenication by SMS – Twitter |
| cms-csp-nonce | Maximum 30 days | This cookie is for security – Twitter |
| kdt | Maximum 30 days | This cookie is to authenticate a known device – Twitter |
| _mb_tk | Maximum 30 days | This cookie is used for authentication on mobile web – Twitter |
| guest_id_marketin g | Maximum 30 days | This cookie is for marketing when logged out – Twitter |
| guest_id | Maximum 30 days | This cookie is used for authentication – Twitter |
| muc | Maximum 30 days | This cookie is for bot detection – Twitter |
| personalization_id | Maximum 30 days | This cookie tracks activities off Twitter for a personalized experience – Twitter |
| syndication_guest_id | Maximum 30 days | This cookie is for video functionality of Tweets off- Twitter – Twitter |
| muc_ads | Maximum 30 days | This cookie is for advertising – Twitter |
| guest_id_ads | Maximum 30 days | This cookie is for advertising when logged out – Twitter |
| twitter_ads_id | Maximum 30 days | This cookie is for advertising personalization – Twitter |
| uuid | Maximum 30 days | This cookie is for ads tracking – Twitter |
| _ga | Maximum 30 days | Google Analytics – Google |
| lv-uid | Maximum 30 days | This cookie is for video functionality on iOS – Twitter |
| lv-ctx- | Maximum 30 days | This cookie is for video functionality for live events – Twitter |
| lv-ctx-zzz | Maximum 30 days | This cookie is for video functionality for live events – Twitter |
| zipbox_auth_token | Maximum 30 days | This cookie is for legal requests – Twitter |
| zipbox_forms_auth_token | Maximum 30 days | This cookie is used for authentication – Twitter |
| _sl | Maximum 30 days | This cookie is for web authentication and security – Twitter |
| att | Maximum 30 days | This cookie is for authenication and password reset – Twitter |
| gt | Maximum 30 days | This cookie is for external app functionality and authorization – Twitter |
| daa | Maximum 30 days | This cookie is for business account functionality on ads.twitter.com – Twitter |
| app_shell_visited | Maximum 30 days | This cookie is for security and functionality – Twitter |
| csrf_same_site_set | Maximum 30 days | This cookie is for security – Twitter |
| aa_u | Maximum 30 days | This cookie is for Teams functionality – Twitter |
| fr | 90 days | Primary advertising cookie, used to measure, deliver and improve the relevance of the ad. – Facebook |
| oo | 5 years | Used to log opt-outs from advertising. – Facebook |
| c_user | 90 days | Used to authenticate your identity on Facebook. – Facebook |
| PI | 90 days | Used to log that your device or browser is connected via Facebook. – Facebook |
| Xs | 90 days | Used to authenticate your identity on Facebook. – Facebook |
| Csm | 90 days | Indicates when an https is needed to access the Facebook service. – Facebook |
| rc | 7 days | Used to optimize site performance for advertisers. – Facebook |
| Js_ver | 7 days | Logs the age of Facebook javascript files. – Facebook |
| local | 7 days | Identifies the country and language selected by the last user who logged in to the browser or international domain. Used to log in to Facebook. – Facebook |
| sb | 2 years | Identifies the browser for authentication purposes at login. – Facebook |
| datr | 2 years | Identifies browsers for site security and integrity reasons. – Facebook |
| s | 90 days | Used to indicate the last time a person entered their password. – Facebook |
| ick | 2 years | Saves an encryption key used to encrypt cookies. – Facebook |
| sfau | 1 day | Optimizes the retrieval flow after failed login attempts. – Facebook |
| dbln | 2 years | Used to enable device-based logins. – Facebook |
| lu | 2 years | Used to log whether the person decides to stay logged in. – Facebook |
| act, reg_ext_ref, reg_fb_gate, reg_fb_ref, reg_uniqid, x-referer, x-src | Session | Session cookies. Used for analysis and research. – Facebook |
| _gaexp | Depends on the length of the experiment, but typically 90 days. | Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in. |
| _opt_awcid | 24 hours | Used for campaigns mapped to Google Ads Customer IDs. |
| _opt_awmid | 24 hours | Used for campaigns mapped to Google Ads Campaign IDs. |
| _opt_awgid | 24 hours | Used for campaigns mapped to Google Ads Ad Group IDs |
| _opt_awkid | 24 hours | Used for campaigns mapped to Google Ads Criterion IDs |
| _opt_utmc | 24 hours | Stores the last utm_campaign query parameter. |
| _opt_expid | 10 seconds | This cookie is created when running a redirect experiment. It stores the experiment ID, the variant ID and the referrer to the page that’s being redirected. |
| __Secure-3PSIDCC | 1 year | Security: We use security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorized parties. For example, we use cookies known as “SIDs” and “HSIDs”, which contain digitally signed and encrypted records for a user’s Google Account ID and their most recent login date. The combination of these two cookies allows us to block many types of attacks, such as attempts to steal the data you enter in forms on web pages. |
| __Secure-3PAPISID | 2 years | Security: We use security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorized parties. For example, we use cookies known as “SIDs” and “HSIDs”, which contain digitally signed and encrypted records for a user’s Google Account ID and their most recent login date. The combination of these two cookies allows us to block many types of attacks, such as attempts to steal the data you enter in forms on web pages. |
| __Secure-3PSID | 2 years | Security: We use security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorized parties. For example, we use cookies known as “SIDs” and “HSIDs”, which contain digitally signed and encrypted records for a user’s Google Account ID and their most recent login date. The combination of these two cookies allows us to block many types of attacks, such as attempts to steal the data you enter in forms on web pages. |
| ANID | 5 months | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| NID | 1 year | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| 1P_JAR | 30 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| IDE | 4 months | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| CONSENT | 2 years | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| HSID | 540 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| SSID | 540 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| APISID | 540 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| SAPISID | 540 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| OGPC | 60 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| AID | 540 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
| OTZ | 30 days | Advertising: We use cookies to make advertising more engaging for users and more useful for publishers and advertisers. Some common uses of cookies include selecting advertising based on what is relevant to a user, improving campaign performance reports, and preventing the display of ads that the user has already seen. Google uses cookies, such as NID and SID cookies, to help personalize ads in features owned by Google, such as Google Search. For example, we use them to store your most recent searches, your previous interactions with an advertiser’s ads or search results, and your visits to an advertiser’s website. This way, we can show you personalized ads on Google. We also use one or more cookies for advertising shown across the web. One of the most important advertising cookies, known as IDE, is saved in browsers under the domain doubleclick.net. Another, ANID, is saved under the domain google.com. We use other cookies, known as DSID, FLC, AID, TAID, and exchange_uid. Other Google companies, such as YouTube, may also use these cookies to show you more relevant advertisements. Sometimes. advertising cookies can be set in the domain of the site you are visiting. For advertisements we show across the web, cookies known as ‘__gads’ or ‘__gac’ can be set on the website you are visiting. Unlike cookies set on Google domains, these cookies cannot be read by Google when you browse a site other than the one on which they were set. They calculate interactions with advertisements on that particular domain and prevent the same ad from being shown to the same person too many times. Google also uses conversion cookies that give the advertiser the opportunity to determine how many people who clicked on their ad have then bought the relevant products. These cookies show Google and the advertiser that you have clicked on the ad and that you have subsequently visited the site. Conversion cookies are not used for personalized ads, which are highlighted and shown only once. This is made possible by a cookie known as ‘Conversion’, usually set under the domains googleadservices.com or google.com (you can find a list of the domains we use for advertising cookies at the end of this page). Some of our other cookies can also be used to calculate conversion events, for example, DoubleClick and Google Analytics cookies. |
3. HOW TO CONTROL AND DELETE COOKIES
Explicit consent is not required for technical and performance cookies, as they are necessary.
On the other hand, functional and profiling cookies are only set with your consent. You can consent to the use of cookies by clicking on the “Accept cookies” button directly from the Banner.
The first time you visit a site, or after you clear your browser cache, you will see the cookie banner, giving you the options to:
- Accept functional and profiling cookies by clicking on the “Accept cookies” button,
- Refuse functional and profiling cookies by clicking “Reject cookies” in the top right, which closes the banner and only accepts strictly necessary technical cookies and performance cookies,
- Manage your preferences for each category of cookies indicated in this cookie policy by clicking on “Manage”.
Subsequently, you can revoke and / or modify your consents whenever you wish by clearing the cache or simply by calling up the control panel via the “Manage” link in the footer of the Site.
- Google Analytics
This Site uses Google Analytics, a web analytics service provided by Google, Inc. (“Google”), via cookies. The data generated by the cookie about your use of the Site will be sent to a Google server, where it will be saved. Google will use this information to analyze your use of the Site, to compile reports on activities on the Site and to provide additional services to the Site operator relating to the use of the Site and of the Internet. Google will not associate the IP address sent by your browser as part of Google Analytics with other data held by Google. You can prevent cookies being saved by changing the settings in your browser software and by downloading and installing the browser plug-in available at the following link: https://tools.google.com/dlpage/gaoptout, but this may make the functions of the Site less personalized based on your preferences. Information on data processing by Google Analytics can be viewed at https://support.google.com/analytics/answer/6004245.
By using the Site, you consent to the processing of your data by Google as an independent data controller in the manner and for the purposes indicated in the Google privacy policy in relation to the use of Google Analytics, which can be viewed at https://policies.google.com/technologies/partner-sites.
For any further information on anonymized Google cookies, please visit https://support.google.com/analytics/answer/2763052
4. NATURE OF THE PROVISION
The provision of Data using cookies, with the exception of those collected using technical and performance cookies, takes place on the basis of the consent of the Data Subject and is optional. In case of non-acceptance, the user can click on the “Reject cookies” button in the banner and the Data Subject will still be able to browse the Site, although Fondazione will not be able to install cookies for the display of advertising, personalized or otherwise. Alternatively, by clicking on the “Accept cookies” button, the Data Subject consents to the installation of functional and profiling cookies. Data Subjects are free to review their choices at any time, via the “Manage” link in the footer of the Site.
5. RETENTION OF THE DATA
The Data will be retained for the period stated for each category of cookies set. Please see the tables containing the relevant retention periods.
In particular, technical cookies and anonymized performance cookies that only identify you to a limited extent are always active and cannot be disabled. When the technical and performance cookies expire, new cookies will then be set automatically.
However, functional and profiling cookies will always remain inactive and can only be set if explicitly authorized by the Data Subject via the “Accept cookies” button or kept inactive using the “Reject cookies” button. The banner will not appear again unless substantial changes occur (e.g. list of third parties), if the Data Controller is unaware whether a cookie is already saved on the device or if 6 months have passed.
6. SCOPE OF PROCESSING, COMMUNICATION, DISSEMINATION
The Data is processed by in-house Fondazione staff appointed for that purpose as processors. The Data collected to fulfill the aforementioned purposes will also be processed by third parties appointed as such as Data Processors, or depending on the case, will be communicated thereto as independent data controllers, and specifically to: i) companies, bodies and associations that perform related and instrumental services to enable Data Subjects to browse the Site; ii) government bodies, to perform institutional tasks within the limits established by the law and regulations.
In addition, the Data may be made accessible, communicated and transferred to Public Bodies, Judicial Authorities, and Law Enforcement Agencies, which will process them as independent data controllers in order to respond to requests for verification or where expressly provided for by law.
The complete and updated list of the subjects who process the Data as processors and independent data controllers is available upon request by writing to the Data Controller at the email address provided at the beginning of this cookie policy.
7. REDIRECTION TO EXTERNAL SITES
The Fondazione Site uses special tools that incorporate Social Network features directly within the Website (e.g. the Facebook “Insight” function). Page Insights are aggregated statistics created by certain events recorded by Facebook servers when people interact with the Pages and the content associated therewith. These events consist of various data as follows, depending on the specific event:
When you visit a page on our Site and use the Facebook Products (including the “Pages”), the corresponding information, e.g. IP addresses, operating system, browser type, language settings, cookie data, is transmitted by the browser directly to the social network platform (in this case Facebook) and saved thereby.
For information on the purposes, type and methods of collection, processing, use and retention of personal data by the social network platform, and on how to exercise your rights, please consult the privacy policy of the social network at https://www.facebook.com/about/privacy.
8. TRANSFER OUTSIDE THE EU
The Controller may transfer the Data outside the European Union. To this end, in accordance with the privacy legislation, the Data Controller assesses the impact of data transfers and where applicable adopts the most appropriate guarantees (for example, adequacy decisions or Standard Contractual Clauses).
For information on the transfer of personal data collected using third-party cookies, please see the privacy policies of each third party, available on their websites. A list of the third parties can be viewed by clicking the “Manage” button.
9. HOW TO MANUALLY ENABLE OR DISABLE COOKIES IN YOUR BROWSER
Data Subjects can authorize the use of functional and profiling cookies by clicking the “Accept cookies” button directly from the Banner, or can choose which functional and profiling cookies to consent to, using the specific “Manage” link in the Banner, which also refers to the list of third parties.
Data Subjects can reject the use of functional and profiling cookies by clicking the “Reject cookies” button directly from the Banner, or can choose which functional and profiling cookies to refuse consent to, using the specific “Manage” link in the Banner, which also refers to the list of third parties.
You can disable cookies at any time by manually changing your browser settings, as follows:
• Chrome: https://support.google.com/chrome/answer/95647
• Firefox: https://support.mozilla.org/en-US/kb/cookies-information-websites-store-on-your-computer
• Internet Explorer: https://support.microsoft.com/en-us/topic/delete-and-manage-cookies-168dab11-0753-043d-7c16-ede5947fc64d
• Opera: https://help.opera.com/en/latest/web-preferences/#cookies
• Safari: http://support.apple.com/kb/HT1677
If you use a Web browser other than those listed above, please see your browser’s documentation or online help for more information. We further specify that the Data Controller merely acts as a technical intermediary for the links contained in this document and cannot assume any responsibility in the event of any change.
In addition, for more information, Data Subjects can write to the Data Controller at the e-mail address info@fondazionebarilla.com, also provided at the beginning of this cookie policy.
10. RIGHTS OF THE DATA SUBJECT
In relation to the processing of Data collected using cookies, Data Subjects may exercise their rights under the GDPR (Articles 15-22), including:
• to receive confirmation of the existence of the Data and access their content (access rights);
• to update, modify and/or correct the Data (right of rectification);
• to request the deletion or restriction of the processing of Data processed in breach of the law, including when it is not necessary to retain the Data in relation to the purposes for which they were collected or otherwise processed (right to be forgotten.and right to restriction);
• to object to the processing (right to object);
• to withdraw consent, where given, without jeopardizing the lawfulness of the processing based on the consent given prior to withdrawal, via the “Manage” section;
• to lodge a complaint with the Supervisory Authority in the event of breach of the data protection regulations;
• to receive an electronic copy of the Data relating to them provided as part of the processing and to request that the said Data be transmitted to another data controller (right to data portability).
To exercise these rights, you can write to the Data Controller at the e-mail address info@fondazionebarilla.com or using the other details provided at the beginning of this cookie policy.
11. CHANGES TO THE COOKIE POLICY
This cookie policy may be subject to change over time. Visitors are therefore invited to check this page from time to time. For this purpose, the date on which it was updated is provided in the policy.
Date of latest change: 05/23/2022