From cb87f554ef6de43671132236127c63a6d5077ac4 Mon Sep 17 00:00:00 2001
From: Phil Porada <philporada@gmail.com>
Date: Fri, 21 Jun 2024 15:56:17 -0400
Subject: [PATCH] Let's Encrypt is never in control of a Subscriber's private
 key and thus has no say in their private key destruction

---
 CP-CPS.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/CP-CPS.md b/CP-CPS.md
index 1bc09d6..53c4efb 100644
--- a/CP-CPS.md
+++ b/CP-CPS.md
@@ -929,8 +929,6 @@ ISRG CA Private Keys are always stored on HSMs and deactivated using the mechani
 
 ISRG CA Private Keys are destroyed by Trusted Contributors using a FIPS 140-2 (or higher) validated zeroize method provided by the HSMs storing the keys. Physical destruction of the HSM is not required.
 
-See the Let's Encrypt Subscriber Agreement for information regarding Subscriber private key destruction.
-
 ### 6.2.11 Cryptographic Module Rating
 
 See Section 6.2.1.