Update how we Save and Propagate Consent Preferences #3013
Assignees
Comments
20 tasks
pattisdr
added a commit
that referenced
this issue
Apr 11, 2023
- Start saving privacy preferences with respect to the "privacy notices" - Start storing a snapshot of the privacy preferences that were changed every single time they are saved for reporting purposes - Separately, have a new table that stores the most recently saved privacy preference for a given notice for ease of displaying a user's current preferences - Expose endpoints to retrieve and save the new privacy preferences after verifying your identity (similar to the consent counterparts that are soon to be deprecated) - For both the old workflow and the new workflow introduced here, start creating privacy requests every single time preferences are saved. - Start adding restrictions as to whether we fire requests for a particular consent saas connector or send consent emails: in particular, start comparing privacy notice history data uses and system data uses. the privacy notice history must be enforceable system wide. - Start adding skipped execution logs for a connector when we don't fire a request (instead of completed logs) and start adding skipped execution logs instead of no execution logs when we opt to not send an email for a connector for clearer record-keeping Note that the old workflow where we save consent with respect to data uses defined in the privacy center config.json is still preserved here for the time being.
|
moving to done
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a specific problem?
Supersedes #2835
Create a
PrivacyPreferencetable that creates new record for every consent preference saved. This is analogous to ourConsenttable but will link preferences with respect to a privacy notice history instead of a data use instead and also preserve a history of saved preferences instead of the latest saved state. It will have a FK to the PrivacyRequest created to propagate that preference.Have consent propagation look at the attached
PrivacyPreferencefor consideration of what preferences need to be propagated for which system.Don't break our existing saving consent/ consent preference workflow.
Describe the solution you'd like
Details here
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: