Details
-
Story
-
Resolution: Outdated
-
Neutral
-
None
-
None
-
None
Description
Implement a solution to keep visitors and their personal data in sync across multiple public instances.
User stories:
As a Data Protection Office, I want a single convenient place to see who my visitors are and where their data resides. (Issue: different visitors are stored on different public instances and I lose oversight.)
As a Visitor, I want the site to remember my consent from one visit to the next. (Issue: A visitor may be stored on different public instances, with different consent info on each.)
As a Visitor, when I change my consent, the site should remember my choice. (Issue: A change of consent on one public instance is not reflected on another public instance.)
As a Visitor, when I request my data to be erased, I want it erased everywhere. (Issue: Data erased from one public instance may still exist on another public instance.)
Acceptance criteria:
- Personal data is recorded and changed consistently in a multi-instance setup.
- The visitor's experience is consistent over time regardless of which public instance they hit in a multi-instance setup.
Checklists
Attachments
Issue Links
- is depended upon by
-
DOCU-1556 Document that GDPR features require special storage setup
-
- Closed
-