Table of Contents

1. Mikkl's view on data collection

I refuse to collect, manage and process any personal data that's not considered a fundamental "legal requirement." Privacy is important, and I do not tolerate practices based around user tracking and data collection.

I am actively combatting the mass media's excessive use of tracking cookies by encouraging tracker blocking and by educating others of the benefits of this concept.

This is why I've opted to not allow 3rd-party advertisements on my website, and in general commit to limiting external dependencies and third-party integrations to a bare minimum.

2. Data Policy

2.1. What's being collected?

All requests sent from your browser to this domain's server will be logged, along with an HTML status code and your IP address, browser name and user agent type. All of which are processed when your browser sends a connection request to this domain by Simply.com A/S's servers, functioning as this domain's hostmaster and data processor, by storing said information on their servers.

All data is temporary, subject to removal after 30 days and is neither shared or showcased to any external party.

To understand Simply.com's role as a data processor, please read Simply's compliance policy: https://www.simply.com/en/compliance/

2.2. Purpose

As HTML status codes from individual requests are being logged and processed, this data can determine individual computer's webflow. By individually comparing page load requests and status code with a timestamp, this allows me to determine a user's webflow and to note fundamental problems and errors, which is an essential factor for long-term maintenance without the use of tracking utilities.

Logging is a fundamental cornerstone for Simply.com's ability to combat bots, spam, illegal and malicious requests forwarded their clients and customers. Records shows this is a serious problem, in which numerous malicious requests are blocked on a daily basis.

3. How to avoid web trackers

It is possible to block and remove web trackers and 3rd-party cookies from common websites through browser extensions.

A key advantage to blocking trackers is that it makes user tracking a lot more difficult and less reliable, which is an effective tool against corporate greed, and as an added bonus, these systems remove advertisements as well as thousands of common "ad-block detection blockades".

3.1. Tutorial: Install anti-tracker extensions

Step 1: Install the following extensions from their respective website

1.   uBlock Origin
2.   Privacy Badger

Step 2: Click the uBlock icon and open the Control Panel by clicking the "gear icon" in the flyout

Step 3: Select the "Filters" tab, click the arrow icons on the left within the list and select as many filters as you'd like. (The more the merrier)

Please note: These anti-trackers double as ad blockers. Google is actively combatting adblockers and may restrict these extensions in the future.

3.2. How do these extensions work?

uBlock Origin is extremely comprehensive and can block IPs and domains of malicious advertisers, but at the same time, it's able to strip HTML code and remove it before it has a chance to send a server request and load.

This is possible, as tens of thousands of users maintain so-called lists with instructions the plugin use to block and filter said elements and, domains and IPs.

Unfortunately, uBlock is unable to edit code that's considered a tracker - so if it's embedded in an important element or web feature, the entire feature will be blocked or removed, which may result in some websites not working properly.

Privacy Badger monitors active connections from 3rd-party sites that's linked to the websites you visit. If these active connections get called from multiple domains or references, they get blocked. This is particularly useful against aggressive means of tracking, such as "super cookies", as well as tracking on niche websites that's not maintained through common filters.

Be aware that this method only protects against "browser fingerprinting" and IP logging to a limited extend.

4. Privacy Policy Changelog

To maintain transparency, a historical change record to this sitewide Privacy Policy is being logged below.

• June 5th, 2024:
  • Clarified a sentence in 2.1 which were questionably incohesive
  • Updated 2.2 "Logging" segment to reflect on an increase of malicious requests
  • Numerus grammatical and spelling amendmands
  • Added segment "4. Privacy Policy Update Log"
  • "4. Contact Information" has been moved to "5. Contact Information"

5. Contact information

Please don't hesitate to reach out to my mail adress at mail@mikkl.info for inqueries or questions regarding your data.