You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

3.8 KiB

layout title description subtitle permalink cover
page Privacy Policy I encourage you to read the whole document. It's not particularly long or difficult to understand. What's being done with your data? /privacy/ /assets/posts/privacy.png

Privacy Policy

This will hopefully be the briefest "legal" document you've ever read as well as the most readable. If you need additional information let me know and I'll add it.

IP Address

Some applications (Gitea, Mumble, XMPP, and NixNet Mail) collect your IP when you register. At the moment, that information is kept indefinitely. However, I'm working on either completely disabling it or setting something up that will periodically delete stored IP addresses. When I do, this document will be updated accordingly.

If you don't want me to have that information to begin with, just use Tor Browser.

Email Address

When you register for a service using an email address, that is obviously collected. You can control whether it's a real one or not. Even though I can see them for services like Gitea and Mastodon, I don't care and won't send you unsolicited mail.

Note: whatever address you use for git is visible in commits.

Browser Fingerprint

Your web browser communicates uniquely identifying information to all websites it visits by allowing the site to know details about your operating system, browser information, plugins installed, fonts installed, screen resolution, and much more. As far as I know, nothing collects or uses any of that information.

Usage and storage of collected information

Whatever data is collected is stored on servers I have sole control over and it won't be shared with any third parties whatsoever.

DNS services

In short:

  • Haproxy TCP/HTTP logs are disabled. No IP addresses are collected.
  • Unbound debug logs are enabled (verbosity: 1).
  • Query amounts coming specifically from the DNS-over-TLS server aren't counted.
  • Website/DNS-over-HTTPS gateway's NGINX logs are disabled.

To elaborate on Unbound's verbosity, if you have it installed, you can run man unbound.conf, search verbosity and read it yourself. More human-readably . . .

  • Level 0 only outputs errors
  • Level 1 gives high-level operational information (debug logs)
  • Level 2 gives detailed debug logs
  • Level 3 shows the admin what queries are going through Unbound
  • Level 4 gives lower-level algorithm information
  • Level 5 logs client information

There's no warranty, no uptime assurance, etc. so I recommend using multiple resolvers; that also improves privacy because the DNS queries are spread across multiple providers

Exceptions

I do live in the US; I have three servers here, three in Germany, and another in Luxembourg. If, for whatever reason, I'm compelled by law enforcement to give up your email, IP address, or any other information, I will even though I don't want to. As such, I do whatever I can to make sure I don't have that information. If I don't have it, I can't share it.

Recommendations

To mitigate invasions of privacy like this, use a throwaway email address for registration, such as one from anonbox if you want a temporary address or cock.li for something a bit more permanent. Also provide a fake name and use the service from behind Tor or a VPN. Rather than a VPN, however, I strongly recommend using Tor across all devices. They have an Android version now and there's another browser they recommend for iOS called Onion Browser. I don't use iOS so I can't say whether or not it's any good, just that the Tor Project recommends it.