diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx
index bfb16fdb153ac..534b008c0da0d 100644
--- a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx
+++ b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx
@@ -30,6 +30,16 @@ OpenTelemetry in .NET is implemented via the System.Diagnostics.Activity namespa
Instead you should either log the exceptions (using `ILogger`) or capture the exceptions directly using `SentrySdk.CaptureException`.
+## Data Collection
+
+The user and span attributes this integration collects don't follow the options you set with `SentryOptions.ConfigureDataCollection`, an experimental API that controls which data the SDK collects automatically. Instead, it:
+
+- Sets the user from ASP.NET Core only when `SendDefaultPii` is `true`.
+- Replaces the values of sensitive URL query parameters on spans, such as `token` or `password`, with `[Filtered]`.
+- Sends all other span attributes as they are.
+
+The `Sentry.OpenTelemetry` integration has been deprecated and we recommend migrating to the OTLP exporter to replace this.
+
## Additional Configuration
If you need more fine grained control over Sentry, take a look at the Configuration page. In case you'd like to filter out transactions before sending them to Sentry (to get rid of health checks, for example), you may find the Filtering page helpful.