This page is a scaffold. It is not in force.
These terms are being prepared with counsel and have not been adopted. Nothing on this page binds you or Comhard Technologies Pvt Ltd, and no sentence here should be read as a commitment on uptime, retention, refunds or jurisdiction. The terms that currently govern your use of Comsky are available on request from legal@comsky.ai, and we will send them the same working day. What follows is the shape of the document and an honest description of our practice today, published so you can see what is coming rather than wait for it.
In force from — · Version —
Terms of service
The agreement between you and Comhard Technologies Pvt Ltd, of Noida, Uttar Pradesh, for use of the Comsky products and the comsky.ai website. Section headings and order below are the ones the final document will carry.
1. Parties and scope
Identifies Comhard Technologies Pvt Ltd, registered in India and operating from Noida, Uttar Pradesh, as the contracting entity for every Comsky product. States that the agreement covers the products, the consoles, the APIs and this website.
2. Definitions
Defines the terms used throughout — Account, Workspace, Product, Customer Data, Wallet, Documentation and Order Form. Definitions are shared across the suite so that one word does not mean two things in two products.
3. Acceptance and order of precedence
Sets out how you accept the agreement and which document wins when two conflict: an executed order form, then any product-specific terms, then these general terms. No precedence rule is settled yet.
4. Eligibility and authority to bind
Requires that the person accepting is authorised to bind the organisation named on the account. Covers use by resellers and distributors accepting on behalf of a customer under the account tree.
5. Accounts, credentials and account security
One identity covers the whole suite, so this section covers credential hygiene, multi-factor enrolment and responsibility for actions taken under your account. It will also state what we do when we believe a credential is compromised.
6. The products and their release status
Comsky Cloud, CRM, TallyBridge and Backup are available now. Books, HRMS, Telephony, Chat and Monitor are not released, and the agreement will not describe an unreleased product as one you can rely on today.
Ownership, residency and getting it back.
The sections that describe what we may do with what you put into the suite, and what happens to it when you stop.
7. Customer data and ownership
Your data stays yours. This section limits our processing to what is needed to run the product, bill for it and support it, and says plainly that we do not use customer data to train models sold to anyone else.
8. Data residency and data protection
Customer data for the Comsky products is held in Indian data centres and Indian object storage. This section will bind that practice and point to the privacy policy and to the per-product residency table on the security page.
9. Confidentiality
A mutual obligation covering what each side learns about the other. The survival period after termination is — and is one of the clauses still with counsel.
10. Audit trail and administrative access
Sign-ins, factor changes and administrative actions are written to an append-only, hash-chained trail you can read. Support staff cannot enter your workspace without an explicit, time-boxed grant, and the grant appears in your own log.
11. Export and deletion
You can export your data in an open format without asking us, at any point in the term. Deletion requests are honoured and confirmed back to you; the window in which deletion completes is —.
12. Acceptable use
Incorporates the acceptable use policy by reference and sets out what happens when it is breached. The policy itself is published separately at /legal/aup so it can be updated without reopening the agreement.
What you pay, and how either side stops.
Comsky is prepaid from a wallet balance, with no minimum term and no notice period. These sections write that down.
13. Fees, wallet and taxes
You top up a wallet balance and we meter against it. There is no card on file being charged behind your back. Invoices are raised in Indian rupees with GST, from the Indian entity, so there is no forex line.
14. Low balance, grace and suspension
You are warned before the balance reaches zero, then given a grace period, then resources are suspended rather than deleted. The length of that grace period is —.
15. Term, termination and suspension for cause
There is no minimum term and no notice period on any product: stop using it and the metering stops. This section covers termination for cause on either side and what triggers an immediate suspension.
16. Refunds
Points to the refund policy and states how an unused wallet balance is treated on exit. The refund window is —, and no figure in this scaffold should be relied on.
17. Service levels and support
Support is included on every product and every tier and is answered from Noida in IST. Availability targets and any service credits live in the SLA at /legal/sla; the percentage is —.
18. Sub-processors and third-party services
Names the categories of third party that may receive customer data and how the current sub-processor list is obtained and how changes to it are notified. The list is available on request today.
The clauses counsel is still writing.
Every value in this group is deliberately blank. These are the clauses where a placeholder would be worse than an omission.
19. Intellectual property
We keep the rights in the software and the documentation, you keep the rights in your data and your content, and neither is granted to the other beyond what running the service requires. Also covers feedback you send us.
20. Warranties and disclaimers
What we do warrant about the products, and what is provided as-is. The specific warranties are not settled, so none is stated here.
21. Limitation of liability
Caps each side’s exposure and carves out the categories that are never capped. The cap is — and the carve-outs are —.
22. Indemnities
Covers third-party claims arising from your content and from our software, and the process each side follows on receiving one.
23. Changes to the products and to these terms
How we notify a material change, how much notice you get, and what you may do if you do not accept it. The notice period is —.
24. Force majeure
Events outside either side’s control, and the effect on obligations while they last.
25. Assignment, notices and entire agreement
Where legal notices are sent, how assignment on a change of control is handled, and the standard closing provisions of severability and waiver.
26. Governing law and dispute resolution
Which law applies, where disputes are heard, and whether arbitration comes first. All three are —. We will not publish a jurisdiction clause before counsel settles it.
27. Grievance officer
India’s IT Rules require a named grievance officer with published contact details and a response time. The appointment is —, and the page at /legal/grievance will carry it once made.
Need the terms that actually apply?
Ask and we will send the binding document, the DPA and the sub-processor list. None of them is held back.