From 88b394db0311da63e60d1119b05a3e12157c974c Mon Sep 17 00:00:00 2001 From: Denys Bohdan Date: Tue, 4 Oct 2022 15:44:34 +0300 Subject: [PATCH] Added personal data disclosure and code of conduct (#35) --- CONTRIBUTING.md | 2 ++ PERSONAL_DATA_DISCLOSURE.md | 58 +++++++++++++++++++++++++++++++++++++ 2 files changed, 60 insertions(+) create mode 100644 PERSONAL_DATA_DISCLOSURE.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c6e1e05..6df6a6e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,3 +2,5 @@ Guidelines for Contributing Code: [dev.folio.org/guidelines/contributing](https://dev.folio.org/guidelines/contributing) + +[Code of Conduct](https://wiki.folio.org/display/COMMUNITY/FOLIO+Code+of+Conduct) diff --git a/PERSONAL_DATA_DISCLOSURE.md b/PERSONAL_DATA_DISCLOSURE.md new file mode 100644 index 0000000..fe5279a --- /dev/null +++ b/PERSONAL_DATA_DISCLOSURE.md @@ -0,0 +1,58 @@ + + +## Overview +The purpose of this form is to disclose the types of personal data stored by each module. This information enables those hosting FOLIO to better manage and comply with various privacy laws and restrictions, e.g. GDPR. + +It's important to note that personal data is not limited to that which can be used to identify a person on it's own (e.g. Social security number), but also data used in conjunction with other data to identify a person (e.g. date of birth + city + gender). + +For the purposes of this form, "store" includes the following: +* Persisting to storage - Either internal (e.g. Postgres) or external (e.g. S3, etc.) to FOLIO +* Caching - In-memory, etc. +* Logging +* Sending to an external piece of infrastructure such as a queue (e.g. Kafka), search engine (e.g. Elasticsearch), distributed table, etc. + +## Personal Data Stored by This Module +- [x] This module does not store any personal data. +- [ ] This module provides [custom fields](https://github.com/folio-org/folio-custom-fields). +- [ ] This module stores fields with free-form text (tags, notes, descriptions, etc.) +- [ ] This module caches personal data +--- +- [ ] First name +- [ ] Last name +- [ ] Middle name +- [ ] Pseudonym / Alias / Nickname / Username / User ID +- [ ] Gender +- [ ] Date of birth +- [ ] Place of birth +- [ ] Racial or ethnic origin +- [ ] Address +- [ ] Location information +- [ ] Phone numbers +- [ ] Passport number / National identification numbers +- [ ] Driver’s license number +- [ ] Social security number +- [ ] Email address +- [ ] Web cookies +- [ ] IP address +- [ ] Geolocation data +- [ ] Financial information +- [ ] Logic or algorithms used to build a user/profile + + + +**NOTE** This is not intended to be a comprehensive list, but instead provide a starting point for module developers/maintainers to use. + +## Privacy Laws, Regulations, and Policies +The following laws and policies were considered when creating the list of personal data fields above. +* [General Data Protection Regulation (GDPR)](https://gdpr.eu/) +* [California Consumer Privacy Act (CCPA)](https://oag.ca.gov/privacy/ccpa) +* [U.S. Department of Labor: Guidance on the Protection of Personal Identifiable Information](https://www.dol.gov/general/ppii) +* Cybersecurity Law of the People's Republic of China + * https://www.newamerica.org/cybersecurity-initiative/digichina/blog/translation-cybersecurity-law-peoples-republic-china/ + * http://en.east-concord.com/zygd/Article/20203/ArticleContent_1690.html?utm_source=Mondaq&utm_medium=syndication&utm_campaign=LinkedIn-integration +* [Personal Data Protection Bill, 2019 (India)](https://www.prsindia.org/billtrack/personal-data-protection-bill-2019) +* [Data protection act 2018 (UK)](https://www.legislation.gov.uk/ukpga/2018/12/section/3/enacted) + +--- + +v1.0 \ No newline at end of file