Version | Editor | Changes |
1.1 | Nico Lück | Reduced examples of “normal” class |
1.0 | Nico Lück, Margus Mägi | Inserted regular revision of document by Governance Committee |
0.8 | Nico Lück, Rachel Lawson, P.S. Ramkumar, Esther Ogunjimi, Moritz Fromageot, Ayush Shukla |
...
Protection Need | Potential damage to GovStack Initiative or partners (Def. See below) | Example cases (incl. Meetings) Initially, it is up to the groups to decide the classification of information not yet listed here. However, in long-term, all groups in the category “normal” should consider to move into “non-classified/public”. | Tools we use in the GovStack project for this purpose |
Non-classified/Public information | No damage expected | General
Governance Committee
Product Committee
Technical Committee
Working Groups (including Building Blocks but also things like Comms, Community etc)
Country Engagement (for comms purposes or digital public goods)
| Confluence Public Areas Jira Public Areas Slack Github Gitbook Website Social Media |
Normal | Damage impacts are limited and manageable. General Personnel non-contractual details of employees/ participants (contact details, email. ..) | Country Engagement Team
| Confluence space, keeping the whole project up to date with their decisions.Communications and Events
Partnership Management (Private and public sector)
Confluence Restricted Areas Jira Restricted Areas MS Teams direct Chat |
High | The damage effects can be considerable. | Founding partner meeting (closed Strategic Governance meeting)
Partnership Management (Donors)
Country Engagement
Communications and Events
| GIZ MS Teams |
Very High | The damage effects can reach an existentially threatening, catastrophic extent | Personal information of target group (e.g. political activists) Sensitive personal data sets for testing purposes (e.g. real data from partner systems) | GovStack does not process this class of information |
...