Draft of the new mission statement to be decided by the membership assembly

[zner0L]

This is a preliminary draft and can only be merged, if we the membership assembly accepts the new mission statement and constitution.

[cypress[bot]]

1 failed test on run #5331 ↗︎

1

79

8

0

0

Details:

A few changes as discussed
Project: datenanfragen/website	Commit: 7c403c0fc4
Status: Failed	Duration: 04:27 💡
Started: Nov 29, 2023 5:46 PM	Ended: Nov 29, 2023 5:50 PM

  cypress/e2e/privacy-controls/company-search-page.spec.js • 1 failed test

View Output Video

Test		Artifacts
Search bar on company search page > is active by default		Screenshots Video

Review all test suite changes for PR #1117 ↗︎

[christian-weiss]

"Forschung" (science) requires data. What kind of research / science do you want to undertake or support? What type of data may be required? Free contribution of data may lead to a bias.

I support a change of your mission statement towards science and statistic data, when contributions are anonymous or optional.

[baltpeter]

"Forschung" (science) requires data. What kind of research / science do you want to undertake or support? What type of data may be required? Free contribution of data may lead to a bias.

I support a change of your mission statement towards science and statistic data, when contributions are anonymous or optional.

We are not talking about research with user data. You can see a few examples of the types of research we done already on our site, e.g.:

https://www.datarequests.org/blog/android-data-safety-labels-analysis/ https://www.datarequests.org/blog/honey-data-collection/ https://www.datarequests.org/verein/event/netzpolitischer-abend-122-2022/ https://www.datenanfragen.de/verein/event/fireshonks-tracking-2022/ https://www.datarequests.org/verein/event/edpb-expert-talk-2023/

[christian-weiss]

We are not talking about research with user data. You can see a few examples of the types of research we done already on our site, e.g.:

https://www.datarequests.org/blog/android-data-safety-labels-analysis/ https://www.datarequests.org/blog/honey-data-collection/ https://www.datarequests.org/verein/event/netzpolitischer-abend-122-2022/ https://www.datenanfragen.de/verein/event/fireshonks-tracking-2022/ https://www.datarequests.org/verein/event/edpb-expert-talk-2023/

I would welcome some statistics about (list is just for illustration; each data point needs to be discussed for sure):

• how often request do not get answers
• how often requests got answers on time (within legal time frame) / how often the requests gets an answers but overdue
• how often the answer is not satisfying the request
• when (in days / hours) the requester gets a confirmation of receipt if at all
• what is the "performance" of each GDPR responsible (good, bad, no response; response time, etc.)
• more ideas to come

Allow GDPR responsible to share "statistic data" as part of their transparency strategy, but also to allow requesters to share data anonymously / pseudonym to allow building up "open data" for science. Collecting of data and analysis could be done by partnering with universities, citizen science organizations.

I would love to see a section about these kind of scientific analysis. Personally i would love to get a better understanding how often (percentage) GDPR requests leads to finding GDPR issues, to GDPR legal complain (court) or to GDPR supervisory complaints. At least approximately (based on science, not on gut feelings). This would help to detect if there is a gap between law maker targets and practical implementation.