Legal

Cookie Policy

Version 1.2 · Last updated 4 October 2026

Which cookies LagnaPrasang sets, which ones outside services set, and how to control both. Short, because we set few.

Contents · 7 sections

The short version

Every cookie our own code sets is one the site needs to work — signing you in, keeping you signed in, carrying you through the sign-up steps, and remembering whether you want the site in English or Gujarati.

We use Google Analytics to count visits and see which pages people use. It sets two cookies of its own; section 5 says how to block them, and the site works the same without them.

We set no advertising or cross-site tracking cookies, and no fingerprinting.

Three outside services — Google Analytics, Google Sign-In and our CDN, Cloudflare — set their own cookies under their own policies. Section 3 names all three.

1. What cookies are

Cookies are small text files placed on your device by a website. They are widely used to make websites work correctly, remember your preferences, and provide information to website owners. Similar technologies include localStorage and session storage, which serve related purposes.

2. Cookies we set

We set a small number of strictly necessary cookies. These are required for the platform to function. You cannot opt out of them without also opting out of using the platform.

prasang_access, prasang_refresh
The two cookies that keep you signed in. HttpOnly and Secure, so JavaScript on the page — ours or anyone else's — cannot read them. They last as long as the sign-in token inside them, and are deleted when you sign out.
prasang_session
A marker that says only “this browser is signed in”. It holds no token and no personal data — its value is the digit 1. It is the one auth cookie readable by JavaScript, deliberately: it is how a page already open notices that you signed in or out in another tab.
prasang_otp_session, prasang_social_pending, prasang_registration
Three cookies that exist only while you are part-way through signing in or registering — the phone-code step, the Google step, and the vendor sign-up step. HttpOnly and Secure, and they expire on their own in 10 to 15 minutes whether you finish or not.
NEXT_LOCALE
Remembers whether you want the site in Gujarati or English, for a year. Readable by JavaScript so the language toggle can show which one is active. It holds a language code and nothing else.

That is the whole list of cookies our own code sets. None of them hold personal information beyond keeping you signed in, and none are used for advertising, tracking or profiling.

Two things people often expect to find here are not cookies at all. The phone number you have just typed into a sign-in form, and whether you have seen the checklist drag hint, are kept in your browser's own session and local storage. They stay on your device and are never sent to us with a request.

3. Third-party cookies

We use three external services that may set their own cookies. We do not control these cookies and their use is governed by the respective third party's own privacy and cookie policies.

Google Analytics — _ga, _ga_RMG78PZFHB
Set on every page to count visits. _ga holds a random identifier that tells one visitor's visits apart from another's; _ga_RMG78PZFHB keeps track of the current visit. Both expire after 2 years and hold no name, phone number or email. Not needed for the site to work. Governed by how Google uses data from sites that use its services.
Google Identity Services
The “Sign in with Google” button loads the Google Identity Services SDK. Google may set cookies on pages where this button appears, in accordance with Google's Privacy Policy. These cookies are only present on pages with the sign-in button.
Cloudflare CDN
Our platform is served through Cloudflare's content delivery network. Cloudflare may set a short-lived cookie (_cf_bm) for bot detection and security purposes. This cookie contains no personally identifiable information and typically expires within 30 minutes.

4. What we do not use

We do not use:

  • Advertising or marketing cookies
  • Cross-site tracking cookies
  • Social media tracking pixels
  • Fingerprinting or device identification techniques

Google Analytics is the only analytics service on this site. If we add another, we will update this policy before doing so.

5. How to control cookies

You can control and delete cookies through your browser settings. Most browsers allow you to refuse all cookies, accept only certain cookies, or delete cookies after each session. Refer to your browser's help documentation:

Chrome
Settings → Privacy and security → Cookies and other site data
Firefox
Settings → Privacy & Security → Cookies and Site Data
Safari
Settings → Privacy → Manage Website Data
Edge
Settings → Cookies and site permissions

To stop Google Analytics on every site, not just ours, install Google's Google Analytics opt-out browser add-on. Blocking the Google Analytics cookies changes nothing about how this site works.

Note that blocking the authentication cookie will prevent you from staying signed in. All other platform features accessible without an account will continue to work.

6. Changes to this policy

We will update this policy if our cookie usage changes. The date at the top of this page reflects when the current version took effect. We recommend checking back periodically if you have concerns about cookie usage.

7. Contact us

Questions about our cookie usage? Write to [email protected] or use the contact form.