Changes

* {{P|3}} - {{Q|96}}

* {{P|3}} - {{Q|96}}

* {{P|17}} - "mailto:johnny@example.com"

* {{P|17}} - "mailto:johnny@example.com"

** with qualifier {{Q|1062}} - {{Q|96}} - not currently checked but it should be, as there may be a general support email as well as a data protection officer specific email address.

** {{Q|1062}} - {{Q|96}}

* {{P|282}} - "https://company/privacy/contact" - this is necessary where there is no known email address for contacting the data protection officer, only a form. In these cases you probably still need to add {{P|17}} but with a dummy email address (and a comment qualifier making clear it is not a real address). The generated email then has to be manually pasted into the contact form for submission. For example see {{Q|3424}}

** qualifier is not currently checked but it should be, as there may be a general support email as well as a data protection officer specific email address.

* {{P|282}} - "https://company/privacy/contact"  

* This is necessary where there is no known email address for contacting the data protection officer, only a form. In these cases you probably still need to add {{P|17}} but with a dummy email address (and a comment qualifier making clear it is not a real address). The generated email then has to be manually pasted into the contact form for submission. For example see {{Q|3424}}

* {{P|10}} - the points of data known to be collected/stored by this company.

* {{P|10}} - the points of data known to be collected/stored by this company.

** with qualifier {{Q|1117}} {{Q|29}} or {{Q|1117}} {{Q|29}}. This is especially important where other data points have already been added to the {{P|10}} list from different sources. We should update our GDPR generators to only include the {{P|10}} items from the sources we want to use (which may differ per project.

** {{Q|1117}} {{Q|29}} or {{Q|1117}} {{Q|29}}

** with qualifier {{P|287}} - "Extract from privacy policy which shows why this data point is believed to be stored." Add more than once if a long extract is needed. Take care to remove spaces from end of string or you will get a `Malformed text` error.

** This qualifier is especially important where other data points have already been added to the {{P|10}} list from different sources. We should update our GDPR generators to only include the {{P|10}} items from the sources we want to use (which may differ per project.

** {{P|287}} - "Extract from privacy policy which shows why this data point is believed to be stored."  

** Add more than once if a long extract is needed. Take care to remove spaces from end of string or you will get a `Malformed text` error.

* {{P|15}} - URL (optional really)

* {{P|15}} - URL (optional really)

* {{P|103}} - Qxxx

* {{P|103}} - Qxxx

(Q: how do we refer to privacy policy? there are a few different ways to do it)

(Q: how do we refer to privacy policy? there are a few different ways to do it)

* The correct one is {{Q|29}} though we have previously used {{Q|3405}} and some usages of this still need to be migrated. {{Q|3667}} and {{Q|173}} are erroneous and should be deleted.

* A: The correct one is {{Q|29}} though we have previously used {{Q|3405}} and some usages of this still need to be migrated. {{Q|3667}} and {{Q|173}} are erroneous and should be deleted.

===Data rights snaks===

===Data rights snaks===