Cookie and browser storage protocol governs active telemetry signals
This notice details the mechanical storage keys, session markers, advertising click tags, and analytical beacons operated across brickpowerwashing.us. Our website functions as an active commercial dispatch channel running live marketing traffic across Northeast Ohio. We document every client-side storage mechanism without ambiguity.
1. Effective Date and Operational Revision Cycle
This Cookie Notice took effect on October 17, 2026. Architectural exterior cleaning operations demand absolute transparency in commercial billing, on-site safety assessments, and browser-level telemetry tracking. When regulatory authorities or platform API specifications update technical transmission requirements, this specification record is amended immediately with revision marks published on this page.
All stored tokens, telemetry logs, and tracking states generated through browsing sessions across Orrville and Wayne County are maintained in compliance with this scheduled specification until retired or superseded.
2. Functional Classification of Storage Mechanisms
We do not group browser data into vague generalities. Browser storage mechanisms on brickpowerwashing.us are categorized strictly into three distinct technical divisions based on operational necessity and transmission criteria:
Strictly Necessary Technical Storage: Essential client-side keys required to maintain core site reliability, form security tokens, user interface preferences, dispatch chat session tokens, and the consent register itself. These mechanisms cannot be turned off because the inquiry dispatch system and anti-abuse honeypots cannot execute without them.
Diagnostic and Aggregated Analytics Storage: Measurement scripts that log technical performance factors, render timings, script latency, viewport dimensions, referral URL origins, and form submission completion ratios. Analytical pings are strictly pseudonymized and cannot be used to isolate an individual without supplemental commercial records.
Commercial Advertising and Click Attribution Storage: Direct tracking parameters and marketing cookies that log campaign responses, measure conversion completion against paid cost-per-click traffic, prevent redundant ad displays, and pass campaign attribution markers back to ad network processors.
3. Exhaustive Storage and Cookie Inventory Ledger
The following registry itemizes every cookie, web storage key, and session marker currently deployed across brickpowerwashing.us:
| Storage Key | Issuing Entity | Classification | Purpose and Operation | Lifespan |
|---|---|---|---|---|
| site_consent_v2 | brickpowerwashing.us | Strictly Necessary | Persists the user's voluntary acceptance or declination of advertising and analytics telemetry across sessions. | 12 months |
| dispatch_chat_token | brickpowerwashing.us | Strictly Necessary | Maintains bidirectional polling token between visitor browser and wojace0.php dispatch desk. | 18 months |
| _gcl_au | Google LLC | Advertising | Stores ad click experiment data and measures conversion efficiency for paid traffic campaigns. | 90 days |
| _gcl_aw | Google LLC | Advertising | Transmits Google Ads conversion tracking markers associated with paid search queries. | 90 days |
| _ga | Google LLC | Analytics | Assigns a pseudo-random identifier to calculate visitor, session, and dispatch interaction volume. | 14 months |
| _ga_* | Google LLC | Analytics | Preserves page view flow and session sequence state across consecutive site navigations. | 14 months |
| _uetsid | Microsoft Advertising | Advertising | Logs live session state for Microsoft Bing Ads Universal Event Tracking conversion counters. | 24 hours |
| _uetvid | Microsoft Advertising | Advertising | Identifies returning visitors referred through Microsoft Advertising network placements. | 13 months |
| _fbp | Meta Platforms | Advertising | Captures ad conversion events and audience attribution when paid campaigns run on Meta. | 90 days |
4. Live Advertising Networks and Click Identifier Strings
This website is a direct commercial marketing destination that actively receives paid advertising traffic today. We run paid campaigns across major advertising platforms to connect residential homeowners, historic property stewards, and commercial facility managers in Orrville, Wooster, and Wayne County with Ivan Petrov's masonry washing operations.
When you click an advertisement sponsored by Brick Power Washing on google ads (Google Ads), Microsoft Advertising, or Meta Ads, advertising networks automatically attach distinctive cryptographic click identifiers to the landing page URL query string. Specifically:
Google Ads: Paid search placements and local campaign listings managed through google ads append the parameter verbatim as gclid (Google Click Identifier). When a visitor submits a quote request or launches a dispatch dialogue, this parameter allows Google Ads systems to correlate the inquiry with the exact commercial keyword query and auction cost. Telemetry data is transmitted directly to Google LLC and Google Ireland Ltd.
Microsoft Advertising: Ads appearing on Bing search, MSN, and partner networks append the click parameter verbatim as msclkid (Microsoft Click Identifier) to track conversion paths to our Wayne County dispatch desk. Telemetry is processed by Microsoft Ireland Operations Ltd and Microsoft Corporation.
Meta Ads: Campaign placements on Facebook and Instagram append the parameter verbatim as fbclid (Meta Click Identifier) to verify lead generation and measure contractor service awareness. Telemetry is processed by Meta Platforms Ireland Ltd and Meta Platforms, Inc.
Our web hosting provider serves site infrastructure and database records, while our authenticated mail transport provider delivers notifications to [email protected]. These click strings are processed solely to verify marketing performance, prevent click fraud, and calculate accurate customer acquisition costs across our masonry washing operations.
5. Consent Mode v2 Signal Architecture and Default Denied States
We enforce Google consent mode v2 as our governing telemetry framework. In accordance with platform privacy mandates, our scripts set all sensitive tracking states to strictly denied before any tracking code, external beacon, or measurement container evaluates.
Prior to receiving explicit affirmative consent from the site visitor, our runtime container establishes the following four signals verbatim in a denied configuration:
Only after a visitor clicks "Accept Storage" in the docked consent banner are these signals updated dynamically to "granted". If a visitor subsequently declines or modifies their preference, all four parameters revert to "denied" instantly.
6. Mechanisms for Setting, Modifying, and Withdrawing Consent
Upon your first arrival at brickpowerwashing.us, a compact docked banner presents two explicit choices: "Decline" or "Accept Storage". We do not utilize pre-ticked checkboxes, forced click-through barriers, or manipulative button styling.
Your selection is written to client storage under the key site_consent_v2. This token is retained for a maximum duration of 12 months, after which you will be prompted again to re-confirm your storage preferences.
You retain the perpetual right to modify, adjust, or withdraw your consent at any time. To reopen your preference controller, simply click the dedicated button labeled Consent Preferences located in the bottom footer row of every page, or activate the preference modal through the link below:
Furthermore, if your browser transmits an automated Global Privacy Control (Sec-GPC) header signal, our system interprets this header as a binding affirmative instruction to decline optional advertising and telemetry storage without displaying any prompt, in compliance with California (CCPA/CPRA) and applicable US state privacy laws.
7. Operational Impacts and Functional Guarantees on Refusal
Declining advertising and analytical cookies will never restrict your access to Brick Power Washing's services, pricing records, technical datasheets, or customer support channels. We do not operate cookie walls or degrade site readability for visitors who opt out.
What remains fully operational when you decline:
You can browse all directory indexes, read our mortar safety preservation guides, inspect equipment pump manifests, calculate estimates with the interactive Option Configurator, transmit inquiries to kobu404.php, and engage directly with Ivan Petrov via the live dispatch desk widget.
What stops functioning when you decline:
Advertising cookies from Google Ads, Microsoft Advertising, and Meta Ads are blocked completely. Telemetry scripts are prevented from logging cross-session analytics, conversion tracking attribution is withheld, and your device cannot be included in any prospective remarketing lists.
8. Governing Platform Privacy Frameworks and External Policies
Third-party ad networks and technology vendors process data according to their own independent governance standards and international security frameworks. We advise customers to inspect the official privacy disclosures of our advertising partners:
For information regarding Microsoft Advertising telemetry, Bing network data collection, and opt-out controls, consult the Microsoft Privacy Statement published at privacy.microsoft.com.
For information detailing Google Ads, tag manager containers, and Consent Mode data handling protocols, inspect the Google Privacy & Terms repository available at policies.google.com.
For information regarding Meta Platforms marketing services and audience measurement, consult the Meta Privacy Policy at facebook.com/privacy/policy.
Nothing in this notice implies that Google, Microsoft, Meta, or any regulatory body has reviewed, certified, or endorsed our specific website implementation.
9. Dispatch Controller and Telemetry Inquiries
For specific questions regarding the deployment of cookies, local storage records, telemetry tokens, or to request manual deletion of session identifiers linked to your submitted quote requests, contact our designated privacy controller: