To comply with the Privacy and Electronic Communications Regulations we periodically conduct a Cookie Audit of our website. This Cookie Audit was last updated on 15 April 2014.
Our website uses a number of cookies to store data on our visitors' computers. For more information about managing cookies, please see http://www.aboutcookies.org/.
Our current assessment of the intrusiveness of the cookies used by our website is as follows:
- Third-party cookies: we use some widely-used third-party plugins as marketing tools for our own business and to provide convenience for our visitors. In our belief the use of these plugins represents current best practice. We have no direct control over the content of the cookies they create, the use made of any data collected, or the security of that data. These third parties may collect information about your visit to our website, and they may use this with other data in order to serve advertising which may be more relevant to you. Some visitors may see this use of data as intrusive to some degree.
We believe there is no reason for our website visitors to be particularly concerned about the privacy implications of any of the cookies we use, but we do recognise the importance of making you aware of the purpose and scope of the data stored in the cookies which are created or updated on your computer when you visit our website. You may choose to delete these cookies from your computer between visits to our website.
We recommend that if you have concerns about the privacy implications of the cookies we use, then you should investigate how to do this using the cookie management tools in your web browser.
In Detail: First party Cookies
First party cookies are specific to the host site that created them (in this case, braemore.co.uk). In all cases these first-party cookies do not store any personal or sensitive information, or anything that makes you personally identifiable to us.
Session IDs: Our web server may create an essential session cookie called ASP.NET_SessionId ,which is essential for your use of some of the interative elements of the website, such as contact forms. The cookie contains a session ID which is a mechanism for distinguishing your visit to our website from any other visitors that may be using the website at the same time. For more information you can read this technical article on the Microsoft website about Session IDs. This cookie expires when you leave our website.
Request Verification Tokens: Our web server may create an essential session cookie called __RequestVerificationToken upon using any of the forms on our website. This cookie allows our server to verify that data provided to the form has come from a visitor, and not a remote machine posting the data directly. This cookie expires when you leave our website.
Analytics: We use Google Analytics, which creates a number of first-party cookies, all prefixed __utm:
- __utma: contains a unique and anonymous identifying ID, which allows us to ensure that subsequent visits to our website are recorded as belonging to the same (unique) visitor. This cookie expires after two years.
- __utmb: used to establish and continue a unique user session. Each time you request another page from the website the cookie is updated to expire after 30minutes.
- __utmc: works with __utmb to determine when to create a new session for a website visitor. This is a session cookie and expires when you exit the browser.
- __utmz: tracks how you found us and is used to calculate traffic and navigation within the website. It is updated with every new page view and expires after 6 months.
- You may also sometimes find a __utmv cookie which relates to custom reporting segments, a feature which may use on Google Analytics.
We don't believe that our use of Google Analytics is privacy-intrusive. We use the data that is collected in the following ways:
- to report, in aggregate, how our visitors find and use our website;
- to understand overall visitor behaviour; and
- to inform how we update and improve our website.
We do allow Google to use this data to collate and aggregate benchmarking data, which they provide to us, about similar websites in our industry. To do this Google further anonymises the analytuics data by removing all identifiable information about our website, and combines the data with hundreds of other anonymous sites in comparable industries.
We do not share our analytics data with any other third parties.
To opt out of our use of Google Analytics you may wish to consider using the Google Analytics Opt-out Browser Add-on.
In Detail: Third-party cookies
In addition to our first-party cookies, you may be served one or more of the following third-party cookies during your visit to our website.
Third party cookies are cookies created by an external service when you use a page on our website. These cookies are specific to the third-party's domain and accordingly the data held in them can be seen and managed by the third party and not by us. We control whether or not we use the third-party service with our website, and how it is integrated and presented on our website. We do not have control over the cookies themselves.
- We provide sharing links for Facebook and Twitter on our property pages. If these links are not clicked, no cookies will be created. However, if the links are clicked, you will be redirected to Facebook or Twitter and prompted to login, whereupon cookies for these services may be created. We provide these buttons as a convenience for our visitors, and we use it on the basis that Facebook and Twitter adhere to their data use policies - see http://www.Facebook.com/about/privacy/ and http://twitter.com/privacy respectively for more information.
- Our "My Braemore" page provides a facility for landlords to log in and view their account balances. This service is hosted separately from the Braemore website and creates a pair of cookies when accessed. It creates one named ASP.NET_SessionId, with similar features to the Braemore site's session ID, documented above. As this service is provided through an Amazon Web Services elastic load balancer, it also creates one named AWSELB. This latter cookie allows the landlord login to be efficiently distributed across several servers so that under heavy loads, performance of the landlord login is not adversely impacted.
For more information