Cookie ledger
Two storage keys are the studio's own. Everything for ads waits for your Allow.
This is the full list of cookies and browser storage on the Vorngix brand studio site, set out as a ledger: the clause, what it means in plain words, and why it applies. If a key is not in this ledger, this site does not write it.
October 6, 2026
Part A
Three categories, and only one of them runs without asking
The first row works the moment the page loads. The other two stay switched off until you press Allow on the banner.
| Clause | What it means | Why it applies |
|---|---|---|
| A.1Strictly necessary | Browser storage that remembers your cookie choice and keeps a chat thread open between pages. No cookie in this group identifies you to anyone outside the studio. | Without it the banner would reappear on every page and the chat would forget you mid-sentence. These run on legitimate interest and need no consent. |
| A.2Analytics | The Google tag counts visits and which pages lead to an inquiry. It stores a random visitor number, not a name. | Tells us whether the websites page or the estimator is doing its job. Off until you allow it; controlled by the analytics_storage signal. |
| A.3Advertising | Tags from Google Ads, Microsoft Advertising and Meta store the click identifier from a paid ad and report back when that click ends in an inquiry. | We pay for clicks and want to know which ones were worth it. Off until you allow it; controlled by ad_storage and its two companion signals. |
Part B
Every key, who writes it and how long it stays
Durations are the maximum. Clearing your browser removes all of them at once.
| Name | Set by and purpose | Lasts |
|---|---|---|
B.1 · necessaryConsent recordsite_consent_v2 |
Vorngix, in local storage. Holds Allow or Decline and the date you chose. The only thing on this site that persists a choice. | 12 months, then the banner asks again |
B.2 · necessaryChat tokenvorngix_chat |
Vorngix, in local storage, only after you start a chat. Holds the conversation token and the number of the last reply you have seen, so you can return to the same thread. | Until you clear it; the transcript behind it is deleted after 6 months |
B.3 · analyticsGoogle visitor id_ga _ga_* |
Google LLC, through the Google tag. Distinguishes one visitor from another and groups page views into a visit. | Up to 2 years |
B.4 · advertisingGoogle Ads conversion linker_gcl_au _gcl_aw |
Google LLC. Stores the gclid from a Google Ads click so an inquiry can be matched to the ad. | 90 days |
B.5 · advertisingMicrosoft UET_uetsid _uetvid _uetmsclkid |
Microsoft, through the Universal Event Tracking tag. Stores the msclkid and a visit id for Microsoft Advertising conversions. | 1 day for the session id, up to 13 months for the others |
B.6 · advertisingMeta pixel_fbp _fbc |
Meta Platforms. Stores a browser id and the fbclid from a Facebook or Instagram ad click. | 90 days |
Part C
Paid clicks arrive carrying an identifier
This site receives traffic from paid campaigns now. Each platform tags its own links.
| Platform | What it attaches | What we do with it |
|---|---|---|
| C.1Google Ads | gclid on the link from a search or display ad. |
Kept in _gcl_aw and reported back only after Allow. |
| C.2Microsoft Advertising | msclkid on the link from Bing and partner ads. |
Kept in _uetmsclkid and reported back only after Allow. |
| C.3Meta Ads | fbclid on the link from Facebook or Instagram, where a campaign runs. |
Kept in _fbc and reported back only after Allow. |
Part D
Consent Mode v2 starts every signal at denied
The default is set in the first script on every page, before any tag can load. Allow flips all four to granted. Decline or withdrawal sets them straight back to denied.
| Signal | What it controls | Default here |
|---|---|---|
D.1ad_storage |
Whether advertising cookies such as _gcl_aw may be written. | Denied until Allow |
D.2ad_user_data |
Whether data about you may be sent to Google for advertising. | Denied until Allow |
D.3ad_personalization |
Whether that data may be used to show you personalised ads elsewhere. | Denied until Allow |
D.4analytics_storage |
Whether analytics cookies such as _ga may be written. | Denied until Allow |
Giving and taking back consent
The banner at the foot of the page has two buttons of equal size: Decline and Allow. It does not cover the page and you can read the whole site without touching it. Your choice is written to site_consent_v2 and the consent mode signals update on the same click.
To change your mind, press here, or the same button in the footer of any page. The banner returns with both options. If your browser sends a Global Privacy Control signal, we treat it as Decline and do not show the question.
What still works if you decline
Everything you would use. The estimator, the inquiry form, the chat, the portfolio and every page load exactly as before. Your inquiry reaches us the same way.
What stops: no analytics or advertising cookie is written, click identifiers stay in the address bar and are never stored or reported, and the platforms receive only the cookieless denied pings consent mode sends, which carry no identifier. We lose the ability to tell which ad brought you. That is a fair trade and we do not nag about it.
The platforms' own documents
Each platform runs its own cookies under its own rules. Read them at the source:
Asking about one cookie
Found a key in your browser that is not in this ledger, or want to know exactly what one held? Write to [email protected] with the name of the key, or call +1 (448) 555-0161. Post reaches us at 83 River Road, Office 12, Austin, Texas 02757. For a copy or deletion of what we hold, the data request form is quicker.