[MGNLPRIV-48] Delegate consent to 3th party services Created: 25/Feb/19 Updated: 30/Jan/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Privacy |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 4h 40m | ||
| Time Spent: | 31m | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Team: |
| Description |
|
The out-of-the-box implementation of the visitor manager stores the data in JCR. It's possible to implement a custom implementation so the data is stored else where (3th party system). But always at one place. Validate if it makes sense to still store consent data in JCR but propagate the data into all configured (consent aware) |
| Comments |
| Comment by Rebekkah Laeuchli [ 25/Feb/19 ] |
|
Hi rkovarik, yes, the Very Cool Thing about the Magnolia GDPR feature is the granularity of the consent handling. But all that data lives inside Magnolia and wouldn't be integrated with our marketing automation tool. So if a visitor withdraws consent to store her/his data via our website using the GDPR feature s/he might still receive our newsletter, since the marketing automation tool wouldn't know that consent has been withdrawn. |
| Comment by Roman Kovařík [ 25/Feb/19 ] |
|
Technical details: The "forget me" feature is implemented, see https://demopublic.magnolia-cms.com/contact/confirmation |
| Comment by Matt Rajkovic [ 30/Jan/23 ] |
|
Very old request - Closing. If needed, can be reopened. |