Cookie Policy

This site sets no analytics cookie, no advertising cookie and no third-party tracking script. Most cookie policies open by explaining which cookies a site uses. This one opens by telling you it uses none, because that is the honest answer and it is unusual enough to say first.

This page is about what is stored on your device. What personal information this site collects, and what happens to it afterwards, is a separate question with its own page — see the Privacy Policy.

A cookie is a small piece of text a website asks your browser to store on your device. On a later page, or a later visit, the site can read it back. That is how a site keeps you signed in between pages — and it is also how some sites recognise you again, or follow you somewhere else.

Does this site use cookies?

No. This site sets no analytics cookie, no advertising cookie and no third-party tracking script. Nothing is stored on your device to recognise you on a later visit. There is one exception in the quote flow, and it is a link rather than a cookie — it is explained in full below.

What this site sets on your device, as at the review date below.
Kind	Set here?	What that means
Analytics cookies	No	Visits are counted on the server instead, so there is nothing to write to your browser.
Advertising and retargeting cookies	No	There is no ad pixel, no remarketing tag and no conversion tracker on any page.
Third-party tracking scripts	No	No script belonging to another company loads on any page.
Embedded third-party content	No	No video players, social widgets or chat bubbles that would set cookies of their own.
Other browser storage	No	Local storage and session storage are unused. No page on this site loads a script that writes to them.
Functional or preference cookies	No	None. The one thing this site ever needs to remember about you is carried in a link, not a cookie.

How does this site count visits without a cookie?

On the server. Every web server can see the requests made to it, so the counting happens there rather than in your browser. That is why no cookie is needed: the record is kept at our end, about a request, instead of at your end, about you.

The server records:

The page: Which page was opened, and when.
The referring page: The page you arrived from, when your browser chooses to send it. Browsers often do not.
Campaign tags in the link (UTM parameters): The tags that can be added to the end of a link in an email, a message or a post, so the server can tell which link brought you here. If the link you clicked had none, there is nothing to record.
An identifier for the visit: An identifier the server creates so that one person reading four pages is counted as one visit rather than four. It is not written to your device, and it is of no use to any other website.
A device class: Whether the request came from a phone, a tablet or a desktop browser. This is read from the request itself.

None of that requires storing anything on your device, and none of it can be read by another website. Clearing your cookies will not change what is recorded here, because none of it was ever in a cookie.

What is the token in the quote flow link?

If you start an application and do not finish it, the link you are given carries a signed token so you can pick the application up where you left off. The token travels in the web address, not on your device, and it stops working after 7 days. It points at one part-finished application and nothing else.

This is functional, not tracking. It does not record where else you go, it is not read by anyone else's website, and it does not survive its own expiry. Clearing cookies has no effect on it either way, because it is not a cookie.

One consequence worth being plain about: because the token is part of the address, anyone who opens that link can continue that application. Treat it like a private document and do not forward it. If you think the link has gone to the wrong person, tell us and we will invalidate it.

Because there is nothing to ask you about. A cookie banner exists to get your consent before non-essential cookies are set, and this site sets none. Showing a banner anyway would be asking permission for something that is not happening, which teaches you to click through the ones that matter.

If that ever changes, the banner comes first — before anything is stored — and declining will be a real choice, not a dead button. This is a description of what this website does. It is not a statement about what the law requires of websites generally.

What changes if analytics is switched on later?

The site is built to support analytics with consent, and that support is switched off. It is a single setting, so the honest position is that this could change without the site being rebuilt. If it is ever switched on:

you would be asked before any non-essential cookie was set;
declining would be as easy as accepting, and the site would work the same either way;
this page would be rewritten to say exactly what was being set and by whom, and the review date would change with it.

How do I control cookies in my browser?

Every current browser lets you see the cookies a site has stored, delete them, and block new ones. The controls sit in the browser's own settings, usually under a heading such as privacy, site settings or site data. Most browsers can also be told to clear everything each time you close them.

We have not linked to individual browser help pages here on purpose. Those pages move, and a confident link to a dead page is worse than telling you where to look. Your browser's own help, searched by its name, is the reliable route.

Blocking cookies will not break this site, because nothing here depends on one.

If this changes

This page carries a review date, printed below. If what this site stores on your device ever changes, we update this page before the change goes live rather than after it.

If anything here is unclear, or you think the site is doing something this page does not describe, write to [email protected] or call +91 87968 39997. If our answer does not satisfy you, you can complain, and you never have to come through us to do it. The four steps — us, then the insurer, then IRDAI, then the Insurance Ombudsman — are on the grievance redressal page.