Find out how we use cookies and how you can manage them

What are cookies?
Cookies are small text files that are stored on your computer by your web browser. We use them to identify how visitors arrive at our site and the subsequent path they take through it. This helps us to improve our service to you.

EDF Energy does not use cookies to collect or store Personally Identifiable Information (PII).

How to control the use of cookies?
If you wish to restrict or block cookies set by EDF Energy websites, or any other website, you can do this through your browser settings.  The "Help" function within your browser should give details of how to do this.  Alternatively, you can find more details on how to control or delete cookies at www.allaboutcookies.org

Please note that you may not be able to use many of the services on our website or other websites without cookies.

How edfenergy.com uses cookies
Our website currently uses cookies and some of our third party suppliers use our website to set cookies on our behalf for internet marketing and performance optimisation.

While on this website your web browser may interact with content from different servers and therefore cookies from other sources may be set on your computer during a visit to this site.

Below you can view a description of the types of cookie that are used, why they are used and details of the individual cookies.

Strictly necessary cookies - MyAccount

MyAccount cookies are essential and are used to enable you to move around your self-service area and use its features. Without these cookie services, parts of the MyAccount site may not function correctly.

Cookie NameDescription
SAPLB_*saplb-Cookie is the load balancing identifier
JSESSIONIDjsessionid-Cookie is the J2EE session identifier 
PORTALALIASMy-account works with ALIAS names for navigation redirection purpose. When we do enable the portal alias in web.xml then the cookie gets generated by SAP application server
_utma, _utmb,
_utmc, _utmz
Related to Google analytics cookie
MYSAPSSO2Cookie gets generated as a part of logon to the SAP portal, generated by SAP application server
BNES*Barracuda cookies which is duplicate of SAP cookies with digital signatures
BNIS*Cookies from Barracuda with holds info on authentication
BNI_persistanceCookies from Barracuda for load balancing

mgea 

mgft

b2bpc

b2bsup

b2bct

bpc

bea

bft

bes

bgs

edfhash80

edfhash112

Temporary cookie stored to pass information between pageviews. Cleared immediately after being read
_#atcOnly for users in phone quote sales (not public users)

 

 

Performance cookies - Website analytics

Website analytics cookies are used to identify how users interact with our site, so that we can see things like the most popular pages and the journey users take though our site.

DC Storm cookies

Non-Cross Domain Tracking: 1st Party Cookies
Non-cross domain tracking uses first party cookies only. These cookies are written in the domain of the site being tracked.

Cookie nameDescriptionExpiry
_#srchistStores the history of traffic sources the user has arrived to the site by1000 days
_#sessStores information about the session1000 days
_#vdefStores the visit definition – ts type, number of visits, expiry1000 days
_#uidStores a user identifier (only within a site)1000 days
_#slidUnique sale ID1000 days
_#clkidUnique identifier for a click generating a landing1 year
_#lpsFlags that the last page was secure and therefore has no referrer20 min
_#tsaStores the referrer details to avoid duplicate Landing events10 min
_#envFlags whether the environment variables (screen size, browser etc) need to be collected again30 days

Cross Domain Tracking: 3rd Party Cookies
Cross-domain tracking uses 3rd party cookies to enable spanning of domains. The availability of third party cookies is tested – if not available a 1st party cookie is used instead, with reduced tracking ability.

Cookie nameDescriptionExpiry
_#stc[site id]This is the third party cookie used to store all the other cookie data in concatenated form. The Cookie’s name has the site ID in it.1000 days
_#nxdis is a 1st party cookie used when access to the third party cookie is blocked. It stores the data similarly to the _#stc cookie.1000 days

Google Analytics Cookies

Google Analytics cookies are written in the domain of the site being tracked.
 

Cookie nameDescriptionExpiry
__utmaThis cookie is typically written to the browser upon the first visit to your site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits your site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to your site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure.2 years from set/update
__utmbThis cookie is used to establish and continue a user session with your site. When a user views a page on your site, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on your site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on your site for longer than 30 minutes. You can modify the default length of a user session with the _setSessionCookieTimeout() method.30 minutes from set/update
__utmzThis cookie stores the type of referral used by the visitor to reach your site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within your own site. The cookie is updated with each page view to your site.6 months from set/update
__utmvThis cookie is not normally present in a default configuration of the tracking code. The __utmv cookie passes the information provided via the _setVar() method, which you use to create a custom user segment. This string is then passed to the Analytics servers in the GIF request URL via the utmcc parameter. This cookie is only written if you have added the _setVar() method for the tracking code on your website page.2 years from set/update
__utmxThis cookie is used by Website Optimizer and only set when the Website Optimizer tracking code is installed and correctly configured for your pages. When the optimizer script executes, this cookie stores the variation this visitor is assigned to for each experiment, so the visitor has a consistent experience on your site.  See the Website Optimizer Help Center for more information.6 months from set/update

Google Analytics Opt-out Browser Add-on: http://tools.google.com/dlpage/gaoptout

Crazy Egg

Cookie nameDescriptionExpiry
Crazy Egg - is_returning1st party cookie that does not include any Personally Identifiable Information to assess usage patterns on the website.Persistent cookie that's stored on  your computer in-between sessions

Maxymiser

Cookie nameDescriptionExpiry
Maximyser-mmcore.pd, mmcore.srvUsed to store anonymous identifiers. They enable the optimisation platform to remember a visitor and to serve them with the appropriate content while ensuring a fast load of the web page.Persistent cookie that is stored on your computer in-between sessions
Maximyser-mmid, mmpa.rh, mmcore.idThese 3 cookies are obsolete. They were used in a previous version of the maxymiser platform, and will eventually expire within 12 months.Persistent cookie that is stored on your computer in-between sessions
Maximyser-mmcore.tst, mmpa.tstThis cookie is used by the platform as a test to see whether or not browser settings allow cookies to be set on the end-user machine. Mmpa.tst is a previous version of the same cookie.This is a session-basedcookie that is deleted when you leave the site.
Maximyser-mm_[description] Sometimes maxymiser need to create a custom cookie to deliver particular functionality on the website. These are prefixed with mm_.Persistent cookie that is stored on your computer in-between sessions

 

 

Third party cookies

EDF Energy uses a number of suppliers who also set cookies on the edfenergy.com website on its behalf or on their own sites in order to deliver the services that they are providing. If you would like more information about the cookies used by these suppliers, please see the list below.

Liverperson.net

Cookie NameSet by (domain)DescriptionExpiry

HumanClickKEY

HumanClickSiteContainerID

HumanClickACTIVE

LivePersonID

server.lon.liveperson.net

liveperson.net

These cookies are set to maintain the visitor session and to track repeat visitors when they click to chat1 year

The companies listed below are some of the providers who work with website operators to collect and use information to provide online behavioural advertising.

Visit http://www.youronlinechoices.com/uk/your-ad-choices where you can use the buttons to control your online behavioural advertising preferences. You can turn off or turn on all companies or alternatively set your preferences for individual ones. By clicking on the button you can find out more about the company itself as well as its behavioural advertising status on the web browser you are using.

awin1.com

Cookie NameSet by (domain)DescriptionExpiry

Aw(merchantid)AWSESSawpv9

(merchantid)

aw3
AW
_aw_m_(clickid)

awin1.comSave data for tracking
Holds link id of currently displayed banner
Identify the affiliate_id and click time
Identify referring affiliate
Track sale / lead
Track sale / lead

variable
session
variable
90 days
variable

 

Google

Cookie NameSet by (domain)DescriptionExpiry
HTTP code - Google Code for EDF Eco X Remarketing List Googlemarketing tag - this piece of code places a cookie on the users system so that we can retarget that particular user with display ads for a given period of time.30 days

iFAQ

Cookie NameSet by (domain)DescriptionExpiry

cp_session

oracle.uix

Custhelp.comStores session specific user data. Session

Kampyle

Cookie NameSet by (domain)DescriptionExpiry

session_start_time

 The time and date that the push invitation was triggeredSession
k_visit Counts the number of user visits1 year
k_push8 A cookie that retains the 21 day invitation opt-out time limit. This is set if / when a user declines a proactive feedback push invitation21 days
push_time_start The time and date that the push invitation was triggeredSession
k_vectors A shared visitor identifier used to support Omniture integrationSession
k_track An identifirer used to support Funnel Reporting integration