Release 25.12.01

src/_includes/content/destination-maintenance.md

@@ -11,5 +11,5 @@
 {% endif %}
 
 <div class="premonition warning"><div class="fa fa-check-square"></div><div class="content"><p class="header">{{page.title | replace: 'Destination', ''}} (Classic) is in Maintenance mode</p>
-<p markdown=1>The {{name}} (Classic) Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}</p>
+<p markdown=1>The {{name}} Destination has entered maintenance mode. Future updates are limited to security updates and bug fixes. {{blurb}}</p>
 </div></div>

src/connections/destinations/catalog/hubspot/index.md

@@ -223,7 +223,7 @@ When using any of Segment's server-side sources, a connector infers `traits.life
 
 ### Loading Forms SDK
 
-Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options){:target="_blank"} alongside their tracking library. Enable the **Load Forms SDK** setting when you your HubSpot integration.
+Segment gives you the option to load the [HubSpot Forms SDK](https://developers.hubspot.com/docs/methods/forms/advanced_form_options){:target="_blank"} alongside HubSpot's tracking library. Enable the **Load Forms SDK** setting for your HubSpot integration.
 
 > info ""
 > The Forms SDK expects to load synchronously but analytics.js loads asynchronously. To interact with the API, run code inside an [analytics.ready](/docs/connections/sources/catalog/libraries/website/javascript/#ready) callback. For example:

src/connections/sources/catalog/libraries/server/pixel-tracking-api/index.md

@@ -55,6 +55,12 @@ Each endpoint *always* responds with a `200 <empty-gif>`, even if an error occur
 eyJ3cml0ZUtleSI6ICJZT1VSX1dSSVRFX0tFWSIsICJ1c2VySWQiOiAiMDI1cGlrYWNodTAyNSIsICJldmVudCI6ICJFbWFpbCBPcGVuZWQiLCAicHJvcGVydGllcyI6IHsgICAic3ViamVjdCI6ICJUaGUgRWxlY3RyaWMgRGFpbHkiLCAgICJlbWFpbCI6ICJwZWVrQXRNZUBlbWFpbC5wb2tlIiB9fQ
 ```
 
+##### If you choose not to encode your payload, send it like this instead:
+
+```
+https://api.segment.io/v1/pixel/track?userId=user_123&event=Email Opened&properties.subject=The Electric Daily&[email protected]&writeKey=<YOUR_WRITE_KEY>
+```
+
 ##### Add an image tag to your email newsletter with `src` pointing to a Pixel API route:
 
 ```html

src/engage/journeys/event-triggered-journeys-steps.md

@@ -8,7 +8,7 @@ plan: engage-foundations
 Steps are the building blocks of a journey. This page explains the **Hold Until** and **Send to Destination** steps, which enable precise control over journey progression and data delivery. 
 
 > info "Public Beta"
-> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible.
+> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. 
 
 ## Hold Until: smart pauses in journeys
 

src/engage/journeys/event-triggered-journeys.md

@@ -10,7 +10,7 @@ Unlike traditional audience-based journeys that rely on pre-defined user segment
 On this page, you'll learn how to create an event-triggered journey, configure entry conditions, and work with published event-triggered journeys.
 
 > info "Public Beta"
-> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible.
+> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
 ## Overview
 

src/engage/journeys/journey-context.md

@@ -8,7 +8,7 @@ plan: engage-foundations
 This page explains Journey context, which can help you dynamically adapt each journey to individual user interactions, creating highly relevant, real-time workflows.
 
 > info "Public Beta"
-> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. Event-Triggered Journeys is not currently HIPAA eligible.
+> Event-Triggered Journeys is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
 
 ## Overview
 

src/privacy/data-retention-policy.md

@@ -35,6 +35,9 @@ The default data retention period for each of the data types is as follows:
 | **Team**     | 365 days                     | Not applicable               | 90 days                           | 365 days | Not applicable |
 | **Free**     | 180 days                     | Not applicable               | 60 days                           | 180 days | Not applicable |
 
+> info ""
+> Segment calculates your data retention period starting from the date Segment ingests an event, not from the date an event originally occurred.
+
 Through the self-serve Data Retention configuration in your workspace, you can configure a custom data retention period through the [Workspace Default Archive Retention Period](#workspace-default-archive-retention-period) setting.
 
 Segment recommends keeping your data for at least 30 days to enable [replays](/docs/guides/what-is-replay/) of your data.

src/unify/data-graph/linked-events.md

@@ -30,9 +30,6 @@ To use Linked Events, you'll need the following:
 2. Access to Unify in your workspace. 
 3. Access to the actions-based destination you'll be using with Linked Events so that you can validate your data. 
 
-> info ""
-> Segment stores and processes all data in the United States.
-
 > info ""
 > Profiles Sync isn't required for Linked Events.