Cookies on Christopher Maltman

Cookies are files saved on your phone, tablet or computer when you visit a website.

We use cookies to store information about how you use the Christopher Maltman website, such as the pages you visit.

Cookie settings

We use 5 types of cookie. You can choose which cookies you're happy for us to use.

Cookies that measure website use

We use Google Analytics to measure how you use the website so we can improve it based on user needs. We do not allow Google to use or share the data about how you use this site.

Google Analytics sets cookies that store anonymised information about:

  • how you got to the site
  • the pages you visit, and how long you spend on each page
  • what you click on while you’re visiting the site
Show more information on these cookies
Name:_ga
Owner:Google Analytics
Purpose:These help us count how many people visit by tracking if you’ve visited before
Duration:2 years
Name:_gid
Owner:Google Analytics
Purpose:These help us count how many people visit by tracking if you’ve visited before
Duration:24 hours

Cookies that remember your settings

These cookies do things like remember your preferences and the choices you make, to personalise your experience of the site.

Show more information on these cookies
Name:cookieconsent_status
Owner:Christopher Maltman
Purpose:Saves your cookie consent settings
Duration:1 year

Strictly necessary cookies

These essential cookies do things like remember if you are logged into the website and confirm that you’re a real person using the website (and not an automated bot).

They always need to be on.

Show more information on these cookies
Name:wordpress_logged_in_
Owner:WordPress
Purpose:Recognises users and provides secure log-in to our website and associated systems. This is mainly used by our staff and contributors.
Duration:Session
Name:_cfuid
Owner:CloudFlare
Purpose:This is for security and set by the proxy firewall that we use called Cloudflare. It identifies individual visitors behind a shared IP address and apply security settings on a per-client basis. For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor’s machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information. For more information on this Cloudflare cookie, visit https://support.cloudflare.com/hc/en-us/articles/200170156-What-does-the-Cloudflare-cfduid-cookie-do-
Duration:Persistent

Your cookie settings were saved