Privacy

Role

When you embed the SentientUI SDK on your site, you are the data controller for your visitors. SentientUI acts as a processor for the signals needed to run personalization, measurement, and reporting. See the DPA for subprocessors and processing terms.

What the SDK may collect

Depending on your integration and consent settings, the SDK / API may process:

• A random session identifier in a first-party cookie (_snt_uid) and matching local storage keys used for assignment continuity
• Device class (mobile / tablet / desktop) derived from the User-Agent
• Traffic source (direct / search / social / referral) derived from the Referer
• UTM parameters when present on the landing URL
• Variant / slot / layout assignment events and goal (conversion) events
• Behavioral engagement signals when enabled: section dwell, scroll depth, rage clicks, copy, hesitation, and tab-loss style micro-signals
• Page-structure graph data when graph scanning is enabled: component ids, semantic section types, prominence, and a path-only page URL (query strings and fragments are stripped). Heading / DOM text is off by default and only sent when you set captureDomText
• Optional stable userId if you call .identify() (stored as you provide it for cross-device continuity)
• A snapshot of rendered variant HTML (up to 30 KB) for dashboard previews, when sent

What we do not collect by default

• Names, email addresses, or contact details — unless you pass them via identify or metadata
• Full page URLs with query strings (graph sync uses origin + pathname only)
• Heading / DOM text unless captureDomText is explicitly enabled
• Cross-site tracking or third-party ad pixels
• IP addresses beyond what hosting infrastructure may log transiently

Personal data and identifiers

Online identifiers (including pseudonymous session UUIDs) and linked behavioral history can be personal data under GDPR / UK GDPR, especially when activity is linked over time. Treat the session id and optional userId accordingly: obtain consent where ePrivacy / GDPR require it, and use the SDK consent prop (and DNT / Global Privacy Control handling) so tracking does not run before permission.

Cookies and consent

The SDK sets one first-party cookie: _snt_uid (random UUID). Gate initialization with the consent prop until your CMP grants consent. See the consent documentation.

Retention, export, and deletion

Raw event data is retained for 90 days by default. Aggregated variant weight data — the optimizer's learned knowledge — is retained until you delete the project. Project owners can export via the management export endpoints and erase a visitor via DELETE /v1/visitor (Art. 17-style erasure across visitor-keyed tables). Contact us for assistance; we respond within 30 days.

Regional processing

Processing location and subprocessors are listed in the DPA. Engage counsel for your jurisdiction; this page is a product inventory, not legal advice.

Contact

Questions about this policy: hello@sentient-ui.com