Note: You are currently viewing documentation for Moodle 4.0. Up-to-date documentation for the latest stable version of Moodle may be available here: Data privacy.

Data privacy: Difference between revisions

From MoodleDocs
(DPO changed to Privacy Officer)
(→‎Data registry: retention period - thanks to Andrew for info https://moodle.org/mod/forum/discuss.php?d=371715#p1498662)
Line 39: Line 39:
The Privacy Officer can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.  
The Privacy Officer can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.  


A default purpose and retention period may be set for course categories, courses, activity modules and blocks.
A default purpose and retention period may be set for course categories, courses, activity modules and blocks. The retention period is measured from the course end date for the course that an activity is in. For a user it is from the last login time for any user who is no longer enrolled (or has already been deleted).


===Example categories===
===Example categories===

Revision as of 08:06, 7 June 2018

New feature
in Moodle 4.0!
The Data privacy plugin provides the workflow for users to submit subject access requests and for the site administrator or Data Protection Officer (DPO) to process these requests.

The Data Privacy plugin forms part of Moodle’s privacy feature set to assist sites to become GDPR compliant. It is included as standard in Moodle 3.5 onwards and available as a separately downloadable plugin for Moodle 3.3.6 and 3.4.3.


Privacy Officer role

After installing the data privacy plugin, the first thing to do is to create a Privacy Officer role and assign it.

(If there is nobody on the site with the role of Privacy Officer i.e. nobody with the capability to manage data requests, then a site admin can respond to data requests and manage the data registry.)

Data requests

Requesting data

Any user can send a message to the Privacy Officer via the 'Contact Privacy Officer' link on their profile page.

In addition, they can request a copy of all of their personal data or request that their personal data should be deleted as follows:

  1. Go to your profile page (via the user menu).
  2. Click the link 'Data requests' then click the 'New request' button.
  3. Select 'Export all of my personal data' or 'Delete all of my personal data' as appropriate.
  4. Save changes.
Request approved

The Privacy Officer will then receive a data request notification.

If the user has requested a copy of all of their personal data, once the request is approved, they will receive a notification to inform them that their personal data may be downloaded from their Data requests page.

If the user has requested that their personal data should be deleted, once the request is approved, they will receive an email to inform them and they will no longer be able to log in to the site.

Responding to data requests

Viewing a data request

The Privacy Officer can respond to data requests as follows:

  1. Go to 'Data requests' in the Site administration (or follow the link in the data request notification).
  2. In the Actions dropdown, select View, Approve, or Deny as appropriate.

Data registry

Data registry

The Privacy Officer can set purposes (why the organisation is processing data) with retention periods and categories for data stored in Moodle in the data registry.

A default purpose and retention period may be set for course categories, courses, activity modules and blocks. The retention period is measured from the course end date for the course that an activity is in. For a user it is from the last login time for any user who is no longer enrolled (or has already been deleted).

Example categories

  • Administrative: Civil status, identity, identification data, images …
  • Personal life (lifestyle, family situation, etc.)
  • Economic and financial information (income, financial situation, tax situation, etc.)
  • Connection data (IP address, logs, etc.)
  • Educational Data (Assessed Coursework, exam scripts etc)
  • Records of Education Attainment (Results of exams, assessments, qualifications awarded etc)
  • Location data (travel, GPS data, GSM, etc.)

Data registry set-up

To add purposes and categories:

  1. Go to 'Data registry' in the Site administration.
  2. In the Edit menu select Categories.
  3. On the 'Edit categories' page, click the + button to add a new category.
  4. Enter a category name and description then click the Save button.
  5. Go to 'Data registry' again and in the Edit menu select Purposes.
  6. On the 'Edit purposes' page, click the + button to add a new purpose.
  7. Enter a purpose name, description and retention period then click the Save button.

To set default categories and purposes:

  1. In 'Data registry' in the Site administration click the 'Set defaults' button.
  2. Select a default category and purpose for the site, and for users, course categories, courses, activity modules and blocks as required.
  3. Save changes.

Capabilities