Moodle plugins directory: Data privacy | Moodle.org
Data privacy
Important: The Data Privacy tool will be part of the standard Moodle distributions from versions 3.4.5+ and 3.3.8+. If you are upgrading to these versions and you have this tool installed as an additional plugin, please remember to remove the folder of the tool's code before upgrading the Moodle codebase.
The Data Privacy plugin forms part of Moodle’s privacy feature set and will assist sites to become GDPR compliant.
This plugin provides the workflow for users to submit subject access and erasure requests and for site administrators and privacy officers to process these requests. It also includes the data registry to define a purpose and retention period for data stored in a Moodle site.
This plugin has been integrated into the Moodle 3.5 release of 17 May 2018 but remains available for Moodle 3.3.6 to 3.3.7 and 3.4.3 to 3.4.4 as a separately downloadable plugin.
thanks for the response. My current version is Moodle 3.4.1+ . My fault...should read better
Best regards
The requirements for the plugin are largely centred around the rights of users; their right of access to their personal data, and their right to be forgotten. Whilst there is a requirement that organisations operating under GDPR must be able to produce registers, describing all personal data they capture, we didn't identify any such requirement allowing Data Protection Officers or Privacy Officers to view the actual personal data for a given user. This would most probably be considered a nice to have, but unfortunately given time constraints, we haven't planned to include this yet.
Following Jun's instructions sets up the Data Protection officer to receive a message whenever a user clicks "Contact Data Protection officer" in their profile and replaces the admin.
However, this only works for the general enquiries at the moment. When a user submits a Delete or Export request, the Data Protection Officers don't receive any message. Hope this is added soon.
Yes, when exporting user data the output data will be in JSON format and this is handled by the privacy\classes\local\request\moodle_content_writer.php class.
The name of the exported data JSON file depends on the particular plugin's logic implemented in the export_user_data() function, but by default most plugin's export data will have the name 'data.json'.
The data export of associated physical files is also supported in the same class.
For this upcoming release, the exported user data and physical files will be organized in a logical folder structure that reflects the Moodle context hierarchy so it is intuitive for users to navigate and access their data.
But we are also looking to add way to present the exported data with a easy-to-use user interface as well, for example, in a web browser.
Users should be able to request data via a 'Data requests' link on their profile page. Please see the documentation https://docs.moodle.org/en/Data_privacy_plugin for more details.
You can also try things out on the Moodle GDPR sandbox demo site https://gdprdemo.moodle.net/.
Can you insert it? TIA
I'm a PT translator
Thanks for commenting, that language string does not exist any more so no need to translate it.
Fatal error: Interface 'core_privacy\metadata\null_provider' not found in /public_html/moodle/blocks/filtered_course_list/classes/privacy/provider.php on line 36
Any help? TIA
What moodle version are you using? Note that this plugin works with Moodle 3.4.2 and Moodle 3.3.5 (onwards).
I uninstalled the block_filtered_course_list and i got this:
Exception - Call to undefined method core_component::get_component_list()
Debug info:
Error code: generalexceptionmessage
Stack trace:
line 125 of /admin/tool/dataprivacy/classes/metadata_registry.php: Error thrown
line 46 of /admin/tool/dataprivacy/classes/metadata_registry.php: call to tool_dataprivacy\metadata_registry->get_full_component_list()
line 41 of /admin/tool/dataprivacy/pluginregistry.php: call to tool_dataprivacy\metadata_registry->get_registry_metadata()