CoachCox

Privacy & Cookie Policy

Who we are

We are https://www.coachcox.co.uk, owned and managed by Russell Cox.

What personal data we collect and why we collect it

We do not directly collect or retain personal data about our visitors. We do use analytics packages and third party services that may collect limited data about visitors, these are all specified on this page. If you have made a donation via Paypal, commented via Disqus or emailed me directly. I will have access to the personal data you provided via those platforms and methods.

Comments

We accept comments using the Disqus platform. When visitors leave comments they provide their name and email to Disqus. You can find out more about the Disqus privacy policy at https://help.disqus.com/terms-and-policies/disqus-privacy-policy

We have previously used WordPress Comments. If you have submitted a comment before 2017 you will have submitted information directly to this site. We will have collected your name and IP address with your comment and you may have submitted your email.

Cookies

We use a number of different cookies. If you don’t know what cookies are, or how to control/delete them, then I recommend you visit http://www.aboutcookies.org for more guidance.

The following list describe the cookies used on this site and what they are used for. Usage of this site implies you are happy to receive these cookies. If you’re not happy, then you should either not use this site, delete the cookies having visited the site, or use the site with your browser’s anonymous usage setting.

WordPress: we run the WordPress CMS and cookies are used to store basic data on your interactions with WordPress and to track pages visited on this site.

More information on session cookies and what they are used for at http://www.allaboutcookies.org/cookies/session-cookies-used-for.html

WordPress.com Stats: we use the WordPress.com Stats analytics package and cookies are used to to gather information on visitor behaviour. WordPress.com collects IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. We do not have access to any of this information via this feature. For example, we can see that a specific post has 285 views, but we cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.

Third Party Cookies: these are cookies set on your machine by external websites whose services are used on this site. Cookies of this type are used by the sharing buttons that allow users to share content onto social networks. Cookies are currently set by Twitter, Facebook, Google+ and Disqus. In order to implement these buttons, and connect them to the relevant social networks, there are scripts from outside of this website. These sites are likely to be collecting information about what you are doing all around the internet, including on this website.

Google Analytics: in the past Google Analytics collected information about visitor behaviour on this website. Google Analytics stores information about what pages you visit, how long you are on the site, how you got here and what you click on. This Analytics data was collected via a JavaScript tag in the pages of this site and is not tied to personally identifiable information. We did not collect or store your personal information (e.g. your name or address) so this information cannot be used to identify you. We no longer use Google Analytics, but the cookie and the data collected may remain.

You can find out more about Google’s position on privacy as regards its analytics service at https://www.google.com/policies/privacy/

Check the respective policies for these sites to see how exactly they use your information and to find out how to opt out, or delete, such information.

Analytics

We use the WordPress.com Stats analytics package.

Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: We do not have access to any of this information via this feature. For example, we can see that a specific post has 285 views, but we cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.

Activity Tracked: Post and page views, outbound link clicks, referring URLs and search engine terms, and country. When this module is enabled, Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, Javascript files, CSS files, etc.).

Who we share your data with

By default we do not share any personal data with anyone.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

Identifying analytical data is held by WordPress.com for 28 days.

What rights you have over your data

We hold limited personal data. If you have left a comment prior to 2017 you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes. For more recent comments requests should be made via Disqus in accordance with their privacy policy.

Contact Information

Questions and concerns around privacy should be directed to Russell Cox.