1
0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2025-07-24 20:31:05 +00:00

Correct Additional HTML Validation Errors

This commit is contained in:
2021-05-01 21:51:24 -05:00
parent d04b88ad06
commit 3c17452009
10 changed files with 47 additions and 45 deletions

View File

@@ -137,7 +137,6 @@ breadcrumb: "VPN"
<ul>
<li>Must self host analytics (no Google Analytics etc). The provider's site must also comply with <a href="https://en.wikipedia.org/wiki/Do_Not_Track">DNT (Do Not Track)</a> for those users who want to opt-out.</li>
</ul>
</li>
<p>Must not have any marketing which is irresponsible:</p>
<ul>
<li>Making guarantees of protecting anonymity 100%. When someone makes a claim that something is 100% it means there is no certainty for failure. We know users can quite easily deanonymize themselves in a number of ways, eg:</li>
@@ -145,7 +144,7 @@ breadcrumb: "VPN"
<li>Reusing personal information eg. (email accounts, unique pseudonyms etc) that they accessed without anonymity software (Tor, VPN etc)</li>
<li><a href="https://www.privacytools.io/browsers/#fingerprint">Browser fingerprinting</a></li>
</ul>
<li>Claim that a single circuit VPN is "more anonymous" than Tor, which is a circuit of 3 or more hops that regularly changes.</a></li>
<li>Claim that a single circuit VPN is "more anonymous" than Tor, which is a circuit of 3 or more hops that regularly changes.</li>
<li>Use responsible language, eg it is okay to say that a VPN is "disconnected" or "not connected", however claiming that a user is "exposed", "vulnerable" or "compromised" is needless use of alarming language that may be incorrect. For example the visiting user might be on another VPN provider's service or using Tor.</li>
</ul>
</div>