This document is a draft. It is not yet in force.
The cookie policy is being prepared with counsel and nothing on this page binds Comsky or you. It is published in this state so you can see how the finished document will be organised and what it will have to answer. The terms that currently apply to your account are available on request from legal@comsky.ai — ask for them and read those instead.
Cookie policy
This page will cover what comsky.ai writes into your browser, why each item is there, how long it stays and how you change it. It covers the marketing site. Each product console states its own position separately.
The contracting entity behind the suite is Comhard Technologies Pvt Ltd, registered in Noida, and that is the entity this policy will be issued by. Where the finished document needs a number, a period or a named role, this draft writes an em dash rather than a placeholder that could be mistaken for a commitment.
What is stored, by category.
The finished policy names every cookie, local-storage key and session-storage key individually. This draft describes what each category is for, so the shape of that table is clear.
1. Strictly necessary
Sign-in session, the CSRF token and request routing. These are set whether or not you accept anything else, because without them you cannot sign in or stay signed in. The finished section lists each one by name and says which service sets it.
2. Preferences
Things you chose and expect to still be true on your next visit, and the record that you answered the consent banner. These stay in the browser rather than on a server, and are readable only by comsky.ai.
3. Analytics
Which pages are read and in what order, used to decide what to write next. Whether analytics runs before consent, and which processor handles it, is one of the questions counsel is settling before this section is fixed.
4. Advertising and retargeting
This section names every advertising or retargeting tag on the site and what each one receives. If the list is empty it will say the list is empty, rather than quietly omitting the heading.
Third parties, lifetime, residency, control.
The four questions that decide whether a cookie policy is useful or decorative.
5. Third parties and embedded content
Web fonts, video and any embedded product demo can set storage of their own. This section lists each embed, names the provider, and states what that provider receives when the page loads.
6. How long each item lasts
A session cookie ends when the browser closes. A preference cookie outlives it. The exact lifetime for each category is —, and it will be stated per cookie rather than as one number for the whole site.
7. Where the resulting data is held
Anything that leaves the browser is held in Indian data centres, which is the same residency position as the rest of the suite. Any processor outside India will be named here along with what it receives.
8. Your choices
You can decline non-essential storage in the banner, change that answer later from the same control, and clear everything from your browser settings. Declining does not restrict what you can read on this site.
Consoles, your rights, changes, contact.
Where this document stops, which requests it obliges us to answer, and who you write to.
9. The product consoles
This policy covers comsky.ai. The consoles for Cloud, CRM, TallyBridge and Backup run on their own subdomains and state their own cookies there. The products still in build — Books, HRMS, Telephony, Chat and Monitor — will do the same when they ship.
10. Export and deletion
A request to see or remove what this site holds about you follows the same route as the rest of the suite: an export in an open format you can read without our software, and a deletion we confirm back to you rather than leave you to assume.
11. Changes to this policy
A new version is published here with the date it takes effect, and the previous version stays available so the change can be compared. The notice period before a material change applies is —.
12. Contact and disputes
Questions about this document go to legal@comsky.ai. The named contact for grievances is —, and the governing law and forum for disputes are —. Support questions belong on the support channels, which are staffed in IST.
Reasonable things to ask about an unfinished policy.
Can I read the terms that actually apply to me today?
Yes. Write to legal@comsky.ai and ask for the current binding terms. They exist, they are not this page, and this page does not replace or amend them.
Why publish it before it is finished?
Because the alternative is a policy that names a retention period nobody has implemented. The headings are correct and the structure is correct; the numbers go in when counsel and engineering agree on them, and not before.
Does declining cookies cost me anything here?
Not on this site. Signing in to a product console is different — that needs its session cookie, and it is not optional, because it is the mechanism by which you stay signed in.
Where does anything this site records end up?
In Indian data centres, consistent with the residency position for the rest of the suite. Any processor outside India will be named in the finished document with what it receives.
Does this apply to the product consoles as well?
No. This covers comsky.ai. Each console states its own cookies on its own domain, and the finished version of this page will link to each of them.
Need the terms that are in force?
Ask and we will send the current binding documents. This draft is here to show the structure, not to stand in for them.
Comhard Technologies Pvt Ltd, Noida. Draft — not in force.