Cookie & ad-storage policy
What Tavlixos stores in your browser, and what a paid click carries with it
Google Ads and Microsoft Advertising run traffic to this catalog, and a Meta Ads campaign may. This page names exactly what each one attaches to your visit, what we store ourselves, and how you switch storage off.
Effective September 24, 2026
| Effective | 2026-09-24 |
|---|---|
| Who | Tavlixos |
| Where | Austin, United States |
| Contact | office@tavlixos.com |
| Site | tavlixos.com |
At a glance
The six things people came to this page to find, before the full explanation underneath.
| Who holds the data | Tavlixos, trading at tavlixos.com, 77 Industrial Blvd, Büro 5, Austin, Texas 16719, United States. |
|---|---|
| Where it sits | Our hosting provider's servers, plus the ad accounts of Google, Microsoft, and Meta where a campaign runs there. |
| How long it's kept | Consent choice 12 months. Enquiry records 36 months. Chat transcripts 12 months. Server logs 60 days. |
| Who else sees it | Google Ireland Ltd / Google LLC, Microsoft Ireland Operations Ltd, Meta Platforms Ireland Ltd where relevant, our hosting provider and our mail provider. |
| How to get a copy out | Email office@tavlixos.com or use the data request page. We reply within 14 days. |
| Who to write to | office@tavlixos.com, or +1 (222) 555-3617 during counter hours. |
Effective date
This notice took effect on September 24, 2026 and applies to every visit to tavlixos.com from that date. When we change how a cookie or a storage key works, we update this date and describe the change in the section below on changes to our policies.
The three kinds of storage on this site
Strictly necessary. These keep the site working: the consent choice itself, and anything the inquiry form or the chat widget needs to hold your place in a conversation. They are not optional and are not covered by the banner, because they are not advertising or analytics storage.
Analytics. If you allow it, we measure which pages get read and which category pages send an inquiry through, so we know which parts of the catalog to keep stocked and clear. This runs under the analytics_storage signal described below and does nothing until you allow it.
Advertising. Google Ads, Microsoft Advertising, and Meta Ads where a campaign runs there, attach a click identifier to a visit that arrives from one of their ads, and use it to measure whether that click led to an inquiry. This runs under ad_storage, ad_user_data, and ad_personalization, all denied until you allow storage.
The cookies and storage keys in use
This is every storage key this site or its advertising partners can set, what each is for, and roughly how long it lasts.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
site_consent_v2 | Tavlixos, this site | Stores the allow or decline choice made in the cookie banner. | 12 months, then the banner asks again |
| gclid capture | Google (Google Ads) | Links a visit that arrived from a Google Ads click to a later inquiry, for measuring which ads bring inquiries. | Set and controlled by Google; see policies.google.com |
| msclkid capture | Microsoft (Microsoft Advertising) | Links a visit that arrived from a Microsoft Advertising click to a later inquiry. | Set and controlled by Microsoft; see privacy.microsoft.com |
| fbclid capture | Meta (Meta Ads, where a campaign runs) | Links a visit that arrived from a Meta Ads click to a later inquiry. | Set and controlled by Meta |
| Analytics measurement key | Our analytics provider, only if allowed | Counts page views and which category pages lead to an inquiry. | Cleared immediately if you decline or later withdraw |
The advertising platforms and their click identifiers
Google Ads, Microsoft Advertising, and Meta Ads send paid traffic to this catalog. Google Ads attaches gclid to a visit that follows a Google ad; Microsoft Advertising attaches msclkid; Meta Ads, where a campaign is active, attaches fbclid. None of these identifiers tell us your name. They let the platform's own reporting tie an ad click to whether an inquiry followed it, so we know which keywords and campaigns are worth the spend.
Consent Mode v2 and what each signal controls
We run Google's Consent Mode v2, which holds four signals: ad_storage, ad_user_data, ad_personalization, and analytics_storage. All four start denied on every visit. Nothing advertising-related or analytics-related is written to your browser until you press Allow in the banner. If you decline, or if you never answer, all four stay denied and Google's and Microsoft's own consent-aware tags run in their reduced, non-identifying mode where that mode exists.
ad_storage- Denied until you allow it. Controls whether an ad click identifier can be written or read.
ad_user_data- Denied until you allow it. Controls whether data about the visit can be sent to an ad platform at all.
ad_personalization- Denied until you allow it. Controls whether that data can be used to personalize an ad.
analytics_storage- Denied until you allow it. Controls whether page-view measurement is stored.
How you give or change consent
The banner at the bottom of every page offers Allow and Decline. Choosing Allow sets all four Consent Mode v2 signals to granted and stores that choice in site_consent_v2 for 12 months. Choosing Decline sets all four back to denied and stores that choice for the same 12 months. You can change your mind at any time using the "Cookie choices" control in the footer of every page, which reopens the same banner.
If your browser sends the Global Privacy Control signal, we treat that as a decline automatically and do not ask again during that visit.
What happens if you decline
The catalog, the category pages, the configurator, the inquiry form and the chat widget all work exactly the same whether you allow storage or not. What stops is measurement: no ad click identifier is stored, no analytics page-view is recorded, and no ad platform receives a personalization signal from your visit. We simply lose the ability to see which ad or keyword you arrived from.
The platforms' own policies
Each advertising platform is responsible for its own handling of the identifier it sets. Google's practices are described at policies.google.com. Microsoft's practices are described in the Microsoft privacy statement at privacy.microsoft.com. Meta's practices, where a Meta campaign runs, are described in Meta's own data policy. We do not control, and cannot speak for, what any of these three companies do with data once it reaches their systems; we can only tell you what leaves this site and under what conditions.
Questions about a specific cookie
Write to office@tavlixos.com or call +1 (222) 555-3617 and ask about the storage key by name; we can tell you whether it is one of ours or one of the platforms' and point you to the right policy. For a formal request to see or delete what we hold, use the data request page. For the rest of how we handle personal information beyond cookies, see the privacy policy, and for the ordering terms that this site runs under, see the terms of service.