{"id":1137,"date":"2022-06-01T15:58:30","date_gmt":"2022-06-01T13:58:30","guid":{"rendered":"https:\/\/staging.fondazionebarilla.com\/cookie-policy\/"},"modified":"2025-03-21T17:26:32","modified_gmt":"2025-03-21T16:26:32","slug":"cookie-policy","status":"publish","type":"page","link":"https:\/\/staging.fondazionebarilla.com\/en\/cookie-policy\/","title":{"rendered":"Cookie Policy"},"content":{"rendered":"\n
\n

Center text consent mode<\/strong><\/p>\n\n\n\n

Paragraph 01: What cookies are<\/strong><\/p>\n\n\n\n

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<\/a><\/p>\n\n\n\n

Paragraph 02: Strictly necessary cookies<\/strong><\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Paragraph 03: Performance cookies<\/strong><\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Paragraph 04: Functionality cookies<\/strong><\/p>\n\n\n\n

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).<\/p>\n\n\n\n

Paragraph 05: Profiling cookies<\/strong><\/p>\n\n\n\n

Profiling cookies analyze how users browse the site and their habits, purchases and behavior, to provide commercial communications in line with their preferences.<\/p>\n\n\n\n

COOKIE POLICY<\/strong><\/p>\n\n\n\n

Barilla Foundation, with its registered office in Parma at Via Madre Teresa di Calcutta, 3\/a \u2013 Tax Code and VAT Number 02716600347, acting as the Data Controller, info@fondazionebarilla.com, (hereinafter \u201cFondazione\u201d) informs users, in accordance with Regulation (EU) 679\/2016 (hereinafter \u201cGDPR\u201d) and the legislation, including Italian legislation, on the protection of personal data applicable at the time (hereinafter \u201cPrivacy Legislation\u201d), that the personal data (hereinafter \u201cData\u201d) relating to users (hereinafter, \u201cData Subjects\u201d) of the website (hereinafter \u201cSite\u201d), collected using cookies will be processed in the manner and for the purposes indicated in this policy.<\/p>\n\n\n\n

1.         DATA CONTROLLERS AND JOINT CONTROLLERS<\/strong><\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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-\u00e0-vis Facebook Ireland can be found in the Facebook Ireland Data Policy at https:\/\/www.facebook.com\/about\/privacy.<\/p>\n\n\n\n

2.         DATA: COOKIES<\/strong><\/p>\n\n\n\n

Cookies are small text files that are saved on the Data Subject\u2019s 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\u2019s device each time the same site is browsed in the future. Cookies also enable the saving of Data Subjects\u2019 browsing preferences, offering them a more functional experience of the Site, and making the content on the Site as personalized as possible.<\/p>\n\n\n\n

TYPES OF COOKIES<\/strong><\/p>\n\n\n\n

Our Site uses the following categories of cookies, which may pertain to Fondazione or to third parties.<\/p>\n\n\n\n

2.1 TECHNICAL COOKIES<\/strong><\/p>\n\n\n\n

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. <\/p>\n\n\n\n

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 \u201csession\u201d and persistent technical cookies<\/strong>, such as:<\/p>\n\n\n\n

Cookies<\/th>Expiration<\/th>Description and provider<\/th><\/tr><\/thead>
_iub_cs-70853207<\/td>12 months<\/td>Third-party technical cookie generated by Iubenda to save the cookie preferences expressed by the user in the Cookie Banner<\/td><\/tr>
 <\/td> <\/td> <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

2.2 PERFORMANCE COOKIES<\/strong><\/p>\n\n\n\n

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).<\/p>\n\n\n\n

Cookies<\/th>Expiration<\/th>Description and provider<\/th><\/tr><\/thead>
_ga<\/td>2 years<\/td>Used to distinguish users.<\/td><\/tr>
_gid<\/td>24 hours<\/td>Used to distinguish users.<\/td><\/tr>
_ga_<\/container-id><\/td>2 years<\/td>Used to persist session state.<\/td><\/tr>
_gac_gb_<\/container-id><\/td>90 days<\/td>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<\/a><\/td><\/tr>
_gat<\/td>1 minute<\/td>Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property- id>
.<\/td><\/tr>
AMP_TOKEN<\/td>30 seconds to 1 year<\/td>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.<\/td><\/tr>
_gac_<\/property-id><\/td>90 days<\/td>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<\/a><\/td><\/tr>
__utma<\/td> 2 years from set\/update<\/td> 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.<\/td><\/tr>
__utmt<\/td>10 minutes<\/td>Used to throttle request rate.<\/td><\/tr>
__utmb<\/td>30 mins from set\/update<\/td>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.<\/td><\/tr>
__utmc<\/td>End of browser session<\/td>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.<\/td><\/tr>
__utmz<\/td>6 months from set\/update<\/td>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.<\/td><\/tr>
__utmv<\/td>2 years from set\/update<\/td>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<\/a><\/td><\/tr>
__utmx<\/td>18 months<\/td>Used to determine a user’s inclusion in an experiment.<\/td><\/tr>
__utmxx<\/td>18 months<\/td>Used to determine the expiry of experiments a user has been included in.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

2.3 FUNCTIONALITY COOKIES<\/strong><\/p>\n\n\n\n

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).<\/p>\n\n\n\n

2.4 PROFILING COOKIES<\/strong><\/p>\n\n\n\n

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<\/strong>:<\/p>\n\n\n\n

Cookies<\/th>Expiration<\/th>Description and provider<\/th><\/tr><\/thead>
t<\/td>30 days<\/td>Stores informtion on the advertisement seen by the user is order to provide a correct conversion report – Datafront<\/a><\/td><\/tr>
e <\/td>12 months <\/td>Backup cookie to store User-ID for a longer time period – Datafront<\/a><\/td><\/tr>
o<\/td>60 days<\/td>Stores the user optout status – Datafront<\/a><\/td><\/tr>
p<\/td>15 days<\/td>Stores User-ID – Datafront<\/a><\/td><\/tr>
tui<\/td>30 days<\/td>Stores information on the user (Dynamic Creative Engine) – Datafront<\/a><\/td><\/tr>
tev<\/td>30 days<\/td>Stores information on the products seen (Dynamic Creative Engine) – Datafront<\/a><\/td><\/tr>
<\/td><\/td><\/td><\/tr>
uuid2<\/td>Persistent \/ 90 days<\/td>This cookie contains a unique randomly-generated value that enables the Platform to distinguish browsers and devices.
It is matched against information \u2013 such as advertising interest segments and histories of ads shown in the browser or device \u2013 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\u2019s 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\u2019 or other third parties\u2019 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 \u201c-1\u201d. – Xandr<\/a><\/td><\/tr>
uids<\/td>Persistent \/ 90 days<\/td>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<\/a><\/td><\/tr>
usersync<\/td>Persistent \/ 90 days<\/td>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<\/a><\/td><\/tr>
icu<\/td>Persistent \/ 90 days<\/td>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<\/a><\/td><\/tr>
anj<\/td>Persistent \/ 90 days<\/td>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<\/a><\/td><\/tr>
<\/td><\/td><\/td><\/tr>
UserMatchHistory<\/td>30 days<\/td>LinkedIn Ads ID syncing – Linkedin<\/td><\/tr>
AnalyticsSyncHistory<\/td>30 days<\/td>Used to store information about when a synchronization with the lms_analytics cookies occurred for users in designated countries – LinkedIn<\/td><\/tr>
li_oatml<\/td>30 days<\/td>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<\/td><\/tr>
lms_ads<\/td>30 days<\/td>Used to identify LinkedIn Users in designated countries for advertising purposes<\/td><\/tr>
lms_analytics<\/td>30 days<\/td>Used to identify LinkedIn Users in designated countries for analytics purposes – LinkedIn<\/td><\/tr>
li_fat_id<\/td>30 days<\/td>Indirect user identifier for Users for conversion tracking, retargeting and analytics purposes – LinkedIn<\/td><\/tr>
li_sugr<\/td>30 days<\/td>Used to make a probabilistic association of the user\u2019s identity outside the designated countries – LinkedIn<\/td><\/tr>
U<\/td>3 months<\/td>Browser identifier for users outside the designated countries – LinkedIn<\/td><\/tr>
_guid<\/td>90 days<\/td>Used to identify a LinkedIn User for advertising purposes via Google Ads – LinkedIn<\/td><\/tr>
BizographicsOptOut<\/td>10 years<\/td>To determine opt-out status for third-party tracking – LinkedIn<\/td><\/tr>
li_giant<\/td>7 days<\/td>Indirect identifier for LinkedIn user groups used for conversion tracking – LinkedIn<\/td><\/tr>
<\/td><\/td><\/td><\/tr>
UserMatchHistory<\/td>30 days<\/td>LinkedIn Ads ID syncing – Linkedin<\/td><\/tr>
li_oatml<\/td>30 days<\/td>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<\/td><\/tr>
lms_ads<\/td>30 days<\/td>Used to identify LinkedIn Users in designated countries for advertising purposes – LinkedIn<\/td><\/tr>
li_fat_id<\/td>30 days<\/td>Indirect user identifier for Users for conversion tracking, retargeting and analytics purposes – LinkedIn<\/td><\/tr>
li_sugr<\/td>90 days<\/td>Used to make a probabilistic association of the user\u2019s identity outside the designated countries – LinkedIn<\/td><\/tr>
U<\/td>3 months<\/td>Browser identifier for users outside the designated countries – LinkedIn<\/td><\/tr>
_guid<\/td>90 days<\/td>Used to identify a LinkedIn User for advertising purposes via Google Ads – LinkedIn<\/td><\/tr>
A3<\/td>1 year<\/td>Advertising\/targeting cookies for Yahoo – LinkedIn<\/td><\/tr>
anj<\/td>3 months<\/td>Advertising\/targeting cookies for AppNexus – LinkedIn<\/td><\/tr>
uuids<\/td>3 months<\/td>Used by AppNexus ad nexus analytics – LinkedIn<\/td><\/tr>
ELOQUA<\/td>2 years<\/td>Used for ELOQUA tracking – LinkedIn<\/td><\/tr>
ELQSTATUS<\/td>2 years<\/td>Used for ELOQUA tracking – LinkedIn<\/td><\/tr>
dpm<\/td>6 months<\/td>Sends events to Adobe Audience Manager – LinkedIn<\/td><\/tr>
dextp<\/td>6 months<\/td>Logs the last time a data sync call was made – LinkedIn<\/td><\/tr>
demdex<\/td>6 months<\/td>Visitor identification – LinkedIn<\/td><\/tr>
dst<\/td>6 months<\/td>Logs when an error occurs sending data to its destination. Used as part of Adobe Audience Manager – LinkedIn<\/td><\/tr>
lnkd<\/td>6 months<\/td>Sends events to Adobe Audience Manager – LinkedIn<\/td><\/tr>
aam_uuid<\/td>30 days <\/td>Set to sync ID for Adobe Audience Manager – LinkedIn<\/td><\/tr>
MUID<\/td>1 year<\/td>Bing tracking – LinkedIn<\/td><\/tr>
MR<\/td>6 months<\/td>Bing tracking – LinkedIn<\/td><\/tr>
MR2<\/td>6 months<\/td>Bing tracking – LinkedIn<\/td><\/tr>
IDE<\/td>2 years <\/td>Advertising\/targeting cookies for DoubleClick – LinkedIn<\/td><\/tr>
fr<\/td>3 months<\/td>Advertising\/targeting cookies for Facebook – LinkedIn<\/td><\/tr>
personalization_id<\/td>2 years <\/td>Advertising\/targeting cookies for Twitter – LinkedIn<\/td><\/tr>
GUC<\/td>5 months<\/td>Yahoo conversion tracking – LinkedIn<\/td><\/tr>
B<\/td>1 year<\/td>Yahoo conversion tracking – LinkedIn<\/td><\/tr>
test_cookie<\/td>1 day<\/td>Testing for cookie installation permissions in the user’s browser – LinkedIn<\/td><\/tr>
_gcl_au<\/td>3 months <\/td>Used via Google Analytics to understand user interactions with the site and advertising – LinkedIn<\/td><\/tr>
_gcl_aw<\/td>3 months <\/td>Used via Google Ads to understand user interactions with the site and advertising – LinkedIn<\/td><\/tr>
_gcl_dc<\/td>3 months <\/td>Used via Google Campaign Manager and DV 360 to understand user interactions with the site and advertising – LinkedIn<\/td><\/tr>
brwsr<\/td>2 years<\/td>Affiliate Marketing Cookies for LinkedIn – LinkedIn<\/td><\/tr>
ABSELB<\/td>2 years<\/td>Load balancing cookies for Affiliate Marketing – LinkedIn<\/td><\/tr>
IRLD<\/td>2 years<\/td>Affiliate Marketing Cookies for LinkedIn – LinkedIn<\/td><\/tr>
barometric[cuid]<\/td>1 year<\/td>Used for conversion tracking on the Veritone\/Barometric podcast on both linkedin.com (product) and microsites (business.linkedin.com) – LinkedIn<\/td><\/tr>
tluid<\/td>90 days<\/td>Used for unique user identification on web pages for advertising purposes – LinkedIn<\/td><\/tr>
oribi_cookie_test<\/td>Session<\/td>To determine whether tracking can be enabled in a current domain – LinkedIn<\/td><\/tr>
oribi_session<\/td>2 hours<\/td>Used to identify a visitor\u2019s session time in a specific domain – LinkedIn<\/td><\/tr>
oribi_user_guid<\/td>6 months<\/td>Used to identify a visitor\u2019s events in different sessions in a specific domain – LinkedIn<\/td><\/tr>
<\/td><\/td><\/td><\/tr>
m_session<\/td>1 day<\/td>This cookie is for video functionality for live events by geolocation – Twitter<\/a><\/td><\/tr>
lang<\/td>Maximum 30 days<\/td>This cookie is for language functionality – Twitter<\/a><\/td><\/tr>
Authorization<\/td>Maximum 30 days<\/td>This cookie is for video functionality for live events – Twitter<\/a><\/td><\/tr>
fontsLoaded<\/td>Maximum 30 days<\/td>This cookie is for fonts functionality – Twitter<\/a><\/td><\/tr>
form-lead-gen<\/td>Maximum 30 days<\/td>This cookie is for Business account functionality – Twitter<\/a><\/td><\/tr>
ssa-calendar- signup<\/td>Maximum 30 days<\/td>This cookie is for Business account functionality – Twitter<\/a><\/td><\/tr>
mp_<\/td>Maximum 30 days<\/td>This cookie analyzes your user interaction on Twitter for product research – Twitter<\/a><\/td><\/tr>
eu_cn<\/td>Maximum 30 days<\/td>This cookie is for cookie notices – Twitter<\/a><\/td><\/tr>
kampyleInvitePres ented<\/td>Maximum 30 days<\/td>This cookie is for help center functionality on help.twitter.com – Twitter<\/a><\/td><\/tr>
md_isSurveySubm ittedInSession<\/td>Maximum 30 days<\/td>This cookie is for help center functionality on help.twitter.com – Twitter<\/a><\/td><\/tr>
aem-lang- preference<\/td>Maximum 30 days<\/td>This cookie is for language functionality – Twitter<\/a><\/td><\/tr>
lang-preference<\/td>Maximum 30 days<\/td>This cookie is for language functionality – Twitter<\/a><\/td><\/tr>
csrf_same_site<\/td>Maximum 30 days<\/td>This cookie is for security – Twitter<\/a><\/td><\/tr>
csrftoken<\/td>Maximum 30 days<\/td>This cookie is for MoPub authentication – https:\/\/www.mopub.com\/en\/legal\/privacy<\/a><\/td><\/tr>
csrftoken<\/td>Maximum 30 days<\/td>This cookie is for MoPub authentication – https:\/\/www.mopub.com\/en\/legal\/privacy<\/a><\/td><\/tr>
ads_prefs<\/td>Maximum 30 days<\/td>This cookie is to opt-out of ads tracking – Twitter<\/a><\/td><\/tr>
auth_token<\/td>Maximum 30 days<\/td>This cookie is for account login and authentication – Twitter<\/a><\/td><\/tr>
twid<\/td>Maximum 30 days<\/td>This cookie is for authentication – Twitter<\/a><\/td><\/tr>
co<\/td>Maximum 30 days<\/td>This cookie is for testing functionality – Twitter<\/a><\/td><\/tr>
night_mode<\/td>Maximum 30 days<\/td>This cookie is for night mode functionality – Twitter<\/a><\/td><\/tr>
mbox<\/td>Maximum 30 days<\/td>This cookie is for marketing on developer.twitter.com – Twitter<\/td><\/tr>
studio_account<\/td>Maximum 30 days<\/td>This cookie is for authentication for Twitter Media Studio – Twitter<\/a><\/td><\/tr>
email_uid<\/td>Maximum 30 days<\/td>This cookie is for authenication by SMS – Twitter<\/a><\/td><\/tr>
cms-csp-nonce<\/td>Maximum 30 days<\/td>This cookie is for security – Twitter<\/a><\/td><\/tr>
kdt<\/td>Maximum 30 days<\/td>This cookie is to authenticate a known device – Twitter<\/a><\/td><\/tr>
_mb_tk<\/td>Maximum 30 days<\/td>This cookie is used for authentication on mobile web – Twitter<\/a><\/td><\/tr>
guest_id_marketin g<\/td>Maximum 30 days<\/td>This cookie is for marketing when logged out – Twitter<\/a><\/td><\/tr>
guest_id<\/td>Maximum 30 days<\/td>This cookie is used for authentication – Twitter<\/a><\/td><\/tr>
muc<\/td>Maximum 30 days<\/td>This cookie is for bot detection – Twitter<\/a><\/td><\/tr>
personalization_id<\/td>Maximum 30 days<\/td>This cookie tracks activities off Twitter for a personalized experience – Twitter<\/a><\/td><\/tr>
syndication_guest_id<\/td>Maximum 30 days<\/td>This cookie is for video functionality of Tweets off- Twitter – Twitter<\/a><\/td><\/tr>
muc_ads<\/td>Maximum 30 days<\/td>This cookie is for advertising – Twitter<\/a><\/td><\/tr>
guest_id_ads<\/td>Maximum 30 days<\/td>This cookie is for advertising when logged out – Twitter<\/a><\/td><\/tr>
twitter_ads_id<\/td>Maximum 30 days<\/td>This cookie is for advertising personalization – Twitter<\/a><\/td><\/tr>
uuid<\/td>Maximum 30 days<\/td>This cookie is for ads tracking – Twitter<\/a><\/td><\/tr>
_ga<\/td>Maximum 30 days<\/td>Google Analytics – Google<\/a><\/td><\/tr>
lv-uid<\/td>Maximum 30 days<\/td>This cookie is for video functionality on iOS – Twitter<\/a><\/td><\/tr>
lv-ctx-<\/td>Maximum 30 days<\/td>This cookie is for video functionality for live events – Twitter<\/a><\/td><\/tr>
lv-ctx-zzz<\/td>Maximum 30 days<\/td>This cookie is for video functionality for live events – Twitter<\/a><\/td><\/tr>
zipbox_auth_token<\/td>Maximum 30 days<\/td>This cookie is for legal requests – Twitter<\/a><\/td><\/tr>
zipbox_forms_auth_token<\/td>Maximum 30 days<\/td>This cookie is used for authentication – Twitter<\/a><\/td><\/tr>
_sl<\/td>Maximum 30 days<\/td>This cookie is for web authentication and security – Twitter<\/a><\/td><\/tr>
att<\/td>Maximum 30 days<\/td>This cookie is for authenication and password reset – Twitter<\/a><\/td><\/tr>
gt<\/td>Maximum 30 days<\/td>This cookie is for external app functionality and authorization – Twitter<\/a><\/td><\/tr>
daa<\/td>Maximum 30 days<\/td>This cookie is for business account functionality on ads.twitter.com – Twitter<\/a><\/td><\/tr>
app_shell_visited<\/td>Maximum 30 days<\/td>This cookie is for security and functionality – Twitter<\/a><\/td><\/tr>
csrf_same_site_set<\/td>Maximum 30 days<\/td>This cookie is for security – Twitter<\/a><\/td><\/tr>
aa_u<\/td>Maximum 30 days<\/td>This cookie is for Teams functionality – Twitter<\/a><\/td><\/tr>
<\/td><\/td><\/td><\/tr>
fr<\/td>90 days<\/td>Primary advertising cookie, used to measure, deliver and improve the relevance of the ad. – Facebook<\/a><\/td><\/tr>
oo<\/td>5 years<\/td>Used to log opt-outs from advertising. – Facebook<\/a><\/td><\/tr>
c_user<\/td>90 days<\/td>Used to authenticate your identity on Facebook. – Facebook<\/a><\/td><\/tr>
PI<\/td>90 days<\/td>Used to log that your device or browser is connected via Facebook. – Facebook<\/a><\/td><\/tr>
Xs<\/td>90 days<\/td>Used to authenticate your identity on Facebook. – Facebook<\/a><\/td><\/tr>
Csm<\/td>90 days<\/td>Indicates when an https is needed to access the Facebook service. – Facebook<\/a><\/td><\/tr>
rc<\/td>7 days<\/td>Used to optimize site performance for advertisers. – Facebook<\/a><\/td><\/tr>
Js_ver<\/td>7 days<\/td>Logs the age of Facebook javascript files. – Facebook<\/a><\/td><\/tr>
local<\/td>7 days<\/td>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<\/a><\/td><\/tr>
sb<\/td>2 years<\/td>Identifies the browser for authentication purposes at login. – Facebook<\/a><\/td><\/tr>
datr<\/td>2 years<\/td>Identifies browsers for site security and integrity reasons. – Facebook<\/a><\/td><\/tr>
s<\/td>90 days<\/td>Used to indicate the last time a person entered their password. – Facebook<\/a><\/td><\/tr>
ick<\/td>2 years<\/td>Saves an encryption key used to encrypt cookies. – Facebook<\/a><\/td><\/tr>
sfau<\/td>1 day<\/td>Optimizes the retrieval flow after failed login attempts. – Facebook<\/a><\/td><\/tr>
dbln<\/td>2 years<\/td>Used to enable device-based logins. – Facebook<\/a><\/td><\/tr>
lu<\/td>2 years<\/td>Used to log whether the person decides to stay logged in. – Facebook<\/a><\/td><\/tr>
act, reg_ext_ref, reg_fb_gate, reg_fb_ref, reg_uniqid, x-referer, x-src<\/td>Session<\/td>Session cookies. Used for analysis and research. – Facebook<\/a><\/td><\/tr>
<\/td><\/td><\/td><\/tr>
_gaexp<\/td>Depends on the length of the experiment, but typically 90 days.<\/td>Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in.<\/td><\/tr>
_opt_awcid<\/td>24 hours<\/td>Used for campaigns mapped to Google Ads Customer IDs.<\/td><\/tr>
_opt_awmid<\/td>24 hours<\/td>Used for campaigns mapped to Google Ads Campaign IDs.<\/td><\/tr>
_opt_awgid<\/td>24 hours<\/td>Used for campaigns mapped to Google Ads Ad Group IDs<\/td><\/tr>
_opt_awkid<\/td>24 hours<\/td>Used for campaigns mapped to Google Ads Criterion IDs<\/td><\/tr>
_opt_utmc<\/td>24 hours<\/td>Stores the last utm_campaign
 query parameter.<\/td><\/tr>
_opt_expid<\/td>10 seconds<\/td>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.<\/td><\/tr>
__Secure-3PSIDCC<\/td>1 year<\/td>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 \u201cSIDs\u201d and \u201cHSIDs\u201d, which contain digitally signed and encrypted records for a user\u2019s 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.<\/td><\/tr>
__Secure-3PAPISID<\/td>2 years<\/td>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 \u201cSIDs\u201d and \u201cHSIDs\u201d, which contain digitally signed and encrypted records for a user\u2019s 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.<\/td><\/tr>
__Secure-3PSID<\/td>2 years<\/td>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 \u201cSIDs\u201d and \u201cHSIDs\u201d, which contain digitally signed and encrypted records for a user\u2019s 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.<\/td><\/tr>
ANID<\/td>5 months<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
NID<\/td>1 year<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
1P_JAR<\/td>30 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
IDE<\/td>4 months<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
CONSENT<\/td>2 years<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
HSID<\/td>540 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
SSID<\/td>540 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
APISID<\/td>540 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
SAPISID<\/td>540 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
OGPC<\/td>60 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
AID<\/td>540 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr>
OTZ<\/td>30 days<\/td>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\u2019s 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 \u2018__gads\u2019 or \u2018__gac\u2019 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 \u2018Conversion\u2019, 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.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

3. HOW TO CONTROL AND DELETE COOKIES<\/strong><\/p>\n\n\n\n

Explicit consent is not required for technical and performance cookies, as they are necessary.<\/p>\n\n\n\n

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 \u201cAccept cookies\u201d button directly from the Banner.<\/p>\n\n\n\n

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:<\/p>\n\n\n\n