[MGNLPRIV-11] Implement consent expiration Created: 23/Apr/18  Updated: 04/May/18  Resolved: 04/May/18

Status: Closed
Project: Privacy
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: GDPR consents
Sprint: Kromeriz 145
Story Points: 5

 Description   
  • Consent status: we currently have given and denied, withdrawn is missing
  • History of consents is managed by using Magnolia versioning.
    • 10 version is maximum
    • Think about using a log as alternative or custom prune policy.
    • Provide a template for an scheduled task that clears old records after a time specified by the client.

Generated at Mon Feb 12 10:30:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.