privacyguides/blog.privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/blog.privacyguides.org.git synced 2025-07-24 04:11:05 +00:00
Code Activity

Cover images

Browse Source
This commit is contained in:
Jonah Aragon
2023-04-15 14:49:05 -05:00
parent aeae57e414
commit a196711848
25 changed files with 43 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/posts/security-privacy-anonymity.md
View File

@@ -13,6 +13,8 @@ license: BY
---
# Security, Privacy, and Anonymity
![](../assets/images/security-privacy-anonymity/cover.jpeg)
We may think that we know the differences between privacy, security and anonymity, however we often mix them up. People will often criticize a product or service as “not private” when they really mean “not anonymous.” Privacy, security, and anonymity often complement each other, but they are not always dependent on each other, and they are definitely not the same thing. A service can be private without being anonymous, or even secure without being private. Which one should you prioritize?<!-- more --> To some extent, there are no wrong answers. It really comes down to your threat model and what your desired goal is. It is perfectly fine to pick a product that provides privacy even though it doesn't provide anonymity. Furthermore, it's okay to pick a product that doesn't provide security if it does provide one of the other features. The important thing is that you need to be aware what these products and services are and aren’t offering you so that you can use them correctly.
There’s lots of ways to define privacy, security, and anonymity. Someone showed me [this](https://github.com/privacytools/privacytools.io/issues/1760#issuecomment-597497298) definition and I really liked it. It seems to pretty much hit the nail on the head when applying these terms specifically to data privacy and cybersecurity: