Waitrose.com and Waitrose App Cookies and Tracking

So that you can make full use of the personalised features on our website, your computer, mobile phone or other device (all referred to here as device) will need to accept cookies.

Here you can see what cookies may be sent to your device by waitrose.com and what we use each cookie for. To manage your cookie preferences you can set your browser to reject cookies (see the ‘Help’ menu of your browser to find out how to do this). If you disable cookies please bear in mind that certain personalised features of this website cannot be provided to you and functionality we feel supports your shopping journey may not work.

Please note that blocking cookies on your web browser does not automatically apply the same changes in the Waitrose app. If you want to block cookies in the app as well, you will need to make changes in your app's Privacy Settings (which is found within the Account area).

Manage your cookies

Essential

Technical

These are essential cookies that support the technical functionality of our website.

Domain Cookie Name Description Scope and Expiry
.waitrose.com ADRUM The purpose of this cookie is technical monitoring of the server
load Example content: "s=1522793539673&r=
http://www.waitrose.com/?0"
Session
.waitrose.com JSESSIONID As our website is split over several servers to improve
performance, this cookie allows us to direct the visitor's
requests to the same server each time, increasing the speed
of the website. Example content: "00009YWx_QLozIjz7x64a0
mMGWC:14re3c682"
Session
.waitrose.com WC_ACTIVEPOINTER This cookie remembers which branch a visitor has previously
selected. This is important as different branches have
different ranges of products, so we can use this cookie to
determine which products to display to the visitor when they
browse our website. Example content: "-11,10235"
Session
.waitrose.com WC_AUTHENTICATION_{####} This cookie provides security when using the website: if a
visitor has left their browser open and not logged out, this
cookie will ensure that they are automatically logged out after
30 minutes of inactivity. Example content: "%2d1002%2cHGD
jhX1NgRbML72pDAquqLDZzGQ%3d"
Session
.waitrose.com WC_GENERIC_ACTIVITYDATA This cookie remembers the preferences of a guest visitor, such
as which language or branch they choose, so that we can
personalise the site for them when they return. Example
content: "[2290123714:true:false:0:SXMArLeVRxtqe4lTMN9tC
EJQFG8=][com.ibm.commerce.context.globalization.
GlobalizationContext|-11&GBP&-11&GBP][com.ibm.commerce
.context.experiment.ExperimentContext|null][com.ibm.
commerce.context.audit.AuditContext|null][com.ibm.
commerce.context.base.BaseContext|10317&-1002&-1002&-1]
[CTXSETNAME|Store][com.ibm.commerce.catalog.
businesscontext.CatalogContext|null&null&false&false&false]
[com.ibm.commerce.store.facade.server.context.
StoreGeoCodeContext|null&null&null&null&null&null][com.ibm
.commerce.context.entitlement.EntitlementContext|null&null&
null&null&null&null&null][com.waitrose.wec.common.
commandcontext.WRCommandContext|null&null&null&null&
null&null&null&null&null&null&null&null&null&null&null&null
&null]"
Session
.waitrose.com WC_PERSISTENT If a visitor selects the Remember Me option when logging
on to the website, this cookie allows us to remember them
when using the website at a later date from the same device.
On returning, visitors will be able to view certain pages as if
they were logged in, however if they view or change any
personal information or checkout, they will be prompted to
login. Example content: "DRro3RrjuIRp4hAewnaE/+tbTPk=
;2018-04-15+09:51:36.397_1523782211119-113140_10235
_485599810,-11,GBP_10235"
Persistent, 28 days
.waitrose.com WC_SESSION_ESTABLISHED This cookie is used to check we have stored a visitor's data
in the secure fast-access part of our server. This ensures
a faster website, which means a more efficient visit.
Example content: "true"
Session
.waitrose.com WC_USER_AUTHENTICATED This cookie helps us recognise a visitor so we can display a
welcome message and they can post comments on our
forums and recipes. Example content:
"YmFjayBNciBZYW5pbg=="
Session
.waitrose.com WC_USER_REMEMBERED This cookie helps us recognise a visitor so we can display a
welcome message and they can post comments on our
forums and recipes. Example content: "TXIgWWFuaW4="
Session
.waitrose.com WC_USERACTIVITY_-{####} This cookie allows us to identify a logged in customer and
their various preferences, such as preferred language and
which product assortment is relevant to them. It helps us
to personalise the website for each visitor. Example
content: "485599810,10235,0,null,1523782296404,
1523784892716
,null,null,null,null,q+LGSHqk7yFIvGCFofeA6+/qhIqeTELJl33
Tc8wOPsKr4tdcWmzwzAMzpYN+2ZPey7co+1f/c53J z7whM
9vzStyES9kPJbeYP30l56bpCz8FY3r/tpi9c6MtmaG7u
WDXYTO0hCQz/2g9bGDSerrx2ECA ng6+vZubDyT+CetduB
vvl2FdQmPRCjUqtHJ71MguFJSm4R
KxKgcTeC4kXAgYhpU7fZw="
Session
www.waitrose.com ADRUM_BT1 The purpose of this cookie is technical monitoring of the
server load Example content: "R:0|i:780667|e:17"
Persistent, 1 minute
www.waitrose.com ADRUM_BTa The purpose of this cookie is technical monitoring of the
server load Example content: "R:0|g:37d29b70-8871-
4cb2-8572-41675121d6c8"
Persistent, 1 minute
www.waitrose.com ADRUM_BTs The purpose of this cookie is technical monitoring of the
server load Example content: "R:0|s:f"
Persistent, 1 minute
www.waitrose.com JSESSIONID As our website is split over several servers to improve
performance, this cookie allows us to direct the visitor's
requests to the same server each time, increasing the speed
of the website. Example content: "00009YWx_QLozIjz7x64a
0mMGWC:14re3c682"
Session
www.waitrose.com sc.ASP.NET_SESSIONID That is a cookie that ASP.NET uses to store a unique
identifier for a site visit. ASP.NET is a Microsoft
framework for building websites. Example content:
"jao0igprxhnqq2wupzk3aia4"
Session
www.waitrose.com sc.UserId That is a cookie that ASP.NET uses to store a unique identifier
for a user. ASP.NET is a Microsoft framework for building
websites. Example content: "da71d3e0-ebfc-4e2c-b38d-
5e777189f80e"
Persistent, 1 year
www.waitrose.com wecInvalidation This cookie allows our platform to manage trolley data
displayed to customers. Example content:
"|https:TrolleyCollection|http:TrolleyCollection|http:Header
TrolleyData|http:HeaderDetails|http:MegaMenuCollection|"
Session
www.waitrose.com wtr_ca This cookie is used as a flag to see if the web browser has
been shown the cookie warning banner. If the cookie is
not found then the banner is shown and the cookie is placed.
If it is found then no banner is shown. Example content: "1"
Persistent, 1 year
www.waitrose.com WTR_PERSISTENT This cookie helps us to identify returning customers from the
same device and will be able to view certain pages as if they
were logged in, however if they view or change any
personal information or checkout, they will be prompted to
login. Example content: "1"
Persistent, 28 days
www.waitrose.com WTR_SSR_USER This cookie helps us to identify a group of visitors, the
cookie will be used to render page on server side
Session
www.waitrose.com wtr_status This session cookie is set during a successful login. It
contains no 'real' data, but helps to display the header
(signed in vs Guest)
Session
www.waitrose.com wtr_wc_np This cookie helps us to redirect specific set of users to our
new platform (beta site).
Persistent, 28 days
www.waitrose.com access_token This cookie contains a unique authentication token that
remembers the identity of an authenticated visitor to the
website. Example content: "eyJhbGciOiJIUzI1NiJ9.eyJhd
WQiOiJ3YWl0cm9zZS5jb20iLCJpc3MiOiJ3YWl0cm9zZS5j
b20iLCJzdWIiOiItMSIsImp0aSI6ImZmZmZmZmZmLWZm
ZmYtZmZmZi1mZmZmLWZmZmZmZmZmZmZmZiIsImV
4cCI6MTU2ODI3Mjk2MiwiaWF0IjoxNTY4MjcxMTYyLCJu
YmYiOjE1NjgyNzExNjIsImh0dHA6Ly93YWl0cm9zZS5jb2
0vY3VzdG9tZXJfaWQiOiItMSIsImh0dHA6Ly93YWl0cm9z
ZS5jb20vcHJpbmNpcGFsX2lkIjoiLTEiLCJodHRwOi8vd2Fp
dHJvc2UuY29tL3JvbGVzIjpbXSwiaHR0cDovL3dhaXRyb3
NlLmNvbS9wZXJtaXNzaW9ucyI6W10sImh0dHA6Ly93Y
Wl0cm9zZS5jb20vdG91Y2hwb2ludCI6IldFQl9BUFAifQ.3
WR_8cA6giTSXMK7dcW3hShKaBTrQNWBW3RuoZElZ3M"
 
www.waitrose.com refresh_token This cookie contains a unique authentication token that can keep an authenticated website visitor signed in for up to 30 days. Example content: "ffffffff-ffff-ffff-ffff-ffffffffffff"  
www.waitrose.com
akacd_mfe_phased_release_prod
While we release versions of pages powered by new applications, this cookie allows us to gradually and safely increase the share of traffic to the new version
 
www.waitrose.com
mfe_enabled
While we release versions of pages powered by new applications, this cookie allows us to direct the visitor's requests to the same version each time, during a single session
 

Monetate

We're constantly working to optimise our website for customers, so that you view what's most relevant to you. These cookies are used to power our testing tool that allows us to show different versions of the same page to different visitors, so we can assess which page layout is best.

For Privacy Policy click here.

Domain Cookie Name Description Scope and Expiry
.waitrose.com mt.i-lbx Used when serving lightboxes (modals or pop-ups to clearly display information to the customer on any page). The cookie prevents the lightbox showing again for the specified time period. 

Expiry: dependent on the setting in the action:

Once ever is 2 years

Once per x days is x days

Once per session is a session cookie

 

.waitrose.com mt

Saving page events if we aren’t able to send them before the page changes, to send in the next page load.

Persistent, 2 years
.waitrose.com mt.v Tracks visitors across the site to provide analytics for Monetate experiences and also tracks products viewed, carted and purchased. Persistent, 2 years

Analytics/Performance

Google Analytics

We use Google Analytics for tracking and reporting of website traffic. This information can be used to gain customer insight and improve the way our site works. Google Analytics does not collect any personal information.

For Privacy Policy click here.

To opt out of the cookies click here.

Domain Cookie Name Description Scope and Expiry    
.google.com SIDCC Security cookie to protect users data from unauthorised access Persistent, 66 days    
.waitrose.com _ga This cookie allows to uniquely identify website users. It contains a randomly generated number associated with the visitor and is used to calculate visitor, session and campaign data for site analytics. Example content: "GA1.2.1620520034.1522825006" Persistent, 2 years    
.waitrose.com _gat This cookie is used to throttle the request rate - limiting the collection of data on high traffic sites. Example content: "1" Persistent, 10 minutes    
.waitrose.com _gat_UA-{########-#} This cookie is used to throttle the request rate - limiting the collection of data on high traffic sites. Example content: "1" Persistent, 10 minutes    
.waitrose.com _gid Used to distinguish users and pages visited, with a timestamp. Example content: "GA1.2.903486210.1522793519" Persistent, 24 hours    
.waitrosecare.secure.force.com __utma Collects data such as number of times a visitor has visited the site, and when their first and last visits occurred to our Help & Support site. Example content: "1.2045696207.1522825080.1522825080.1522825080.1" Persistent, 2 years    
.waitrosecare.secure.
force.com
__utmb Stores a timestamp of the exact moment a visitor enters our Help & Support site. Used to calculate how long a website visit takes. Example content: "1.1.10.1522825080" Persistent, 30 minutes    
.waitrosecare.secure.
force.com
__utmc Stores a timestamp of the exact moment a visitor leaves our Help & Support site. Used to calculate how long a website visit takes. Example content: "208198921" Session    
.waitrosecare.secure.
force.com
__utmt Indicates the type of request, such as event, transaction, item, or custom variable on our Help & Support site. Example content: "1" Persistent, 10 minutes    
.waitrosecare.secure.
force.com
__utmz This cookie keeps track of where the visitor came from, what search engine you used, links clicked and keywords used, and also the visitor's geographic location. This cookie works on our Help & Support site. Example content: "1.1522825080.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)" Persistent, 6 months    
.waitrose.com _cs_id Contains the following data separated by dots: user ID, user creation timestamp, number of visits, last pageview timestamp, last visit timestamp, timestamp of the last time this visitor was drawn, cookie expiration date, cookie SameSite attribute, cookie Secure attribute value (0/1). 13 months*    
.waitrose.com _cs_s Contains the number of pages viewed in the current session and the recording type: ".1" (not recorded for Session Replay), ".3" (to include a visitor for Session Replay recording service) or ".5" (to include a visitor for Session Replay recording service after a specific trigger). For Advanced recording pipeline: value is 0 when not recorded for Session Replay/ Value is .5 when recorded. 30 minutes    
.waitrose.com _cs_cvars Includes the session's Custom variables URL encoded. Session duration    
.waitrose.com _cs_ex
When set, the user is excluded from tracking. Contains the timestamp of the last time this visitor was drawn.
30 days    
.waitrose.com _cs_c Contains the user consent state (not expressed, granted, withdrawn).
13 months    
.waitrose.com _cs_optout When set, the user is opted-out from tracking 13 months    
.waitrose.com _cs_mk This cookie is used for the Google Analytics and Adobe Analytics integrations 30 minutes    
.waitrose.com _cs_rl This cookie is used for a few integrations we have that require us to generate replay links and put them into cookies. 1 year    
.waitrose.com _cs_t This is used to check if the browser supports cookies and if the tag must set the SameSite flag to None and the Secure flag to Yes. Immediate removal    
.waitrose.com _cs_
same_site
This is used to check if the browser supports the SameSite flag.
Immediate removal
   
wiatrose.com _cs_root_
domain
This is used to get the root domain. Immediate removal
           

 

_cs_c
_cs_c
_cs_c
This is used to get the root domain
This is used to get the root domain

Google Tag Manager

We use Google Tag Manager to manage web page code used for tracking and analytics on our websites.

Domain Cookie Name Description Scope and Expiry
.waitrose.com _dc_gtm_UA-{########-#} Used by Tag Manager to control the loading of a Google Analytics script tag. Example content: "1" Persistent, 2 years
www.waitrose.com gtm.login Indicates whether the user has logged in. Example content: true Session

Adobe Analytics (previously known as Adobe Site Catalyst & Adobe Omniture)

Our business partner Adobe uses analytics software to help us and them to take and analyse visitor information such as browser usage, new visitor numbers, response to marketing activity and shopping times. This information helps us to make improvements to our website, the shopping experience and marketing campaigns.

The data stored by these cookies can be seen only by the relevant teams at Waitrose and Adobe, and never shows any confidential information.

It is possible to opt out of having your anonymised browsing activity within websites recorded by analytics cookies. Waitrose.com uses the following analytics provider and you can opt out of their cookies by clicking on the following links. Please note that this will take you to the relevant third party's website and generate a ‘no thanks' cookie, which will stop any further cookies being set by those third parties.

Don't forget that by not allowing analytics cookies, this stops us from being able to learn what people like or don't like about our Digital Products and Services so that we can make them better.

Domain Cookie Name Description Scope and Expiry
.waitrose.com s_cc This cookie determines if cookies are enabled (simply set to "True") Example content: "true" Session
.waitrose.com s_cm This cookie is used by the channelManager plugin to record the channels used to access our website. Example content: "Typed/BookmarkedTyped/Bookmarked" Session
.waitrose.com s_ev61 Contains information on whether the current page was accessesed from a marketing campaign or directly. Example content: "[['Typed/Bookmarked','1523782210396']]" Persistent, 5 years
.waitrose.com s_ev62 Contains information on whether the current page was accessesed from a partner website or directly. Example content: "[['Typed/Bookmarked','1523782210396']]" Persistent, 5 years
.waitrose.com s_fid Is used to store a "fallback" visitor ID along with date and time, if third party cookies are disabled. Example content: "665ECBC3A9F74163-1374BE989714ECEE" Persistent, 2 years
.waitrose.com s_nr Is used to identify whether the customer is new or has visited the site before. Example content: "1523782210388-New" Persistent, 1.5 months
.waitrose.com s_ppv Is used to record the portion of a page that a customer has viewed and retrieve this information on the next page view. Example content: "-%2C15%2C15%2C1286" Session
.waitrose.com s_prevpage This cookie contains the title of the current Waitrose page. It is updated every time a new page on the website is opened. Example content: "WR:Groceries:Promotion Landing Page - 14632164" Persistent, 30 minutes
.waitrose.com s_sq This cookie contains information about the previous link clicked on by the visitor. Example content: "[[B]]" Session
.waitrose.com s_ttc_ev40 This cookie contains the date and time a customer was on the final page of the checkout. Contains a numeric representation of time, for example: "1522794522297" Session
.waitrose.com s_ttc_ev41 This cookie contains the date and time a visitor opens the shopping cart for the first time. Contains a numeric representation of time, for example: "1522794522297" Session
.waitrose.com s_ttc_ev42 This cookie contains the date and time a customer was on the first page of the checkout. Contains a numeric representation of time, for example: "1522794522297" Session
.waitrose.com s_ttc_ev43 This cookie contains the date and time of the first product search of the current session. Contains a numeric representation of time, for example: "1522794522297" Session
.waitrose.com s_typed Example content: 1 Session
.waitrose.com s_vi This cookie identifes a unique visitor. It containsan anonymous individual visitor ID (with date and time stamp). Example content: "[CS]v1|2D69892105311BDB-60000128E0000CEC[CE]" Persistent, 2 years
.waitrose.com s_visit This is a session cookie for Adobe Analytics. It contains a unique visitor ID and date / time stamp. Example content: 1 Persistent, 30 minutes
www.waitrose.com renderid This cookie is used for load balancing (managing traffic) on Adobe servers. Example content: "rend04" Session

MARU Group / eDigitalResearch

Our business partner MARU (previously known as eDigitalResearch) invites our visitors to take part in a survey of their experience when using the Waitrose.com website. We use this survey to prioritise our ongoing web improvements. Cookies are used in this process to ensure we get a representative sample of visitors for our research and that no individual visitor is unfairly asked to participate in the survey.

For Privacy Policy click here.

 

Domain Cookie Name Description Scope and Expiry
.edigitalsurvey.com __cfduid The "__cfduid" cookie is set by the CloudFlare service to identify trusted web traffic. It does not correspond to any particular user id in and does not store any personally identifiable information. More info on CloudFlare can be found on their site. Persistent, 1 day
.edrcdn.com __cfduid The "__cfduid" cookie is set by the CloudFlare service to identify trusted web traffic. It does not correspond to any particular user id in and does not store any personally identifiable information. More info on CloudFlare can be found on their site. Persistent, 1 day
.infolinks.com __cfduid The "__cfduid" cookie is set by the CloudFlare service to identify trusted web traffic. It does not correspond to any particular user id in and does not store any personally identifiable information. More info on CloudFlare can be found on their site. Persistent, 1 day
.www.waitrose.com ecos.dt This cookie is updated every half a second with the current date and time. It tracks the latest point in time a customer is present on our website, and is used to accurately trigger exit surveys. Example content: "1522793527673" (a timestamp) Session
.www.waitrose.com eds This cookie is only set if a visitor is invited to participate in a survey. It stores no identifiable information. It contains pairs of survey IDs and date+time when the visitor was last invited to participate in each survey. Example content: "INS-vi42-303388996:265076283-1522793684^709016667-1522793684" Persistent, 3 months
public.edigitalresearch.com en-persist This cookie is created in order to ensure web traffic is evenly distributed between eDR servers. This cookie contains no tracking information and is only used to ensure the traffic is correctly distributed. Session
www.waitrose.com edr_sc_tst   Persistent, 1 day

Hotjar

We use Hotjar in order to better understand our users’ needs and to optimize this service and experience. Hotjar is a technology service that helps us better understand our users’ experience (e.g. how much time they spend on which pages, which links they choose to click, what users do and don’t like, etc.) and this enables us to build and maintain our service with user feedback. Hotjar uses cookies and other technologies to collect data on our users’ behavior and their devices. This includes a device's IP address (processed during your session and stored in a de-identified form), device screen size, device type (unique device identifiers), browser information, geographic location (country only), and the preferred language used to display our website. Hotjar stores this information on our behalf in a pseudonymized user profile. Hotjar is contractually forbidden to sell any of the data collected on our behalf.

For further details, please see About Hotjar and Privacy Policy.

Domain Cookie Name Description Scope and Expiry
.hotjar.com _hjClosedSurveyInvites This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. Persistent, 365 days
.waitrose.com

_hjDonePolls This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in. Persistent, 365 days
.hotjar.com

_hjMinimizedPolls This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. Persistent, 365 days
.waitrose.com
_hjDoneTestersWidgets This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. Persistent, 365 days
.waitrose.com
_hjIncludedInSample This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels. Persistent, 365 days
.waitrose.com
_hjShownFeedbackMessage This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show. Persistent, 365 days
.waitrose.com
_hjid This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. Persistent, 365 days
N/A _hjRecordingLastActivity This should be found in sessionStorage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). Session
.waitrose.com _hjTLDTest When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. Session
.waitrose.com _hjUserAttributesHash User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. Session
.hotjar.com _hjCachedUserAttributes This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. Session
.waitrose.com _hjLocalStorageTest This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in _hjLocalStorageTest has no expiration time, but it is deleted immediately after creating it so the expected storage time is under 100ms. N/A
.waitrose.com _hjptid This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site. Session
.waitrose.com _hjAbsoluteSessionInProgress The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. Persistent, 30minutes

Functional

Bazaarvoice

Waitrose uses Bazaarvoice to collect and display product reviews on waitrose.com. Product reviews are very important to us, they help customers make informed choices about the products they may be interested in purchasing.

For Privacy Policy click here.

To opt out of the cookies click here.

Domain Cookie Name Description Scope and Expiry
.network-eu.bazaarvoice.com BVID Allows BV software to recognise the user when they visit our site, making it easier to review products on subsequent visits. Persistent, 1 year
.network-eu.bazaarvoice.com BVSID Allows BV software to recognise the user when they visit our site, making it easier to review products on subsequent visits. Session
.waitrose.com BVBRANDID Unique user identifier which exists only within BV systems. Allows BV web analytics to be correlated to the correct user. Example content: "21531d20-9fd6-4118-91d4-36c1e7647da9" Persistent, 1 year
.waitrose.com BVBRANDSID A unique user / session identifier which only exists in BV system. Allows BV web analytics to be correlated to the correct user. Example content: "eb91a990-b724-4205-833e-65e683e68499" Persistent, 15 minutes
www.waitrose.com BVImplecom Stores user configuration for A/B testing. Example content: "17263_2_0" Session

Salesforce Live Agent

Waitrose uses Live Agent, part of Salesforce Service Cloud, to connect with customers and visitors to waitrose.com in real time through a web-based, text-only live chat.

For Privacy Policy click here.

Domain Cookie Name Description Scope and Expiry
devsscr1-waitrosecare.cs84.force.com
force-stream Used to redirect server requests for sticky sessions 3 hours
devsscr1-waitrosecare.cs84.force.com
force-proxy-stream Ensure client requests hit the same proxy hosts and are more likely to retrieve content from cache 3 hours
devsscr1-waitrosecare.cs84.force.com

sfdc-stream Used to properly route server requests within Salesforce infrastructure for sticky sessions 3 hours
.force.com BrowserId Used for security protections 1 year
.force.com BrowserId_sec Used for security protections 1 year

Targeting/Advertising

YouTube

We embed videos from our official YouTube channel using YouTube’s privacy-enhanced mode. This mode may set cookies on your computer once you click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos using the privacy-enhanced mode. {re-phrase}

For Privacy Policy click here.

If you are in the UK, you can opt out of seeing online interest-based ads from participating companies through the European Interactive Digital Advertising Alliance.

Domain Cookie Name Description Scope and Expiry
.youtube.com PREF Registers a unique ID that is used by Google to keep statistics of how the visitor uses YouTube videos across different websites. Example content: "f1=50000000" Persistent, 8 months
.youtube.com VISITOR_INFO1_LIVE Used to estimate the users' internet connection bandwidth. Example content: "3QoiRKzTXQo" Persistent, 8 months
.youtube.com YSC Contains a unique idetifier given to site visitor when viewing a video. Allows to keep statistics of what videos from YouTube users have watched. Example content: "_3NB5ZnpuH8" Session

Facebook

The Facebook cookies are placed when you have been on Facebook and visit our site. This then enables Facebook to personalise possible adverts or posts based on your browsing habits.

For Privacy Policy click here.

To opt out of the cookies click here.

If you are in the UK, you can opt out of seeing online interest-based ads from participating companies through the European Interactive Digital Advertising Alliance.

Domain Cookie Name Description Scope and Expiry
.facebook.com fr This cookie contians encrypted Facebook ID and Browser ID Example content: "0woG5R5xknSsY3caf..Ba6Ifk...1.0.Ba6Ifk." Persistent, 3 months
www.facebook.com   Content: blank Session

DoubleClick by Google

We use DoubleClick Digital Marketing platform in order to provide our customers with the most relevant advertising across screens and channels, including search ads in Google, Yahoo and Bing. Cookies set up by DoubleClick track browsing habits and activity, and allow us to measure ad performance. Please refer to this link to find out how to opt out of personalised ads.

For Privacy Policy click here.

To opt out of the cookies click here.

If you are in the UK, you can opt out of seeing online interest-based ads from participating companies through the European Interactive Digital Advertising Alliance.

Domain Cookie Name Description Scope and Expiry
.doubleclick.net IDE This cookie holds information that allows DoubleClick to determine which advertiesements have been shown on a device. Example content: "AHWqTUkWuve80YgUoEqXZVY8ScyXyoR1SrUbBwq3ii
GkKJyUSiEmeZg0-nKKRyQr"
Persistent, 2 years
.doubleclick.net test_cookie Used to check if the user's browser supports cookies. Example content: "CheckForPermission" Session

How to manage cookies in your browser

Our cookies do not store financial information, or information which is capable of directly identifying you (such as your name or address). Cookies simply allow our website to retrieve this information in order to personalise and improve your experience of our website.

However, if you wish to restrict, block or delete cookies from Waitrose.com – or any other website - you can use your browser to do this. Each browser is different so check the ‘Help’ menu of your particular browser to learn how to change your cookie preferences.

Please bear in mind that if you do this, certain personalised features of this website cannot be provided to you.

Most modern browsers will allow you to:

·         See what cookies you've got and delete them on an individual basis.

·         Block third party cookies.

·         Block cookies from particular sites.

·         Block all cookies from being set.

·         Delete all cookies when you close your browser.

 You should be aware that any preferences will be lost if you delete cookies. Ironically, this includes where you have opted out from cookies, as this requires an opt-out cookie to be set. Also, if you block cookies completely many websites will not work properly and some functionality on these websites will not work at all. We do not recommend turning cookies off when using our Digital Products and Services for these reasons.

If you are primarily concerned about third party cookies generated by advertisers, you can turn these off separately. This is discussed in more detail below.

The links below take you to the ‘Help' sections for each of the major browsers so that you can find out more about how to manage your cookies.

Internet Explorer

http://support.microsoft.com/kb/196955

Firefox

http://support.mozilla.org/en-US/kb/Cookies

Google Chrome

http://support.google.com/chrome/bin/answer.py?hl=en&answer=95647

Opera

http://www.opera.com/browser/tutorials/security/privacy/

Safari

http://docs.info.apple.com/article.html?path=Safari/5.0/en/9277.html

Safari iOS

http://support.apple.com/kb/HT1677

Android

https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DAndroid&hl=en

Blackberry

https://uk.blackberry.com/legal/cookies

Windows Phone

http://www.microsoft.com/windowsphone/en-us/howto/wp7/web/changing-privacy-and-other-browser-settings.aspx



Mobile users

For mobile and app users, managing your cookie preferences may work slightly differently. This is usually done through your phone settings; managing cookies across your whole device. We’ve added some useful steps below to get you started:

How to check cookies are enabled on IOS Safari

  • Tap on the ‘Settings’ application from your home screen
  • Find and tap on the ‘Safari’ menu item
  • Under the ‘Privacy & Security’ section tap on the ‘Block cookies’ menu item
  • Select any other option other than ‘Always block’


How to check cookies are enabled on Android

  • Tap on the ‘Settings’ application from your home screen or under ‘Apps’
  • Under the ‘Device’ section tap on the ‘Applications’ menu item
  • Find and tap the ‘Internet’ menu item
  • Find and tap the ‘Privacy’ menu item
  • Enable ‘Accept cookies’

For all other browsers, please consult your online help files

How to manage mobile device identifiers used within Apps:

To exercise the mobile device privacy settings controls, please visit the privacy settings of your Android or iOS device and select opt-out of interest based ads (Android) or limit ad tracking (Apple iOS).

The links below take you to the ‘Help' sections for each of the major browsers so that you can find out more about how to manage your cookies.

Safari iOS

http://support.apple.com/kb/HT1677

Android

https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DAndroid&hl=en


iOS App Tracking
Essential Tracking


Firebase
In-App Messaging:

  • Firebase In-App Messaging uses Firebase installation IDs to determine which devices to deliver messages to.
  • Retention: Firebase retains Firebase installation IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

Performance Monitoring:

  • Performance Monitoring uses Firebase installation IDs to calculate the number of unique Firebase installations that access network resources – ensures access patterns are sufficiently anonymous. It also uses Firebase installation IDs with Firebase Remote Config to manage the rate of performance event reporting. Additionally, it uses IP addresses to map performance events to the countries they originate from.
  • Retention: Performance Monitoring keeps installation and IP-associated events for 30 days and de-identified performance data for 90 days.

Realtime Database:

  • Realtime Database uses IP addresses and user agents to enable the profiler tool, which helps Firebase customers understand usage trends and platform breakdowns
  • Retention: Firebase retains Firebase installation IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

Remote Config:

  • Remote Config uses Firebase installation IDs to select configuration values to return to end-user devices.
  • Retention: Firebase retains Firebase installation IDs until the Firebase customer makes an API call to delete the ID. After the call, data is removed from live and backup systems within 180 days.

Salesforce Marketing Cloud

  • Salesforce Marketing Cloud stores user permissions for push notifications and analytics tracking


Non-Essential Tracking
Meta

We use an integration with Meta (Facebook) to get a better understanding of the amount of users that reach our app and products through advertisements on Facebook.

ContentSquare

  • We use ContentSquare to measure the level of User Engagement by looking at information such as the Revenue and Transactions generated over a period of time.

NewRelic

  • We use NewRelic to monitor technical aspects of the Application and its respective services, such as Crashes and Performance Metrics.

Logs

  • We use logs in order to monitor any events that happen while using the app. We use the logs to create a timeline of occurrences which will help us investigate any problem a user might run into.
  • No personal data that can identify a specific user is logged, only data such as interactions, User and Product IDs, etc.

Salesforce Marketing Cloud

  • We use analytics within Salesforce Marketing Cloud to measure customer engagement with push notifications (if a customer has given notification permissions).

Firebase/Google Analytics

  • We use Firebase and Google Analytics for tracking and reporting of app traffic. This information can be used to gain customer insight and improve the way our app works. Firebase and Google Analytics do not collect any personal information.


Third-party cookies

When you are on Waitrose.com. you may notice that there is content from other websites - for example a video from YouTube or a store locator map from Google. We may also provide you with the opportunity to share information with others using social networks such as Facebook. We add this content from time to time to improve the user experience. As a result, you may be sent cookies from these other websites. Waitrose does not control these cookies and we suggest you check these third-party websites for more information about the cookies they use and how you can manage them.

Managing advertising cookies

Please note that if you want to opt out from receiving targeted advertising, this does not mean that you will receive less advertising when you use our services. This just means that the advertising you see will not be as relevant or customised to you.

However, if you still want to opt out of these third party advertising cookies, you can do this by visiting the Interactive Advertising Bureau's website www.youronlinechoices.com/uk which lists all ad serving cookies that are currently set on your device and tells you how to opt-out from each of them. Please note that this website lists many more networks than those used at Waitrose.com.

We have also set out links to some of the specific partners we work with who set cookies on our websites, and therefore on your computer, each of which have instructions on how to opt out of their cookies.

Please remember that if you choose to opt out of targeted advertising from a specific company or via www.youronlinechoices.com, it only applies to the web browser on the device you are using. You will therefore need to follow the same process on every device you use or different web browser that you use to exercise the same choice.

Further information about cookies

If you wish to learn more about cookies in general and how to manage them, visit www.aboutcookies.org.