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

Foundation for Propagating Consent Requests via the Privacy Request workflow (POC cleanup) #2146

Closed
seanpreston opened this issue Jan 5, 2023 · 3 comments · Fixed by #2125
Assignees

Comments

@seanpreston
Copy link
Contributor

Address all comments in the original POC PR and turn into a feature branch.

@pattisdr
Copy link
Contributor

pattisdr commented Jan 8, 2023

Note from Rachel:

  • Add that PrivacyRequest is only queued if ConsentRequest made a change to preferences.

@pattisdr
Copy link
Contributor

pattisdr commented Jan 8, 2023

Enforce RuleTargets can’t be attached to consent Rules (This isn’t in the POC, but consent Rules don’t try to access RuleTargets at any rate)

@pattisdr
Copy link
Contributor

pattisdr commented Jan 8, 2023

Allow set_consent_preferences to take in an optional Policy for now.

@pattisdr pattisdr changed the title POC clean-up Foundation for Propagating Consent Requests via the Privacy Request workflow Jan 10, 2023
@pattisdr pattisdr changed the title Foundation for Propagating Consent Requests via the Privacy Request workflow Foundation for Propagating Consent Requests via the Privacy Request workflow (POC cleanup) Jan 10, 2023
pattisdr added a commit that referenced this issue Jan 10, 2023
…2146] (#2125)

Adds the foundation to execute consent requests via the privacy request execution framework. When consent preferences are changed, a PrivacyRequest is created (with a Policy > Consent Rule attached) to propagate those consent preferences to third party services, server-side.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants