View plugin privacy registry: Difference between revisions
From MoodleDocs
(This (your_server_URL/admin/tool/dataprivacy/pluginregistry.php ) page) |
(. See the clamAV antivirus plugin example below:) |
||
| Line 3: | Line 3: | ||
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. | 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: | 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]] | [[File:Plugin privacy compliance registry screen.png|400px]] | ||
Revision as of 13:39, 30 May 2018
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.
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:
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."
