diff --git a/develop-docs/sdk/foundations/client/data-collection/index.mdx b/develop-docs/sdk/foundations/client/data-collection/index.mdx
index 8c6d9f5073fed..16f1e5769342c 100644
--- a/develop-docs/sdk/foundations/client/data-collection/index.mdx
+++ b/develop-docs/sdk/foundations/client/data-collection/index.mdx
@@ -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.
@@ -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
 
@@ -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
 
@@ -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
 
@@ -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
 
@@ -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
 
@@ -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
 
@@ -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
 
@@ -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