Why have a cookie policy?
We have created this statement about our use of cookies in order to demonstrate our firm and continuing commitment to the privacy of personal information provided by those visiting and interacting with this web site. We hold the privacy of your personal information in the highest regard. The following discloses our information gathering and dissemination practices for this website.
What Are Cookies?
A cookie is a very small text document, which often includes an anonymous unique identifier. When you visit a Web site, that site’s computer asks your computer for permission to store this file in a part of your hard drive specifically designated for cookies. Each Web site can send its own cookie to your browser if your browser’s preferences allow it, but (to protect your privacy) your browser only permits a Web site to access the cookies it has already sent to you, not the cookies sent to you by other sites. Browsers are usually set to accept cookies. However, if you would prefer not to receive cookies, you may alter the configuration of your browser to refuse cookies. If you choose to have your browser refuse cookies, it is possible that some areas of our site will not function as effectively when viewed by the users. A cookie cannot retrieve any other data from your hard drive or pass on computer viruses.
How Do We Use Information We Collect from Cookies?
As you visit and browse our Web site, the site uses cookies to differentiate you from other users. In some cases, we also use cookies to prevent you from having to log in more than is necessary for security. Cookies, in conjunction with our Web server’s log files, allow us to calculate the aggregate number of people visiting our Web site and which parts of the site are most popular. This helps us gather feedback to constantly improve our Web site and better serve our clients. Cookies do not allow us to gather any personal information about you and we do not intentionally store any personal information that your browser provided to us in your cookies.
This site uses Google Analytics to anonymously collect data about visits to the site.
Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with website content. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen, for example the URL of the page. The Google Analytics JavaScript libraries use HTTP Cookies to “remember” what a user has done on previous pages / interactions with the website.
Important: Google Analytics does not store any personal information about your use of this website.
Google Analytics supports two JavaScript libraries (tags) for measuring website usage: analytics.js and ga.js. The following sections describe how each use cookies.
The analytics.js JavaScript library is part of Universal Analytics and uses these cookies:
_ga expires after 2 years and is used to distinguish users
_gat expires after 10 minutes and is used to throttle request rate
The ga.js JavaScript library uses these cookies:
__utma expires after 2 years from set/update and is 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.
__utmt expires after 10 minutes and is used to throttle request rate.
__utmb expires after 30 mins from set/update and is used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmc expires after the end of browser session and is 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.
__utmz expires after 6 months from set/update and is used to store the traffic source or campaign that explains how the user reached the site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
__utmv expires after 2 years from set/update and is 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.
Google Analytics for Display Advertisers – cookie usage
For websites that are using Google Analytics’ Display Advertiser features, such as remarketing, a third-party DoubleClick cookie is used in addition to the other cookies described in this document for just these features.
– Third party vendors, including Google, use cookies to serve ads based on your prior visits to this website.
– Google’s use of the DoubleClick cookie enables it and its partners to serve ads to you based on your visit to this sites and/or other sites on the Internet.
– You may opt out of the use of the DoubleClick cookie for interest-based advertising by visiting Ads Settings.
Google Analytics-powered experiments, the following cookies are used for these features:
__utmx expires after 18 months and is used to determine a user’s inclusion in an experiment.
__utmxx expires after 18 months and is used to determine the expiry of experiments a user has been included in.
This site is built with WordPress which uses cookies to help you better navigate and use the site.
On login, WordPress uses this cookie:
wordpress_[hash] expires at the end of the session and is used to store your authentication details. Its use is limited to the admin console area, /wp-admin/
After login, WordPress uses this cookie:
wordpress_logged_in_[hash] expires at the end of the session and is used to indicate when you’re logged in, and who you are, for most interface use.
WordPress also sets other cookies with this form:
wp-settings-{time}-[UID] expires after a year. 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.