Cookie Policy

Nothing is stored on your device while you read this site, unless you agree to it. The question at the foot of the page controls Google Analytics: say no and it is never loaded. There is one thing it does not control — if you complete and submit an application, Meta (Facebook) is told that an application was completed, so we can see which adverts produce enquiries, and a cookie is set at that moment. It carries none of your answers and nothing about your health.

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?

Only two, and neither while you are simply reading. Google Analytics sets cookies if you press “Allow these cookies”, and none if you decline — it is not loaded at all in that case. An advertising cookie is set by Meta only at the moment a completed application is submitted, and never otherwise.

Two things are true whatever you choose. Your answer itself is remembered, so you are not asked again — in local storage, not a cookie, so it never leaves your device. And the quote flow has an exception that is a link rather than a cookie, explained in full below.

One thing worth stating plainly rather than leaving you to infer it: the banner governs analytics. It is not a switch over the advertising measurement, which is tied to completing an application rather than to reading the site. If you would rather that measurement did not happen, the section on controlling cookies below explains what you can do in your browser, and you are welcome to apply by phone or email instead.

What this site sets on your device, as at the review date below. The first row depends on whether you complete an application; two of the others depend on how you answered the analytics question.
Kind	Set here?	What that means
Analytics cookies	Only if you accept	If you press “Allow these cookies”, Google Analytics sets two cookies (_ga and one beginning _ga_). They let it tell that a browser has been here before, so one person reading four pages is counted as one visit rather than four. If you decline, neither is set.
Third-party scripts	Some always, some only if you accept	Two, from two companies, neither of which runs while you are simply reading. Google Analytics loads only if you accept, and if you decline it is never fetched. Meta’s advertising script is present only on the application page, does nothing while you fill the form in, and contacts Meta once, at the moment a completed application is submitted.
Advertising cookies	Only if you complete an application	Nothing is set while you read this site or while you fill the form in. At the moment an application is successfully submitted, Meta (Facebook) is told that an application was completed, and sets a cookie at that point. This is how we tell which adverts produce enquiries. The message carries none of your answers and nothing about your health. If you never submit an application, no advertising cookie is ever set and Meta is told nothing about you.
Embedded third-party content	No	No video players, social widgets or chat bubbles that would set cookies of their own.
A record of your answer	Yes, either way	One entry in your browser’s local storage remembers whether you accepted or declined, so you are not asked on every page. It is not a cookie, which means it is never transmitted — it stays on your device and is readable only by this site.
Functional or preference cookies	No	None of this site’s own. The one thing it needs to remember about you during an application is carried in a link, not a cookie. The advertising cookie in the first row is set by Meta for Meta’s purposes, not to make anything here work — nothing on this site stops working if you block it.

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 analytics is switched on, and it sets a cookie. Until 4 September 2026 there was no banner here, for the honest reason that there was nothing to ask about: showing one anyway would have been asking permission for something that was not happening, which teaches people to click through the ones that matter.

The undertaking made on this page at the time was that if it ever changed, the question would come first — before anything was stored — and that declining would be a real choice rather than a dead button.

For analytics that undertaking is kept: Google Analytics loads only after you accept, and the two buttons are the same size, the same colour and in the same place, because a decline that is harder to find than an accept is not a choice.

The advertising measurement added on 5 September 2026 sits outside that question, and we would rather say so than let the banner imply otherwise. It is not triggered by reading anything, so there is no browsing to consent to; it is triggered by completing an application, which is an act you choose to take. Nothing is stored for it unless and until you do.

There is no “manage preferences” path. When the banner was written there was exactly one thing to decide, and a settings screen with a single switch in it is a way of making declining slower than accepting. That reasoning covers analytics. It does not cover the advertising pixel, which is not offered as a decision at all.

This is a description of what this website does. It is not a statement about what the law requires of websites generally.

What the analytics actually collects

If you accept, Google Analytics records which pages are opened and in what order, roughly where in the world the request came from, and whether the browser is a phone or a desktop. It does not receive your name, your phone number, your email address or anything you type into a form.

The application form is the part worth being specific about, because it asks about your health. What we send to Google Analytics from it is how far through the form people get and whether a submission succeeded — a position and a count, so that we can see where the form loses people. It does not report which questions you were shown or how you answered any of them. That distinction is deliberate: several questions only appear once an earlier one has been answered a particular way, so naming the question would disclose the answer. The underwriting result is not reported either.

The advertising measurement is held to the same line, and deliberately so. It is not present on any page you read, it is inactive on the form the whole time you are filling it in, and it runs once — after a completed application has been stored — to report that an application was completed. It is not told which questions you saw, how you answered any of them, or what the underwriting result was.

This is narrower than an advertising pixel usually is. That is on purpose: a pixel left to watch a form that asks about medical conditions, tobacco use and family history would be reading exactly the sort of thing it must never be given. If you would still rather it did not happen at all, you can block it in your browser, or contact us directly and apply by phone or email instead.

Nothing is sent to Google before you accept, and if you decline nothing is sent to Google at all. Nothing is sent to Meta unless you complete and submit an application.
Declining is one click, in the same place, and the site behaves identically afterwards. It stops the analytics cookies. The advertising measurement is separate, and is tied to completing an application rather than to the question.
To change your mind about analytics, clear this site’s data in your browser (see below) and the question will be asked again on your next visit. To avoid the advertising measurement entirely, block it in your browser, or apply by phone or email instead of using the form.

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 admin@prakashfinserv.com 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.