diff --git a/changelogs/client_server/newsfragments/1196.removal b/changelogs/client_server/newsfragments/1196.removal
new file mode 100644
index 000000000..c09a4b0de
--- /dev/null
+++ b/changelogs/client_server/newsfragments/1196.removal
@@ -0,0 +1 @@
+Remove unused policy room sharing mechanism, as per [MSC3844](https://github.com/matrix-org/matrix-spec-proposals/pull/3844).
\ No newline at end of file
diff --git a/content/client-server-api/modules/moderation_policies.md b/content/client-server-api/modules/moderation_policies.md
index 027edd5d5..0f537e117 100644
--- a/content/client-server-api/modules/moderation_policies.md
+++ b/content/client-server-api/modules/moderation_policies.md
@@ -76,18 +76,6 @@ joining or peeking the room. Joining or peeking is not required,
 however: an implementation could poll for updates or use a different
 technique for receiving updates to the policy's rules.
 
-#### Sharing
-
-In addition to sharing a direct reference to the room which contains the
-policy's rules, plain http or https URLs can be used to share links to
-the list. When the URL is approached with a `Accept: application/json`
-header or has `.json` appended to the end of the URL, it should return a
-JSON object containing a `room_uri` property which references the room.
-Currently this would be a `matrix.to` URI, however in future it could be
-a Matrix-schemed URI instead. When not approached with the intent of
-JSON, the service could return a user-friendly page describing what is
-included in the ban list.
-
 #### Events
 
 The `entity` described by the state events can contain `*` and `?` to