From 3346a02179229af314ecec171e8f85b6a751ede2 Mon Sep 17 00:00:00 2001
From: utopiatopia <98685984+utopiatopia@users.noreply.github.com>
Date: Sun, 26 Nov 2023 00:55:23 -0800
Subject: [PATCH] Add security risks of eavesdropping

---
 docs/privacy-and-security.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/docs/privacy-and-security.md b/docs/privacy-and-security.md
index f855cc3e..f21f8aa0 100644
--- a/docs/privacy-and-security.md
+++ b/docs/privacy-and-security.md
@@ -198,7 +198,9 @@ vim.api.nvim_create_autocmd( {"BufNewFile","BufReadPre" }, {
 
 Please see `:h <option>` in Neovim for more information about the options mentioned.
 
-## Plausible deniability
+## Limitations
+
+### Plausible deniability
 
 You may be able to hide the contents of your journal behind a layer of encryption,
 but if someone has access to your configuration file, then they can figure out that
@@ -206,6 +208,16 @@ you have a journal, where that journal file is, and when you last edited it.
 With a sufficient power imbalance, someone may be able to force you to unencrypt
 it through non-technical means.
 
+### Spying
+
+While `jrnl` can protect against unauthorized access to your journal entries while
+it isn't open, it cannot protect you against an unsafe computer/location.
+For example:
+
+- Someone installs a keylogger, tracking what you type into your journal.
+- Someone watches your screen while you write your entry.
+- Someone installs a backdoor into `jrnl` or poisons your journal into revealing your entries.
+
 ## Saved Passwords
 
 When creating an encrypted journal, you'll be prompted as to whether or not you