From a287d7dbc269710dca0b184042ff27e4cf1ce5db Mon Sep 17 00:00:00 2001 From: Alexander Dinauer Date: Thu, 24 Sep 2026 06:11:00 +0200 Subject: [PATCH] docs(java): Warn about sendDefaultPii removal Mark sendDefaultPii as deprecated in the Java and Android option references. Tell users it will be removed in v9 and direct them to dataCollection before upgrading. Co-Authored-By: Claude --- docs/platforms/android/configuration/options.mdx | 7 +++++-- docs/platforms/java/common/configuration/options.mdx | 7 +++++-- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/platforms/android/configuration/options.mdx b/docs/platforms/android/configuration/options.mdx index 02de766b60f17..0b0d5d9b3ad29 100644 --- a/docs/platforms/android/configuration/options.mdx +++ b/docs/platforms/android/configuration/options.mdx @@ -98,9 +98,12 @@ AndroidManifest.xml key: `io.sentry.additional-context`. -If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. + + `sendDefaultPii` is deprecated and will be removed in the next major version + (v9). Use [`dataCollection`](#dataCollection) instead. + -This is a legacy flag. Use [`dataCollection`](#dataCollection) for granular control over automatically collected data. +If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. For backwards compatibility, `sendDefaultPii` keeps its existing behavior when no Data Collection field is configured. As soon as you configure any `dataCollection` field, Data Collection becomes the source of truth for its categories and `sendDefaultPii` no longer controls them. diff --git a/docs/platforms/java/common/configuration/options.mdx b/docs/platforms/java/common/configuration/options.mdx index 492083bb5df34..28e28b75dcc17 100644 --- a/docs/platforms/java/common/configuration/options.mdx +++ b/docs/platforms/java/common/configuration/options.mdx @@ -102,14 +102,17 @@ Note that enabling this option may increase the payload size of events sent to S + + `sendDefaultPii` is deprecated and will be removed in the next major version + (v9). Use [`dataCollection`](#dataCollection) instead. + + If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent. This option is turned off by default. If you enable this option, be sure to manually remove what you don't want to send using our features for managing [_Sensitive Data_](../../data-management/sensitive-data/). -This is a legacy flag. Use [`dataCollection`](#dataCollection) for granular control over automatically collected data. - For backwards compatibility, `sendDefaultPii` keeps its existing behavior when no Data Collection field is configured. As soon as you configure any `dataCollection` field, Data Collection becomes the source of truth for its categories and `sendDefaultPii` no longer controls them. Unencoded Logback messages aren't a Data Collection category. To include original message templates and parameters when an encoder is configured, use the Logback appender's `includeUnencodedMessage` option. The legacy `sendDefaultPii` behavior remains supported for compatibility. OpenTelemetry-derived HTTP data also isn't controlled by Data Collection yet. Sensitive HTTP header attributes continue to use `sendDefaultPii`; URL and query string attributes are collected when present regardless of that flag.