You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a data processor, I want to query for the consent status of a data subject, so that I know what I am allowed to use.
DETAILS
In Pro's Control Panel today an admin can create Data Use Cases. These use cases show under Consent Management in the Privacy Center for a user to opt in or out. We will add Data Sharing as a new type when creating data use cases to comply with CPRA/VCPA in ##1397 and #https://github.com/ethyca/fidesctl-plus/issues/321.
We need to add to the Data Sharing to the existing Consent API.
Given that a user has opted in to data sharing, when I query for their ID by email, then I get a record of the timestamp their consent was recorded and the ID of the consent type granted.
Given that a user has NOT opted in to data sharing, when I query for their ID by email then I get an empty response or a “not found/404” and therefore now that I cannot process sensitive information.
Given that a user has changed their opt-in status from consenting to data sharing to NOT consenting to data sharing, when I query for a their ID by email, then I get a record of the consent with a property which indicates they are opted out.
The text was updated successfully, but these errors were encountered:
USER STORY
As a data processor, I want to query for the consent status of a data subject, so that I know what I am allowed to use.
DETAILS
In Pro's Control Panel today an admin can create Data Use Cases. These use cases show under Consent Management in the Privacy Center for a user to opt in or out. We will add Data Sharing as a new type when creating data use cases to comply with CPRA/VCPA in ##1397 and #https://github.com/ethyca/fidesctl-plus/issues/321.
We need to add to the Data Sharing to the existing Consent API.
Pro Docs - Consent API
EPIC DOC
AC
The text was updated successfully, but these errors were encountered: