From 03283010df75899bf46f88c4e8c72cbd91c3886b Mon Sep 17 00:00:00 2001 From: Dan Adler Date: Mon, 7 Oct 2024 10:58:35 -0700 Subject: [PATCH] Update description of telemetry events in docs I know this is our outdated docs page, but it is still linked from a few places and I paused when I saw this --- docs/admin/telemetry/index.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/admin/telemetry/index.mdx b/docs/admin/telemetry/index.mdx index cd6cb37b0..c5f8dc568 100644 --- a/docs/admin/telemetry/index.mdx +++ b/docs/admin/telemetry/index.mdx @@ -12,10 +12,7 @@ If you have any questions about telemetry collection, please reach out to your S Sourcegraph 5.2.1+ -> WARNING: This section refers to a new system for collecting telemetry introduced in Sourcegraph 5.2.1, and only applies to telemetry that has been migrated to use this new system. -> Certain Sourcegraph components - namely [Cody editor extensions](/cody/) - will continue to use a legacy mechanism for reporting telemetry directly to Sourcegraph.com until the migration is complete. - -Sourcegraph instances 5.2.1 and later collect telemetry events to understand usage patterns and help improve the product. Telemetry events can be generated when certain user actions occur, like opening files or performing searches. This data helps us provide the highest level of support to Sourcegraph's customers. +Sourcegraph instances 5.2.1 and later collect telemetry events from all Sourcegraph end-user client applications to understand usage patterns and help improve the product. Telemetry events can be generated when certain user actions occur, like opening files or performing searches. This data helps us provide the highest level of support to Sourcegraph's customers. Sensitive data/PII exfiltration, intentional or not, is a significant concern to Sourcegraph that we take very seriously. Some of the measures we take to ensure privacy and data security are: