|
|
(9 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
| This (your_server_URL/admin/tool/dataprivacy/pluginregistry.php ) Moodle 3.5 page lists all the installed Moodle (core and additional) plugins and whether they implement the Moodle privacy API.
| | #redirect [[Data privacy]] |
| | |
| If a plugin does not implement the Moodle privacy API and stores any personal data, it will not be able to be exported or deleted through Moodle's privacy system.
| |
| | |
| All core Moodle 3.5 plugins do implement the Moodle privacy API. See the clamAV antivirus plugin example below:
| |
| | |
| [[File:Plugin privacy compliance registry screen.png|400px]] | |
| | |
| | |
| | |
| Some 3.5 additional plugins do, but others don't.
| |
| | |
| Most additional plugins that do currently state that "The xxxx plugin does not store any personal data."
| |
| | |
| [[File:Plugin privacy compliance registry screen additional plugin OK.png|400px]]
| |
| | |
| ==See also==
| |
| | |
| * [https://github.com/ndunand/moodle-qtype_regexp/commit/6d7d9b05c198811cb80a9efd048a7faff6ba77f4 This one example] and [https://github.com/dthies/moodle-atto_cloze/commit/70d88c939f3601e3ffc37885e725a5c7592688b8 this other] of the code changes needed in order to implement null_provider for Privacy API for an additional Moodle 3.5 plugin
| |