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.

Documents on your disk are out of a cookie's reach, and nothing inside one can infect them; it records only that this browser has been in touch before.

2. How we use cookies

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

A visitor who ignores the notice has, in practice, refused. The optional categories stay dormant until a positive choice is recorded.

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. 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. The preference panel lists this group without a switch beside it. What they run on is legitimate interest, not permission.

Functional. Anything adjusted by hand — the interface language, a chosen view — is written down here so that the adjustment survives until you come back. This category can be refused.

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. They are optional and are only set with consent.

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

We set the shortest lifespan that still serves the purpose. A record of your cookie choice is kept long enough that you are not asked repeatedly, which would be its own kind of nuisance.

5. Cookies set by third parties

Some cookies may be set by services we embed rather than by us directly. Where that happens, the provider is also responsible for what it stores.

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.

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.

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.

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

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

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

The relevant setting is usually under privacy or security in your browser's preferences. Blocking strictly necessary cookies will stop parts of most sites from working, including this one.

8. Records of consent

Your decision is stored together with its date. That record is what allows us to honour the decision and to show it was made freely.

Stored alongside the choice is a timestamp and nothing more — no name, no address, nothing that reaches beyond the browser holding it.

If you clear site data, the record goes with it and you will be asked once more — not out of persistence, but because the answer is genuinely gone.

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.

The cookies in use are the necessary ones and, with consent, analytics; an opt-out signal finds none of the kind it was designed against.

10. Why you are asked at all

The law draws its line at necessity: what the page cannot work without may be stored, and everything else waits to be asked for. The banner exists to put that question.

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.

The record of your choice expires. When it does, the banner reappears rather than assuming that what you thought once you still think.

11. Seeing what is stored at this moment

Nothing here needs to be believed on our word: the stored items can be inspected one by one, with their names, values and expiry dates visible.

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.

The plainer route is the padlock or information icon beside the address, which in most browsers opens a summary of what the current site has set and offers to clear it.

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. 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. Open the settings, then the privacy and security panel, where the enhanced tracking protection and the block for cookies and stored site data both live.
• 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.

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

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 hides the value from JavaScript altogether, closing the most common path to reading it from the page.
• 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 loss is continuity, not access. Anything you configured is configured again next time, because nothing was kept to remind the page of it.

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.

The privacy policy takes the broader subject: what personal data exists, on what lawful basis it is handled, who else sees it and what rights you hold over it.

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

A change to the cookies in use is followed by a change here, with a new date printed at the bottom.

As soon as optional cookies of a new kind are switched on, we put the question again instead of treating the earlier answer as covering them.

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.

Yalithist
1553 Raha Lane
713325 Āsansol
India
[email protected]
+91 341 1027382