diff --git a/api/DEPS b/api/DEPS
index 58b673646e..5b3267e993 100644
--- a/api/DEPS
+++ b/api/DEPS
@@ -9,7 +9,6 @@ include_rules = [
   "-call",
   "-common_audio",
   "-common_video",
-  "-crypto",
   "-data",
   "-examples",
   "-ios",
diff --git a/crypto/OWNERS b/crypto/OWNERS
deleted file mode 100644
index e5b632a4eb..0000000000
--- a/crypto/OWNERS
+++ /dev/null
@@ -1,8 +0,0 @@
-benwright@webrtc.org
-steveanton@webrtc.org
-qingsi@webrtc.org
-
-# These are for the common case of adding or renaming files. If you're doing
-# structural changes, please get a review from a reviewer in this file.
-per-file *.gn=*
-per-file *.gni=*
diff --git a/crypto/README.md b/crypto/README.md
deleted file mode 100644
index acb40eb6dd..0000000000
--- a/crypto/README.md
+++ /dev/null
@@ -1,11 +0,0 @@
-## What should be in the crypto directory
-The crypto directory is intended to be a centralized location for all
-cryptography code in WebRTC. This includes DTLS-SRTP, SRTP, HTTPS,
-TLS, cryptography primitives interfaces such as HKDF and secure random
-(backed by a concrete implementation in BoringSSL).
-
-## What should not be in the crypto directory
-The crypto directory is not a general purpose security directory. Security
-utilities such as ZeroBufferOnFree should still go in rtc_base/ and fuzzing
-utilities in test/fuzzers. ASAN, TSAN and MSAN sanatizer utilities should also
-not be in this directory.