Optional storage needs your permission.
You can read about our website search service or send a company listing inquiry without allowing optional storage. This notice explains the necessary preferences, support connection and advertising signals used on Yondexy.
Last updatedThis notice applies from October 10, 2026.
Effective date and last update: . No amendments are recorded. The notice concerns browser storage and related consent signals on yondexy.com, operated by Yondexy in Austin, Texas, United States.
A cookie is one way a browser keeps information for a website. Local storage is another. The difference matters: deleting cookies alone does not necessarily remove local storage, and deleting either does not erase a message already received by the inquiry server.
For the wider handling of your name and correspondence, read the Privacy statement. This notice deals with what happens in the browser and what your choice tells advertising and analytics systems. It is not a condition of using the website search service inquiry route.
A necessary preference is not advertising consent.
The site distinguishes strictly necessary storage from optional analytics and advertising storage. A visitor's decision about the optional categories does not disable the information pages or the inquiry form.
Strictly necessary
The preference record remembers whether optional storage is allowed or declined. The site stores that choice under site_consent_v2; no other key on this site persists a consent choice. Remembering a refusal is part of respecting it, not a way to turn it into permission.
Starting support chat stores a token in the browser to keep the conversation connected. That token belongs to the support service you requested. It is separate from advertising storage and is not created as an advertising audience identifier. It allows the chat to return to the relevant thread.
Analytics
Analytics storage supports measurement of website use. It is optional. The analytics_storage signal stays denied until storage is allowed and returns to denied when permission is withdrawn. A submitted service inquiry remains a server record even when analytics storage is declined.
Advertising
Advertising storage supports campaign attribution and related advertising functions for traffic from Google Ads, Microsoft Advertising and Meta Ads. It is optional and is governed by the choice and applicable privacy signals. Advertising click parameters arriving in a URL are not themselves proof that a cookie has been written.
Known keys are listed without invented expiry dates.
The table separates the site's confirmed preference key from a support token and incoming advertising parameters. Not every row is a cookie. Platform-generated storage can vary with the tag, campaign and consent state; this notice does not assign a made-up cookie name to that activity.
| Name or record | Who sets or supplies it | Purpose and location | How long it lasts |
|---|---|---|---|
site_consent_v2 | Yondexy | Necessary browser storage recording the consent choice. The only site key that persists this preference. | 12 months for the consent choice record; browser deletion can remove it earlier. |
| Support conversation token | Yondexy support chat | Browser local storage connecting a visitor to the conversation they started. This is a descriptive label, not a published literal key name. | No fixed browser-token expiry is specified. Clearing its storage removes the local connection. Chat transcripts are kept for 12 months. |
gclid | Google Ads | Incoming URL parameter identifying a Google advertising click. It is not itself a cookie. | No cookie expiry applies to a URL parameter. Browser history and copied URLs can retain it; Google's downstream records follow its policy. |
msclkid | Microsoft Advertising | Incoming URL parameter for Microsoft advertising attribution. | Not a cookie with an expiry. A saved URL can keep the value; Microsoft's data handling follows its privacy statement. |
fbclid | Meta Ads | Incoming URL parameter associated with a Meta campaign click. | No local cookie lifetime is inferred from this parameter. Meta's own records follow its privacy information. |
| Optional platform analytics and advertising identifiers | The applicable advertising or analytics platform | Storage permitted only after an allow choice, subject to the consent state and opt-out signals. | Platform-specific. No unobserved key name or expiry is asserted here; use the linked platform information or ask about an observed key. |
A local-storage value does not have the same automatic browser expiry mechanism as an expiring cookie. The 12-month consent record period is the site's retention rule, not a claim that every browser independently deletes the value at that time. Private browsing, storage restrictions or manual deletion can make a preference unavailable sooner.
If a technical or referring URL record contains a click identifier, its retention depends on the record containing it. Server and access logs are retained for 60 days. Inquiries and their email copies are retained for 18 months. These server-side periods are not cookie durations and are not changed by closing a tab.
You can inspect this site's stored values in your browser's site-data settings. Avoid publishing the values themselves: a support token or click identifier can be associated with a conversation or visit. When asking a question, the key name and category are generally a better starting point than its full value.
Paid clicks arrive with source information.
Google Ads, Microsoft Advertising and Meta Ads send traffic to Yondexy. Their links can carry gclid for Google, msclkid for Microsoft and fbclid for Meta. A visitor can therefore arrive with an advertising identifier in the address bar before making a local storage choice.
- Google Ads / gclid
- Google Ireland Ltd / Google LLC provides the advertising service and receives the consent signals used by supporting Google tags.
- Microsoft Advertising / msclkid
- Microsoft Ireland Operations Ltd provides the advertising service. Its privacy statement covers Microsoft's handling of the click information.
- Meta Ads / fbclid
- Meta Platforms Ireland Ltd provides Meta advertising, including identifiers attached where a campaign runs there.
Those identifiers are not described as anonymous. A platform can use an identifier to associate events with an advertising click under its own processing rules. Optional storage is controlled separately from the presence of the parameter in the incoming URL.
Yondexy does not send a name, email address, phone number or message body as advertising-event content. A request for search project support is correspondence with the studio, not permission to use its text for advertising. Keep private information out of links you paste into any form.
Declining storage changes the consent state; it cannot rewrite a link that an advertising platform already generated or remove a URL from another person's copy. Read the refusal section for the practical limits of withdrawing a browser choice.
All four signals begin denied.
Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until the visitor allows storage. Declining or withdrawing sets all four back to denied immediately. This consent mode state is not inferred from scrolling, opening a service page or sending an inquiry.
ad_storageControls advertising-related storage. It remains denied before permission and returns to denied on decline.
ad_user_dataCommunicates permission for sending user data for advertising purposes. An inquiry checkbox does not grant it.
ad_personalizationCommunicates permission for personalized advertising. It is not automatically granted by reading catalogue information.
analytics_storageControls analytics-related storage. The same allow or decline choice governs this optional category.
An allow action grants the optional storage choice to supporting integrations, subject to applicable opt-outs and browser restrictions. A missing or unreadable preference is not an allow action. Optional storage does not precede a visitor's permission.
“Denied” is a consent signal, not a statement that every platform connection has stopped. Supporting tags can handle consent-related or limited measurement requests without optional storage. This notice does not equate a declined cookie choice with the absence of all network traffic to an advertising platform.
Global Privacy Control, including the Sec-GPC header, is honored as an opt-out without asking again. A browser-level opt-out is not treated as permission to personalize advertising. Enable that preference in each browser where you want it to apply.
You can withdraw on this page.
Use “Allow storage” to permit optional advertising and analytics storage. Use “Decline” to refuse it or withdraw an earlier allow choice. The same options appear in the consent banner. Your choice applies to this browser and is stored under site_consent_v2.
Storage choice for this browser
Select either action. Decline resets ad_storage, ad_user_data, ad_personalization and analytics_storage to denied. The necessary preference remains so the site can remember your decision.
Where to change it later
Every page has a “Cookie choices” control in the footer when the preference controls are available. It reopens the banner. You can also return directly to this section through the Cookies link and choose Decline; there is no account sign-in and no service purchase required.
Withdrawal changes future consent handling. It does not reverse processing that lawfully occurred before withdrawal and is not a deletion request for records already received. To request deletion or access, use the data request page.
When a choice appears again
The preference is local to the browser. Clearing site storage, moving to a different device or ending a private browsing session can remove that local record. A new choice prompt after that is not evidence that an earlier inquiry was lost; inquiry records are stored separately.
Reopening the choices does not require you to allow storage. To withdraw, make the explicit Decline choice rather than merely close the browser window. If you want to remove already stored browser data as well, use the browser controls described below.
Declining keeps the service pages available.
You can continue reading about search, indexing, place data and company records. The inquiry form remains available. Starting support chat still uses the necessary conversation token because that token connects the conversation you request, not an advertising profile.
Decline prevents permission for optional advertising and analytics storage and returns the four Consent Mode v2 signals to denied. It does not cancel an inquiry already sent, delete its email copy or remove a chat transcript. The consent preference itself stays available so the site can respect the refusal.
A decline does not guarantee that you will see no advertising elsewhere. It controls this site's consent state, not your entire browser history or an advertising platform's account settings. Incoming advertising URLs can still contain click identifiers.
Removing existing browser data
Open your browser's privacy or site-data settings and look for yondexy.com. Review both cookies and local storage. Removing only cookies can leave the preference or support token in local storage; removing all site data can remove both.
Deleting a support token can prevent that browser from reopening its previous conversation. It does not by itself delete the server transcript. If you need continued support, keep the inquiry reference or contact route available before clearing the browser's connection state.
If storage is blocked entirely
A browser that blocks local storage may not remember an allow or decline choice between visits. That is not permission to assume consent. Some support continuity can also be unavailable. Use the contact form or direct email if a browser setting prevents the chat from staying connected.
A service inquiry's consent checkbox concerns the handling of that message. Leaving advertising storage declined does not make a checked inquiry permission invalid. These choices perform different jobs and are not exchanged for one another.
Each platform explains its own handling.
Yondexy's consent choice communicates the visitor's preference on this site. The advertising providers also publish their own information about collected identifiers, retention and account-level controls. Read the relevant provider's policy when your question concerns data it holds.
Google Ireland Ltd / Google LLC provides Google Ads. Google's privacy policy at policies.google.com explains its processing. Google's cookie information explains categories of technologies used by Google. These documents are separate from the inquiry retention periods published by Yondexy.
Microsoft
Microsoft Ireland Operations Ltd provides Microsoft Advertising. The Microsoft privacy statement at privacy.microsoft.com covers Microsoft's handling of information, including its advertising activities. Use that document for Microsoft-specific privacy choices and explanations.
Meta
Meta Platforms Ireland Ltd provides Meta Ads. Meta's privacy policy describes its processing, and Meta's cookie policy provides information about its storage technologies. A choice in a Meta account is distinct from the local preference on yondexy.com.
These are external sites. Opening a policy link takes you to that provider, where its own notice applies. Linking to a policy does not replace Yondexy's responsibility to honor the consent choice on this site.
Ask about the key you actually see.
Contact Yondexy at [email protected] or +1 (435) 555-4934 with a browser-storage question. Postal contact: 174 Mill Street, Apt 3, Austin, Texas 28536, United States.
Give the key name, the page and whether you had allowed or declined storage. Say whether you found it under cookies, local storage or the page URL. Browser and device information can help reproduce a control problem, but do not send a support token's value or private browsing history.
If your question is about consent not being respected, mention any Global Privacy Control setting. The operator can then distinguish a missing preference, an incoming URL parameter and a stored optional identifier. Those are different issues and need different checks.
For search project support rather than a privacy question, send a service inquiry. For access to or removal of personal information, follow the data request instructions. You can report a keyboard or screen-reader problem with these controls through the accessibility route.
The Privacy statement names the controller and explains rights and recipients. The Terms cover use of the inquiry-only website. No cookie choice creates a service order, checkout or payment obligation.