Consent

Consent works in two layers. Both have to be satisfied before Luria does anything on a visitor's screen.

Layer 1: your consent

When you install, you accept Luria's Data Processing Terms (a checkbox with a timestamp). Nothing runs on your site until you do. If you later withdraw, Luria stops serving and collecting for that site. You can read the terms at any time at luriart.com/privacy.

Layer 2: your visitors' consent

What Luria does for a given visitor depends on their privacy signals and, on Shopify, on your store's Customer Privacy settings.

Signals Luria always honours

• Global Privacy Control (GPC) and Do Not Track (DNT). If either is on in the visitor's browser, Luria collects nothing, stores nothing, and serves nothing. That visitor sees your original page. Luria treats GPC as a denial.

On Shopify

Luria follows your store's Customer Privacy settings (Settings > Customer privacy in Shopify admin). You do not configure anything extra in Luria.

• In regions where consent is not required, Luria runs fully from the first page view.
• In consent-required regions (EU, UK, Switzerland, and others you add), before the visitor decides, only strictly necessary processing runs: the visitor is shown a consistent page version and is counted in aggregate. Nothing else is collected.
• When the visitor accepts, full collection starts.
• When the visitor declines, the extra collection is dropped. Aggregate counting continues so your results are not skewed, but no behavioural detail is kept.

Outside Shopify

The snippet checks whether the visitor's region requires consent. If it does, and the visitor has not yet decided, Luria shows a small one-line prompt with equal Accept and Decline buttons. Decline is remembered and Luria stays off for that browser.

If you already run a consent banner or CMP (Cookiebot, OneTrust, Termly, a built-in platform banner), you have two options:

1. Load the snippet only after consent. Add the Luria tag through your CMP's "analytics" category, or through Google Tag Manager with a consent trigger. See Install with GTM.
2. Let Luria's own prompt handle it. Simplest, but your visitors may see two prompts.

A dedicated "tell Luria the visitor already consented" hook is not public yet. If you need it, write to support.

Region table

Privacy-policy clause for your site

Most privacy laws expect you to tell visitors about tools like Luria. Here is a generic clause you can adapt.

We use Luria, a service operated by Luria (luriart.com), to test and improve the content of our website. Luria may record page views, clicks, scroll activity, and purchases or sign-ups, using a random identifier stored in your browser. It does not collect payment details, passwords, or the text you type into forms. Luria acts as our service provider and processes this information only on our instructions. Where required by law, we ask for your consent first, and we honour Global Privacy Control signals.

Frequently asked

Next steps

• Data and privacy
• Security
• Install with Google Tag Manager