By default, Breinify’s API Library (see GitHub Repository) sets only two first-party cookies:
- x-breinify-uuid
- x-breinify-bid
Both are randomly generated universally unique identifiers (UUIDs) that enable anonymous tracking and the collection of journey-based metrics. These identifiers allow us to understand user flows and experiences without storing any personally identifiable information (PII).
Other than these two cookies, Breinify does not, by default, store or collect additional information in the browser’s localStorage, sessionStorage, or through any other cookies.
Importantly, Breinify does not use third-party cookies for advertising or retargeting purposes. All identifiers remain first-party and strictly limited to platform functionality.
In the following table, you will find a table that provides details on each general entity - its name, purpose, where it is stored (cookie, localStorage, or sessionStorage), and its retention period. This ensures full transparency into how Breinify manages browser-based storage.
| Name | Purpose | Storage | Life Span |
|---|---|---|---|
| x-breinify-uuid |
anonymous UUID, used to identify a visitor's session |
sessionStorage |
resets for each browser session |
| x-breinify-bid | anonymous UUID, used to identify returning visitors | localStorage |
1 year, extends after each read |
Optional Cookies & Storage
In addition to the default identifiers, Breinify may set optional cookies or storage entries depending on specific platform configurations and feature usage. These optional items are not enabled by default and only occur when a customer chooses to activate certain capabilities - such as split-test based experiments, or analytics modules.
Whenever optional cookies or local/session storage entries are used, they follow the same principles as the default identifiers, i.e., all entities are first-party only (no third-party retargeting or advertising cookies). In the following table the name, purpose, storage mechanism, and retention period of optional cookies are summarized.
| Name | Purpose | Storage | Life Span |
|---|---|---|---|
| breinify-split-test-data |
stores the split-test (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 can be successfully sent | localStorage |
normally seconds, until the activity is sent |