Cookie Policy
Cookies are small snippets of text that are placed on your machine to help the site provide a better user experience. In general, cookies can be used to retain user preferences, store information for things like shopping carts, and provide anonymised tracking data to third party applications like Google Analytics.
However, the software that underpins this website only uses cookies in order to keep track of the number of unique visitors that view the site, in other words to see how many people are visiting us and so that we do not count people twice. Cookies expire on a regular basis and are not stored permanently.
No data on individuals is collected or stored by this website.
As a rule, cookies will make your browsing experience better. However, you may prefer to disable cookies on this site and on others. The most effective way to do this is to disable cookies in your browser. We suggest consulting the Help section of your browser or taking a look at the About Cookies website which offers guidance for all modern browsers
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: The site owner does not have access to any of this information via this feature.
For example, a site owner can see that a specific post has 285 views, but he/she 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 (WordPress) 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.).