Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Johennes
Copy link
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
@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
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
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.

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.

3 participants