Notice record
What this notice covers
This notice took effect on September 28, 2026 and describes the storage and advertising identifiers used on the live Zavellora site.
Zavellora is a small Austin catalogue for perfume, personal care and gift sets. Visitors can read product notes and send an inquiry without creating an account. The site receives paid traffic from Google Ads and Microsoft Advertising, and Meta Ads sends traffic here where a campaign runs there. This page explains the browser signals around that visit. It is not a checkout notice because nothing is sold or paid for on this site.
The effective date is September 28, 2026. This notice applies to visitors in the United States and to visitors who reach the site from Europe. The privacy notice explains inquiry, chat and server data in more detail. The consent preferences page gives the same practical route back to the current control.
Three categories
Which storage is used?
Strictly necessary storage keeps a choice or conversation working; analytics and advertising storage remain controlled choices.
Strictly necessary storage supports the navigation drawer, consent controls and support chat. The consent record under site_consent_v2 keeps the banner from asking again on every page. A chat token lets a visitor return to an open conversation in the same browser. These functions do not create an account.
Analytics storage supports measurement of visits and page use after permission. It is not needed to read the personal care catalogue, use the contact details or send an inquiry. If storage is declined, analytics storage stays denied and the page remains usable.
Advertising storage supports measurement of paid traffic from Google Ads, Microsoft Advertising and Meta Ads. The click identifiers are described below. Declining stops optional advertising storage while leaving the catalogue and its inquiry path available.
Storage register
What names may appear in the browser?
The table names the browser keys and their practical purpose rather than hiding them behind a general label.
| Name | Who sets it | What it does | How long |
|---|---|---|---|
site_consent_v2 | Zavellora | Stores the visitor's consent choice so the banner can respect it across the site. | 12 months |
| Chat token | Zavellora support chat | Returns a visitor to their support conversation in the same browser. | Chat transcripts are kept 12 months |
gclid | Google Ads | Identifies a Google Ads click for campaign and visit measurement. | Controlled by the advertising platform and browser settings |
msclkid | Microsoft Advertising | Identifies a Microsoft Advertising click for campaign measurement. | Controlled by the advertising platform and browser settings |
fbclid | Meta Ads | Identifies a Meta Ads click where a campaign runs there. | Controlled by the advertising platform and browser settings |
A click identifier may arrive in the page address rather than as a cookie. It is not a payment record. The site has no account, password or card-data function. The hosting provider serves the pages and stores the inquiry database, while a mail provider carries inquiry notifications to the operator's inbox.
Paid traffic
Which platforms attach identifiers?
Google Ads, Microsoft Advertising and Meta Ads send traffic here, with a separate identifier for each platform.
google ads uses gclid on a click. Google Ireland Ltd / Google LLC receives the consent signals associated with that visit. Microsoft Advertising uses msclkid; Microsoft Ireland Operations Ltd handles its own advertising data. Meta Ads uses fbclid where a campaign runs there; Meta Platforms Ireland Ltd is the named recipient.
The identifiers help connect an advertising click with activity on the destination. They do not turn the catalogue into a marketplace and they do not create a product order. Zavellora does not claim that any platform has reviewed, approved or verified this site.
Signal policy
How does Consent Mode v2 work?
Consent Mode v2 starts optional storage in a denied state and changes that state only after a visitor allows it.
The site uses consent mode with Consent Mode v2. Before the visitor allows storage, these four signals are denied: ad_storage, ad_user_data, ad_personalization and analytics_storage. This default keeps the catalogue available while optional storage waits for a clear choice.
When a visitor allows storage, the relevant signals can be updated to reflect that permission. When a visitor declines or withdraws permission, the site sets ad_storage, ad_user_data, ad_personalization and analytics_storage back to denied at that moment. Global Privacy Control through the Sec-GPC header is honoured as an opt-out without asking again.
Your choice
Where can consent be changed?
Use Cookie settings in the footer whenever you want to allow, decline or withdraw optional storage.
The banner offers Allow and Decline while the page remains usable. The current choice is stored under site_consent_v2 for 12 months. Select Cookie settings in the footer to revisit it. Choosing Decline is the practical route for withdrawing optional storage; the four Consent Mode v2 signals return to denied.
Browser settings provide another layer. You can clear site data, block cookies or restrict storage through the browser controls. Clearing the consent key may show the banner again. Browser restrictions may affect the convenience of returning to chat, but product notes, phone, email and the inquiry route remain available.
If you decline
What still works without optional storage?
Declining does not block the catalogue; it stops optional measurement and advertising storage instead.
You can browse the perfume shop Austin catalogue, compare eau de parfum notes, read body care and face care products, explore hair care products, and open the fragrance gift sets Austin selection. You can call +1 (534) 555-5106, email [email protected] or send an inquiry. There is no cookie wall in front of those actions.
Optional analytics and advertising storage stop when you decline. Paid click identifiers may still be present in an address supplied by a platform, but the consent signals do not authorise optional storage. If browser restrictions affect support chat, email remains the fallback.
Platform documents
Where do the platforms explain their handling?
The platforms publish their own privacy documents, and those documents govern their separate processing.
Read Microsoft's privacy statement at privacy.microsoft.com. Google publishes its privacy policy at policies.google.com. Meta publishes privacy information through its own policy centre. Those documents describe platform handling, not a promise that Zavellora controls every platform practice.
Google Ireland Ltd / Google LLC, Microsoft Ireland Operations Ltd and Meta Platforms Ireland Ltd are named above because their advertising systems attach the relevant identifiers. The hosting provider and mail provider receive information needed to serve the site and carry inquiry notifications. Each recipient has a different task.
A specific question
Who can answer a cookie question?
Send the exact key, page address or advertising identifier to Zavellora so the operator can understand the question.
Write to [email protected] or call +1 (534) 555-5106. Postal correspondence goes to 158 Mill Street, Suite 4, Austin, Texas 26808, United States. Include the browser key or page address if you are asking about a specific event. Do not send payment details because the site does not take them.
For access, correction or deletion, use the direct data request route. For wider data handling, read Privacy. The catalogue stays inquiry-only; no cookie choice creates an order or a binding USD quote.