feat(privacy): add explicit consent and data controls for Sentry - #799
Open
Ugooweb wants to merge 1 commit into
Open
feat(privacy): add explicit consent and data controls for Sentry#799Ugooweb wants to merge 1 commit into
Ugooweb wants to merge 1 commit into
Conversation
|
@Ugooweb is attempting to deploy a commit to the nanle-code's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@Ugooweb Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #775
Adds explicit consent and data controls for Sentry initialization, including clear data retention policies.
Changes
src/utils/monitoring.tsto check for explicit consent. If no consent is given, Sentry initialization is safely skipped.revokeSentryConsentfunction that cleanly shuts down the Sentry client when a user revokes consent.src/utils/preferences.jsto manage thediagnosticsConsentstatus by defaulting it to false (no consent).src/utils/__tests__/monitoring.consent.test.tsto cover Sentry initialization behaviors (initialization with consent, initialization without consent, and revocation).