86STAFF.COM – COOKIES OVERVIEW

A cookie is a small text file containing a unique identification number that is transferred (through your browser) from a website to the hard drive of your computer. The cookie identifies your browser but will not let a website know any personal information about you, such as your name and/or address. These files are then used by websites to identify when users revisit that website.

Cookies placed in your browser’s memory are called session cookies and cookies placed on your computer’s hard drive are called persistent cookies. Session cookies are deleted when you close your browser, while persistent cookies remain on your hard drive, even after closing your browser. Session cookies are generally used to improve the user experience when using a website. Persistent cookies are generally used to store user preferences  between browser sessions.

We use cookies to ensure that you get the most out of our website. You can delete cookies at any time or you can set your browser to reject or disable cookies. However, if you use your browser settings to block all cookies you may not be able to access all or parts of our site. For more information about how to reject cookies using your internet browser settings please consult the “Help” section of your internet browser (or alternatively visit http://www.aboutcookies.org).

Please find below the list of cookies used on 86staff.com; the list outlines the names of services and/or components that require/instantiate the cookie(s) through the website and/or its third-party components.

For each cookie, the following information will be displayed:

  • Cookie name or expected name structure
  • Cookie description
  • Cookie expiration (when estimable)

When cookie names or part of those are enclosed within square brackets, please expect to have a dynamic value instead of the static text shown: e.g. if cookie name is displayed as “cookiename_[random_number]” – the actual real-life cookie name could be both “cookiename_123456” or “cookiename_987, as “[random_number]” would be replaced by any actual value that is required by the cookie.

WORDPRESS:

Find below the list of cookies set by WordPress – the main Content Management System of the website.

  • wordpress_[hash]
    On login, wordpress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area, /wp-admin/.
  • wordpress_logged_in_[hash]
    After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you’re logged in, and who you are, for most interface use.
  • wp-settings-[time][UID]
    WordPress also sets a few wp-settings-[time][UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface.

These cookies aren’t considered strictly necessary for users, unless these want to access a WordPress account (perform the login).

These cookies have a lifetime of two days, then they expire. If – on login – a user ticks the “Remember me” option, the cookie will be stored for fourteen days instead.

Official information about WordPress cookies can be found here: https://codex.wordpress.org/WordPress_Cookies

WOOCOMMERCE:

WooCommerce is a WordPress plugin (a component that can be hooked into the WordPress CMS in order to expand its native functionalities), which we use to keep track of orders, products, subscriptions, etc – and associate them to users that exist within the WordPress system.

WooCommerce uses the following cookies to keep track of cart data:

  • woocommerce_cart_hash
    Stores an encoded string representing the contents of the WooCommerce shopping cart
  • woocommerce_items_in_cart
    Records if there are any items in the WooCommerce shopping cart
  • wp_woocommerce_session_[hash]
    The cookie contains information identifying the customer and session expiration time. For guest shoppers this a randomly generated cryptographically strong ID.

These cookies are strictly necessary for the WooCommerce component to work – and therefore for the website in order to be able to process transactions and operations on products, subscriptions and orders.

The first two cookies contain information about the cart as a whole and helps WooCommerce know when the cart data changes.

The final cookie (wp_woocommerce_session_[hash]) contains a unique code for each customer so that it knows where to find the cart data in the database for each customer.

No personal information is stored within these cookies.

For each of these cookies, the cookie duration is configurable.

Official information about WooCommerce cookies can be found here: https://docs.woocommerce.com/document/woocommerce-cookies/

STRIPE

Stripe is the payment gateway that has been configured to process the payments that run through WooCommerce. Stripe does this using their own external servers and services, which process all the transactions within the website.

Stripe will set the following cookies:

  • _stripe_mid
  • _stripe_sid

All the available information regarding these cookies can be found in the Stripe Privacy Policy and the Stripe Cookie Policy. No additional information nor detailed description of these cookies was provided by Stripe.

The usage of these two cookies within WooCommerce is outlined in WooCommerce’s “Privacy Considerations when using official payments extensions” under the section “Stripe”, which can be found at the following URL: https://docs.woocommerce.com/document/privacy-payments/#woocommerce-gateway-stripe

WORDFENCE

Wordfence is a WordPress plugin (a component that can be hooked into the WordPress CMS in order to expand its native functionalities), which we use for security monitoring, hacking prevention, website security scanning, traffic analysis and firewall configuration.

A full list of cookies set by Wordfence is not available at the moment – however, the following information is available; from the official Wordfence documentation:

Wordfence uses cookies:

  • To distinguish between bots and humans.
  • To distinguish between logged in administrators and other users.
  • To identify if a user has visited a unique page you’ve set to allow them to bypass country blocking so that country-blocking does not prevent them from viewing the site.

If you disable Wordfence cookies, Wordfence will still function normally except that

  • Live Traffic will not show if a visitor is human.
  • Admins are exempt from some of the Firewall rules. This means that they are allowed to perform some actions that regular users are not. If you disable Wordfence cookies, admins will lose this ability and will be treated as regular users. If you disable Wordfence cookies you may therefore need to whitelist some actions. If this is necessary you will be prompted to do so.
  • Country-blocking bypass by visiting a special hidden URL will not function correctly.

GOOGLE ANALYTICS

We use Google Analytics for traffic analysis on the website. The JavaScript files named “gtag.js” and “analytics.js” might set the following cookies, when Google Analytics is enabled:

  • _ga
    Used to distinguish users. Expires after two years.
  • _gid
    Used to distinguish users. Expires after 24 hours.
  • _gat / _dc_gtm_[property-id]
    Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
    [property-id]. Expires after one minute.
  • AMP_TOKEN
    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. Could expire at any time between 30 seconds and a year.
  • _gat_[property_id]
    Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out. More details. Expires in 90 days.

More information on how Google Analytics manages cookies can be found at the following link: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage