diff --git a/docs/platforms/android/configuration/options.mdx b/docs/platforms/android/configuration/options.mdx
index 72f905bb05daec..e3696cfb9b0ecc 100644
--- a/docs/platforms/android/configuration/options.mdx
+++ b/docs/platforms/android/configuration/options.mdx
@@ -88,6 +88,16 @@ Grouping in Sentry is different for events with stack traces and without. As a r
+
+
+When enabled, information about all threads is attached to events, not just the crashing thread. This provides a more complete picture of the application state at the time of an error, including stack traces from all running threads.
+
+This option is turned off by default.
+
+Note that enabling this option may increase the payload size of events sent to Sentry.
+
+
+
If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
diff --git a/docs/platforms/java/common/configuration/options.mdx b/docs/platforms/java/common/configuration/options.mdx
index ee73ae47d2e26b..32166d53eee777 100644
--- a/docs/platforms/java/common/configuration/options.mdx
+++ b/docs/platforms/java/common/configuration/options.mdx
@@ -88,6 +88,16 @@ Grouping in Sentry is different for events with stack traces and without. As a r
+
+
+When enabled, information about all threads is attached to events, not just the crashing thread. This provides a more complete picture of the application state at the time of an error, including stack traces from all running threads.
+
+This option is turned off by default.
+
+Note that enabling this option may increase the payload size of events sent to Sentry.
+
+
+
If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.