Cookie policy
Nothing that tracks an ad click is stored until you press Allow.
This is the full list of what the Knox Roofing site keeps in your browser, who reads it, and how long it stays. We run paid ads to find people who need a roof inspection in Dallas, so the ad side is written out here plainly rather than buried.
Effective October 1, 2026 · Last updated October 1, 2026
- Consent keysite_consent_v2
- Choice kept6 months
- Default stateAll ad signals denied
- GPC headerHonored as opt-out
Section 01
Effective date and what this covers
This cookie policy took effect on October 1, 2026, and that is also the date it was last updated. It covers knoxroofingpros.org and nothing else: every page, the inquiry form that posts to our server, and the support chat in the bottom corner.
The site is run by Knoxroofingpros, trading as Knox Roofing, from 9659 Wendell Rd, Dallas, Texas 75243, United States. What we do with the details you type into a form is in the privacy policy. This page is narrower. It is about what sits in your browser.
A cookie is a small text file a site asks your browser to keep. Local storage does the same job without being sent back to the server on every request. We treat both the same way here, because to you they behave the same: something stays on your device after you leave the page.
Section 02
The three categories we use
Strictly necessary
Two things. The record of your cookie choice, so the banner does not ask you again on every page. And the chat token, so a conversation you started with the office is still there when you come back after lunch. Neither one identifies you to anybody outside Knox Roofing. Neither one is used for ads. These run without asking, because without them the banner and the chat would not work.
Analytics
Counts of visits and which pages get read. We use this to find out whether people looking for a roof inspection in Dallas reach the contact page or give up on the roofing page halfway down. Analytics storage is off until you press Allow. Consent Mode reports it as analytics_storage.
Advertising
We pay Google Ads, Microsoft Advertising and Meta Ads to show our listing to people searching for a Dallas roofing contractor. When you allow storage, cookies from those platforms record that a click on one of our ads led to an inquiry. That is how we know which ad paid for itself and which one we should stop paying for. Advertising storage is off until you press Allow.
Section 03
Every cookie and storage key, by name
If a name is not in this table, this site does not set it. The ad and analytics rows are only written after you press Allow. The table scrolls sideways inside its own box on a phone.
| Name | Set by | Category | What it is for | How long |
|---|---|---|---|---|
site_consent_v2 |
Knox Roofing | Strictly necessary | Holds your Allow or Decline answer so the banner stays closed and the right Consent Mode signals load on each page. | 6 months, then you are asked again |
| Chat token | Knox Roofing | Strictly necessary | A random token in local storage that links your browser to your support chat so you can return to the conversation. | Until you clear site data; the transcript on our server is kept 18 months |
_gcl_au |
Google Ads | Advertising | Links a Google Ads click, carried in by gclid, to an inquiry sent from this site. |
90 days |
_ga, _ga_* |
Analytics | Tells one visit from another so page counts are not doubled. | Up to 2 years | |
_uetsid |
Microsoft Advertising | Advertising | Session record for Microsoft's tag, tied to the msclkid on the landing URL. |
1 day |
_uetvid |
Microsoft Advertising | Advertising | Recognizes a returning browser so a conversion is credited to the right Microsoft ad. | 13 months |
_fbp, _fbc |
Meta | Advertising | Records a visit from a Meta ad and the fbclid it carried, where a Meta campaign is running. |
90 days |
Lifetimes for the platform cookies are the ones Google, Microsoft and Meta set. They can change them. When they do, we update this table.
Section 04
Ad platforms and the click identifiers they attach
Paid clicks reach this site today from three places. Each one adds its own tag to the end of the web address when you click an ad.
- Google Ads
gclid, a click ID from Google Ireland Ltd and Google LLC. Google Ads also receives the Consent Mode signals described in the next section.- Microsoft
msclkid, from Microsoft Ireland Operations Ltd for Microsoft Advertising, which also places our ads on Bing.- Meta
fbclid, from Meta Platforms Ireland Ltd for Meta Ads, on clicks from Facebook or Instagram where a campaign runs there.
The ID arrives in the address bar whether or not you have made a choice, because the platform puts it there before you reach us. What changes with your choice is whether we keep it. With storage allowed, the ID is written into the matching cookie in the table above, and an inquiry sent later counts as a conversion for that ad. With storage declined, nothing is written, and the ID is gone the moment you move to another page.
The click ID is a string of characters. It does not carry your name, your phone number or your street address, and we do not send those to any ad platform.
Section 05
How Consent Mode v2 behaves on this site
Google's consent mode is a set of switches that tell its tags what they are allowed to do. Version 2 has four that matter here, and on this site every one starts at denied before any page content loads:
ad_storagecontrols whether advertising cookies can be written.ad_user_datacontrols whether data about you can be sent to Google for advertising.ad_personalizationcontrols whether that data can be used to show you ads later.analytics_storagecontrols whether analytics cookies can be written.
Press Allow and all four are set to granted, the choice is saved under site_consent_v2, and the advertising and analytics rows in the table can be written. Press Decline, or withdraw an earlier yes, and all four are set back to denied on the spot. They stay denied on every page after that.
If your browser sends the Global Privacy Control signal, the Sec-GPC header, we read it as a decline and do not ask. The four signals stay denied and the banner does not show.
With the signals denied, Google's tags can still send a cookieless ping saying that a page loaded. That ping carries no advertising cookie and no identifier from storage. Microsoft and Meta tags do not load at all until you allow.
Section 06
Giving consent, and changing it later
The first time you land here, a strip opens along the bottom of the screen. It does not cover the page and you can read every page with it open. It has two buttons of the same size. Allow turns storage on. Decline keeps it off. Ignoring the strip is the same as Decline.
To change your mind, use the Cookie settings link in the bottom row of every page footer, next to Privacy and Terms. It opens the same strip with the same two buttons. Pick the other one and the change applies from that moment. You can also use the button below.
Clearing this site's data in your browser settings removes site_consent_v2 and the chat token together, and the strip will ask again on your next visit. Cookies already set by Google, Microsoft or Meta under their own domains are removed through your browser or through their ad settings pages.
Your choice is kept for 6 months. After that we ask once more, because a yes given half a year ago is not much of a yes.
Section 07
What still works if you decline
Everything you came for. Every page reads the same. The inquiry form on the contact page sends, the phone number dials, the support chat opens and keeps your thread. Nobody at the office can tell from your inquiry whether you allowed cookies or not, and it makes no difference to how fast somebody calls you back about the roof.
What stops: no advertising cookie is written, no analytics cookie is written, the Microsoft and Meta tags are not loaded, and a click ID in the address bar is not kept. The cost lands on us, not you. We lose the ability to tell which ad brought your inquiry in.
The two strictly necessary items still run. One remembers that you said no. Without it, the banner would ask on every page, which would be its own kind of nuisance.
Section 08
The platforms' own privacy documents
Once a cookie is set under a platform's domain, that platform's own rules govern what it does with it. Their documents, in full:
- Google, for Google Ads and analytics: policies.google.com/privacy, and how Google uses data from partner sites: policies.google.com/technologies/partner-sites
- Microsoft, for Microsoft Advertising: privacy.microsoft.com/privacystatement
- Meta, for Meta Ads: facebook.com/privacy/policy
We do not write those policies and we cannot change them. If a platform's practice bothers you, the cleanest fix is the Decline button here, and the ad settings inside your Google, Microsoft or Meta account.
Section 09
Asking about a specific cookie
Found something in your browser from knoxroofingpros.org that is not in the table? Tell us the name and the page you were on. Email [email protected], call 214-646-6625, or write to Knox Roofing, 9659 Wendell Rd, Dallas, Texas 75243, United States.
Requests to see or delete what we hold about you go through the data request route in the privacy policy. We answer those within 14 days. The rules for using the site itself are in the terms of use.
And if you came here looking for a Dallas roofing contractor rather than a cookie list, the residential roofing and commercial and sheet metal pages are where the actual work is.