A cookie is a small file of letters and numbers that is sent and stored on your computer and/or mobile device which provides us with information in relation to your website usage, and allows us to recognise that you have used our website before.
Cookies are safe and secure and are commonly used by websites.
A cookie typically contains:
- the name of the server the cookie was sent from;
- the lifetime of the cookie; and
- a unique identifier (usually a number).
How cookies work
When you visit the Codex website, our website server sends a cookie to your device and uses this number to recognise you when you return to the site or browse from page to page. This cookie is then stored on your computer or mobile device.
All websites can send a cookie to your browser if your browser settings allow it. Many websites do this to track online flow.
Types of cookies
Cookies may be categorised on the basis of their life span:
- Session or temporary cookies: these cookies expire when you close your browser or when the session times out.
- Persistent or permanent cookies: these are usually stored on your hard disk and survive across multiple sessions but have a longer expiration date.
Please find below a table detailing the types of cookies used on our website:
|Cookie Name||Set by||Data Stored||Purpose||More info|
|PHPSESSID||Wordpress||A random unique number or string of letters and numbers.||As you browse around the pages on this site, the session cookie tells the website that you are the same person requesting the webpages, and not a new visitor to each page. This cookie does not identify you personally and is not linked to any other information we store about you.||wordpress.org|
|tk_tc||Wordpress||Anonymous||This cookie collects metrics about the users use of the website related to the WordPress.com features so that WordPress.com can improve their services||wordpress.com|
|_ga||Google Analytics||Anonymous||Used to distinguish users.||developers.google.com|
|_gid||Google Analytics||Anonymous||Used to distinguish users.||developers.google.com|
|_gat||Google Analytics||Anonymous||Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
|AMP_TOKEN||Google Analytics||Anonymous||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.||developers.google.com|
|__utmt||Google Analytics||Anonymous||Used to throttle request rate.||developers.google.com|
|__utmc||Google Analytics||Anonymous||Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operates in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.||developers.google.com|
|__utmv||Google Analytics||Anonymous||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.||developers.google.com|
Controlling or deleting cookies
You can easily control and disable cookies through your browser settings. Learn how to remove cookies set on your device. Removal of cookies may impact the experience whilst using the website through repeated requirements for entry of confirmation.