- Home
- Cookies
Two small keys run by default. The ad tags wait for your yes.
A machine shop site in Newark, Delaware doesn't need much in your browser. It needs to remember whether you said yes or no, and which chat thread is yours. Everything else on this page stays off until you press Allow.
01 Dated and in force
This cookie statement took effect on 27 September 2026 and was last updated that day. It sits beside the privacy notice, which covers what the inquiry form and the chat keep. This page covers only what is written into your browser, and the tags that could write it.
Last updated 27 September 2026
02 Three kinds, and only one runs by default
Strictly necessary
The key that stores your consent answer, and the chat token that lets you return to a conversation you started. Without the first, the banner would ask you on every page. Neither tracks you across other sites. These run without asking, because the site can't remember a no without storing the no.
Analytics
Google's measurement tag counts visits and which pages people read before sending a drawing. It tells us whether the fixtures page answers the questions buyers call about. It stays off until you allow it, under analytics_storage.
Advertising
The Google Ads, Microsoft Advertising and Meta tags. They record that someone who clicked an ad went on to send an inquiry, so the shop stops paying for ads that bring nobody. Off until you allow them, under ad_storage and its two companions.
03 The full list, with lifetimes
Every name the site or its tags can set. Lifetimes are the maximum; clearing your browser removes them sooner. The platforms can rename their cookies without notice; when they do, this table is corrected.
| Name | Set by | Purpose | Lasts | Category |
|---|---|---|---|---|
| site_consent_v2 | This site (local storage) | Holds your Allow or Decline answer | 6 months | Necessary |
| chat token | This site (local storage) | Reconnects you to your own support chat thread | Until cleared; thread kept 12 months | Necessary |
| _ga | Tells one visit from another for page counts | 2 years | Analytics | |
| _ga_* | Keeps the state of a visit session | 2 years | Analytics | |
| _gcl_au | Google Ads | Links an inquiry back to the ad click | 90 days | Advertising |
| _gcl_aw | Google Ads | Stores the gclid from the landing link | 90 days | Advertising |
| _uetsid | Microsoft Advertising | Session ID for conversion tracking | 1 day | Advertising |
| _uetvid | Microsoft Advertising | Visitor ID for conversion tracking | 13 months | Advertising |
| _uetmsclkid | Microsoft Advertising | Stores the msclkid from the landing link | 90 days | Advertising |
| MUID | Microsoft | Identifies the browser to Microsoft ad services | 13 months | Advertising |
| _fbp | Meta | Browser ID for Meta ad measurement | 90 days | Advertising |
| _fbc | Meta | Stores the fbclid from the landing link | 90 days | Advertising |
No cookie holds your name, your phone number or the contents of your drawing. Those go to the server through the form and nowhere else.
04 The ads that bring people here
The shop pays for clicks. Google Ads and Microsoft Advertising send traffic here today, and Meta Ads does where a campaign runs there. Each platform tacks an identifier onto the link you click:
gclidon a click from Google Adsmsclkidon a click from Microsoft Advertisingfbclidon a click from Meta Ads
The identifier is in the address bar before our page has loaded a single byte, so we can't stop it arriving. What we control is whether it gets saved. After Decline, it isn't written to any cookie and no conversion is reported. After Allow, the platform's tag stores it in the cookies listed above and reports back if you send an inquiry. The report says a conversion happened. It carries no form field.
05 Consent Mode v2 starts at denied
Google's tags here run in Consent Mode v2. The default is written into the page before any Google script loads, and it looks like this:
| Signal | Default | After Allow | After Decline or withdrawal |
|---|---|---|---|
| ad_storage | denied | granted | denied |
| ad_user_data | denied | granted | denied |
| ad_personalization | denied | granted | denied |
| analytics_storage | denied | granted | denied |
The update to granted happens only when you press Allow. Press Decline, or change your mind later, and all four go straight back to denied. While they are denied Google may receive a cookieless ping: a page was loaded, from roughly where, with no identifier set. The Microsoft UET tag and the Meta pixel don't load at all until you allow storage. A Global Privacy Control signal from your browser keeps everything at denied without asking.
06 Saying yes, saying no, changing your mind
On your first visit a bar sits along the bottom of the page with three buttons: Allow, Decline and Settings. It doesn't cover the page and you can read the site with it still open. Nothing optional runs while you ignore it.
To change your answer later, use Cookie settings in the footer of any page. It reopens the same bar. You can also press the button below. Your new answer takes effect on the spot and is saved under site_consent_v2 for six months, after which we ask again.
Clearing your browser's site data for duhadawaytool.us also resets it. The platform cookies already set can be deleted the same way; withdrawing consent stops new ones and stops reporting, but a cookie already sitting in your browser stays there until it expires or you clear it.
07 What still works if you decline
Everything that matters for getting a job quoted. The inquiry form sends. The fit check gives its verdict. The chat opens and keeps your thread. Every page loads the same.
What stops: no analytics cookie, no ad cookie, no conversion reported to Google, Microsoft or Meta. The shop loses track of which ad brought you, which is our problem, not yours. You may still see our ads elsewhere, because declining here doesn't reach the platforms' own settings; those are controlled in your Google, Microsoft or Meta account.
08 The platforms' own rules
Once a platform receives a signal, its own policy governs what it does next. Read them at the source:
- Google: policies.google.com/privacy, and how Google uses data from sites like this at policies.google.com/technologies/partner-sites
- Microsoft: privacy.microsoft.com/privacystatement
- Meta: facebook.com/privacy/policy
09 Asking about one cookie
If a name shows up in your browser that isn't in the table, tell us which one and on which page. Email [email protected], call +1 (302) 366-0113, or write to Duhadawaytool, 1 801 DAWSON DR, NEWARK, DE 19713, United States. For a copy or deletion of your data, the data request page is quicker.