From 219402c0ff6eb95af8100cf540d75d6b32376e5a Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Thu, 12 Dec 2024 10:33:37 +0100 Subject: [PATCH] Update docs/platforms/android/data-management/sensitive-data/index.mdx Co-authored-by: Liza Mock --- docs/platforms/android/data-management/sensitive-data/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/android/data-management/sensitive-data/index.mdx b/docs/platforms/android/data-management/sensitive-data/index.mdx index 2a47808281046..341b30cc930d6 100644 --- a/docs/platforms/android/data-management/sensitive-data/index.mdx +++ b/docs/platforms/android/data-management/sensitive-data/index.mdx @@ -54,7 +54,7 @@ Sensitive data may appear in the following areas: - User context → Automated behavior is controlled via . - HTTP context → Query strings may be picked up in some frameworks as part of the HTTP request context. - Transaction Names → In certain situations, transaction names might contain sensitive data. For example, a browser's pageload transaction might have a raw URL like `/users/1234/details` as its name (where `1234` is a user id, which may be considered PII). In most cases, our SDKs can parameterize URLs and routes successfully, that is, turn `/users/1234/details` into `/users/:userid/details`. However, depending on the framework, your routing configuration, race conditions, and a few other factors, the SDKs might not be able to completely parameterize all of your URLs. -- HTTP Spans → Most SDKs will add the HTTP query string and fragment as a data attribute to the span, which may need to be scrubbed. +- HTTP Spans → Most SDKs will include the HTTP query string and fragment as a data attribute, which means the HTTP span may need to be scrubbed. For more details and data filtering instructions, see Filtering Events.