Skip to Overview
Skip to cookies section.

image of wolf looking after sheep

Do you feel safer now?

This is all rather silly. The regulations that site owners are forced to implement only give an illusion of privacy. Governments and big corporations don’t care at all about your privacy, in fact, they would rather you had none. It’s better to understand that and not ask the predators to protect us.

However, some governments decided to impose some regulations on some types of sites. Rather than wade through those regulations to see if we might be in danger, we thought it would be quicker to just comply anyway. We think if you take a look (pdf), you’ll agree. (scroll down… it’s unbelievable, no wonder they need all those billions in taxes!)

And there is more crap on the way too, see Update on EU’s Copyright Reform Proposal (youtube)


We don’t ask for any personal info except your email address. If you like, you can use a different address set up just for this site, or even something like (but then we would not be able to contact you). You must accept that anything you enter in the site could be leaked or stolen by third parties. Nothing is 100% secure anywhere.

Over time, we aim to get rid of anything google, facebook, etc, but for now, there may be a bit of tracking going on from them. It’s hard to do a site without that getting in these days.

We’ve made it relatively easy to make it difficult to identify you if you want it to be, at least on our side. The rest is up to you.

For ads, we use a-ads, who don’t track you. See our review!

We use for the wallet addresses, but the only data that they have is the currency addresses and the amounts transferred. You can only transfer funds within the site to other users (i.e. those running the projects you can see on the site). Without external transfers on the blockchain happening, the usual stuff about using blockchain analytics tools to personally identify a user does not apply here (as far as we know…).

Transferring funds in from an external wallet that you own might be identifiable, depending on how you’ve set up and used your own wallets.

Site Metrics

Instead of using an external site analytics service we use our own, located on our own server. The tracker is called Matomo, and you can see what data it can track on their FAQ page. The settings we used in our instance are recorded in this pdf: Anonymize data – Administration – Matomo.pdf. The purpose of this tracking is to see what sites our visitors come from, what pages they view and which links they leave from.

CoinPayments Adapter

When you perform cryptocurrency transactions on this site, we may transmit some of the transactions that you perform to a third party service, This service maintains cloud wallets and may use transaction information to perform withdrawals or to receive deposits on your behalf. This transaction information can include blockchain addresses and transaction IDs that, using analytics tools or via other means, can be used to identify your financial transactions on a cryptocurrency network.

Bitcoin and Altcoin Wallets

When you perform cryptocurrency transactions to and from this site, such as deposits or withdrawals, we record details of these transactions to credit or debit your cryptocurrency wallets. The details recorded for cryptocurrency transactions include blockchain addresses and transaction IDs that can potentially be used to personally identify you via blockchain analytics tools or other methods (let your imagination run wild!).


Contact Form

Data Used: If Akismet is enabled on the site, the contact form submission data — IP address, user agent, name, email address, website, and message — is submitted to the Akismet service (also owned by Automattic) for the sole purpose of spam checking. The actual submission data is stored in the database of the site on which it was submitted and is emailed directly to the owner of the form (i.e. the site author who published the page on which the contact form resides). This email will include the submitter’s IP address, timestamp, name, email address, website, and message.

Data Synced (?): Post and post meta data associated with a user’s contact form submission. If Akismet is enabled on the site, the IP address and user agent originally submitted with the comment are synced, as well, as they are stored in post meta.

Jetpack Comments

Data Used: Commenter’s name, email address, and site URL (if provided via the comment form), timestamp, and IP address. Additionally, a IFrame receives the following data: blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content. If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.

Activity Tracked: The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.

Data Synced (?): All data and metadata (see above) associated with comments. This includes the status of the comment and, if Akismet is enabled on the site, whether or not it was classified as spam by Akismet.

Mobile Theme

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. Stats

Data Used: IP address, user ID (if logged in), 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 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.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.

Social Media

We offer you the possibility to use so-called “Social Media Buttons”. The share buttons are implemented as static images, which contain a link to the corresponding social network site. If you click on such a button, you will be redirected to the respective social network site in the same way, as normal links would do as well. If you do not click on such a share button, no data will be transmitted.


If you’re not a member, these are the cookies we found in our last audit. For the most up-to-date cookie scan, see the cookie scan page.

For Members, we use additional cookies to track wallet transactions and to save you from being logged out each time you open a new page.


Leave Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.