From 72e86293ee33513e5fdc58102eebb3a800bf81ee Mon Sep 17 00:00:00 2001 From: ehfeng <279398+ehfeng@users.noreply.github.com> Date: Wed, 19 Aug 2026 18:15:54 +0000 Subject: [PATCH 1/2] Document 30-day retention for telemetry events --- browsers/telemetry/categories.mdx | 2 +- browsers/telemetry/overview.mdx | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/browsers/telemetry/categories.mdx b/browsers/telemetry/categories.mdx index 2ebacd2..e209af2 100644 --- a/browsers/telemetry/categories.mdx +++ b/browsers/telemetry/categories.mdx @@ -53,7 +53,7 @@ Telemetry is off by default and the default set carries operational metadata onl | `screenshot` | A full rendered image of the page - the broadest exposure, capturing anything visible on screen. | | `control`, `connection`, `system`, `captcha`, `monitor` | Session metadata only (control calls, connection and health events). No page content. | -Captured events are persisted and can be replayed by [resuming the stream](/browsers/telemetry/streaming#resuming-after-a-disconnect), so this sensitivity applies to the data at rest, not just the live stream. Treat captured telemetry - and anywhere you forward or store it - with the same care as the underlying content. For how Kernel encrypts, retains, and processes data overall, see [Security](/security) and the [Data Processing Addendum](/dpa). +Captured events are persisted and can be replayed by [resuming the stream](/browsers/telemetry/streaming#resuming-after-a-disconnect), so this sensitivity applies to the data at rest, not just the live stream. Events are retained for 30 days, then expired (see [Retention](/browsers/telemetry/overview#retention)). Treat captured telemetry - and anywhere you forward or store it - with the same care as the underlying content. For how Kernel encrypts, retains, and processes data overall, see [Security](/security) and the [Data Processing Addendum](/dpa). Some exposure is reduced for you automatically: input into sensitive fields such as passwords is suppressed (`interaction_key` isn't emitted for them, and `interaction_click` omits the element text). Beyond that, because selection is opt-in, the most effective control is to capture only the categories you need - enable `network`, `console`, `page`, `interaction`, or `screenshot` deliberately, and prefer the operational categories when you only need session health. diff --git a/browsers/telemetry/overview.mdx b/browsers/telemetry/overview.mdx index 71f50e1..90ff0cf 100644 --- a/browsers/telemetry/overview.mdx +++ b/browsers/telemetry/overview.mdx @@ -108,6 +108,10 @@ kernel browsers update --telemetry=off On update, a category list patches the current selection - categories you don't include keep their current state. To reset the selection instead, send `enabled: true` (it replaces the selection with the categories you provide, or the default set if you provide none); send `enabled: false` to turn telemetry off. +## Retention + +Captured events are retained for 30 days, then expired. You can [stream](/browsers/telemetry/streaming) events live or pull them later for analysis within that window; after 30 days the events are no longer available. If your org has [Zero Data Retention](/info/zero-data-retention) enabled, telemetry isn't persisted at all. + ## What's next - [Categories](/browsers/telemetry/categories) - every category, what it captures, the default set, and cost characteristics. From fd06c3fc12407fdb2f45346560b3920994244584 Mon Sep 17 00:00:00 2001 From: Eric Feng Date: Wed, 19 Aug 2026 15:12:40 -0400 Subject: [PATCH 2/2] Apply suggestion from @Sayan- Co-authored-by: Sayan --- browsers/telemetry/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/browsers/telemetry/overview.mdx b/browsers/telemetry/overview.mdx index 90ff0cf..8fdbc0e 100644 --- a/browsers/telemetry/overview.mdx +++ b/browsers/telemetry/overview.mdx @@ -110,7 +110,7 @@ On update, a category list patches the current selection - categories you don't ## Retention -Captured events are retained for 30 days, then expired. You can [stream](/browsers/telemetry/streaming) events live or pull them later for analysis within that window; after 30 days the events are no longer available. If your org has [Zero Data Retention](/info/zero-data-retention) enabled, telemetry isn't persisted at all. +Captured events are retained for 30 days, then expired. You can [stream](/browsers/telemetry/streaming) events live or pull them later for analysis within that window; after 30 days the events are no longer available. ## What's next