Cookie Policy

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.

Storage areas inside the browser and single-pixel images serve the purpose described above, so this document treats them no differently, whatever heading they happen to appear under.

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

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

Reading further down a page tells us nothing about your wishes, so it is not read as approval. The switch stays off until you move it.

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. This group carries a visit across pages, keeps a note of the decision made at the banner, and helps the server tell a genuine request from one manufactured on another site. There is no consent step for this group, and no switch that disables it; the lawful basis is legitimate interest.

Functional. These retain small choices such as language or layout so that the site does not forget them between visits. Nothing here is compulsory.

Analytics. What this group produces is a table of numbers about pages. It shows that an article goes unread without saying anything about the people who skipped it. Consent comes first; measurement follows it, or does not happen at all.

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. Cookies set by third parties

Not every cookie on a page comes from the owner of the site. Anything an embedded component writes falls under that component's own terms as well as this document.

Every widget added to a page introduces an organisation the visitor never selected, which is the reason our pages carry so few of them.

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

5. How long cookies last

There are two lifespans in use here, and every cookie has one or the other:

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

Expiry dates are chosen against the job the cookie does, and no further. The exception is the note of your own decision, which has to outlast the visit or the banner would return every morning.

6. Managing your preferences

Nothing about a first answer binds you to it; taking permission back costs no more effort than granting it did.

Separately from anything offered here, the browser itself can:

• block the whole lot, or reject outside storage while leaving a site's own cookies alone
• empty the existing store, whole or in part, at any moment
• have the browser ask first rather than decide on its own
• clear what has accumulated at the end of every session

You will find these controls under privacy or security in browser settings. Blocking essential cookies breaks functionality on most websites, this one included.

7. Cookies and personal data

A cookie identifier is personal data when it can single out a browser, even if we never learn a name behind it. We treat identifiers on that basis rather than arguing about the label.

A request to see, to delete or to object therefore covers what a cookie recorded, and not merely the fields of a contact form.

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. Nothing else tells the site how to behave next, or shows a regulator that a decision took place.

What is written is the setting and the moment it was set. No contact details are attached; the note describes a browser rather than a person.

The note lives in the browser, so a browser that is wiped keeps no note. The question comes round again, the earlier answer having been removed by you rather than disregarded by us.

9. Do Not Track and global signals

Certain browsers and extensions attach an opt-out signal to outgoing traffic. Practice on honouring it varies because no single standard governs 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

Storing anything on your device that is not strictly needed to deliver the page requires permission first. That rule is what produces the banner, and it is why the necessary category has no switch beside it.

We treat the choice as genuine, which has a practical consequence in the design: saying no takes one action, exactly as saying yes does.

Nothing here is settled permanently: the stored answer runs out in time and the question is put afresh.

11. Cookies on phones and tablets

This policy does not have a separate mobile edition, because there is nothing separate to say — the same cookies behave the same way.

Only the route differs: an iPhone puts Safari's cookie options with the rest of the phone's settings, whereas Android browsers hold theirs internally, as they do on a computer.

Decisions are stored per browser rather than per person, so refusing here in one application leaves the question unanswered in the next, and switching device starts the matter afresh.

12. Turning cookies off in your browser

Each browser keeps its own cookie settings, and a change made there covers the whole web rather than a single address. Version to version the wording moves about, so treat these routes as approximate.

• Chrome. The settings hold a privacy and security section; cookies from other domains are governed there, and the permissions for one particular site 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. 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. The page for cookies and site permissions in the settings does two jobs: it blocks new cookies and clears those already on the machine.

A private window achieves something similar without any configuration — whatever is stored during the session goes when the window does.

13. How the stored items are protected

Alongside its value, each cookie carries instructions about how it may travel. Those instructions are configured, not inherited.

• Secure keeps the cookie off any connection that is not encrypted, so it is never sent in clear text across the network.
• 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 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.

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.

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.

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

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

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

Where a change means new optional cookies, your previous permission is not stretched to fit them and the banner returns.

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.

Xugararn
1990 Darga Road
585105 Kalaburagi
India
[email protected]
+91 8472 891736