Cookies & consent
No ad cookie is written on this site until you press Allow.
Austin Roofing Company buys clicks from Google, Microsoft and Meta, and those platforms want cookies. This page lists every one of them, every storage key our own code writes, and every consent signal we send, as a ledger: one row per clause, what it means, why it is there.
Ledger A. Scope and date
2 clauses| Clause | In plain words | Why it applies |
|---|---|---|
| A.1Effective date2026-10-02 | This cookie notice takes effect on October 2, 2026. | So you can tell which version you agreed to. When the list below changes, the date changes and the banner asks again. |
| A.2Whose siteaustinroofingcompany.de | Austinroofingcompany, trading at austinroofingcompany.de, 12430 Metric Blvd, Austin, Texas 78758, United States. | The roofing contractor in Austin, Texas that runs the ads and reads the enquiries is the one answerable for the cookies. The full picture of what we keep is in the privacy notice. |
Ledger B. The three categories
3 clauses| Category | What it does | Why it applies |
|---|---|---|
| B.1Strictly necessaryAlways on | Remembers your cookie choice and keeps your chat thread open between visits. Written by our own code, read by our own code. | Without them the banner would ask on every page and the chat would forget you mid-conversation about a leak. No tracking, no ad use. |
| B.2AnalyticsOff until allowed | Counts visits and which pages people read before calling, under the analytics_storage signal. |
Tells us whether anyone reads the storm damage section or whether it needs rewriting. Never written before you allow it. |
| B.3AdvertisingOff until allowed | Lets Google Ads, Microsoft Advertising and Meta Ads link a sent estimate form back to the ad you clicked. | We pay per click. Conversion data is how we stop paying for searches that bring nobody with a roof in Austin. |
Ledger C. Every cookie and storage key
10 entries| Name and setter | What it is for | How long it lasts |
|---|---|---|
| C.1 · Necessarysite_consent_v2Set by: this site, browser storage | Stores Allow or Decline and the time you chose. | 12 months, then the banner asks again |
| C.2 · NecessaryChat tokenSet by: this site, browser storage | A random token that reconnects you to your chat thread. Written only after you start a chat. | Until you clear browser storage; the transcript itself is kept 12 months on our side |
| C.3 · Advertising_gcl_auSet by: Google Ads | Ties ad clicks to conversions on this site. | 90 days |
| C.4 · Advertising_gcl_awSet by: Google Ads | Holds the gclid of the ad click that brought you here. | 90 days |
| C.5 · Analytics_ga and _ga_ with the property IDSet by: Google | Separates one visitor from another for visit counts. | Up to 2 years |
| C.6 · Advertising_uetsidSet by: Microsoft Advertising | Groups the pages of one visit for conversion tracking. | 1 day |
| C.7 · Advertising_uetvidSet by: Microsoft Advertising | Recognises a returning browser across visits. | 13 months |
| C.8 · Advertising_uetmsclkidSet by: Microsoft Advertising | Holds the msclkid of the ad click. | 90 days |
| C.9 · Advertising_fbpSet by: Meta Ads | Identifies the browser for Meta ad delivery and measurement. | 90 days |
| C.10 · Advertising_fbcSet by: Meta Ads | Holds the fbclid of the ad click. | 90 days |
Rows C.3 to C.10 belong to the platforms, not to us. Their names and lifetimes are the ones the platforms publish today; if a platform renames one, this ledger follows. None of them exists in your browser before you press Allow, and our server never reads them.
Ledger D. Ad platforms and click identifiers
3 clauses| Platform | What it attaches | Why it applies |
|---|---|---|
| D.1Google Adsgclid | Adds gclid to the link when you click one of our search ads, for example a search for roof repair in Austin, TX. |
Google Ads sends traffic here today. Google Ireland Ltd and Google LLC also receive the four consent signals. |
| D.2Microsoft Advertisingmsclkid | Adds msclkid to clicks from Bing and its partner sites. |
Microsoft Advertising sends traffic here today, through Microsoft Ireland Operations Ltd. |
| D.3Meta Adsfbclid | Adds fbclid to clicks from Facebook and Instagram. |
Meta Ads sends traffic here when a campaign runs there, through Meta Platforms Ireland Ltd. |
A click identifier sits in the address bar whether you allow cookies or not; the platform put it there before you arrived. What your choice decides is whether a tag on this page may store it and report a conversion. Decline, and it is never written down. No platform has reviewed or approved this site; we are a customer buying clicks.
Ledger E. Consent Mode v2 signals
4 signals| Signal | What it controls | State before you choose |
|---|---|---|
| E.1ad_storageConsent mode v2 | Whether advertising cookies such as _gcl_au may be written. | Denied |
| E.2ad_user_dataConsent mode v2 | Whether data about you may be sent to Google for advertising. | Denied |
| E.3ad_personalizationConsent mode v2 | Whether your visit may be used to personalise ads, including remarketing. | Denied |
| E.4analytics_storageConsent mode v2 | Whether analytics cookies such as _ga may be written. | Denied |
The four signals load as denied before any tag runs. Allow sets all four to Granted. Decline, or withdrawing later, sets them straight back to denied. If your browser sends Global Privacy Control, they stay denied and the banner does not pester you. The Microsoft and Meta tags obey the same choice.
Ledger F. Giving, changing and withdrawing consent
3 clauses| Clause | In plain words | Why it applies |
|---|---|---|
| F.1How you give it | The bar at the bottom of the screen on your first visit: Allow, Decline or Settings. It never covers the page; you can read and send the form without touching it. | Consent has to be an action you take. Scrolling and staying on the page are not consent here. |
| F.2Where you change it | The Cookie settings button in the footer of every page, or the two buttons below on this page. | Taking consent back must be as easy as giving it. One click, same place every time. |
| F.3What withdrawal doessite_consent_v2 | Sets the four signals back to denied, stops the tags writing anything new, and updates the stored choice. Platform cookies already set can be cleared in your browser settings. | We cannot reach into a cookie Google or Microsoft owns, but we can stop feeding it. |
Your choice on this browser
Change it here
Until you choose, the default is denied for ad_storage, ad_user_data, ad_personalization and analytics_storage.
Ledger G. If you decline
2 clauses| Clause | Still works | Stops |
|---|---|---|
| G.1The whole site | Every page, the estimate form, the phone links, the chat, the roof diagram. Your enquiry reaches us exactly the same and gets the same callback. | Nothing you can see. |
| G.2Behind the scenes | site_consent_v2 records the decline so we do not ask again for 12 months. | Google, Microsoft and Meta cookies, conversion reporting, remarketing and visit counting. We lose the data on which ad worked. That is our problem, not yours. |
Ledger H. The platforms' own rules
3 links| Platform | Their document | Why read it |
|---|---|---|
| H.1Google | policies.google.com/privacy and policies.google.com/technologies/ads | How Google uses ad and analytics cookies once they exist, and how to adjust your Google ad settings. |
| H.2Microsoft | privacy.microsoft.com/privacystatement | How Microsoft Advertising handles the msclkid and UET cookies. |
| H.3Meta | facebook.com/privacy/policy | How Meta uses the fbclid and its pixel cookies. |
Asking about a specific cookie
Name the row, we answer.
Quote the ledger number, C.7 for instance, and email [email protected] or call 512-952-7454. Post goes to 12430 Metric Blvd, Austin, Texas 78758. Requests to see or delete what we hold are handled under the data request process and answered within 10 days.
Here about a roof rather than a cookie? The roofing services page shows how each job is priced, and the free estimate form gets someone up the ladder.