Scope
This notice applies to legal.lornez.com, operated by LORNEZ GROUP. It also describes the common principles followed when a Lornez Group website uses cookies or similar technologies.
A dedicated business website may provide an additional notice where its technologies, services, or consent choices differ. That more specific notice supplements this document for the relevant website.
Current position
As of the date shown above, this Legal & Trust Center does not use analytics, advertising, profiling, social-media tracking, or other non-essential cookies. It does not present a consent banner because there is currently no optional cookie choice to make here.
The web server may create limited security and access logs when a page is requested. Those server records are not cookies and are addressed in the Privacy Notice.
Tableware measurement
This section applies to tableware.lornez.com. It is not a statement that analytics or advertising measurement is active on every Lornez Group website. On Tableware, the technologies that may operate depend on the visitor's actual cookie choice and whether the corresponding production tag has been enabled.
Tableware uses a consent interface built and operated by Lornez Group on the site. Before a visitor grants an optional category, the corresponding optional technology is not loaded or called. If all optional categories are refused or no choice has been made, Google measurement tags and Meta Pixel/CAPI are not called from that setup.
The Google and Meta services and site-managed browser storage covered by this setup are set out below. Names and lifetimes are indicative: the technologies actually used can vary with the consent choice, browser, configuration, and each provider's operation of its services.
| Service and category | Purpose | Typical technologies and approximate period |
|---|---|---|
| Site consent control — strictly necessary | Remember the visitor's analytics and advertising choices and allow those choices to be changed later. | A first-party consent cookie stored for up to 180 days (approximately 6 months). |
| First-touch attribution storage — analytics or advertising | Preserve the first campaign source for an RFQ. After analytics consent, the site may store UTM parameters, the landing page, and referrer. After advertising consent, it may store Google click identifiers such as gclid, gbraid, or wbraid and Meta attribution values such as fbclid, _fbp, and _fbc where available. Each data group is retained only while the corresponding consent remains in place. | First-party browser localStorage, described here as first-touch attribution storage. A record is treated as expired 90 days after it is recorded and is automatically deleted when the site next runs and checks it. Browser localStorage does not expire independently while the site is not running. Withdrawing the relevant consent or clearing browser data can remove it earlier. This is site-managed storage, not a Google cookie. |
| Google Analytics 4 — analytics Measurement ID: G-1YXSVCBW30 | Understand aggregate website use, navigation, performance, and successful request-for-quotation activity after analytics consent. | Cookies commonly named _ga and _ga_*, ordinarily up to approximately 2 years, subject to configuration and user controls. |
| Google Ads — advertising measurement | Measure a successful request for quotation and attribute it to an advertising click after advertising consent. The Tableware setup does not use enhanced conversions, advertising personalization, remarketing audiences, or cross-site profiling. | Cookies or click-attribution storage commonly including _gcl_au and, depending on the visit and Google configuration, other _gcl_* identifiers; commonly around 90 days, although actual periods may vary. |
| Meta Pixel and Website Conversions API — advertising | After Advertising consent, measure PageView, RFQ ViewContent, and a successful Lead for advertising attribution, measurement, and delivery optimization. Browser Pixel and server CAPI copies use the same server-generated event ID for deduplication. | Meta Pixel may use _fbp and _fbc values and fbclid may be stored by the site where available. CAPI sends event data from the server and does not itself place a browser cookie. Meta independently states its retention in its own privacy policy. |
| Google Tag Manager — tag management Container ID: GTM-TXV8KHW9 | Manage when the permitted analytics and conversion tags run. Tag Manager is not used as a separate analytics profile. | The container is loaded only after relevant optional consent and only if its production configuration has been enabled. Any storage then depends on the permitted service that the container activates. |
Measurement data does not include the contents of an RFQ form. Names, email addresses, telephone numbers, company details, inquiry text, specifications, and attachments are not placed in the Google Tag Manager data layer or sent to Google Analytics or Google Ads through this setup. A successful RFQ may instead be represented by a technical event and a non-contact reference used for measurement and duplicate prevention. For Meta CAPI, the server may send the event ID, IP address, user-agent, _fbp/_fbc/fbclid values where available, limited page/source information, and a hashed email for a successful Lead. It does not send the RFQ message, quantities, attachments, or plain-text email through that event.
The browser-storage periods above are not the same as the period for which event data is retained inside a Google Analytics property. In the current Tableware Google Analytics property, event data retention is set to 2 months and user data retention is set to 14 months. Resetting the user-data retention period on new activity is enabled, so the applicable user-data period starts again when that user identifier records new activity. These property settings do not extend or replace the browser-cookie periods described above and do not determine the availability of standard aggregated Analytics reports.
Technology categories
If technologies are introduced on this or another group website, they are assessed according to their actual purpose:
| Category | Purpose | Ordinary consent position |
|---|---|---|
| Strictly necessary | Security, network delivery, user-requested functionality, or preservation of an explicit privacy choice. | May operate without optional consent where legally permitted. |
| Preferences | Remember a non-essential language, display, or interface choice. | Enabled only with the required choice or consent. |
| Analytics | Measure audiences, navigation, performance, or campaign effectiveness. | Disabled until consent where consent is required. |
| Advertising measurement and social media | Conversion measurement, click attribution, or separately disclosed social-media features. Lornez does not configure separate Meta audience creation or remarketing through this Tableware setup. This description does not limit Meta's own processing under its policies. | Disabled until valid consent where required. |
Consent and choice
Before a group website activates optional technologies that require consent, it should provide clear information and a genuine choice. Refusing optional technologies should be as accessible as accepting them, and withdrawal should be available without affecting essential website access.
Consent is not treated as a basis for technologies that are not actually deployed. On Tableware, accepting analytics does not by itself grant advertising consent, and refusing optional technologies does not prevent access to the website's essential content or RFQ function. Refusing or withdrawing Advertising consent stops Lornez from sending new Meta Pixel/CAPI events through this setup; it does not recall data Meta received before the choice changed.
Third-party services
A link to Facebook, Instagram, Threads, or another external website does not itself place that provider's cookie through this Legal & Trust Center. When you follow an external link, the destination service may process information under its own policies.
When the relevant production tag has been enabled and the visitor has granted the corresponding consent, Google may receive browser and device information, page and event data, consent signals, campaign parameters, and click identifiers for the purposes described above. Google may process information under its own terms and privacy information. The Tableware setup limits activation to the categories selected by the visitor.
When the Meta integration is enabled and the visitor has selected Advertising, Meta may receive the limited Pixel/CAPI data described above. Meta independently processes that information under its Privacy Policy. Choosing Advertising on Tableware governs Lornez's future event transmission from this website; Meta account and provider-level controls remain available through Meta.
Your controls
You may use browser or device settings to view, block, or delete stored cookies. Blocking strictly necessary technologies can prevent a requested feature from working. Browser controls do not always remove information already transmitted to a service before the setting was changed.
On Tableware, the Cookie settings control allows a visitor to revisit or withdraw optional consent at any time. The site removes first-touch attribution data for a withdrawn category, and removes the entire first-touch record when both optional categories are refused. A changed choice applies to future tag activity, including new Meta Pixel/CAPI events. Cookies or other site data already stored can also be removed through browser controls.
Changes and contact
We may update this notice when technology, providers, legal requirements, or group website practices change. The effective date at the top of the page identifies the current version.
Questions about cookies or related technologies may be sent to lornez@lornez.com. Broader information about personal-data processing and rights is available in the Privacy Notice.