This policy explains how LigiComms (operated by LigimeX, MSME Udyam registered, Lucknow, India) uses cookies on ligicomms.in and in the dashboard. It sits alongside our Privacy Policy, which covers everything else we hold about you.
What cookies are
A cookie is a small file a website asks your browser to keep, so the next page you open knows something the last one did — that you are signed in, for example. Cookies set by the site you are visiting are called first-party; cookies set by another company whose code runs on the page are third-party. Third-party cookies are the ones that can follow you between websites.
Every cookie in our own list below is first-party, except Google's anti-bot cookies on three forms, which are explained in full.
Every cookie we set
This is the complete list — not a sample. If a cookie is not here, we do not set it.
Strictly necessary cookies 5
These are required for LigiComms to work at all — signing you in, keeping the page you asked for, and stopping automated abuse of our forms. They cannot be switched off, and none of them track you across other websites.
| Name | Set by | What it does | Expires | Where |
|---|---|---|---|---|
ligi.session |
LigiComms | Keeps you signed in. It holds only a session identifier; your access token stays on our server and never reaches the browser. HTTP-only | When you close the browser, or after 2 hours idle | Dashboard |
ligi_theme |
LigiComms | Stores the word "dark" or "light" so a page renders in your chosen theme immediately instead of flashing the wrong one. No identity, no token. | 1 year | Whole site |
ligi_nav_open |
LigiComms | Remembers which dashboard menu groups you left open, so the sidebar does not jump on every page. Stores menu labels only. HTTP-only | 1 year | Dashboard |
_GRECAPTCHA |
Google reCAPTCHA Enterprise | Tells a real person from an automated script on the sign-in, sign-up and contact forms. Set only on those three pages. | About 6 months | Sign in, Sign up, Contact |
rc::a, rc::b, rc::c, rc::f |
Google reCAPTCHA Enterprise | Browser storage reCAPTCHA uses alongside the cookie above to score the same three forms. | Persistent or session, depending on the entry | Sign in, Sign up, Contact |
Analytics and customisation cookies 5
These tell us how the marketing site is used, so we can fix what is confusing and see where visitors come from. We use Google Analytics, which counts visits and shows us which pages and referrers bring people here, and Microsoft Clarity, which records how a page was used — scrolling, clicks and where people get stuck — with typed input masked. They run on the public website only, never inside your signed-in dashboard, and nothing here is used for advertising. They load only if you accept them, and you can change your mind at any time.
| Name | Set by | What it does | Expires | Where |
|---|---|---|---|---|
_ga |
Google Analytics 4 | Gives your browser a random id so repeat visits count as one visitor rather than several. It carries no name, email or account of yours. | 2 years | Public site |
_ga_* |
Google Analytics 4 | Holds the state of the current visit — when it started and which pages it covered — so a session is measured once. | 2 years | Public site |
_clck |
Microsoft Clarity | Keeps a random id for your browser so repeat visits are recognised as the same one. | 1 year | Public site |
_clsk |
Microsoft Clarity | Joins the pages of a single visit into one recording, so a session reads as a journey rather than separate hits. | 1 day | Public site |
CLID |
Microsoft Clarity | Set on Microsoft's own domain to identify the browser across the visit. | 1 year | Public site |
What we don't use
These categories appear on nearly every cookie policy you will read. Ours are empty, and we would rather say so plainly than leave you to notice.
What we do run is listed in section 02 — analytics on this marketing website, and only after you accept it.
- Advertising cookies — These would make adverts elsewhere more relevant to you. We run none, and we are not part of any advertising network.
- Social networking cookies — These would let social networks track your visit for sharing or advertising. We embed no social widgets, no share pixels and no third-party video players on this website.
Concretely: no advertising network, no Facebook pixel, no DoubleClick, no LinkedIn or TikTok tags, no HubSpot, no Mixpanel, and no embedded third-party video players anywhere on this website.
Third-party services
Google reCAPTCHA Enterprise runs on the sign-in, sign-up and contact pages only, to tell a real person from an automated script. It is what stops our contact form filling up with spam. Google receives your IP address and browser signals for that check and may set the cookies listed above; their handling is governed by Google's Privacy Policy. It is not used to profile you and we receive only a score.
Two more third parties run inside the signed-in dashboard, never on the public website:
- Cashfree and Razorpay load their own checkout script on the Wallet and Subscriptions pages. Card handling has to run from the payment provider's own domain — that is a PCI requirement, not a choice — and they may set cookies needed to complete a payment.
- Meta's JavaScript SDK loads on the Channels page, and only there, so a tenant can connect their WhatsApp Business number through Meta's own sign-up window.
Both appear only on the page that needs them, only after you have signed in, and neither is used for analytics or advertising.
Your choices
Analytics cookies load only if you accept them. The first time you visit, a notice asks; nothing analytics-related is placed on your device before you answer. You can change your answer whenever you like from the Cookie settings link in the footer, and switching it off stops them from your next page onward.
Declining costs you nothing — every part of the site works the same. We simply learn less about which pages help people.
Essential cookies cannot be declined, because signing in depends on them. That is the one thing this choice does not cover.
You can also refuse or delete cookies through your browser. If you block the session cookie you will not be able to sign in, because it is what keeps you signed in from one page to the next. Blocking the theme or sidebar cookie only means the dashboard forgets how you set it up.
Browser instructions: Chrome, Firefox, Safari, Edge.
This page is built from the same list the product itself uses, so when a tool is switched on or off the table above changes with it.
India & the DPDP Act
LigiComms is built and operated in India and serves Indian businesses. The Digital Personal Data Protection Act, 2023 is the law we are written against. It has no separate cookie rule of the kind the EU has; what it requires is that personal data be processed with notice and, where consent is the basis, with consent that is free, specific, informed and unambiguous.
The cookies above are used for the service you asked for — signing in, keeping your settings, and stopping abuse of our forms. This page, together with the Privacy Policy, is the notice. There is no separate consent to collect while nothing optional is in use, and we will not manufacture one to look compliant.
Your rights over the data we do hold — access, correction, erasure, grievance redressal — are set out in the Privacy Policy, and a tenant admin can export or delete their whole workspace from the dashboard without asking us.
Other technologies
Cookies are not the only way a site can recognise a visitor, so for completeness:
- Tracking pixels and web beacons — we use none on this website.
- Local and session storage — the dashboard keeps small conveniences here, such as a remembered filter or an unsent draft. It stays in your browser, is never sent to us, and holds no identity.
- Flash cookies — none. Flash has not existed in browsers for years; policies that still mention it were copied from an older template.
- Server logs — our servers record errors, which can include an IP address. That is covered by the Privacy Policy, not by this page, because it is not a cookie.
Changes
If the cookies we set change, this page changes with them in the same release — the table above is generated from the same list the product itself uses, so it cannot quietly fall out of date. The date at the top tells you when it was last revised.
Contact
Questions about anything on this page? Write to info@ligicomms.in or use our contact page — a real person will answer.
If it is a formal grievance about your personal data rather than a question, it goes to our Grievance Officer, Shivanshu Tiwari, at grievance@ligicomms.in. What they handle and how long they take is set out in section 15 of the Privacy Policy.