From ddd83ec75fa98c193d95ebaa2d80b1c49b4cf0fd7127b3fbc3aa52393e3e563e Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Tue, 2 Aug 2022 00:00:00 +0000 Subject: Remove the privacy-notice page It clutters up the homepage with a link to information that is explained in one sentence on the about page: for maximum privacy, use Tor or I2P. --- content/privacy-notice.md | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 content/privacy-notice.md (limited to 'content/privacy-notice.md') diff --git a/content/privacy-notice.md b/content/privacy-notice.md deleted file mode 100644 index 4add63b..0000000 --- a/content/privacy-notice.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: "Privacy Notice" -date: 2022-04-27T00:00:00 -draft: false -_build: - list: never ---- -# PRIVACY NOTICE -## IP Logging -The main Nicksphere mirror (nicksphere.ch) is configured not to log any IP addresses whatsoever. It does not log Gemini requests nor Web requests. It does not log IP addresses for the clearnet, Tor, nor I2P. I have no control over what the other mirrors log. - -You shouldn't trust mine or anyone else's claims about IP logging. You have no way to confirm that I don't log IPs and even if I don't, there are several other ways an attacker can see that you're accessing the Nicksphere. So if privacy is important to you, use Tor or I2P. - -## Referrer Header -There's one more privacy concern, but it only applies to Web mirrors. HTTP supports a nasty anti-feature called a referrer header. When you click on a link, the destination website can see which website you came from. - -The "noreferrer" attribute I added in the HTML prevents this on the main mirror and on SourceHut. The Flounder mirror leaks the referrer header and there's nothing I can do about it. -- cgit v1.2.3