A cookie consists of information sent by a web server to a web browser, and stored by the browser. The information is then sent back to the server each time the browser requests a page from the server. This enables the web server to identify and track the web browser. Most browsers allow you to reject all cookies, whilst some browsers allow you to reject just third party cookies. For example, in Internet Explorer you can refuse all cookies by clicking "Tools", "Internet Options", "Privacy", and selecting "Block all cookies" using the sliding selector. Blocking all cookies will, however, have a negative impact upon the usability of many websites.

Policy

This policy explains in detail how "MyFamilySolicitor.net" along with its affiliated companies (hereinafter "we", "us", "our", "MyFamilySolicitor.net", "http://www.myfamilysolicitor.net/") use any information collected during any session of usage by you (hereinafter "your information").

Your information is collected via two ways. Firstly, by browsing the pages of "MyFamilySolicitor.net" will cause our software to create a number of cookies, which are small text files that are downloaded on to your computer's web browser temporary files. The first two cookies just contain a user identifier (phpbb3_bcsg1_u hereinafter "user-id") and an anonymous session identifier (phpbb3_bcsg1_sid hereinafter "session-id"), automatically assigned to you by our software.

We may also create cookies external to our software whilst browsing "MyFamilySolicitor.net", though these are outside the scope of this document which is intended to only cover the pages created by our software.

Blog Cookies

Our Blog uses cookies, or tiny pieces of information stored on your computer, to verify who you are. There are cookies for logged in users and for commenters.

Users
Users are those people who have registered an account with the Blog.

On login, our blog software uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area.

After login, our blog software sets the wordpress_logged_in_[hash] cookie, which indicates when you're logged in, and who you are, for most interface use.

Our blog software 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.

Commenters
When visitors comment on our blog, they too get cookies stored on their computer. This is purely a convenience, so that the visitor won't need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:

  • comment_author
  • comment_author_email
  • comment_author_url

The commenter cookies are set to expire a little under one year from the time they're set.

Data
The actual cookies contain hashed data, so you don't have to worry about someone gleaning your username and password by reading the cookie data. A hash is the result of a specific mathematical formula applied to some input data (in this case your user name and password, respectively). It's quite hard to reverse a hash (bordering on practical infeasibility with today's computers). This means it is very difficult to take a hash and "unhash" it to find the original input data.

Our blog software uses the two cookies to bypass the password entry portion of wp-login.php. If you don't have the cookies, or they're expired, or in some other way invalid (like you edited them manually for some reason), our blog software may require you to log in again, in order to obtain new cookies.

Third Party Cookies

When we provide links to third party services you find useful, they may place a cookie on your device to make their service easier to use. Our website may also carry embedded Maps from Google Inc (by use of the interactive Google maps on our Contact Me page), 'share' buttons to enable users of the site to easily share articles with their friends through a number of popular social networks. These sites may also set cookies when you are also logged in to their service. We do not control the dissemination of these cookies and you should check the relevant third party website for more information about these cookies.

How can I help?

* indicates entry required
cron