By default, Breinify’s API Library (see GitHub Repository) uses the following first-party browser-storage entries:
- x-breinify-uuid
- x-breinify-bid
- x-breinify-rfr
The x-breinify-uuid and x-breinify-bid entries contain randomly generated universally unique identifiers (UUIDs). They enable anonymous session and returning-visitor identification and support the collection of journey-based metrics.
The x-breinify-rfr entry stores session-entry attribution information. This allows the original entry URL and referrer to remain available throughout the browser session and records the navigation distance from the session-entry page.
Breinify uses sessionStorage and localStorage when these browser-storage mechanisms are available. If they are unavailable, equivalent first-party cookies may be used as a fallback.
Other than the entries listed below, Breinify does not, by default, store additional information in the browser’s localStorage, sessionStorage, or cookies. Additional entries may be created when optional features are enabled, as described in the Optional Cookies & Storage section.
Breinify does not use third-party cookies for advertising or retargeting purposes. All browser-storage entries remain first-party and are limited to platform functionality.
The following table describes each default entry, its purpose, where it is stored, and its retention period.
| Name | Purpose | Storage | Life Span |
|---|---|---|---|
| x-breinify-uuid | Anonymous UUID used to identify a visitor’s browser session | sessionStorage first-party session-cookie fallback |
Resets for each browser session |
| x-breinify-bid | Anonymous UUID used to identify returning visitors | localStorage first-party persistent-cookie fallback |
10 years; expired data is removed when accessed |
| x-breinify-rfr | Stores session-entry attribution information, including the entry URL, entry referrer, most recently processed URL, and navigation distance | sessionStorage first-party session-cookie fallback |
Resets for each browser session |
Optional Cookies & Storage
In addition to the default entries, Breinify may create optional cookies or browser-storage entries depending on specific platform configurations and feature usage. These optional entries occur only when a customer activates capabilities such as split-test-based experiments, scheduled activities, get-parameter activities, feature persistence, or other analytics and personalization modules.
Optional cookies and local or session storage entries follow the same principles as the default entries. All entries are first-party only; Breinify does not use third-party retargeting or advertising cookies. The following table summarizes their names, purposes, storage mechanisms, and retention periods.
A customer implementation may also use additional first-party browser-storage entries to support customer-specific functionality or configurations. Because the names, purposes, and retention periods of those entries depend on the individual implementation, they are not part of the standard Breinify entries listed below and are documented separately within the applicable customer-specific documentation.
| Name | Purpose | Storage | Life Span |
|---|---|---|---|
| breinify-split-test-data | Stores split-test or A/B-experiment group assignments for the browser | localStorage | 30 days; cleanup is lazy and occurs on access |
| breinify-gp-data | Marks get-parameter-based activities as already sent to prevent duplicate triggers | localStorage | 1 minute; cleanup is lazy and occurs on access |
| breinify-sa-data-* | Temporarily stores scheduled activities until they are processed | localStorage | Normally milliseconds or seconds; standard scheduled activities expire after no more than 60 seconds and are removed after processing or when detected as expired |
| x-breinify-delayed | Provides first-party fallback storage for scheduled activities when localStorage is unavailable | First-party session cookie fallback only |
Normally milliseconds or seconds; standard scheduled activities expire after no more than 60 seconds and are removed after processing or when detected as expired |
| breinify::featureStorage::feature::* | Stores temporary feature values, associated metadata, and expiration information used by enabled personalization features | localStorage | Feature-specific; 24 hours by default. Expired entries are removed during periodic cleanup |
| breinify::featureStorage::cleanupAt | Records the most recent feature-storage cleanup to avoid repeatedly scanning browser storage for expired feature entries | localStorage | Retained until replaced or localStorage is cleared; normally updated when periodic cleanup runs, with cleanup checks limited to once every 6 hours |