Cookie Policy

We Set One Cookie

Most cookie policies are long because most sites track you. Ours is short for the opposite reason. Here is the single cookie HealthGridERP places, what it does, and how to be rid of it.

Last updated: April 1, 2026

1. Cookies in Plain Terms

A cookie is a small piece of text a website asks your browser to hold on to and hand back on the next request. It exists because the web has no memory of its own — without one, every page you opened would treat you as a stranger.

Some vanish the moment you close the browser; others sit on the device until they expire or you clear them. Some are placed by the site you are actually looking at, others by outside companies whose code the site has embedded. That last kind is where tracking usually creeps in — and it is the kind we do not use.

2. What We Use Them For

Exactly one thing: keeping you signed in. When you log in, we hand your browser a session cookie; every screen you open afterwards presents it so we know which hospital and which role is asking. Take it away and the platform simply cannot tell a doctor from a receptionist, so this one is not optional.

It doubles as a security control — the same cookie is what lets us reject requests that arrive without a valid session, and cut a session short when someone signs out.

3. The Cookie We Set

hms_session — strictly necessary

What it holds. A signed session token. Not your name, not your email, nothing about a patient.
Locked to the server. It is marked HTTP-only, so no JavaScript in the page — ours or anyone else's — can read it.
Encrypted in transit. On our live service it is flagged secure, so it only ever travels over HTTPS.
Same-site only. Strict same-site rules mean it is never sent along with a request that another website triggered.
Seven days. Then it expires and you sign in again. Signing out clears it immediately.

That is the complete list. There is no analytics cookie, no preference cookie and no advertising cookie behind it.

4. What We Do Not Set

Worth stating plainly, because most healthcare software does otherwise:

No Google Analytics, and no third-party analytics of any kind.
No advertising, retargeting or remarketing pixels — from Meta, LinkedIn or anyone else.
No social media tracking scripts. Our social links are ordinary links; following one takes you to that platform, where its own rules take over.
No cross-site profiling, no data brokers, nothing sold on.

Payment pages are the one exception, and they are not ours. When you pay a subscription invoice, the payment provider's own page may set cookies it needs to complete the transaction securely. Those are governed by that provider's policy, not this one.

5. Taking Control

You are never locked in. Since we set nothing optional, there is no consent banner to wade through and no preference panel to hunt for — but the ordinary browser controls all work:

Clear it. Every browser lets you delete cookies for a single site. Doing that to us signs you out, nothing more.
Block it. You can refuse our cookie outright. Be aware that the platform then has no way to keep you logged in, so the workspace becomes unusable — it is not a trade-off we can engineer around.
Sign out. The quickest route. The cookie is destroyed on the spot, on your device and on our side.

7. If This Changes

Should we ever introduce a cookie beyond the one described here — analytics on our marketing pages, say — this page is updated before it goes live, with a new date at the top, and anything non-essential will ask your permission first rather than assume it.

8. Talk to Us

Questions about cookies, or anything on this page:

Emailhealthgriderp@gmail.com

Phone+91 98765 43210

OfficePune, Maharashtra, India

For the wider picture on how we handle data, see the Privacy Policy.