Do inbound emails (i.e. not member-to-member) need a privacy policy?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 65
- Forks
- 85
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 1
Description
This repo enables a path for Node.js community members to engage with individuals in the project privately.
I think we need to asses the possibility of a privacy policy around inbound emails that AREN'T for member <> member discussions. This would likely need to include something around confidentiality of private info (like name, email address, etc.) and ensuring that the usage of any inbound emails is not used for anything outside of work in the Node.js project.
Here's a list of email aliases that are relatively obviously for inbound emails:
- report@
- security@
- admin@
- accounts@
- moderation@
- user-feedback@
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the inbound aliases listed in the issue: report@, security@, admin@, accounts@, moderation@, and user-feedback@. Determine whether a privacy policy is needed for these channels and what confidentiality and permitted-use requirements it should cover; done means the policy scope and next steps are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100