One key is kept by default. Every ad cookie waits for your yes.

Effective date and version

Version 1.0 of this policy took effect on September 28, 2026. It was last updated on the same day. When a cookie is added, removed or its lifetime changes, the version number goes up and the date above changes with it. Nothing gets added quietly.

The controller is Lunivexa, trading at lunivexa.us, 73 Workshop Way, Büro 5, Austin, Texas 51576, United States. The wider picture of what we hold about you, and for how long, sits in the privacy policy. This page covers only what lives in your browser.

The categories we use

A cookie is a small text file a site asks your browser to keep. Local storage does the same job without being sent back to the server on every request. We treat both the same way, and both are listed in the table below.

• Strictly necessary. The key that remembers your cookie choice, and the chat token that lets you come back to a conversation with the desk. The site works without the chat token; it simply forgets the thread. These run without asking, because asking you about your answer would loop forever.
• Analytics. Counting visits and which medicine cards get read. Held off until you allow storage. Controlled by the analytics_storage signal.
• Advertising. Cookies from Google Ads, Microsoft Advertising and Meta that record which paid click brought you here, so the platform can tell us a campaign produced an inquiry. Held off until you allow storage.

There are no preference cookies, no account cookies and no payment cookies. There is no account to log into and nothing to pay for on this site.

Every cookie and key, by name

Lifetimes are the maximum. Clearing your browser removes all of them sooner. Anything marked "after Allow" is never written if you decline.

Paid clicks and the IDs they carry

This site receives paid traffic today. Google Ads, Microsoft Advertising and Meta Ads send visitors here from search results and feeds. When you arrive from one of those ads, the platform adds an identifier to the address in your browser bar:

• gclid from Google Ads, run by Google Ireland Ltd and Google LLC.
• msclkid from Microsoft Advertising, run by Microsoft Ireland Operations Ltd.
• fbclid from Meta Ads, run by Meta Platforms Ireland Ltd, where a campaign runs there.

The identifier is in the link whether or not you accept cookies. That part is the platform's doing, not ours. What we control is whether it gets written to a cookie and reported back as a conversion. Without your Allow, it stays in the address bar and goes nowhere.

We tell platforms that an inquiry happened. We do not send them what you wrote, which medicine card you asked about, or your name. A question about zolpidem is not an ad signal.

Consent Mode v2, set to denied first

Google Consent Mode v2 is a set of four signals the page sends before any Google tag is allowed to store anything. Before the page draws a single pixel, our code sets all four to denied:

• ad_storage, which covers ad cookies such as _gcl_aw.
• ad_user_data, which covers sending data about you to Google for advertising.
• ad_personalization, which covers using your visit for remarketing.
• analytics_storage, which covers analytics cookies such as _ga.

When you press Allow, all four switch to granted. When you press Decline, or withdraw an earlier Allow, all four go back to denied at once, on that page, without a reload. Under consent mode denied, Google tags may send cookieless pings with no identifier; they do not read or write the cookies in the table.

A browser that sends the Global Privacy Control signal (the Sec-GPC header) is treated as a Decline. We do not ask again.

Giving consent, changing it, taking it back

On your first visit a strip appears at the bottom of the screen with two buttons of equal size: Decline and Allow. It does not cover the page. You can read every medicine card with it still open, and ignoring it counts as no.

To change your mind later, use the Cookie settings button in the footer of any page, or the button at the foot of this document. It brings the strip back. Your new choice replaces the old one in site_consent_v2 straight away.

Clearing site data in your browser also resets it. You will see the strip again on the next page.

What happens when you decline

Everything a reader needs keeps working. The five medicine families on the medicines page, the safety rules, the inquiry form and the support chat all run on Decline. The desk answers a question the same way whichever button you pressed.

What stops: no analytics cookie, no ad cookie, no remarketing list. The platforms cannot link your visit to their ad click, so our reports undercount. That is our problem, not yours.

One key is still written: site_consent_v2, holding the word Decline, so the strip does not reappear on every page. It is kept 12 months.

The platforms' own policies

Each ad platform decides what it does with data once it has it. Read theirs directly:

• Google: policies.google.com/privacy and, for how Google uses data from sites like this one, policies.google.com/technologies/partner-sites.
• Microsoft: the Microsoft privacy statement at privacy.microsoft.com/privacystatement.
• Meta: facebook.com/privacy/policy.

Each platform also offers its own ad settings where you can switch off personalised ads across every site, not just this one.

Asking about a specific cookie

Name the cookie from the table and write to [email protected], call +1 (530) 555-0805, or post to Lunivexa, 73 Workshop Way, Büro 5, Austin, Texas 51576, United States. A data request is answered within 10 days. The route for access and deletion is set out under data requests in the privacy policy, and the rules for using this site are in the terms of use.