These terms govern your organisation’s use of eCorpOS, the platform at
os.ecorpit.com, and of eClock, the desktop application
supplied with it. They are separate from
the terms for ecorpit.com, which
govern only browsing that website.
Where your organisation has signed a Master Services Agreement, order form or Data
Processing Agreement with us, that signed agreement prevails over these
terms wherever the two conflict.
1. Who these terms are between
Us: eCorp Information Technologies Private Limited (“eCorpIT”), 1120, 11th Floor, SVH 83 Metro Street, Sector 83, Gurugram, Haryana 122012, India
You: the organisation that holds the subscription, and every person who signs in under it
By creating an account or using eCorpOS you accept these terms on behalf of your
organisation, and confirm you are authorised to do so.
2. Your account
Accounts are for organisations and the people acting for them. eCorpOS is not offered to consumers or to anyone under 18.
Sign-in is by a one-time code sent to a work email address. You are responsible for who holds access to those mailboxes.
You are responsible for what the people you invite do in your account, including administrators you appoint.
Tell us promptly at security@ecorpit.com if you believe an account has been compromised.
3. Plans, billing and what each state means
eCorpOS is sold as modules, priced per user per month. What you can do depends on the state
of your subscription, and the states are deliberate:
State
What it means
Trialing
Full access to everything, so an evaluation is honest.
Active
Everything your plan includes.
Grace
A bill is overdue, or a trial has ended and paid service has not been started. Service is not degraded. A grace period that quietly reduced what worked would be a shorter deadline wearing a kinder name.
Suspended or cancelled
Read-only. You can still read and export everything. We do not lock you out of your own records — your data remains yours and retrievable.
How you are billed
Paid service starts when you start it. An owner or administrator of your
organisation presses Start paid service. That press is your organisation’s acceptance
of these terms, and nothing is charged when it is made. Started during a trial, billing begins
the day after the trial ends. An organisation that never starts paid service is never invoiced:
30 days after its trial ends it becomes read-only.
You are billed for the calendar month, after it. The billing month is the
calendar month in Indian Standard Time. On the 1st of each month we raise one GST invoice for
the month just ended. It is due on the 10th.
You pay for what you used, by the day. Each day is charged at that day’s
monthly price for your plan, multiplied by the number of people who could sign in to your
organisation at 3 am that day, divided by the number of days in that month. A full month
therefore costs exactly the monthly price, in February as in March. A person added on the 11th
is charged from the 12th; a person removed on the 20th is charged for the 20th. There is no
limit on how many people you may add.
Changing your plan. Adding a module or moving up a tier takes effect
immediately and is charged from the next day; the bill for that month shows the days on the old
plan and the days on the new one as separate lines. Reducing a plan is done by us at your
request and applies from the day after it is made. Where a reduction shortens a monitoring
retention period, the shorter window applies to data captured after the change; anything already
captured keeps the window it was captured under. Data leaving your window is not deleted at
once — it moves into the sealed copy the Privacy Statement describes, which nobody in your
organisation can read, and is destroyed 365 days after capture.
If a bill is not paid. From the day after it is due a bill is overdue, and
service is not degraded. If it is still unpaid 30 days after the date of the bill, your
organisation becomes read-only until every overdue bill is paid in full, and is restored as
soon as they are.
Stopping. The owner may stop paid service at any time. The day you stop is
the last day charged. From the next day your organisation is read-only, a final bill is raised
on the 1st for the days used, and nothing is billed after it. Stopping deletes nothing.
Paying a year in advance. You may instead pay for twelve months in advance
at the price of ten. Days paid for in advance are never billed again. A module or tier added
during that year is charged pro rata for the days remaining on it, at the difference in price,
added to your next invoice. When the year ends you are billed by the month as above, unless you
pay for another year.
Discount codes. A discount code takes off what it says, on the monthly bills
it says, starting with the bill for the month in which it is entered; it is shown on each bill
as a discount, before GST. One code applies at a time. A code has no cash value and cannot be
exchanged, carried over or used on a year paid in advance.
We may withdraw a code so that nobody new can use it; that does not end it for an organisation
already using it.
How you pay. Bills are paid from Settings → Billing by UPI, card or
netbanking, or by bank transfer quoting the invoice number. We do not take a payment
automatically.
Fees are exclusive of GST and other taxes, which are added where applicable.
Refunds. Within 30 days of your first payment we refund it in
full, whether or not you have used the service. After that, cancelling refunds any time you have
paid for in advance and not used, calculated to the day. The 30-day window
applies to your first payment only; it does not start again with a later bill or renewal.
A refund goes back the way the money came in — a card or UPI payment returns to
the same card or account. Where our payment provider can no longer do that, which it cannot once a
payment is more than six months old, we send it by bank transfer to the account you paid from.
Allow 5–7 working days for it to reach you after we send it.
We do not deduct payment-processing fees or tax from a refund — you receive the full amount you
paid for the time you did not use. Where GST was charged we issue a credit note for it.
A refund ends the subscription it refunds: your organisation becomes read-only from that day,
which means you can still read and export everything. No refund is due where we end an account
for the reasons in section 8.
4. Your data is yours
You own everything you put into eCorpOS — your records, your customers’ details, your staff data, your documents.
You grant us only the licence needed to host, process, back up and display it in order to provide the service, and to support you when you ask.
We do not sell it, and we do not use it to train models.
We act as your Data Processor for it. The terms of that processing are set out in our Data Processing Agreement, which forms part of these terms and applies automatically — you do not need to sign it separately. Who a person should ask about their own data is set out in the Privacy Statement.
Support engineers can enter your organisation only under a grant an administrator has
explicitly approved, and everything done under one is recorded against it.
5. What you must not do
Break the law, or use eCorpOS to help someone else do so.
Upload data you have no right to hold, or use it for a purpose the people it describes were never told about.
Send marketing to people who have not agreed to receive it, or to addresses obtained without consent. Repeated spam complaints put the sending reputation of every customer at risk and we will suspend an account that causes them.
Attempt to access another organisation’s data, or probe, scan or load-test the service without written permission. Good-faith security research reported to security@ecorpit.com is welcome and we will not pursue it.
Resell or white-label eCorpOS without a written agreement.
Circumvent plan limits, or misrepresent how many people are using the service.
6. eClock, and what you take responsibility for
We supply the tool. You decide to monitor your staff with it, and that decision
is yours in law. eClock can record attendance alone, or — where you buy
monitoring — what your package includes: activity levels, application names, window
titles, web addresses and screenshots.
By enabling any monitoring feature, you confirm that:
You have a lawful basis for it in every jurisdiction where your staff work, and that monitoring is proportionate to a legitimate purpose you can state.
You have told the people affected, before it starts, what is collected, why, and for how long — in your own employment policy or contract, not only through the notice eClock displays.
You will not use it to monitor anyone on a device you do not have the right to monitor, or outside working time contrary to local law.
You will handle what it produces as the Data Fiduciary you are, including answering your own staff’s requests about their data.
Where you adopt eCorpIT’s monitoring notice v4 or later, you rely on your employment of the people monitored as the lawful basis — in India, the Digital Personal Data Protection Act 2023, section 7(i) — and we process what eClock records for you as your Data Processor.
Remote control. Where your package includes it and you have adopted notice
v5 or later, the owner, or an administrator the owner allows, can control an employee’s
computer: its screen, pointer and keyboard, copied text, and files sent or fetched. By
using it you also confirm that:
You use it to support and administer the computer for work, and for nothing else.
The person is asked each time, unless they have themselves allowed control without asking on that computer. You will not make allowing it a condition of their work.
What a controller does on the computer is done by your organisation, and you are responsible for it as for any other act of your staff.
You will not switch it on if you are a government department or a public-sector body, whose networks CERT-In’s guidelines close to remote-desktop software.
Recording sessions is your choice. A recording is kept for 90 days, and every playback is recorded on the person’s own record.
How the product constrains this, deliberately. Nobody can read a
monitoring notice on an employee’s behalf: the person signs in from their own machine and
reads the notice there before anything is recorded. Under notice v4 or later they are told what your
package records rather than asked; under an earlier notice they see each permission by name
and may decline any of them, and declining does not stop them recording their own hours.
Either way clocking out stops everything, and blocking needs their own agreement on their
own computer. Nobody controls their computer without their Allow, or their own switch for
it, and a banner names whoever is in control for the whole session, with a Stop button.
eClock is visible, closeable and uninstallable by the
person using the computer, and it never records keystrokes, the clipboard, the camera or
the microphone. We will not add a feature that removes these properties, and we will not
build a hidden or unremovable mode on request.
You are responsible for the consequences of monitoring you choose to carry out. We are
responsible for the tool doing what this page and the Privacy Statement say it does.
7. Availability and changes
We aim to keep eCorpOS available continuously but do not commit to an uptime figure unless a signed agreement states one. Maintenance may cause short interruptions.
The service depends on providers named in the Privacy Statement; an outage at one can interrupt eCorpOS.
We add and improve features continuously. Where a change removes something you rely on, or materially changes what eClock collects, we will tell you before it takes effect.
Support is by email at contact@ecorpit.com during Indian business hours unless agreed otherwise.
8. Ending the subscription
You may stop using eCorpOS at any time. We refund the part of the term you have paid for and not used, on the terms set out in section 3.
We may suspend an account for unlawful use, non-payment beyond the grace period, or conduct that threatens the service or other customers. Except where the law or an emergency prevents it, we will tell you first and give you a chance to put it right.
A suspended account stays readable and exportable. We do not hold data hostage over an invoice.
After termination you may export your data for 30 days. After that we delete it on the schedule in the Privacy Statement, except where law requires us to keep records for longer.
You may ask us to erase your organisation’s monitoring data at any time. That erasure destroys the encryption key, which makes the retained copies unreadable — it is not reversible, and a backup restore cannot undo it.
9. Confidentiality
Each of us will protect the other’s confidential information and use it only to perform
these terms. Your data in eCorpOS is your confidential information. This does not cover
anything already public, independently developed, or required to be disclosed by law.
10. Intellectual property
eCorpOS, eClock and everything in them other than your data remain ours. These terms grant
you a non-exclusive, non-transferable right to use them during your subscription, and
nothing more. Feedback you give us we may use freely, with no obligation and no claim on
it by you.
11. Warranties and what we do not promise
We will provide eCorpOS with reasonable skill and care. Beyond that, and to the extent the
law allows, it is provided as is: we do not warrant it will be
uninterrupted, error-free, or fit for a purpose we have not agreed in writing.
eCorpOS is not a substitute for professional advice. It computes GST, TDS
and payroll figures from the data and settings you supply, and those outputs are aids to
your own compliance, not a certification of it. Statutory filings, their accuracy and
their deadlines remain yours. Check them with your accountant.
12. Liability
Neither of us limits liability for anything the law does not permit to be limited —
including fraud, and death or personal injury caused by negligence.
Otherwise, and to the extent Indian law allows, neither party is liable for indirect or
consequential loss, loss of profits, revenue, goodwill or anticipated savings; and each
party’s total liability arising out of these terms is limited to the fees paid by you for
eCorpOS in the twelve months before the claim arose.
This limit does not apply to your obligation to pay fees, or to either party’s breach of
confidentiality or of applicable data-protection law.
13. Indemnity
You will indemnify us against claims brought by a third party — including your own staff
or a regulator — arising from data you put into eCorpOS that you had no right to hold, or
from monitoring you carried out without the lawful basis and notice required by section 6.
14. Changes to these terms
We may update these terms. Material changes are announced in the product and take effect
at your next renewal, or 30 days after notice, whichever is later — so you always have the
option to leave rather than accept them. Continuing to use eCorpOS after that is
acceptance.
Version 1.6 (17 October 2026) adds remote control to section 6, for organisations that
adopt eCorpIT’s monitoring notice v5, and section 4’s Data Processing Agreement is now
version 1.3: it names Cloudflare Realtime as the relay for live views and remote control,
which carries them encrypted end to end. It applies to an organisation from the day its
owner or administrator adopts notice v5, which is an explicit acceptance; nothing changes
for an organisation that keeps notice v4. Billing is unchanged from version 1.5.
Version 1.5 (15 October 2026) rewrites section 6 for eCorpIT’s monitoring notice v4: under
it the people you monitor are told what your package records rather than asked, and you
rely on employing them as the lawful basis, with us as your processor. It applies to an
organisation from the day its owner or administrator adopts notice v4, which is an explicit
acceptance; nothing changes for an organisation that keeps an earlier notice. Billing is
unchanged from version 1.4.
Version 1.4 (14 October 2026) adds one thing: discount codes, in section 3. It takes nothing
away and changes no price, so it applies from the day it is published.
Version 1.3 (12 October 2026) changes how monthly service is billed: by the calendar month,
after it has been used, by the day and by the number of people, on an invoice raised on the
1st and due on the 10th. Version 1.2 billed a month in advance, counted from the day of
payment. It also reverses one rule of version 1.2: on monthly billing an upgrade is now
charged from the day after it is made, where before nothing was charged until renewal.
Version 1.3 applies to an organisation from the day its owner or administrator starts paid
service under it, which is an explicit acceptance. Time already paid for in advance under an
earlier version is kept, on the terms it was bought under.
Version 1.2 (21 September 2026) changed one thing: a module or tier added part-way
through a term of more than one month is now charged pro rata for the days
remaining on that term, added to the next invoice. Version 1.1 said no mid-term change was
pro-rated, which was written when every plan was monthly and the rest of a month was a
matter of days.
15. Governing law and disputes
These terms are governed by the laws of India. The courts at Gurugram,
Haryana have exclusive jurisdiction, and each of us submits to them.
Before starting proceedings, both of us agree to raise the matter in writing and try in
good faith to resolve it within 30 days.
16. General
If a clause is unenforceable, the rest stands.
Not enforcing something once does not waive it.
You may not assign these terms without our written consent; we may assign them to a successor of our business.
Neither party is liable for delay caused by events beyond reasonable control.
There is no partnership, agency or employment between us.
These terms, with any signed agreement and the documents they reference, are the whole agreement about eCorpOS.