Skip to content

Policy

Cookie policy

How ÉCLATAUR uses cookies to power your shopping cart, secure checkout, and browsing experience.

Last updated November 10, 2026

This Cookie Policy explains how Eclataur LLC (doing business as ÉCLATAUR) uses cookies and similar technologies when you visit eclataur.com. It should be read together with our Privacy Policy.

01

What cookies are

Cookies are small text files placed on your device when you visit a website. They are widely used to make sites work, to work more efficiently, and to report information back to site owners. Cookies set by the site you are visiting are called first-party cookies. Cookies set by anyone else are called third-party cookies, and they are what enable embedded third-party features such as analytics, advertising, and payment processing.

02

What this site actually sets

The pages themselves set no cookies. They are built as static pages, so there is no server session to keep while you browse. Nothing that measures or advertises loads unless you say yes to it. On your first visit the consent bar asks about both tools below in one question: Accept allows both, Decline refuses both, and Choose separately lets you allow one without the other. Each answer is stored by itself.

Our commerce server sets two, both strictly necessary, and only when you use what needs them. Neither can be read by the page's scripts, neither is shared with anyone, and neither is used for analytics or advertising:

  • Your sign-in (connect.sid), if you sign in to your account. It keeps you signed in as you move between pages, lasts at most 10 hours, and is removed when you sign out.
  • Your conversation with the house (ecl_chat), if you start one in Ask the house. It holds a long random reference so the conversation follows you from page to page and is still there when you reopen the panel on the same device. It lasts 30 days, is sent only to the chat itself, and holds nothing about you; the server keeps only a scrambled copy of it.

Analytics asks first. We use Google Analytics 4 to see which pages are read and how the shop is used: which fragrances are viewed, added to the cart, and bought. It loads only after you choose Accept on the consent bar at the bottom of your first visit; its cookies (the _ga family) exist only from that moment. Choose Decline and nothing loads, no analytics cookie is ever set, and the site works identically. Your choice is remembered on this device either way, so you are asked once.

Advertising asks first too, and its answer is kept apart. We advertise on Instagram and Facebook, and we use the Meta Pixel to learn whether those adverts work. If you say yes to Meta on the consent bar, the pixel tells Meta which pages you open here, which fragrances you view and add to your cart, and whether you buy, and Meta may use that to measure our adverts and to decide who sees them. It sets two cookies of its own (_fbp, and _fbc if you arrived from an advert), which exist only from that moment and last up to 90 days. When you place an order after saying yes, our commerce server also tells Meta that the sale happened: the value of the goods, the products, those two cookie values, and a scrambled form of your email that Meta can match only against an account it already holds. Never your name, your address, or anything about how you paid. Choose Decline and none of this happens: the pixel never loads, no cookie is set, and nothing about your order is sent to Meta. A yes to analytics alone, given through Choose separately or before this question existed, is never taken as a yes to this.

One measurement runs without asking, because it has nothing to ask about. Cloudflare Web Analytics tells us how quickly pages load for real visitors: how long the main image took to appear, whether the page jumped while loading, how fast it answered a tap. It sets no cookie, stores nothing on your device, and identifies no one; it sees a page's address and its timings, and that is all. It is how we know whether a change made the site faster or slower for you rather than for us.

A few things do need to be remembered between pages, and all use your browser's local storage rather than cookies. Local storage stays on your device and is not transmitted automatically with your requests, which is the main way it differs from a cookie:

  • Your cart is stored as a single reference that points at the cart held on our commerce server. It holds no payment information and no personal details. Without it, your cart would empty every time you moved between pages.
  • A signed-in marker, if you sign in: a single flag that tells the pages to ask for your account, so a guest's pages do not. It is not your sign-in (that is the cookie above) and grants nothing on its own. Signing out removes it.
  • Your analytics choice and your advertising choice, each stored by itself, whichever way you decided, so the consent bar asks once rather than on every visit. Clearing one simply means being asked that question again.
  • Your wishlist and recently viewed fragrances, so both survive between visits without needing an account. They hold product references only, nothing about you.
  • An offer code from a link, if you arrive through a link that carries one, so it can be tried when you reach the payment step. It holds the code alone, for up to 30 days, and is cleared after 30 days or when you sign out.
  • A review draft, while you are writing one, so a closed tab does not cost you the text. It is removed the moment the review is submitted.
  • How you arrived: the page your visit began on, the name of the site that linked you here if one did (for example instagram.com, never the full address), and, if you came through a link in one of our letters, the name of that letter. It holds those three things and the date, for 30 days, so we can tell which pages and which letters are worth anyone's time. It names a page and a site, not you, it is never read by a third party, and it is kept as it was on your first visit rather than being overwritten by every later one.
  • A collaborator reference, if you arrived through a link one of our collaborators shared. It holds only their code and the date, for 30 days, so that an order you place credits the person who sent you. It identifies them, not you, and no third party ever reads it.

The following entries use session storage, which your browser empties by itself when the tab closes: the order confirmation handed from an express wallet payment to the confirmation page, and a marker that stops an already-counted purchase being counted twice in analytics. Neither leaves your device.

Checkout also keeps your entered contact and address details, delivery choices, gift notes and current step in session storage so a refresh or return visit in the same tab does not make you start again. This draft is used for up to two hours and is cleared when you finish checkout or sign out. It contains no password or card details. A temporary rewards request reference lets our server recognize a retry without converting your points twice; it is removed after the redemption is applied or you sign out.

The cart reference is removed when your cart is completed, the sign-in when you sign out, the review draft when the review is submitted, and the collaborator reference expires by itself. You can clear any of them at any time through your browser's site data settings; clearing them signs you out, empties your cart, and forgets your wishlist, and nothing else on the site stops working.

04

Third parties that may set cookies

  • Stripe, our payment processor, sets cookies during payment. These process your transaction and detect fraud, and they are strictly necessary: card payments cannot be taken without them. Stripe acts as its own data controller here, under its own policies.
  • PayPal, our other payment processor, sets cookies when you choose to pay with PayPal. Like Stripe's, these exist to process the transaction and prevent fraud, and PayPal acts as its own data controller under its own policies.
  • Google, our analytics provider, sets the _ga cookie family, and only after you accept on the consent bar. These measure page visits and shopping activity, such as products viewed, carted, and purchased; Google acts as its own data controller for them, under its own policies.
  • Meta (Instagram and Facebook), our advertising platform, sets the_fbp and _fbc cookies, and only after you say yes to Meta on the consent bar. They let Meta recognise the same browser across your visits here and connect a visit to the advert that led to it; Meta acts as its own data controller for them, under its own policies.
  • Cloudflare, which serves and protects this site, may set a cookie to identify trusted traffic or to mitigate an attack in progress. This is a security function rather than tracking, and it is not used to build a profile of you.

Each of them maintains its own privacy and cookie policies, and we would encourage you to read them for detail on their own handling.

05

How to control or disable cookies

Change either choice here. Each button stops that tool and reloads the page with the consent bar, where you can accept or decline again. Changing the advertising choice also removes Meta's two cookies and takes the mark off your open cart, so an order you place afterwards is not reported to Meta. Your cart and account are otherwise unaffected.

  • Browser settings: every major browser lets you block or delete cookies and site data, and warn you before accepting new ones. The controls sit under privacy or site settings.
  • Do Not Track: some browsers send a Do Not Track signal. Nothing here measures or advertises until you say yes on the consent bar, whatever that signal says, so the answer you give there is the one we follow.

Blocking cookies entirely will prevent checkout from completing, because neither Stripe nor PayPal can process a payment without their own strictly necessary cookies. Browsing and reading the site are unaffected.

06

Retention

  • Session cookies are deleted when you close your browser.
  • Our two cookies: the sign-in lasts at most 10 hours and ends when you sign out; the conversation reference lasts 30 days.
  • Persistent cookies remain for a set period or until you delete them. The Stripe, PayPal, Google, Meta, and Cloudflare cookies above are governed by their own retention periods.
  • Local storage has no expiry date. It stays until cleared by us on sign-out or cart completion, or by you through your browser.
07

Changes to this policy

We may update this policy to reflect changes in the technologies we use, or for operational, legal, or regulatory reasons. If we ever introduce another analytics or advertising technology, this page will say so before it goes live, and the date above will change.

Questions about this policy?

We are here to help. Our team responds within one business day.

Eclataur LLC (dba ÉCLATAUR) · 310 Silver Creek Trl, Sunnyvale, Texas 75182, USA · support@eclataur.com · +1 (469) 434-6194

Ask the house