From 13865340c23a3c970245025822b5612a4b427c20 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Sat, 24 Feb 2024 15:01:44 +0100 Subject: [PATCH] Add local user erasure requests MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit As per MSC4025. Signed-off-by: Kévin Commaille --- data/api/client-server/registration.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/data/api/client-server/registration.yaml b/data/api/client-server/registration.yaml index 1f823ac8..14d12262 100644 --- a/data/api/client-server/registration.yaml +++ b/data/api/client-server/registration.yaml @@ -614,6 +614,24 @@ paths: it must return an `id_server_unbind_result` of `no-support`. example: example.org + erase: + x-addedInMatrixVersion: "1.10" + type: boolean + description: |- + Whether the user would like their content to be erased as + much as possible from the server. + + Erasure means that any users (or servers) which join the + room after the erasure request are served redacted copies of + the events sent by this account. Users which had visibility + on those events prior to the erasure are still able to see + unredacted copies. No redactions are sent and the erasure + request is not shared over federation, so other servers + might still serve unredacted copies. + + The server should additionally erase any non-event data + associated with the user, such as [account data](/client-server-api/#client-config) + and [contact 3PIDs](/client-server-api/#adding-account-administrative-contact-information). required: true responses: "200":