View plugin privacy registry: Difference between revisions

From MoodleDocs
(tidy up)
(Added 400px)
Line 9: Line 9:
[[File:Plugin privacy compliance registry screen.png|400px]]
[[File:Plugin privacy compliance registry screen.png|400px]]


Some 3.5 additional plugins comply, but others don't. If your site uses a non-compliant third party plugin, please contact the plugin maintainer and ask him/her to provide an updated version.


 
[[File:block todo non privacy compliant.png|400px]]
Some 3.5 additional plugins comply, but others don't. If your site uses a non-compliant third party plugin, please contact the plugin maintainer and ask him/her to provide an updated version.


Most additional plugins that do comply currently state that "The xxxx plugin does not store any personal data."
Most additional plugins that do comply currently state that "The xxxx plugin does not store any personal data."

Revision as of 17:18, 7 July 2018


This page lists all the plugins in Moodle, and identifies whether they comply with the privacy API or not. Any external service is flagged.

Any plugins which are flagged with the warning icon do not yet implement the Moodle privacy API. If this plugin 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:

Plugin privacy compliance registry screen.png

Some 3.5 additional plugins comply, but others don't. If your site uses a non-compliant third party plugin, please contact the plugin maintainer and ask him/her to provide an updated version.

block todo non privacy compliant.png

Most additional plugins that do comply currently state that "The xxxx plugin does not store any personal data."

Plugin privacy compliance registry screen additional plugin OK.png

See also

  • This one example and this other of the code changes needed in order to implement null_provider for Privacy API for an additional Moodle 3.5 plugin
  • Privacy API developer's documentation. The intended audience for this document is Moodle plugin developers, who are aiming to ensure their plugins are updated to comply with GDPR requirements coming into effect in the EU in May, 2018.