Cookies and consent ledger

Dates and periods that govern this notice

This notice took effect on October 6, 2026 and replaces anything published here before that date. It applies to ve-bex.click and to nothing else; the meeting client, the admin console and the API have their own contract with the workspace that bought them. If a row changes, the date above changes with it, and the previous wording stops applying from the moment the new page is published.

6 months how long your allow or decline choice is kept in the browser under site_consent_v2

30 days how long server and access logs are kept before deletion

24 months how long an inquiry and its email copy stay in the database

7 days the window we answer a cookie or data question in

Two things are true at once and people find them contradictory. Nothing on this site is sold, so there is no account, no password and no card. And this site still runs paid advertising, so there are tags here that measure which click led to an inquiry. The ledger below is how both facts are reconciled, row by row.

The three categories in use

Categories, in the order they load
Clause	What it means	Why it applies
C-01Strictly necessary	Storage the page cannot work without: your consent choice itself, the support chat token that lets you reopen a conversation, and the short-lived values that keep an inquiry form from being submitted twice. First-party only. No tag from anyone else sits in this category.	You cannot switch these off and still have the page behave. We keep the category as small as two keys on purpose, so declining advertising storage costs you nothing you would notice.Always on
C-02Analytics	Aggregate measurement of which pages a visit touched and whether it ended in an inquiry. We look at it to find out which module page in the catalogue is doing the work and which one nobody reads to the bottom.	Loaded only after you press Allow. Until then `analytics_storage` is denied and the tag writes nothing to your browser.Consent first
C-03Advertising	Conversion measurement for Google Ads, Microsoft Advertising and Meta Ads. It answers one question: did the click that was paid for turn into an inquiry for a video conferencing platform for business, or not.	Paid clicks reach this site every working day. Without this category we are bidding blind. It still stays denied until you allow it, and it goes back to denied the moment you withdraw.Consent first

There is no fourth category. Nothing here personalises the page you are reading, nothing changes the copy based on who you are, and no tag on this site follows you into the meeting client. The product has its own rule about this and it is short: we do not score who looked away from the camera. That feature does not exist here and will not.

Every cookie and storage key, named

Four of these only exist after you press Allow. If you decline, or never answer, the only entries in your browser from this site are the consent record and, if you open the support chat, the chat token.

Cookies and browser storage set by ve-bex.click
Name	Set by and purpose	Lifetime
Necessarysite_consent_v2	Vebex, first party, stored in the browser's local storage. Holds one word: whether you allowed or declined storage, and when. It is what stops the bar from asking you again on the next page.	6 months, then the bar asks once more. Clearing site data removes it immediately.
Necessaryvebex_chat_token	Vebex, first party, local storage. Written only when you open the support chat and send a message. It is the key that reconnects you to the same conversation after a reload, so a support specialist is not reading half a thread.	Up to 12 months, matching how long the transcript is kept. Closing the widget does not delete it; clearing site data does.
Advertising_gcl_au	Google, through the Google Ads conversion tag. Links the click that carried a `gclid` to an inquiry submitted later in the same browser.	90 days. Not written at all while `ad_storage` is denied.
Advertising_uetsid and _uetvid	Microsoft, through the Microsoft Advertising tag. The pair identifies a session and a returning browser so a `msclkid` click can be matched to a conversion.	_uetsid lasts one day, _uetvid up to 390 days. Neither is written while advertising storage is denied.
Advertising_fbp	Meta, through the Meta pixel, where a campaign is running there. Ties a `fbclid` click to an inquiry.	90 days. Written only after consent, and only while a Meta campaign is live.
Analytics_ga and _ga_<id>	Google, through the analytics tag. Counts a visit, the pages in it and whether it reached the inquiry form. We read it at the level of a page, never a person.	Up to 24 months from the last visit, and only from the moment `analytics_storage` is granted.
Not a cookieopened	A hidden field in the inquiry form holding the unix time the page rendered. It never leaves the form and is not stored in your browser. It exists because a form filled in under two seconds is a bot, not a buyer.	Lives as long as the open tab. Discarded once the inquiry is stored.

A visitor makes a consent choice on a laptop browser — The bar sits at the bottom of the content column. It does not cover the page, and the page works with it ignored.

Advertising platforms and the click identifiers they attach

Google Ads, Microsoft Advertising and Meta Ads send traffic to this site. Each of them attaches a parameter to the link before the browser ever reaches us, and that parameter arrives in the address bar whether or not any tag is allowed to load.

Who sends the click and what rides along with it
Platform	Identifier and what it does	Why it applies
A-01Google Ads	Google Ireland Ltd and Google LLC. A paid click arrives carrying `gclid` in the URL. With advertising storage allowed, the conversion tag reports back that this click reached an inquiry; the consent signals go to Google with every measurement call.	Most of the search traffic for terms like online meeting software and video meeting software with dial-in comes through Google Ads. Without the identifier we cannot tell a working keyword from a wasted one.
A-02Microsoft Advertising	Microsoft Ireland Operations Ltd. A click from Bing carries `msclkid`. The Microsoft tag matches it to an inquiry only after you allow storage. Microsoft's own handling of what it receives is covered by its privacy statement.	A meaningful share of buyers researching secure video conferencing for companies arrive from Bing on a work machine.
A-03Meta Ads	Meta Platforms Ireland Ltd. Where a campaign runs there, the click carries `fbclid` and the pixel reports the same single event: an inquiry was sent.	Campaigns on Meta run in bursts rather than continuously. The pixel is present on the page and stays denied until consent, running or not.
A-04The identifier in the inquiry record	The inquiry form carries a `source` field. If you arrived on a paid click, the identifier in the address bar can end up in that field and is stored with the inquiry for 24 months, the same period as the rest of the record.	It is how a proposal written on a Tuesday is traced back to the campaign that paid for it. No platform has reviewed or approved this site, and nothing here claims otherwise.

Consent Mode v2 and its four signals

This site runs consent mode in its second version. Before you answer the bar, all four signals are set to denied and the Google and Microsoft tags behave accordingly: they may count an anonymous ping, they do not write storage, and they do not build a profile from your visit.

The four signals and their default state
Signal	What it controls	State
S-01ad_storage	Whether an advertising cookie may be written or read in your browser at all.	Denied on arrival. Granted when you press Allow. Set back to denied the instant you decline or withdraw.
S-02ad_user_data	Whether data connected to your visit may be sent to the advertising platform for measurement.	Denied on arrival, granted on Allow, denied again on Decline or withdrawal.
S-03ad_personalization	Whether your visit may feed audience building and personalised advertising.	Denied on arrival, granted on Allow, denied again on Decline or withdrawal.
S-04analytics_storage	Whether the analytics tag may keep a visit identifier in your browser.	Denied on arrival, granted on Allow, denied again on Decline or withdrawal.
S-05Global Privacy Control	The `Sec-GPC` header some browsers and extensions send on every request.	Treated as an opt-out from sale and sharing, honoured without asking you again. The four signals stay denied for that visit.

One consequence worth saying out loud: when consent is denied, conversion counts in the advertising accounts are modelled rather than measured. That is a cost we carry, not a reason to pre-tick a box for you.

How you give consent, and where to change it

The choice, step by step
Clause	What it means	Why it applies
U-01Giving it	A slim bar appears at the bottom of the content column on your first visit with two buttons, Allow and Decline, both the same size. Pressing Allow grants the four signals and lets the analytics and advertising tags load.	Consent has to be an act. Scrolling is not an act, and neither is ignoring a bar, so neither counts here.
U-02Changing it	Every page of this site carries a Cookie settings button in the footer legal row. Press it, the bar comes back, and the new answer replaces the old one immediately.	Withdrawing has to be as easy as giving. Two clicks from the bottom of any page is the whole procedure.
U-03Withdrawing entirely	Clearing site data in your browser deletes `site_consent_v2`, the chat token and every advertising cookie listed above. The next visit starts from denied with nothing remembered.	Nothing on this site reconstructs a cleared choice from the server side. There is no shadow copy.
U-04What the record holds	The consent record is the answer and its timestamp, kept for 6 months. It is not tied to a name, because this site has no accounts to tie it to.	We have to be able to show that a choice was made and when. That is the whole reason it persists.

If you decline

What still works, and what stops
Clause	What it means	Why it applies
R-01The site keeps working	Every page, the full catalogue, the deployment configurator and the inquiry form behave exactly as they do for someone who allowed storage. No feature is held back, no page is blurred, and the bar does not come back on the next click.	A cookie wall would be a worse experience than the product we are selling. We do not run one.
R-02The configurator still saves nothing	The configurator calculates bandwidth, storage and licence tier in your browser and writes the result into the inquiry's `spec` field only when you choose to send it. Declining changes none of that.	The arithmetic never needed a cookie. Nothing about it is stored between visits either way.
R-03Measurement stops	No analytics cookie is written, no advertising cookie is written, and the Google, Microsoft and Meta tags receive denied for all four signals. Conversions from your visit are not matched to a click.	That is the entire practical effect of declining, and it falls on us rather than on you.
R-04Server logs continue	The host that serves this page records the request: IP address, user-agent and referring URL. Those logs are kept 30 days and are not consent-based, because a server that cannot log cannot be defended.	Security and abuse handling. They are never fed to an advertising platform.

The platforms' own documents

Once a measurement call leaves this site, the receiving company becomes responsible for what it does with it. Read their terms rather than ours for that part.

Microsoft Advertising: privacy.microsoft.com/privacystatement covers what Microsoft Ireland Operations Ltd does with a msclkid click and the tag data behind it.
Google Ads and analytics: policies.google.com/privacy covers Google Ireland Ltd and Google LLC, including the consent signals we send and the gclid match.
Meta Ads: Meta privacy policy covers Meta Platforms Ireland Ltd and the fbclid identifier where a campaign is running.
Infrastructure: The hosting provider that serves this site also stores the inquiry database; the mail provider carries the notification to [email protected]. Neither receives advertising data and neither is given access for any other purpose.

Ask about one specific cookie

Email [email protected]

Phone +1 (925) 555-2231

Post Ve Bex, 167 Mill Street, Office 12, Austin, Texas 31098, United States

Name the cookie in the subject line and we will answer which category it sits in, who set it and how long it lasts, within 7 days. If the answer is that we got a row on this page wrong, the page is corrected and the effective date at the top moves.

To ask for a copy of what the inquiry database holds about you, or to have it deleted, use the data request page instead. It has the form and the timelines. The privacy notice covers the legal bases, the recipients and the retention periods in full, and the terms of service cover what this site is and is not.

One more thing people ask about and it belongs here: the support chat at the corner of the screen posts to our own server, not to a third-party widget service. The transcript is kept 12 months and the token in your browser is what reconnects you to it.

Request your data

Every cookie we set is listed on this page.