Cookies Policy
by SEQ Legal
Cookies Policy
(1) Introduction
Our website uses cookies.
[We will ask you to consent to our use of cookies in accordance with the terms of this policy when you first visit our website. / By using our website and agreeing to this policy, you consent to our use of cookies in accordance with the terms of this policy].
(2) Credit
This document was created using an SEQ Legal template.
(3) About cookies
A cookie is a file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.
Cookies can be used by web servers to identity and track users as they navigate different pages on a website and identify users returning to a website.
Cookies may be either “persistent” cookies or “session” cookies.
A persistent cookie consists of a text file sent by a web server to a web browser, which will be stored by the browser and will remain valid until its set expiry date (unless deleted by the user before the expiry date).
A session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.
(4) Our cookies
We use [both] [session cookies] [and] [persistent cookies] on this website.
We [will] send to you the following cookies:
(a) [wp-settings-3] – We will use this [persistent ] cookie to [verify who you are and check if you are logged in to the site or not.].
(b) [wp-settings-time-3] – We will use this [persistent ] cookie to [verify who you are and check if you are logged in to the site or not.].
(c) [wordpress_test_cookie] – We will use this [persistant] cookie to [test if our other cookies work].
(d) [__utma] – We will use this [persistent] cookie 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.].
(e) [__utmb] – We will use this [session] cookie 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.].
(f) [__utmc] 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.].
(g) [__utmv] – We will use this [persistent] cookie 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.].
(h) [__utmz] – We will use this [persistent] cookie to store the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.].
(5) Third party [and analytics] cookies
When you use our website, you may also be sent third party cookies.
[In addition, we use [Google Analytics] to analyse the use of this website. [Google Analytics] generates statistical and other information about website use by means of cookies, which are stored on users’ computers. The information generated relating to our website is used to create reports about the use of the website. [Google] will store this information. [Google’s] privacy policy is available at: [http://www.google.com/privacypolicy.html].]
(6) Cookies and personal information
Cookies do not contain any information that personally identifies you, and no personal information that you submit via the contact form will be linked, by us, to the information stored in and obtained from cookies.
(7) Blocking cookies
Most browsers allow you to refuse to accept cookies. For example:
(a) in Internet Explorer (version 9) you can block cookies using the cookie handling override settings available by clicking “Tools”, “Internet Options”, “Privacy” and then “Advanced”;
(b) in Firefox (version 16) you can block all cookies by clicking “Tools”, “Options”, “Privacy”, selecting “Use custom settings for history” from the drop-down menu, and unticking “Accept cookies from sites”; and
(c) in Chrome (version 23), you can block all cookies by accessing the “Customise and control” menu, and clicking “Settings”, “Show advanced settings” and “Content settings”, and then selecting “Block sites from setting any data” under the “Cookies” heading.
Blocking all cookies will, however, have a negative impact upon the usability of many websites.
(8) Deleting cookies
You can also delete cookies already stored on your computer. For example:
(a) in Internet Explorer (version 9), you must manually delete cookie files (you can find instructions for doing so at http://support.microsoft.com/kb/278835);
(b) in Firefox (version 16), you can delete cookies by clicking “Tools”, “Options”, “Privacy” and then “Show Cookies”, and then clicking “Remove All Cookies”; and
(c) in Chrome (version 23), you can delete all cookies by accessing the “Customise and control” menu, and clicking “Settings”, “Show advanced settings” and “Clear browsing data”, and then selecting “Delete cookies and other site and plug-in data” before clicking “Clear browsing data”.
Again, doing this may have a negative impact on the usability of many websites.
(10) Contact us
This website is owned and operated by [Laura Harvey].
If you have any questions about our cookies or this cookies policy, please contact our webmaster:
(a) by email (to [info@reyeng.com]);
You must retain the SEQ Legal credit and link set out in Section 2 above. However, professional legal documents do not ordinarily include such credits and links. You can purchase the right to use this document without the credit and link here:
http://www.website-contracts.co.uk/acatalog/cookies_policy.html
Unless you have purchased this right, it is an infringement of copyright and breach of licence to use this document without the credit and link.