Nine things this site stores in your browser, and what each one does.
tufelan.com sets very few cookies of its own. Most of what a browser stores here comes from the advertising platforms that sent the click, and from a single choice you make in the banner at the bottom of the screen. This page lists every one of them by name.
Effective and last updated: September 14, 2026
When this took effect
This notice decides what counts as current, and from when.
This cookie notice took effect on September 14, 2026, and covers every cookie and browser storage key described below from that date forward. If a category or a key changes, the date at the top of this page moves and we say so in plain terms rather than only quietly updating the table.
The three categories in use
This decides what each cookie is allowed to do before you ever see the table.
Strictly necessary storage keeps the site itself working — remembering that you have already answered the cookie banner, and, if you open the chat widget, the token that lets a conversation continue when you come back. This category runs regardless of your choice, because without it the banner would ask you again on every page.
Analytics storage would tell us which pages get read and which ones get abandoned; it is off until you allow it.
Advertising storage lets Google Ads and Microsoft Advertising, and Meta Ads where a campaign is running, connect a visit back to the ad that caused it; it is also off until you allow it, and it is what actually reads a click identifier like gclid.
Every cookie and storage key
This decides exactly what is set, by whom, and how long it survives.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
site_consent_v2 | tufelan.com (necessary) | Stores your allow/decline choice so the banner does not ask again this year. | 12 months |
| Chat token | tufelan.com (necessary) | Lets an open chat conversation survive a page reload or a return visit, stored in localStorage rather than a cookie. | Until you clear it, or the transcript ages past 18 months |
_ga, _ga_* | Google (analytics, if allowed) | Distinguishes visitors and sessions to measure page use. | Up to 13 months |
_gcl_au | Google Ads (advertising, if allowed) | Links an ad click carrying gclid to a later inquiry. | Up to 90 days |
| Microsoft Advertising click storage | Microsoft Advertising (advertising, if allowed) | Links an ad click carrying msclkid to a later inquiry. | Up to 180 days |
_fbp, fbclid reference | Meta Ads (advertising, if allowed, where a Meta campaign runs) | Links an ad click carrying fbclid to a later inquiry. | Up to 90 days |
The exact lifetime of a platform's own cookie is set by that platform and can change on their side without changing this table's intent: necessary storage always runs, analytics and advertising storage only run once you allow it.
The click identifiers we read
This decides which parameter on the incoming link gets tied to your later visit.
Google Ads attaches gclid to a link when you click one of its ads. Microsoft Advertising attaches msclkid. Meta Ads attaches fbclid where a campaign is running there. All three send paid traffic to this site today, and each identifier is read by that platform's own advertising storage once you have allowed it — never before.
Consent Mode v2, in detail
This decides what "denied" and "granted" actually switch on and off.
This site runs Google's Consent Mode v2 on every page load. Four signals are held denied before you answer the banner: ad_storage, ad_user_data, ad_personalization and analytics_storage. Allowing storage in the banner sets all four to granted for that browser. Declining, or later withdrawing through the cookie choices control in the footer, sets all four straight back to denied. Consent Mode does not block the page, the form or the chat widget — those keep working regardless — it only controls whether the advertising and analytics cookies in the table above are permitted to write anything.
ad_storageWhether an advertising cookie like Google's _gcl_au may be written at all.
ad_user_dataWhether data about this visit may be sent to an ad platform for measurement.
ad_personalizationWhether that data may be used to personalise an ad you see elsewhere.
analytics_storageWhether an analytics cookie like _ga may be written at all.
How you give, and change, consent
This decides where the switch actually lives on the page.
The banner that appears at the bottom of the screen on your first visit gives you two buttons: Allow storage and Decline. Whichever you press is written to site_consent_v2 and applied to the four Consent Mode signals immediately. To change your mind later, use the "Cookie choices" control in the footer of every page — it reopens the same banner so you can flip the choice, and the new choice takes effect at once, replacing the old one rather than adding to it.
What happens if you decline
This decides what still works and what simply does not run.
Declining stops every analytics and advertising cookie in the table above from being written, and holds all four Consent Mode signals at denied. It does not stop anything else: the inquiry form still submits to our own server, the estimator still runs entirely in your browser without contacting an ad platform, and the chat widget still works, because its token is necessary storage rather than advertising storage. The only thing lost is our ability to see which ad, if any, led to your visit.
The platforms' own documents
This decides where to read the fine print each platform writes for itself.
Google's own account of how it uses cookies and ad identifiers sits at policies.google.com. Microsoft's is the Microsoft privacy statement at privacy.microsoft.com. Neither document being linked here means either platform has reviewed or endorsed this site; it only points you to how they each describe their own advertising storage.
Questions about a specific cookie
This decides who to ask, and how, if a line above needs explaining.
Email office@tufelan.com with the name of the cookie or storage key from the table above, or call +1 (499) 555-0889. For anything broader about how we handle personal data, see the privacy policy, which covers the inquiry form and chat data this notice does not.