Privacy API: Difference between revisions
From MoodleDocs
(Created page with "==Overview== The Privacy API has been implemented to help report the use of data within Moodle Plugins as part of General Data Protection Regulations. It shall be expected t...") |
|||
| Line 14: | Line 14: | ||
==Plugins that do not hold personal data== | ==Plugins that do not hold personal data== | ||
If a plugin does not hold any personal data it should implement a provider class that implements the <code>core_privacy\local\metadata\null_provider</code>. | If a plugin does not hold any personal data it should implement a provider class that implements the <code>core_privacy\local\metadata\null_provider</code>. | ||
===get_reason(): string== | ===get_reason(): string=== | ||
This function should return a string that explains why the plugin is asserting that it holds no personal data. | This function should return a string that explains why the plugin is asserting that it holds no personal data. | ||
Revision as of 16:39, 21 March 2018
Overview
The Privacy API has been implemented to help report the use of data within Moodle Plugins as part of General Data Protection Regulations.
It shall be expected that *all* plugins will require to report their use of and storing of personal data.
All plugins will be expected to implement a privacy provider class. This class will provide details on:
- personal data being held by the plugin in:
- database tables
- subsystems
- user preferences
- external locations
Plugins that do not hold personal data
If a plugin does not hold any personal data it should implement a provider class that implements the core_privacy\local\metadata\null_provider.
get_reason(): string
This function should return a string that explains why the plugin is asserting that it holds no personal data.
