Cookie Policy
Last updated: 05-02-2026 | Ynuroivo
1. What cookies are
When a page opens, the server can hand your browser a short piece of text to keep and return next time round. That is a cookie, and what it identifies is the browser rather than the person at the keyboard.
Related technologies do the same job by other means — local storage, session storage and pixels among them. Where this policy says “cookies” it covers those too.
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
Ynuroivo uses cookies sparingly. Some are needed for ynuroivo.world to function at all; the rest are optional and wait for your consent.
A visitor who ignores the notice has, in practice, refused. The optional categories stay dormant until a positive choice is recorded.
Whether the answer given is yes or no, the site that loads is the same one; a refusal removes no page and closes no route to us.
3. Categories of cookie we use
Strictly necessary. One cookie here stops a visit from breaking when you move to the next page. Another holds the answer you already gave the notice. A third lets the server see whether a request really came from you. They are set on the basis of legitimate interest and cannot be turned off within the site.
Functional. Anything adjusted by hand — the interface language, a chosen view — is written down here so that the adjustment survives until you come back. They are optional.
Analytics. These count visits and record which pages are read, in aggregate. They tell us that a page is unpopular; they do not tell us who found it dull. Nothing in this group runs before permission is given.
Marketing. Any cookie of this kind exists to show whether an advertisement led anywhere. The default state is off, and it changes only by a deliberate act on your part.
4. How long cookies last
How long a cookie survives puts it into one of two classes:
- Session cookies are temporary: closing the browser deletes them without any action from you.
- Persistent cookies have a stated lifetime and stay readable until it runs out or you remove them.
Lifespans are set to the minimum that works. The consent record itself is the longest-lived, because re-asking on every visit defeats the point of asking.
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.
The fewer third-party components a page loads, the fewer parties receive data about you. We treat that as a design constraint rather than an afterthought.
The consent screen lists external cookies in advance rather than reporting them once they are already on the device.
6. 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.
A request to see, to delete or to object therefore covers what a cookie recorded, and not merely the fields of a contact form.
The reports we open contain sums and averages. Reconstructing the movements of one visitor would take deliberate effort, and there is no reason to make it.
7. Managing your preferences
An answer given today can be reversed tomorrow, by the same route and in the same number of steps.
Controls exist outside this site as well. In the browser you can:
- turn storage off altogether, or keep a site's own cookies and drop the rest
- inspect the stored list and take out individual entries
- require a prompt before anything is allowed to be written
- arrange for everything to be discarded when the window closes
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.
8. Records of consent
A cookie choice is written down at the moment it is made, with the time attached. That record is what allows us to honour the decision and to show it was made freely.
Two fields make up the entry: the categories you allowed, and the time you allowed them. Neither carries an identity, and the entry means nothing away from the browser it sits in.
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
A browser can be set to announce with each request that the visitor prefers no tracking. The mechanism arrived without an agreed rule for the receiving end, so treatment is uneven.
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. 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, then the privacy and security section, then the entry for third-party cookies; data kept site by site sits under the per-site settings in that same section.
- Firefox. In the settings, the privacy and security panel holds the enhanced tracking protection alongside the controls for cookies and stored site data.
- Safari. Cross-site tracking is switched in the privacy tab of the browser settings, and on a phone the same switches are reached through the device's own settings rather than from inside the browser.
- Edge. Look in the settings for the page on cookies and site permissions; blocking rules and the delete-on-close option are both there.
The incognito mode most browsers offer keeps a separate store and throws it away at the end, which spares you changing any setting at all.
11. Seeing what is stored at this moment
This document describes intent; the browser reports fact. If the two ever disagree, the browser is right, and it is worth knowing how to ask it.
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.
Simpler still, the small icon to the left of the web address usually opens a panel naming what this page has stored, with a button to remove it.
12. 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.
For permission to count it must be freely given, and a refusal buried two screens down is not free. Ours sits beside the acceptance, in the same size.
Nothing here is settled permanently: the stored answer runs out in time and the question is put afresh.
13. How the stored items are protected
There are several switches attached to every cookie which decide how exposed it is. We set them rather than accept whatever the default happens to be.
- 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.
None of this makes a cookie a safe place for anything sensitive, and we do not treat it as one. Passwords, payment details and identity documents are not written to cookies under any circumstances.
14. What a refusal actually changes
A warning that the site may not work properly would be false in our case, so it is not made. Everything readable with cookies on is readable with them off.
One effect is real: convenience. Choices that would have survived until your next visit are lost when the tab closes, and repeat themselves each time.
This produces one small irony: block everything, including the cookie that remembers your refusal, and the banner returns each time, since the refusal itself has nowhere to live.
15. How this notice fits with the privacy policy
This page has a narrow remit — the mechanism of storage — and stops where the wider question of personal data begins.
Everything about personal data more generally — the legal grounds, the recipients, the retention periods, your rights — belongs to the privacy policy rather than here.
Where the two appear to conflict on a point of personal data, the privacy policy governs. This notice is not intended to narrow anything stated there.
16. Changes to this policy
When the list of cookies is altered, this text is brought into line with it and carries the date of that revision.
As soon as optional cookies of a new kind are switched on, consent is asked for again rather than carried over from the old set.
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.
Ynuroivo
1626 North Car Street
627004 Tirunelveli
India
[email protected]
+91 462 3879798