feat(user): [Data Collection 14] Apply user information policy#5812
Draft
adinauer wants to merge 1 commit into
Draft
feat(user): [Data Collection 14] Apply user information policy#5812adinauer wants to merge 1 commit into
adinauer wants to merge 1 commit into
Conversation
Gate automatic user and device identity enrichment across core, Android, and Spring integrations with the Data Collection policy. Preserve legacy sendDefaultPii and Android installation identity behavior when Data Collection is absent. Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Jul 22, 2026
Contributor
🚨 Detected changes in high risk code 🚨High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:
|
This was referenced Jul 22, 2026
Contributor
|
This was referenced Jul 22, 2026
📲 Install BuildsAndroid
|
Contributor
Performance metrics 🚀
|
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
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.
PR Stack (Data Collection)
📜 Description
Apply the user information Data Collection policy to automatic identity enrichment across core, Android, and Spring integrations.
The policy controls automatic
{{auto}}IP addresses, Spring request and Spring Security usernames, and SDK-generated Android installation identifiers written touser.idanddevice.id. ExplicituserInfo=falsesuppresses these automatic values, while application-supplied user data and customSentryUserProvidervalues remain untouched.When Data Collection is absent, existing behavior is preserved:
sendDefaultPiicontinues to control automatic IP and Spring user enrichment, while Android installation identifiers remain enabled. The unused privateTraceContextuser-ID helper is removed without changing generated trace context data.💡 Motivation and Context
Automatic user identity fields can contain personal or stable identifying data. This wires the existing
dataCollection.userInfooption to all supported Java and Android collectors while preserving the legacy bridge for applications that have not configured Data Collection.Refs #5666
💚 How did you test it?
./gradlew spotlessApply apiDump./gradlew :sentry:apiCheckgit diff --check📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Complete the remaining Data Collection configuration, documentation, and migration work.
#skip-changelog