diff --git a/src/plugins/FreedomChat-Paper-1.7.0.jar b/src/plugins/FreedomChat-Paper-1.7.0.jar
new file mode 100644
index 0000000..e8de65a
--- /dev/null
+++ b/src/plugins/FreedomChat-Paper-1.7.0.jar
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc5cda172c9548035bba469df3f261a7918d2eab57f632fbbbce0f00a544a8d6
+size 9303
diff --git a/src/plugins/FreedomChat/config.yml b/src/plugins/FreedomChat/config.yml
new file mode 100644
index 0000000..4172088
--- /dev/null
+++ b/src/plugins/FreedomChat/config.yml
@@ -0,0 +1,17 @@
+# Whether FreedomChat should replace player (signed or unsigned) chat with
+# system messages. This is what makes chat not reportable.
+rewrite-chat: true
+
+# Whether FreedomChat should claim to clients that secure chat is enforced.
+# With this set to true, the "Chat messages can't be verified" toast will not
+# be shown. This is, in default configurations, unrelated to allowing clients
+# not signing their messages join. In modern versions, clients also
+# require a valid access token to be present for the toast to be hidden.
+# That being said, you may still see the toast even if this option is enabled.
+claim-secure-chat-enforced: true
+
+# Whether to report the server as secure (disabling chat reporting) to the
+# NoChatReports client mod. This displays a green icon on the server list
+# screen and if enforce-secure-profiles is disabled the open chat screen
+# for users of the client-side mod.
+send-prevents-chat-reports-to-client: true
diff --git a/src/server.properties b/src/server.properties
index d7a014a..6a3d21e 100644
--- a/src/server.properties
+++ b/src/server.properties
@@ -13,7 +13,7 @@ enable-jmx-monitoring=false
 enable-query=false
 enable-rcon=false
 enable-status=true
-enforce-secure-profile=true
+enforce-secure-profile=false
 enforce-whitelist=false
 entity-broadcast-range-percentage=100
 force-gamemode=false