Cookie Policy

1. What cookies are

A cookie is a small text file that a website asks your browser to store and send back on later visits. It lets a site recognise a returning browser without knowing who is using it.

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.

A cookie holds text, not code: it runs nothing, opens nothing on your disk, and delivers no malware. All it establishes is that the same browser has been here.

2. How we use cookies

Only a handful of cookies operate on ynvesero.world. Without the first group the pages themselves misbehave; the second group sits idle until permission arrives.

Consent is not inferred from scrolling or from continued browsing. Until you make a choice, optional cookies are not set.

A refusal costs you nothing in content. The text, the navigation and the forms behave identically in both cases.

3. Categories of cookie we use

Strictly necessary. Three jobs fall to this group: keeping a visit continuous from one page to the next, holding the answer already given to the cookie notice, and letting the server reject requests forged elsewhere. They are set on the basis of legitimate interest and cannot be turned off within the site.

Functional. Where you have told the site how you would like it to appear, that instruction is kept here rather than being asked for a second time. They are optional.

Analytics. The questions answered here take the form of how many and in what order. Which particular person read which article forms no part of the report we receive. Consent comes first; measurement follows it, or does not happen at all.

Marketing. The purpose of this category, when it is populated at all, is attribution of a campaign. Nothing in it starts without an explicit instruction from the visitor.

4. Cookies set by third parties

Embedded services can set their own cookies. Those are governed by the provider's policy in addition to ours.

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

The consent screen lists external cookies in advance rather than reporting them once they are already on the device.

5. How long cookies last

Cookies fall into two groups by lifespan:

• Session cookies disappear the moment the browser is shut, leaving nothing behind for the next visit.
• Persistent cookies stay on the device until an expiry date passes, which is what lets a setting outlive a visit.

Nothing is given a year when a week suffices. The single entry allowed to sit for longer is the answer you gave the notice, which loses its value the moment it expires.

6. Cookies and personal data

Even without a name attached, an identifier that distinguishes one visitor from another counts as personal data, and we handle it accordingly.

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.

7. 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:

• block all cookies, or block only third-party cookies
• remove cookies that are already stored, one at a time or all together
• be prompted before any cookie is set
• clear cookies automatically each time the browser closes

The menu is usually labelled privacy, sometimes security. A total block is your right to exercise, but it also removes what the pages need, and much of the web stops responding properly.

8. Records of consent

An answer given in the banner leaves a short entry: which categories were accepted, and when. Without that record we could neither respect the choice nor demonstrate that it was given.

Beyond the categories chosen and the time of choosing, the entry holds nothing. There is no field in it for a name and none for an email address.

Delete the site's stored data and the entry goes too. The banner returns on your next visit, since nothing is left to say what you decided.

9. Do Not Track and global signals

Certain browsers and extensions attach an opt-out signal to outgoing traffic. The mechanism arrived without an agreed rule for the receiving end, so treatment is uneven.

The practice these headers exist to prevent does not take place here, which leaves the signal with nothing to alter.

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.

A consent that is awkward to refuse is not consent, so the two answers are presented alike: same prominence, same number of clicks, no second dialogue for the visitor who declines.

Permission ages. We ask again after a while instead of relying on an answer given under conditions that may no longer hold.

11. Cookies on phones and tablets

The size of the device makes no difference to any of this. What is written here holds whether the page arrives on a monitor or in your hand.

Where the switches live does change. Apple keeps Safari's privacy controls among the device settings, while on Android they stay inside whichever browser you are using.

Because the record sits with the browser, the same person using two of them will be asked twice, and a second device counts as a first visit however familiar the site may be.

12. Turning cookies off in your browser

The controls below sit in the browser itself, so they apply to every site you open and not only to this one. Menu names shift between versions; the path is usually close to what is written here.

• 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. Open the settings, then the page for cookies and site permissions, which covers both blocking and the removal of what is already stored.

Private or incognito windows are a blunter version of the same idea: cookies set inside one are discarded when the last such window closes.

13. 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.

What does change is small and entirely to do with memory. Preferences you set by hand are forgotten between visits, so a language or display choice has to be made again on arrival.

Blocking the necessary group along with the rest means the banner cannot remember being answered, so it appears afresh on every visit. That is the mechanism working, not failing.

14. How the stored items are protected

A cookie is not simply text: it comes with flags that restrict its use, and those flags are set deliberately here instead of being ignored.

• Secure means an unencrypted request leaves the cookie behind rather than carrying it into the open.
• HttpOnly puts the cookie out of reach of scripts running on the page, which is the usual route by which such values are stolen.
• SameSite stops the cookie from being attached to requests that originate on other sites, which is what makes cross-site request forgery difficult.

These attributes reduce exposure; they do not create a vault. What goes into a cookie on this site is a session marker or a preference, never a credential.

15. Changes to this policy

Any addition or removal on the technical side shows up in this document, which is dated on the day it is edited.

If a revision introduces optional cookies that were not covered before, your previous permission is not stretched to fit them and the banner returns.

16. 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.

Ynvesero
538 Old Club Road
522438 Guntur
India
[email protected]
+91 863 9067642