PII data

PII data is collected and stored and distributed.

Mechanisms to ensure data privacy & security

An adopter of Sunbird may choose to share PII data with third parties if they so require, as per the workflows they choose to configure. Implementers/Adopters of Sunbird, have the autonomy to decide what fields to capture/maintain, which other systems to integrate with, and whether they share this data with other authorised parties. (An example of this would be a Sunbird adopter choosing to share the profile data of registered users - after obtaining explicit user consent to do so - with a Course mentor, to permit further analysis of the batch by the mentor),While the Sunbird technical architecture has taken privacy and security controls into consideration as default implementation, it is up to the Implementers/Adopters to establish a suitable privacy policy at their end to cover the various implementation-specific scenarios regarding the. management & sharing of PII/non PII data.,As an open source-code solution, Sunbird Lern should be viewed differently from hosted service/product solutions. While the source code is open, free and available to all interested implementers/adopters (on GitHub), individual implementations may have their own view of how they address data management (PII/non-PII) and hosting of the solution. Sunbird Lern software has implemented many best practices in its building blocks to keep user data safe and secure. Users are empowered to safeguard and share their data with appropriate consent management mechanisms. Default software has implemented data collection in an open and transparent manner. Sunbird Lern software implements principles of minimalism, consent, transparency of data collection, and other best practices. Sunbird has capabilities for curating and reviewing content before it is published for consumption. Please see earlier and following responses for details about privacy, safety of minors, and data security. As an open source-code solution, Sunbird Lern will have to be viewed differently from hosted service/product solutions. While the source code is open, free and available to all interested implementers/adopters (on GitHub), individual implementations may have their own view of how they may have addressed data management (PII/non-PII), hosting of the solution and so forth. Management of PII/non-PII data in Sunbird is purely a "highly extensible/configurable/non-opinionated open-software solution", and it's source code lies in GitHub (Sunbird is not a 'hosted service or product'). Implementers/adopters of Sunbird, have the autonomy to decide "what" fields to be capture/maintain, "what" other systems will they integrate with, "will" they share this data with other authorized parties (e.g. one Government sharing this dataset with other Government, or one Department sharing this dataset with other Department). While the Sunbird technical architecture has taken privacy and security controls into consideration as default implementation, it is up to the Implementers/Adopters to establish a privacy policy at their end to cover the various implementation scenarios (e.g. management & sharing of PII/non PII data).