View plugin privacy registry: Difference between revisions

From MoodleDocs
(language cleanup)
(Added see also * [https://docs.moodle.org/dev/Privacy_API Privacy API] developer's documentation)
Line 21: Line 21:
* [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
* [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


* [https://docs.moodle.org/dev/Privacy_API Privacy API] developer's documentation


[[es:admin/tool/dataprivacy/pluginregistry]]
[[es:admin/tool/dataprivacy/pluginregistry]]

Revision as of 14:32, 25 June 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.

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