Optional storage is a separate choice.

Set by: this website in your browser. Purpose: record and apply your analytics and advertising decisions, including a decline. Nothing else on this site persists a consent choice.

Retention: the record of a consent choice is kept for 6 months. You can replace the decision before then through Cookie choices. Clearing browser storage may remove it sooner.

Remembering your choice stops a page change from silently resetting it. This is an essential preference record, not evidence that you agreed to every category.

A record of an allowance is used to apply that allowance; a record of a decline keeps optional storage off.

Set by: this website after you start support chat. Purpose: connect the browser to your conversation when you return. It is saved in local storage where storage is available.

Duration: the token can remain in the browser until removed or invalidated; no fixed browser expiry is specified here. The associated chat transcript is retained for 6 months. A transcript retention period is not a promise about a browser key's expiry.

You requested a support conversation. The token serves that request rather than campaign attribution. On a shared device, another person using the same browser may be able to return to the session.

Closing the chat panel stops the visible interaction. It is not a deletion request for the server-held conversation.

Set by: the relevant advertising platform in a click URL. Purpose: attribute a visit or inquiry to a paid click. An identifier can arrive before you make any storage decision.

Duration: being present in the URL does not establish a cookie lifespan. Optional persistence is subject to advertising consent. Provider retention follows the provider's policy; there is no single expiry period covering every platform.

A URL parameter and a saved browser identifier are not the same thing. Receiving the link is not an allowance to keep the identifier in optional storage.

The site does not carry those identifiers forward in visible internal links or copy them into your inquiry notes.

Set by: the relevant measurement or advertising service under the choices that apply. Purpose: optional visit measurement or campaign attribution, not the delivery of your support message.

Duration: provider-controlled storage and records have provider-specific rules. No unverified cookie name or fixed lifespan is asserted here. Use the policy links below for the providers' handling and ask us about an observed item you cannot identify.

A click parameter identifies the incoming advertising link, not every item a provider stores. If you want to ask about a storage item, send its name and the page where it appears. Do not send its value.

Google Ads attaches gclid to a click. Google Ireland Ltd / Google LLC receives the consent signals and handles permitted Google Ads measurement. The identifier connects a campaign click with later activity where that processing is allowed.

This site receives paid clicks from Google Ads. The identifier can appear on arrival even while all optional consent signals remain denied.

Microsoft Advertising attaches msclkid. Microsoft Ireland Operations Ltd handles the relevant advertising information under its privacy statement. Optional storage for attribution follows the advertising choice made here.

Microsoft Advertising runs traffic to moxbey.com. A Microsoft click is not counted as permission to bypass a stored decline or a recognised browser opt-out.

Meta Ads attaches fbclid. Meta Platforms Ireland Ltd handles Meta advertising information where a campaign runs there. A visit carrying this identifier is subject to the same optional advertising choice.

Meta Ads also sends traffic here. The existence of a campaign does not make advertising storage essential to an inquiry or support session.

Current measurement distinguishes permitted storage from denied-consent handling. A tag can receive a denied consent state, and providers can handle limited signals under their own policies. A declined choice is not represented as a guarantee that no network request or tag exists.

The relevant promise is about the choice being applied, not the absence of advertising. Provider processing is explained in the linked policies and the recipient section.

ad_storage remains denied until you allow advertising storage and use. The advertising control is the relevant switch, not the analytics control or inquiry-consent checkbox.

This signal controls permission for advertising-related storage. Selecting decline or withdrawing an allowance returns it to denied.

ad_user_data remains denied until you allow advertising storage and use. It communicates the choice about advertising user data separately from the physical act of saving a cookie.

An advertising choice is broader than a storage toggle alone. Decline and withdrawal reset this signal along with the other advertising signals.

ad_personalization remains denied until advertising is allowed. It covers advertising personalisation, not the ability to change your requested product areas in the setup builder.

Customising a setup inquiry does not imply permission to personalise ads. This signal returns to denied when you decline or withdraw.

analytics_storage remains denied until you allow analytics. It has its own checkbox, so analytics can be allowed while all advertising signals stay denied.

Separate controls make a partial choice possible. Declining optional storage or withdrawing an allowance returns all four signals to denied; a subsequent saved partial allowance enables only its selected category.

You can read about the workspace, assemble a setup request and submit an inquiry after declining optional storage. Necessary form processing still receives the information you actively submit.

An inquiry needs a reply route and agreement to process that inquiry. It does not need advertising consent. See the inquiry process for the information worth preparing.

Decline or withdrawal returns all four consent signals to denied. Optional analytics storage and advertising storage or use no longer have an allowance from this browser decision. Known optional first-party storage under site control is cleared on withdrawal.

A later refusal is a real change, not merely a hidden banner. It does not rewrite the fact that some processing took place under a previous valid allowance.

You can request support while advertising is declined. Starting chat saves a support token where browser storage is available. The widget checks for new messages every five seconds only while open and stops polling when closed or the page is hidden.

The token supports a service you actively requested. Closing the widget or clearing its token does not erase the transcript. Use the data-request route for records held by the operator.

Website controls cannot promise deletion of a platform's independently retained records. You can use the relevant provider's privacy routes for those records and contact the operator about information held here.

Consent state, browser storage and server-held records are different layers. A button can update consent now without having the power to erase every recipient's history.

Google Ads receives consent signals and handles its advertising measurement. Read the policy at policies.google.com/privacy for Google's purposes and user choices.

The operator's six-month consent-record period is not Google's retention policy. Refer to the provider for its own records.

Microsoft Advertising information is covered by the Microsoft privacy statement at privacy.microsoft.com. The statement explains Microsoft's processing beyond this page's preference controls.

A Microsoft campaign can bring a visitor here with msclkid. The platform's own privacy policy remains relevant to that advertising relationship.

Read Meta's privacy policy for its advertising processing and controls where Meta Ads supplies the visit.

Withdrawing the destination's advertising allowance is not the same action as changing your privacy settings with Meta.