Ronevexa runs paid ads to this site, and this page says exactly what that stores on your device.

Effective date

This cookie policy took effect on September 24, 2026. It covers every cookie, local storage key and click identifier that ronevexa.com sets or reads, on the homepage, on every trade page, on the Scope Builder and on the inquiry forms. If Ronevexa changes what it stores, this page is republished with a new date before the change goes live, not after.

The three categories in use

Strictly necessary. Keeps the site working: the mobile navigation drawer state, the support chat token, and the record of your storage choice itself. These run without asking, because the site cannot function without them.

Analytics. Counts visits, pages viewed and which trade pages a paid click lands on, so Ronevexa can tell whether an ad is sending people to a page that actually answers their question. Held denied until you allow storage.

Advertising. Attaches a click identifier to your visit so Google Ads, Microsoft Advertising or Meta Ads can tell that an ad click led to an inquiry. Also held denied until you allow storage, and reset to denied the moment you decline.

Cookies and storage keys, one by one

The Google and Microsoft rows only write to your device once you allow storage. The Meta row only applies while a Meta campaign is actually running.

Advertising platforms and their click identifiers

Paid clicks from Google Ads arrive at ronevexa.com carrying a gclid parameter. Clicks from Microsoft Advertising carry an msclkid parameter. Where a Meta Ads campaign is running, clicks carry an fbclid parameter. Each identifier lets the sending platform match a click to whatever happens next on this site, such as an inquiry form submitted through teto9b7.php. None of the three identifiers is used to build a profile of you beyond that one campaign's performance.

Consent Mode v2

This site runs Google's consent mode, which governs four signals: ad_storage, ad_user_data, ad_personalization and analytics_storage. All four load denied by default, on every first visit, before you have made a choice. If you allow storage in the banner, all four are set to granted for that browser. If you decline, or if you had granted earlier and change your mind, all four are set back to denied immediately. Denied still lets a click identifier travel with the link for that single click, but the platform receives it without the storage that would otherwise tie it to a returning visit.

Giving, changing or withdrawing your choice

A banner offers Allow storage or Decline the first time you land on any page of ronevexa.com. Your answer is written to site_consent_v2 in your browser and applied before any analytics or advertising storage runs. If your browser sends the Global Privacy Control signal, Ronevexa treats that as a decline automatically and does not ask again.

To change your mind later, open the Storage choices button in the footer of any page. It reopens the same banner so you can switch between Allow storage and Decline at any time, and the new choice takes effect immediately.

What happens if you decline

The site itself does not change. Every trade page, the Scope Builder, the inquiry forms and the support chat work exactly the same whether you allow storage or not, because none of them require analytics or advertising cookies to function. What stops is measurement: Google Ads and Microsoft Advertising stop receiving the signals that would tie your visit to a later inquiry, analytics stops counting your session, and no advertising cookie is written to your browser. Strictly necessary storage, such as the consent record itself and an open chat token, is unaffected either way.

The platforms' own policies

Each advertising and analytics platform handles the data it receives under its own published terms, not under Ronevexa's control once the data reaches them. Google's practices are described at policies.google.com. Microsoft Advertising's handling of msclkid and related data is described in the Microsoft privacy statement at privacy.microsoft.com. Meta's handling of fbclid-linked data is described in Meta's own data policy. Nothing on this page or elsewhere on ronevexa.com states that any of these platforms has reviewed or approved this site.

Questions about a specific cookie

Ask about any row in the table above and Ronevexa will tell you plainly what it does and why it is there. For a request to see or delete what Ronevexa itself holds about you, use the data request page rather than this one.