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

Single user export for GDPR #4351

Open
piperswe opened this issue Jul 2, 2018 · 8 comments
Open

Single user export for GDPR #4351

piperswe opened this issue Jul 2, 2018 · 8 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@piperswe
Copy link

piperswe commented Jul 2, 2018

For GDPR compliance on a Gitea instance I host, the ability to export the data pertaining to a single user would be extremely useful so I don't have to resort to writing dodgy SQL queries.

@T100D
Copy link

T100D commented Jul 2, 2018

To be compliant, GDPR is only in count for personal or profile info imho. So only the data in the Public Profile page is at stake here.

@tarelda
Copy link
Contributor

tarelda commented Jul 3, 2018

T100D, you are actually wrong here. According to answer to question made by T-Mobile, all customer data, that was willingly uploaded into the service, can be requested for a review or deletion, but doesn't include data automatically generated due to user activity (for example activity logs etc.).

@T100D
Copy link

T100D commented Jul 3, 2018

@tarelda GDPR only concerns personal and/or identity related data. It is not related to business like data that one personally owns, or has created and stored on-line, despite the splendid service by T-Mobile.

There is an exclusion in GDPR when it concerns business related data for example. Messages in issue's, and programs in Gitea could fall under the business exclusion, Gitea just has to mention that when people create online accounts on open internet Gitea services.

The Github privacy statement is highly usable imho: https://help.github.com/articles/github-privacy-statement/#githubs-global-privacy-practices

@tarelda
Copy link
Contributor

tarelda commented Jul 3, 2018

@T100D, only exclusion I am aware of is that you don't have to delete or share information vital for your business operation. Otherwise you have to and even in this situation you have to provide user with reasoning for that (ATM I don't have access and time to GPDR source text to point paras and points, but I actually read it).
Github privacy statement claims that data is collected under US law instead of European and is compliant with GPDR as external entity, which falls under different category, than being European organization.

@jonasfranz jonasfranz added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Jul 4, 2018
@stale
Copy link

stale bot commented Jan 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 20, 2019
@stale
Copy link

stale bot commented Feb 18, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Feb 18, 2019
@lesderid
Copy link

Was this added? Anyone publicly deploying Gitea for users in the EU needs this.

@zeripath zeripath reopened this Jun 14, 2019
@stale stale bot removed the issue/stale label Jun 14, 2019
@zeripath zeripath added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jun 14, 2019
@i5heu
Copy link

i5heu commented Jun 15, 2019

#2012 is also important for EU users - a privacy and imprint section is legally required!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

7 participants