Cookie Policy

1. What cookies are

A cookie is easier to follow as a sequence than as a definition: the site asks the browser to hold a short labelled string, the browser returns it the next time that same site is called, and the page then starts where the last one finished rather than from nothing.

Read every mention of “cookies” below as a wider word than it looks: it takes in storage the browser keeps for a session or for longer, and the invisible images that report that a page has been opened.

Nothing in a cookie can reach into the rest of your machine or infect it. Its only power is to note that this browser has called by already.

2. How we use cookies

We use a small number of cookies on zuvenova.world. The essential ones cannot be switched off; nothing else runs until you allow it.

Carrying on to a second page is not an answer to the question. Nothing beyond the necessary set is written while the banner stands unanswered.

Nothing is withheld from visitors who refuse. Every page reads the same whether the optional categories are on or off.

3. Categories of cookie we use

Strictly necessary. These make the site work: they maintain your session, remember your cookie choice so you are not asked again on every page, and support basic security such as protection against forged requests. There is no consent step for this group, and no switch that disables it; the lawful basis is legitimate interest.

Functional. Anything adjusted by hand — the interface language, a chosen view — is written down here so that the adjustment survives until you come back. Consent governs them.

Analytics. Reading figures come from this group: how often a page was opened, and in what order pages followed one another. Totals are the point; individuals are not. They are optional and are only set with consent.

Marketing. Where used at all, these would support measurement of a campaign. They are optional, off by default, and set only with explicit consent.

4. How long cookies last

Duration divides them in two:

• Session cookies live for the length of one visit and are discarded with the window that held them.
• Persistent cookies carry a fixed expiry, so a choice made today is still in place tomorrow.

Where a shorter period does the work, the shorter period is used. Only the consent record is given real length, since a choice forgotten overnight is barely a choice.

5. Cookies set by third parties

Where a page loads material hosted elsewhere, the host of that material may write its own cookie. Two sets of rules then apply to it, theirs and ours.

Outside code is kept off these pages wherever a plain alternative exists, because inviting it in also invites its owner to watch.

Nothing external is placed silently: the consent panel names the provider first, and only then is the cookie written.

6. Managing your preferences

A choice made once is not permanent. You can revisit it whenever you like.

Whatever a website would prefer, the same decisions can be enforced at browser level, where you may:

• refuse every cookie, or refuse only those arriving from other domains
• delete what has already been stored, either selectively or in one sweep
• ask to be warned whenever a site wants to write something
• wipe the store on exit, without having to remember to do it

Look in the preferences under a heading such as privacy or security. Be aware that a blanket block also removes the necessary category, after which sign-ins and forms fail here and elsewhere.

7. Cookies and personal data

An identifier need not carry a name to be regulated. If it separates one browser from every other browser, we treat it as information about a person.

Nothing about the technical origin of the data narrows your rights over it. What applies to a message you sent us applies equally to an identifier stored in your browser.

Statistics are consulted at the level of the page rather than the person; nobody sits down to follow one browser through a week of visits.

8. Records of consent

When you make a cookie choice we record what you chose and when. Both the handling of your preference and any account of how consent was obtained rest on it.

The entry runs to a choice and a date. Whatever would tie it to you personally is simply absent from it.

Whatever you erase from the browser includes this entry. What comes back afterwards is the original question, put by a site that no longer holds your previous answer.

9. Do Not Track and global signals

A Do Not Track header, or the newer global privacy signal, travels with the request itself. There is no settled standard for how sites must respond to it.

Since we set no advertising or cross-site tracking cookies, the practical effect of such a signal here is limited: there is little for it to switch off.

10. Why you are asked at all

Behind the banner is a simple division. Storage the site genuinely needs is allowed; storage it merely finds useful is not, unless you say so.

Consent has to be a real choice, which means refusing must be as easy as accepting and must cost nothing. Both buttons on our notice carry the same weight, and neither is hidden behind an extra step.

An answer is not kept indefinitely. After a period the question returns, so that a decision made long ago is not treated as a decision made today.

11. Seeing what is stored at this moment

You do not have to take this page on trust. Every modern browser can list what a site has actually stored, and the list is authoritative in a way that a policy document cannot be.

The developer tools carry this information in all four browsers: Application in Chrome and Edge, Storage in Firefox, and in Safari a panel that only shows itself after the Develop menu is turned on in settings.

If the developer tools are more than you want, the icon next to the address bar gives a shorter answer and a single control for deleting what it finds.

12. Turning cookies off in your browser

None of this depends on us: the settings live with the browser and are enforced against every site it loads. Labels are renamed fairly often, so expect a near match rather than an exact one.

• Chrome. Open the settings and look under the privacy and security section, where third-party cookies have their own entry and individual sites are listed under the per-site settings.
• Firefox. The privacy and security panel inside the settings is the relevant one: tracking protection sits at the top of it and cookie storage further down.
• Safari. Open the settings, then the privacy section, for cross-site tracking and stored data; on a phone or tablet the same options sit in the device settings, under the list of apps.
• Edge. The page for cookies and site permissions in the settings does two jobs: it blocks new cookies and clears those already on the machine.

Browsing privately reaches the same end by a shorter route, since the store is emptied as soon as the final private window is shut.

13. How the stored items are protected

Cookies carry attributes that limit what can be done with them, and the ones that matter are set rather than left at their defaults.

• Secure means an unencrypted request leaves the cookie behind rather than carrying it into the open.
• HttpOnly makes the cookie invisible to code running in the browser, so a script injected into a page cannot read it.
• SameSite withholds the cookie when the request comes from somewhere else, and that restriction is what defeats forged cross-site requests.

Even with all three set, a cookie remains the wrong container for confidential material, and nothing of that kind is put into one here.

14. What a refusal actually changes

It is worth being precise about this, because vague warnings are often used to discourage people from declining. Refusing optional cookies removes no page, hides no section and blocks no form on this site.

The difference shows up only in what is remembered. A setting adjusted today will not be waiting tomorrow, and will need adjusting a second time.

If even the record of the decision is refused, the site has no way to know it was made, and asks once more. Nothing is broken when that happens.

15. How this notice fits with the privacy policy

Of the two documents, this is the technical one: it describes what is kept in the browser and for how long.

For the wider picture, including lawful bases and the rights you can exercise, the privacy policy is the document to read.

Should a reading of this page seem to contradict the privacy policy, the privacy policy prevails; nothing written here is meant to cut down its terms.

16. Changes to this policy

This document is revised whenever the underlying set of cookies changes, and re-dated accordingly.

As soon as optional cookies of a new kind are switched on, the old consent stays with the cookies it covered, and a new one is requested.

17. Contact

Questions about this document, or a request concerning your data, can be sent to the address below. We answer written enquiries in the order received and aim to reply within one calendar month.

Zuvenova
1801 Ujjain - Makshi Highway
456010 Ujjain
India
[email protected]
+91 734 5453759