Skip to content

MSC4265: Data Protection Officer contact in /.well-known/matrix/support#4265

Open
Johennes wants to merge 1 commit into
matrix-org:mainfrom
Johennes:johannes/dpo-role
Open

MSC4265: Data Protection Officer contact in /.well-known/matrix/support#4265
Johennes wants to merge 1 commit into
matrix-org:mainfrom
Johennes:johannes/dpo-role

Conversation

@Johennes
Copy link
Copy Markdown
Contributor

@Johennes Johennes commented Feb 14, 2025

Rendered


In line with matrix-org/matrix-spec#1700, the following disclosure applies:

I am a Systems Architect at gematik, Software Engineer at Unomed, Matrix community member and former Element employee. This proposal was written and published with my gematik hat on.

@Johennes Johennes marked this pull request as ready for review February 14, 2025 14:20
@Johennes Johennes changed the title MSCXXXX: Data Protection Officer contact in /.well-known/matrix/support MSC4265: Data Protection Officer contact in /.well-known/matrix/support Feb 14, 2025
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Feb 14, 2025
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Server publishing this
  • Client using this

While a server's support document under [/.well-known/matrix/support] can expose
an "admin" contact, this might not be specific enough for the purposes outlined
above – especially since server administrators and data protection officers are
usually different roles in companies.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes a good point and is similar to the point made in #4121. Its also a very useful bit of knowledge to have easy access to the DPO contact via this standardised pathway.

@aine-etke
Copy link
Copy Markdown

Used by MRS via go-msc1929 library

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants