Skip to content

docs(dev-docs): Bump dataCollection spec to candidate #18017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chargome merged 3 commits into from
Jun 8, 2026
Merged

docs(dev-docs): Bump dataCollection spec to candidate #18017

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
73c69e2
bump
chargome Jun 3, 2026
1708d69
Merge branch 'master' into cg/datacollection-specs-candidate
chargome Jun 8, 2026
e31f8ea
adapt to maturity lifecycle
chargome Jun 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 13 additions & 10 deletions develop-docs/sdk/foundations/client/data-collection/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,15 @@
title: Data Collection
description: Configuration for what data SDKs collect by default, including technical context, PII, and sensitive data.
spec_id: sdk/foundations/client/data-collection
spec_version: 0.2.0
spec_status: draft
spec_version: 0.3.0
spec_status: candidate
spec_depends_on:
- id: sdk/foundations/client
version: ">=1.0.0"
spec_changelog:
- version: 0.3.0
date: 2026-06-05
summary: Promoted to candidate following the initial JavaScript SDK implementation. Version stays `0.x` until the contract is frozen at `stable`.
- version: 0.2.0
date: 2026-06-05
summary: Collect more data by default. `userInfo` now defaults to `true` and `httpBodies` now defaults to all valid body types. Both can be disabled to opt out.
Expand Down Expand Up @@ -38,7 +41,7 @@ Related specs:

## Concepts

<SpecSection id="data-sensitivity-levels" status="draft" since="0.1.0">
<SpecSection id="data-sensitivity-levels" status="candidate" since="0.1.0">

### Data Sensitivity Levels

Expand Down Expand Up @@ -83,7 +86,7 @@ For the canonical list of terms used to detect sensitive values at collection ti

## Behavior

<SpecSection id="configuration-surface" status="draft" since="0.1.0">
<SpecSection id="configuration-surface" status="candidate" since="0.1.0">

### Configuration Requirements

Expand All @@ -93,7 +96,7 @@ SDKs **MUST** support at least the `userInfo` option, key-value collection modes

</SpecSection>

<SpecSection id="collection-defaults" status="draft" since="0.1.0">
<SpecSection id="collection-defaults" status="candidate" since="0.2.0">

### Default Collection Behavior

Expand All @@ -105,7 +108,7 @@ The three sensitivity levels determine whether data is collected by default:

</SpecSection>

<SpecSection id="sensitive-denylist" status="draft" since="0.1.0">
<SpecSection id="sensitive-denylist" status="candidate" since="0.1.0">

### Sensitive Denylist

Expand Down Expand Up @@ -196,7 +199,7 @@ No built-in option scrubs **keys**; users who need to hide header or cookie name

</SpecSection>

<SpecSection id="integration-overrides" status="draft" since="0.1.0">
<SpecSection id="integration-overrides" status="candidate" since="0.1.0">

### Integration-Level Overrides

Expand All @@ -214,7 +217,7 @@ corresponding global `dataCollection` values for the data that integration colle

</SpecSection>

<SpecSection id="user-set-data-scrubbing" status="draft" since="0.1.0">
<SpecSection id="user-set-data-scrubbing" status="candidate" since="0.1.0">

### User-Set Data and Scrubbing

Expand Down Expand Up @@ -242,7 +245,7 @@ This means if a user calls `Sentry.setUser({ email: "jane@example.com" })`, that

## Public API

<SpecSection id="option-types" status="draft" since="0.1.0">
<SpecSection id="option-types" status="candidate" since="0.2.0">

### Option Types

Expand Down Expand Up @@ -478,7 +481,7 @@ public enum BodyType {

</SpecSection>

<SpecSection id="datacollection-options" status="draft" since="0.1.0">
<SpecSection id="datacollection-options" status="candidate" since="0.2.0">

### `dataCollection` Options

Expand Down
Loading