editors
3,524
edits
Changes
Jump to navigation
Jump to search
Line 22:
Line 22: + + − + − +
no edit summary
* 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}}
* 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.
** {{P|27}} - "alternative string name"
*** This qualifier allows existing items to be re-used. The idea is that the 'named as' value is the display name that is used in the GDPR request letter. So if we already have 'location' but want to include 'geolocation info' because that is the term used for this concept from the company's privacy policy, we can include {{Q|1078}} in the {{P|10}} list but add {{P|27}} - 'geolocation info' as a qualifier. This is important to allow the eventual unification of different data concepts into one model despite companies describing them differently.
** {{Q|1117}} {{Q|29}} or {{Q|1117}} {{Q|29}}
** {{Q|1117}} {{Q|29}} or {{Q|1117}} {{Q|29}}
** 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.
*** 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."
** {{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.
*** 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