ADS and Cookies

WHY DO WE USE COOKIES?

Cookies enable us to identify your device, or you when you have logged in.

  • We may use cookies that are strictly necessary to enable you to move around the site or to provide certain basic features.
  • We may use cookies to enhance the functionality of the website by storing your preferences, for example.
  • We may also use cookies to help us to improve the performance of our website to provide you with a better user experience.

We do not sell the information collected by cookies, nor do we disclose the information to third parties, except where required by law (for example to government bodies and law enforcement agencies).

If you wish to control what cookies are set on your device through the ADS website then you can find out how to do this below.

COOKIES WE USE

Cookie Name Description & purpose Persistence More information
PHPSESSID This stores the user’s session ID End of session Functional
Members-lounge-hasIdentity Used to flag whether the user is logged in to the Member’s Lounge. This is used by the Word press Plugin to decide upon displaying a “Login” button. End of session Functional
Members-lounger-fullName Used to store the Full Name of the user logged in to Member’s Lounge.  This is sued by the WordPress Plugin to display in the header if a user is logged in to the Member’s Lounge End of session Functional
WordPress
wordpress_test_cookie
wordpress_
wordpress_logged_in_
wp-settings-
wp-settings-time-

These cookies are only set when administrators and editors of the website log into the WordPress administration area. They are not set for ordinary website visitors.

More information about WordPress cookies

End of session
End of session
15 days
1 year
1 year
Google Analytics Performance The ADS website uses Google Analytics. This is a web analytics service provided by Google, Inc. Google Analytics sets a cookie in order to evaluate use of those services and compile a report for us.
_utma

 

Used to distinguish users and sessions.  The cookie is created when the javascript library executes and no existing _utma cookies exists.  The cookie is updated every time data is sent to Google Analytics 30 mins Analytical (Google Analytics)
_utmt Used to throttle request rate. 30 mins Analytical (Google Analytics)
_utmc End of browser session.  Not used in ga.js.  Set for interoperability with urchin.js.  Historically, this cookie operated in conjunction with the _utmb cookie to determine whether the user was in a new session/visit End of session Analytical (Google Analytics)
_utmz Stores the traffic source or campaign that explains how the user reached your site.  The cookie is created when the javascript library executives and is updated every time data is sent to Google Analytics. 6 months Analytical (Google Analytics)
_utmv   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 2 years Analytical (Google Analytics)

HOW CAN I CONTROL COOKIES?

If you do not want to receive cookies, you can modify your web browser so that it notifies you when cookies are sent to it or you can refuse cookies altogether. You can also delete cookies that have already been set.

If you wish to restrict or block web browser cookies which are set on your device then you can do this through your browser settings; the Help function within your browser should tell you how. Alternatively, you may wish to visit www.aboutcookies.org, which contains comprehensive information on how to do this on a wide variety of desktop browsers.