This page names every storage key this site writes, which advertising platform reads it, and when each one clears.

Why this gets its own page

A site running paid traffic from three ad platforms at once has more storage keys in play than a typical business-card site, and folding all of it into the general privacy policy would bury the detail that actually matters to someone deciding whether to click "Allow storage." This page is that detail, on its own, with nothing else mixed in.

It sits alongside, not instead of, the privacy policy, which covers what we do with the data you type into a form, and the terms of service, which covers the work itself.

Storage that runs the site and cannot be switched off

Two categories of storage load no matter what you choose in the banner, because the site would not function correctly without them. Consent Mode v2 labels these functionality_storage and security_storage, and both stay set to granted at all times. In practice that covers the banner remembering that it already asked you, the chat widget keeping its conversation token so a page refresh does not start a new conversation from scratch, and the browser session used to prevent duplicate form submissions.

None of this is used for advertising. If it were, it would be gated behind the same consent switch as everything else on this page.

Storage tied to advertising and analytics

Google Ads, Microsoft Advertising and Meta Ads can each set cookies in your browser once you allow storage, used to measure whether the ad you clicked led to a visit, a call or a form submission. That measurement is what a business running paid search and social campaigns needs to know whether the spend is working; it is not used to build a profile of you for resale, and we have no access to sell even if we wanted to — each platform holds its own measurement data on its own servers, under its own account controls.

Until you allow storage, ad_storage, ad_user_data and ad_personalization all stay denied, which means none of those platforms can write a durable cookie tied to your visit, and none of them receive user-identifying signals from this site. The fourth signal, analytics_storage, follows the same default because we do not separate advertising measurement from general analytics on this site; there is one signal for both, one switch, and one answer either way.

Click identifiers carried in the URL

Click a Google ad and the link you land on carries a gclid parameter, or occasionally wbraid or gbraid for device-based conversion tracking. Microsoft Advertising attaches msclkid. Meta attaches fbclid. These arrive in the address bar the moment the page loads, regardless of your consent choice, because the ad platform put them there before your browser ever reached this site.

What happens next depends entirely on the banner. Decline, or do nothing, and the identifier sits in the URL, unread beyond a basic check for its presence, and is discarded when you navigate away. Allow storage, and the identifier is copied into your browser's session storage under the key lsg.click and attached to the hidden source field of any inquiry form you submit during that session, so the office can see that a given lead came from a specific Google, Microsoft or Meta campaign rather than from a phone book search. Session storage clears itself the moment you close the browser tab.

Every storage key in use, in one table

This is the complete list. Nothing on this site writes browser storage that is not named below.

Consent Mode v2 in practice

On first load, before any script runs, four Consent Mode v2 signals are pushed as denied: ad_storage, ad_user_data, ad_personalization and analytics_storage. Google Ads and Microsoft Advertising both honour this signal directly through their own tag libraries; the Meta pixel is treated the same way on this site even though Meta's own consent framework differs slightly, so that no platform is treated more leniently than another by accident.

Tap "Allow storage" and all four flip to granted in the same instant, the ad and analytics tags begin writing cookies, and the URL-based click identifiers described above start getting captured. Tap "Decline," or let a Global Privacy Control signal from your browser decide for you, and all four are set to denied — not just left alone, but actively reset, even if a previous visit had them granted.

Changing your choice later

The "Cookie preferences" link sits in the legal row of the footer on every page of this site, not just this one. Click it and the same banner reopens with the same two buttons, and whatever you pick overwrites the previous choice immediately. There is no separate settings screen to dig through and no confirmation email required.

Clearing your browser's site data for larksprucelean.com has the same effect as declining: every key listed in the table above disappears, and the banner will ask again on your next visit.

Third-party notices

Each advertising platform publishes its own account of what it collects and how long it keeps it, and those notices are the authoritative source for anything happening on that platform's own servers, not this page. Microsoft's is published as the Microsoft Privacy Statement. Google publishes its practices for ad cookies at Google's advertising technology page. Meta's data policy covers the pixel referenced above.

None of these three companies has reviewed, certified or approved this website or the way it is built. Their role here is limited to reading the click identifiers and storage keys described on this page once you allow storage.

Questions about this notice

Write to office@larksprucelean.com or call +1 (897) 555-6004. For anything about how your personal data is used beyond storage mechanics, see the privacy policy, which also covers the accessibility statement and the data-request process.