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

General Data Protection Regulations question #373

Open
SueChaplain opened this issue May 11, 2018 · 2 comments
Open

General Data Protection Regulations question #373

SueChaplain opened this issue May 11, 2018 · 2 comments

Comments

@SueChaplain
Copy link

Hi

We are using slackin to automate invites to our slack workspace and it's been working well - thank you! At the moment we are needing to be mindful of the new GDPR regulations that come into effect in Europe (storage of user personal data). I've had some difficulty viewing the log files for our instance to see what information is recorded, but slackin does seem to know if a user has previously requested an invite. This suggests the storage of the email address. Is there any way to prevent email addresses being stored please? Is there any other user information held in the instance logs please (IP addresses etc)?

Thanks

@SueChaplain
Copy link
Author

I have just discovered that you can find a list of Accepted Invitations in the slack workspace, which suggests that slackin is using an API to query whether someone has already received one. Perhaps no personal data is being stored by slackin?

Please can someone confirm so I can close this issue? Thanks :)

@ad-m
Copy link

ad-m commented Jan 1, 2020

no personal data is being stored in slackin. See https://github.com/rauchg/slackin/blob/master/lib/slack-invite.js#L12-L42 for details how slackin verify whether someone has already received one (it doesn't, it pass error up).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants