diff --git a/FAQ.md b/FAQ.md
index 29009b1ec4..666a47da9f 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -1134,9 +1134,9 @@ You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
-*pretty Easy privacy*
+*Planck Security* (formerly: *pretty Easy privacy* or p≡p)
-There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people are using it.
+There is still no approved standard for p≡p and not many people are using it.
However, FairEmail can send and receive PGP encrypted messages, which are compatible with p≡p.
Also, FairEmail understands incoming p≡p messages since version 1.1519,
diff --git a/index.html b/index.html
index f38153a134..c548463313 100644
--- a/index.html
+++ b/index.html
@@ -8,10 +8,19 @@
@@ -778,8 +787,8 @@ openssl pkcs12 -export -legacy -in certbag.pem >legacy.p12
openssl smime -verify <xxx.eml
You can decode S/MIME signatures, etc, here.
pretty Easy privacy
-There is still no approved standard for pretty Easy privacy (p≡p) and not many people are using it.
+Planck Security (formerly: pretty Easy privacy or p≡p)
+There is still no approved standard for p≡p and not many people are using it.
However, FairEmail can send and receive PGP encrypted messages, which are compatible with p≡p. Also, FairEmail understands incoming p≡p messages since version 1.1519, so the encrypted subject will be shown and the embedded message text will be shown more nicely.
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.