[MKTAUT-10] [INVESTIGATION] GDPR for connectors Created: 30/Jul/19  Updated: 20/Aug/19  Resolved: 20/Aug/19

Status: Closed
Project: Marketing Automation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Laura Delnevo Assignee: Laura Delnevo
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Forms export
Sprint: Add-Ons 18
Story Points: 0.5

 Description   

For this and other connectors (impact should be minimal as we don't store data ... unlike AB Testing, where we store data) // Cehck with ahietala



 Comments   
Comment by Antti Hietala [ 13/Aug/19 ]

When you capture personal data from visitors in a form and store the data in a connected service, you are a data processor under GDPR. As a processor, Magnolia needs to make it easy for clients to uphold and fulfill the rights of data subjects.

Data privacy requirements are the same as for any external forms. Use our Data privacy API to ask visitor consent, delete data on request, update consent etc.

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