Issue #1951
openDocument more precisely GDPR compliance
0%
Updated by Denis 'GNUtoo' Carikli about 5 years ago
- how and what kind of data we are using for what
how we can be contacted for requests- how you can gather your data
how you can disable/forget all your dataThis feature is available through the account interfaces of the various software we use.
This has been inspired from https://git.card10.badge.events.ccc.de/card10/meta/issues/1
Updated by Fil Lupin over 4 years ago
Denis 'GNUtoo' Carikli wrote:
how you can disable/forget all your dataThis feature is available through the account interfaces of the various software we use.
I saw another interesting question: how to forget personal information inside commits message.
The only solution I see currently is to avoid/forbid mail address allowing identification.
Updated by Denis 'GNUtoo' Carikli over 4 years ago
Fil Lupin wrote:
Denis 'GNUtoo' Carikli wrote:
how you can disable/forget all your dataThis feature is available through the account interfaces of the various software we use.I saw another interesting question: how to forget personal information inside commits message.
The only solution I see currently is to avoid/forbid mail address allowing identification.
Commit messages are most of the time public so, as I understand it's not an issue for the GDPR.
What might be more interesting to tackle would be to have the ability to cloak users when contributing to upstream projects.
For instance an association for the public interest could gather copyright assignments and this way people could contribute anonymously to various upstream project that require a certificate of origin in the form of Signed-off-by.
Years ago, I've tried to convince several people involved in LGBTQI++ communities to do that through a 501C3-like association but as far as I understand no one did it yet.
Replicant is unfortunately not able to do that as it only legally exists through the agreement we have with the FSF.