The data collected with this site and its underlying mechanisms are for maintaining the website and simple reach measurements only. This includes all data collected by the webserver that is stored in logfiles. These data contain your IP address (at the moment of access), your browser name, the referring link, and other technical data like the files transferred, their size, the http code, timestamp etc. Since this blog is a private business, there is no purpose for these logs other than measuring the site’s popularity. Logfiles get deleted after a couple of months.
There are affility links that, once clicked, send you to the original producer’s website. In almost all cases my affiliate code is the only relevant bit of information that gets sent to that site. There is no personal information (other than your IP address) that gets transferred. If you don’t want your IP address logged by me or anything else in the world (there are good reasons for doing so), I’d recommend using a VPN or similar techniques of covering up this information.
I have disabled all methods of submitting comments here. There is also no contact form where you would be able to leave your personal data and ‘liking’ posts isn’t possible, either. This site is connected to Akismet, but no spam filtering will happen until the day I’m going to enable commenting again. There’s also no possibility to share any content. This is both good and bad, but actually I don’t want Google and facebook make money with the things you and I like.
This website is hosted in the US. That means all data transmitted from my site to your client and back is leaving the legal space of EU. There is not much that I can do (or want to do). Since there is no other personal information but your IP address I assume that you accept this fact implicitly.
Here is what WordPress has to say about all this:
This feature only records activities of a site’s registered users, and the retention duration of activity data will depend on the site’s plan and activity type.
Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may also include the actor’s IP address (login attempts, for example) and user agent.
Activity Tracked: Login attempts/actions, post and page update and publish actions, comment/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of other various site settings and options. Retention duration of activity data depends on the site’s plan and activity type. See the complete list of currently-recorded activities (along with retention information).
Data Synced (?): Successful and failed login attempts, which will include the actor’s IP address and user agent.
This feature is only available to sites on the Premium and Professional plans.
Data Used: The following information (made available from the visitor’s browser) is collected and sent to Automattic’s Demand Partners: IP address, geographical data (derived from the IP address), user agent, operating system, device type, unique user ID (randomly generated identifier), current URL, and IAB (Interactive Advertising Bureau) interest category. Log data (IP address, geographical data, user agent, operating system, device type) is stored for 30 days. The unique user ID is stored in cookies and is retained for 1 year.
Activity Tracked: Ad impressions, video-related events (i.e. pause, mute, 100% plays, etc.) or errors, and ad click events. Various cookies are used for the following purposes: delivering targeted advertisements to specific visitors, storing user identifiers, and collecting anonymous ad platform stats.
Image views are only recorded if the site owner, has explicitly enabled image view stats tracking for this feature via the
Data Used: If image view tracking is enabled, the following information is 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.
Activity Tracked: Image views.
Data Used: A visitor’s preference on viewing the mobile version of a site.
Activity Tracked: A cookie (
akm_mobile) is stored for 3.5 days to remember whether or not a visitor of the site wishes to view its mobile version. Learn more about this cookie.
Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.
Activity Tracked: Failed login attempts (these include IP address and user agent). We also set a cookie (
jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.
Data Synced (?): Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.
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 for 28 days and are used for the sole purpose of powering this feature.