Privacy Policy

My Take on Privacy

As of , I am using NearlyFreeSpeech.net for hosting Take on Rules.

Personally, I do not log requests nor set cookies. I’ve read over NearlyFreeSpeech’s privacy policy, which directly applies to me.

In combing their forums, one of the representatives wrote the following:

If you do not have access logs enabled, IP address of visitors to your site are only retained for a limited time for purposes of network and information security. No consent is required for that, and access control is very limited. (I.e. even you can’t have them.)

If you do have access logs enabled and you have concerns, you could disable them, or you could set up a scheduled task to post-process them to remove information and/or wipe out older ones on a regular basis.

In the above quote, “you” means me (Jeremy) and “your site” means TakeOnRules.com.

What that means is I don’t know who’s requesting pages from my site. I do have the capability to turn on logging, which I might use if I need to troubleshoot something. On I turned on logging for about 10 minutes as I tested caching. I turned off logging, and set the rotation timeframe to one day. So on those files should be cleared and their content deleted.

Another topic that warrants mentioning. This site does not provide a direct commenting mechanism. Instead, I will often post a link to my blog post on Twitter, Mastodon, and/or Reddit. I also receive emails from people. On those sites, I respond to comments.

Those comments matter, because I enabled Webmentions via webmention.io. I use Bridgy to capture those replies and add them to the post as a webmention. Which means someone’s comments could show up on my site. If you want one of your comments removed, please contact me.

If you send me an email, I’ll respond. Sometimes your email might trigger an idea for a blog post. Before I use any of your words, I’ll get your explicit approval. And that’s something we would both need to work out.

Hosting for Take on Rules between and Since , I have used Github Pages to host Take on Rules.

Below is Github’s privacy policy regarding site’s hosted via Github Pages:

If you create a GitHub Pages website, it is your responsibility to post a privacy statement that accurately describes how you collect, use, and share personal information and other visitor information, and how you comply with applicable data privacy laws, rules, and regulations. Please note that GitHub may collect User Personal Information from visitors to your GitHub Pages website, including logs of visitor IP addresses, to comply with legal obligations, and to maintain the security and integrity of the Website and the Service.

In I removed Google Analytics and Google Tag Manager from my site. Also in , I removed custom fonts. I instead use common fonts (e.g. Times, Helvetica, Courier).

I use javascript to provide a site-wide search and dynamic data-tables. You can turn off javascript and the site still functions. I use javascript to offer progressive enhancement. I don’t use javascript to track clicks or your actions on the site.

On I moved away from using an external Content Delivery Network (CDN 📖) to deliver javascript assets.

All of this is to say, I don’t track your personal nor visitor information. I’m also structuring the site so that only the server’s host (e.g. Github) has access to your interaction with this site.

, I am open to moving away from Github, but for now it’s working well enough.