Cookies

Cookie Policy

Last updated: 10-07-2026 | Zelithora

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.

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 cannot read files on your device, and it cannot carry a virus. What it can do is record that a particular browser was here before.

2. How we use cookies

Zelithora uses cookies sparingly. Some are needed for zelithora.world to function at all; the rest are optional and wait for your consent.

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

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. 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. Consent governs them.

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. Should anything appear under this heading, its job is to connect a visit with the advertisement that prompted it. Until you say otherwise, the heading stays empty.

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

Disclosure comes ahead of storage. If an outside cookie is due to be set, it appears in the consent panel while there is still a decision to make.

5. How long cookies last

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

  • Session cookies are erased when you close the browser. They exist only for the visit.
  • Persistent cookies remain for a set period so a preference survives between visits.

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.

6. Cookies and personal data

We do not first establish who is behind an identifier and then decide how to treat it. If the value picks out one device from all the others, it goes under the same rules as a name or an address.

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.

Analytics data is aggregated before it is of any use to us. We look at how many people read a page, not at who they were.

7. Managing your preferences

An answer given today can be reversed tomorrow, by the same route and in the same number of steps.

Separately from anything offered here, the browser itself can:

  • 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 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. Do Not Track and global signals

Certain browsers and extensions attach an opt-out signal to outgoing traffic. Nothing obliges a site to act on one, which is why the same signal is honoured in one place and ignored in another.

As we do not run cross-site tracking, such a signal changes little in our case — the behaviour it targets is already absent.

9. Turning cookies off in your browser

What follows belongs to the browser, not to this site, and takes effect everywhere it goes. Menus are reorganised between releases, so the names may sit a little differently on your screen.

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

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

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

11. Seeing what is stored at this moment

Rather than rely on the description above, you can read the real contents directly — the browser keeps a record and will show it on request.

In Chrome and Edge the developer tools open with F12; the Application panel lists cookies and storage by site. Firefox uses the Storage panel, and Safari exposes the same under its Develop menu once that menu is enabled.

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

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

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.

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.

The loss is continuity, not access. Anything you configured is configured again next time, because nothing was kept to remind the page of it.

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.

14. 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 confines the cookie to requests that begin here, so a form on another domain cannot borrow your session.

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

The page tracks the practice it describes: alter the cookies, and both the wording and the date below are amended.

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.

Zelithora
514 Patna-Gaya Rd
823002 Gaya
India
[email protected]
+91 631 3337315

Questions about this policy?

Contact us at [email protected]

Contact Us