Privacy Policy

How Brandz handles store owners' and shoppers' data — in plain language.

Last updated 4 October 2026 · questions: [email protected]. Brandz runs on the DigitalU platform; this page covers brandz.live and app.brandz.live.

If you run a store on Brandz

Your account: your email and your plan.
Your store: the catalog (products, variants, prices, images), your public store policies, and the settings you choose (face, voice, greeting, rules). On Shopify we read these with the access you grant when you install; on WooCommerce from your store's public data.
Orders, if you turn on retargeting: for each order, its reference, amount and currency, the shopper's anonymous id carried in the cart, and the customer's email as a one-way hash — to count which sales followed a conversation.
If you connect Klaviyo: we read the emails on the list you pick and write each person's own link into their profile — nothing else.

If you shop on a store that uses Brandz

The conversation with the store's concierge, as text. Your voice is turned into text so it can answer; the audio isn't kept. The store can read its concierge's conversations.
A pseudonymous shopper id in your browser, so the concierge can continue where you left off.
What you choose to give: an email for updates or a "talk to a person" request, and products you add to your cart through the concierge.

Returning shoppers (retargeting)

A store can turn on retargeting so that when you come back — from its ad, its email, or on your own — the concierge picks up where you left off. When it's on, on that store:

What you looked at: the products you viewed, added to cart or took to checkout (name, price, page).
An id kept in your browser: stored in local storage, a cookie on the store's site and the browser database, so clearing one doesn't make you a stranger. On Shopify it also rides in the cart, so a sale can be counted.
Device signals: browser and system family, screen size, time zone, language, hardware hints, and short codes computed in your browser from how it draws text and graphics, plays a test sound and which fonts and voices it has — plus the first three parts of your IP address — to recognise a returning device. Collected on every visit while retargeting is on, and only compared within that one store.
Across devices: if you give your email, are signed in to the store (we receive its customer id), or click a link the store emailed to you personally (it carries a signed code made from a one-way hash of your email, never the email), we can recognise you on your other devices.

The concierge may open on what you looked at and, when we're sure it's you, remember what you talked about. When we only think it's you (device signals alone), it may mention products but never what you said. Some shoppers are deliberately shown nothing extra, so the store can measure the difference. The store decides to use retargeting and is responsible for it; we run it for them.

Demos and advertising

We sometimes build a demo concierge from a store's public catalog and send its owner the link. We record whether the demo was opened, talked to, and whether the store signed up, and share that with the outreach tool that sent it. On those demo pages, and when someone signs up, we may load the advertising tags of Meta, Google, LinkedIn and X, so we can show relevant ads later; those networks set their own cookies under their own policies. Ask us not to contact you and we keep only a one-way hash of your email so you're left out of outreach, retargeting and personal links.

Cookies and browser storage

Ours: sign-in cookies for store owners; the shopper id and, with retargeting, the id described above (local storage, a cookie, the browser database).
Advertising networks' cookies, only where their tags load.

Analytics

Our pages load our own analytics (analytics.leedz.co): a page view (the page, where you came from, campaign tags, your browser type) and a random visitor id kept in your browser's local storage. We use it to count visits and to connect a visit to the demo or sign-up it led to, across our own sites. It isn't sold and isn't shared with advertising networks; clearing your site data removes the id.

Who processes it for us

Providers that run parts of the service under contract: real-time voice and video (speech-to-text, text-to-speech and the avatar video), the language models that write the answers, hosting and storage, email delivery, and payments (Stripe — we never see a card number). Shopify or WooCommerce provide your store's data; Klaviyo only if you connect it; advertising networks receive what their tags collect.

Why we use it

To run the concierge, show stores what shoppers asked and what sold, follow up with interested shoppers for the store, bill plans, and keep the service secure. We don't sell personal data and don't use conversations to advertise to you.

How long we keep it, and deleting it

Catalog, settings and conversations are kept while the store is connected. Uninstall or delete the store and they go with it; Shopify's data-deletion requests are honoured automatically.
Retargeting records (what you looked at, device records) are kept for the period the store sets — 180 days unless it changes it — and a device is only matched against the last 90 days.
To see, correct, export or delete what we hold about you, or to stop being recognised or contacted, write to [email protected] (shoppers can also ask the store). We answer within 30 days.

Your rights

Wherever you live, you can ask us to access, correct, delete or export your personal data, or to stop using it; in the EU or UK these are your GDPR rights, and you can complain to your data-protection authority. We process data to provide the service (contract), to keep it secure and to let stores follow up with interested shoppers (legitimate interest — you can object), and where you've agreed (consent).

Children

Brandz isn't for children under 16.

Changes

If we change this policy in a way that matters, we'll say so here and, for store owners, by email.