SentientUI
Get started

Privacy

Last updated: September 2026

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 visitor identifier in a first-party cookie (_snt_uid_<key>, 365 days) 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 — we look an address up to derive country and network operator during the request, then discard it; neither the address nor anything finer than a country is stored

Data sources we rely on

Country and network-operator lookups use IP Geolocation by DB-IP, licensed under CC BY 4.0. The lookup runs offline inside our infrastructure — no visitor address is sent to a third party.

Shopify stores

When a store is connected through the SentientUI Shopify app we also process, per paid, cancelled or refunded order, its Shopify order id, total, currency and time, attributed to the visitor's pseudonymous session — never the customer's name, email, address or what they bought. The checkout pixel binds Shopify's cart/checkout token to that session (deleted after 90 days). A customer-tag → visitor-type mapping, if the merchant sets one, is applied in the storefront; the tags are not sent to us. Merchants who buy a plan through the app are billed by Shopify, which sends us the plan and subscription status.

Shopify's customers/redact removes the named orders' ids from our records (anonymous totals remain in revenue reports), customers/data_request is answered to the store owner, and shop/redact deletes the app's stored keys and session.

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_<key> (random UUID, 365 days). Gate it on your consent platform with consentFrom, or the consent prop. See the consent documentation.

On this website, you choose which categories we may use — optimisation & analytics (the SDK above) and marketing (the Meta Pixel) — and can change or withdraw that choice at any time; a withdrawal takes effect immediately: .

Separately, this website and the dashboard use Vercel Web Analytics and Speed Insights: cookie-less page-view and performance measurement that stores nothing on your device. Shared-report and connect links are redacted before anything is sent.

Retention, export, and deletion

Raw event data is retained for 90 days by default. Forwarded Shopify orders follow the same project retention window: an attributed order is deleted with the visitor's session data once that session has been inactive for the window. 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