Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Pro Consent API to include Data Sharing #1402

Closed
Kelsey-Ethyca opened this issue Oct 12, 2022 · 1 comment
Closed

Update Pro Consent API to include Data Sharing #1402

Kelsey-Ethyca opened this issue Oct 12, 2022 · 1 comment

Comments

@Kelsey-Ethyca
Copy link
Contributor

Kelsey-Ethyca commented Oct 12, 2022

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

  • 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.
@Kelsey-Ethyca
Copy link
Contributor Author

We may not need this as the response looks to be Data Use Title not Type

@Kelsey-Ethyca Kelsey-Ethyca closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants