From 073239adfab4ceb32718f2b36c65cc91d5a9a5bd Mon Sep 17 00:00:00 2001 From: JoshuaMoelans <60878493+JoshuaMoelans@users.noreply.github.com> Date: Wed, 23 Apr 2025 15:01:54 +0200 Subject: [PATCH 1/5] Create data-collected.mdx --- .../native/common/data-management/data-collected.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 docs/platforms/native/common/data-management/data-collected.mdx diff --git a/docs/platforms/native/common/data-management/data-collected.mdx b/docs/platforms/native/common/data-management/data-collected.mdx new file mode 100644 index 0000000000000..bb08cc16777ec --- /dev/null +++ b/docs/platforms/native/common/data-management/data-collected.mdx @@ -0,0 +1,9 @@ +--- +title: Data Collected +description: "See what data is collected by the Sentry SDK." +sidebar_order: 1 +--- + +Sentry takes data privacy very seriously and has default settings in place that prioritize data safety, especially when it comes to personally identifiable information (PII) data. When you add the Sentry SDK to your application, you allow it to collect data and send it to Sentry during the runtime of your application. + +The category types and amount of data collected vary, depending on the integrations you've enabled in the Sentry SDK. Here's a list of data categories the Sentry Native SDK collects: From 3f74eba47c58d70c8cc8a8c974e61fb3c7cb5420 Mon Sep 17 00:00:00 2001 From: JoshuaMoelans <60878493+JoshuaMoelans@users.noreply.github.com> Date: Wed, 23 Apr 2025 15:56:57 +0200 Subject: [PATCH 2/5] Update data-collected.mdx --- .../native/common/data-management/data-collected.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/platforms/native/common/data-management/data-collected.mdx b/docs/platforms/native/common/data-management/data-collected.mdx index bb08cc16777ec..8ecb30446e2c0 100644 --- a/docs/platforms/native/common/data-management/data-collected.mdx +++ b/docs/platforms/native/common/data-management/data-collected.mdx @@ -7,3 +7,11 @@ sidebar_order: 1 Sentry takes data privacy very seriously and has default settings in place that prioritize data safety, especially when it comes to personally identifiable information (PII) data. When you add the Sentry SDK to your application, you allow it to collect data and send it to Sentry during the runtime of your application. The category types and amount of data collected vary, depending on the integrations you've enabled in the Sentry SDK. Here's a list of data categories the Sentry Native SDK collects: + +## Device Information + +The Sentry SDK collects information about the device, such as the operating system/Linux distribution name, version and build. This information is sent to Sentry by default. + +## Information About Logged-in User + +By default, the Sentry SDK doesn't send any information about the logged-in user, such as email address, user ID, or username. Even if enabled, the type of logged-in user information you send depends on the data that was set by calling `sentry_set_user()`. From 0fd26ecd7e167621d840722463a90200f5ae1cad Mon Sep 17 00:00:00 2001 From: JoshuaMoelans <60878493+JoshuaMoelans@users.noreply.github.com> Date: Wed, 23 Apr 2025 16:46:50 +0200 Subject: [PATCH 3/5] Update data-collected.mdx --- .../native/common/data-management/data-collected.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/platforms/native/common/data-management/data-collected.mdx b/docs/platforms/native/common/data-management/data-collected.mdx index 8ecb30446e2c0..05849b88dd142 100644 --- a/docs/platforms/native/common/data-management/data-collected.mdx +++ b/docs/platforms/native/common/data-management/data-collected.mdx @@ -12,6 +12,7 @@ The category types and amount of data collected vary, depending on the integrati The Sentry SDK collects information about the device, such as the operating system/Linux distribution name, version and build. This information is sent to Sentry by default. -## Information About Logged-in User +## Thread Stack Information +At the time of a crash, the stack of each thread is collected and sent to Sentry. This information is sent to Sentry by default, but dropped after parsing the event in the backend. -By default, the Sentry SDK doesn't send any information about the logged-in user, such as email address, user ID, or username. Even if enabled, the type of logged-in user information you send depends on the data that was set by calling `sentry_set_user()`. +These files are not stored by default, but you can [enable Minidump Storage](https://docs.sentry.io/platforms/native/guides/minidumps/enriching-events/attachments/#store-minidumps-as-attachments) in the Sentry organization or project settings. From 923dc25a05f922b16e75f92df4ba1929e03ac03d Mon Sep 17 00:00:00 2001 From: JoshuaMoelans <60878493+JoshuaMoelans@users.noreply.github.com> Date: Wed, 23 Apr 2025 17:07:05 +0200 Subject: [PATCH 4/5] Update data-collected.mdx --- docs/platforms/native/common/data-management/data-collected.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/native/common/data-management/data-collected.mdx b/docs/platforms/native/common/data-management/data-collected.mdx index 05849b88dd142..abda6357368c6 100644 --- a/docs/platforms/native/common/data-management/data-collected.mdx +++ b/docs/platforms/native/common/data-management/data-collected.mdx @@ -10,7 +10,7 @@ The category types and amount of data collected vary, depending on the integrati ## Device Information -The Sentry SDK collects information about the device, such as the operating system/Linux distribution name, version and build. This information is sent to Sentry by default. +The Sentry SDK collects information about the device, such as the name, version and build of your operating system or Linux distribution. This information is sent to Sentry by default. ## Thread Stack Information At the time of a crash, the stack of each thread is collected and sent to Sentry. This information is sent to Sentry by default, but dropped after parsing the event in the backend. From 351d766c59418ac23427a8a79243d5bc0f9ad047 Mon Sep 17 00:00:00 2001 From: JoshuaMoelans <60878493+JoshuaMoelans@users.noreply.github.com> Date: Thu, 24 Apr 2025 10:36:42 +0200 Subject: [PATCH 5/5] Apply suggestions from code review Co-authored-by: Mischan Toosarani-Hausberger --- .../native/common/data-management/data-collected.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/platforms/native/common/data-management/data-collected.mdx b/docs/platforms/native/common/data-management/data-collected.mdx index abda6357368c6..c87e8410db1ce 100644 --- a/docs/platforms/native/common/data-management/data-collected.mdx +++ b/docs/platforms/native/common/data-management/data-collected.mdx @@ -13,6 +13,8 @@ The category types and amount of data collected vary, depending on the integrati The Sentry SDK collects information about the device, such as the name, version and build of your operating system or Linux distribution. This information is sent to Sentry by default. ## Thread Stack Information -At the time of a crash, the stack of each thread is collected and sent to Sentry. This information is sent to Sentry by default, but dropped after parsing the event in the backend. +At the time of a crash, the stack of each thread is collected and sent to Sentry as part of the Minidump snapshot for backends `crashpad` and `breakpad`. This information is sent to Sentry by default, but dropped after processing the event in the backend. These files are not stored by default, but you can [enable Minidump Storage](https://docs.sentry.io/platforms/native/guides/minidumps/enriching-events/attachments/#store-minidumps-as-attachments) in the Sentry organization or project settings. + +The `inproc` backend stack walks solely in the client and thus only sends the resulting stack traces.