-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add retention period #74
Comments
This is a long outstanding issue and there was a pin put in this until now. The reason why this was outstanding is that the field termination - is meant to be controlled and provided by the user in a consent receipt. For all other justifications - Data Retention is a required field from the Data Controller. Now propose that data retention for the consent receipt is a sub-category of purpose termination and that this is set by the individual or inherits a default as defined by by purpose sub-category field, there is also a requirement for a 'retention rational' sub-field (or meta notice) for the means to be able to figure out or calculate the data retention period for a purpose in the GDPR if it can not be listed as a date and time. In this regard there seems to be a missing topic in CR discourse around consent preferences - especially in this specific context. , |
This may not be required in all jurisdictions so I assume the field should be optional? |
This was removed from Sprint 3 to allow further discussion on "termination" and "retention" fields. |
This is the proposal I sent to the mailing list on 08/14/17 Propose 4 new fields - The first two are at the "top" level of the CR and should be used when the fields cover all uses of information. The second two fields are to be included as a subset of a "purpose" and should be used when there are terms unique to that "purpose". Label: Termination Label: Retention Label: Purpose Termination Label: Purpose Retention |
a defined retention period (in seconds) for the collected data
The text was updated successfully, but these errors were encountered: