Terms of Service

Covio is operated by Covio (covio.in). These terms are between Covio and the company that holds a Covio account — not between Covio and the individual people who sign in. Throughout, "you" means the company.

Covio has no public sign-up. An account exists only because Covio, or a Covio partner, created the company and invited its owner. Everyone else is invited by that owner or by an administrator the owner appoints. There is no way to create a company by filling in a form, and there is therefore no moment at which an individual person agrees to these terms on the company's behalf by clicking a box.

Not settled / not in placeBecause onboarding is operator-driven and there is no sign-up checkpoint, nothing in the product today records a company's acceptance of these terms. How acceptance is to be captured — a signed order form, a first-sign-in acknowledgement, or a countersigned agreement — is a decision for counsel and the founder, not a fact about the current system.

Covio is a multi-tenant platform for factory visibility. Depending on what your company has been given, it may include: a record of machines and what they produced; a document library with expiry tracking; compliance activities and approvals; and Covio Connect, which reads your TallyPrime books from the computer they already run on.

Parts of Covio are switched on per company. A screen that says a panel is not switched on for your company is stating a fact about your entitlement, not a fault.

Covio Connect only reads. It never writes to your accounting books. This is enforced in two places rather than promised once: the job table accepts only read-kind jobs, and every request composed for your connector must match an allowlist of read shapes before it is sent.

• Every person signs in with their own credentials. Shared logins defeat every record Covio keeps of who did what.
• Owners and administrators must complete a second sign-in step. Covio sends a six-digit code to WhatsApp; there is a seven-day grace period from first sign-in, after which the account cannot be used until the second step is set up.
• Your owner and administrators decide who is in your company, what role each person holds, which sites they see and which panels they can open. Covio does not add, remove or re-role your people except on your instruction or as required to operate the platform.
• You are responsible for removing people who leave your company. Covio gives your administrators the controls to do it; it cannot know that somebody has left.

Everything your company puts into Covio, and everything Covio's platform measures or reads on your behalf, remains yours. Covio holds it in order to provide the service to you.

Covio does not sell your data, and does not use one company's data to serve another. Every query the platform makes is scoped to the signed-in person's company, and no endpoint accepts a company, an email address or a role supplied by the browser.

• What Covio collects and why →
• Covio's role as a processor →

• Do not attempt to reach another company's data, or to test whether you can, without Covio's written agreement.
• Do not share device keys, connector activation codes or recovery codes outside the people who need them.
• Keep the contact details Covio holds for your owner and administrators current, because incident notices and sign-in codes go there.
• Use Covio for your own business. Reselling access, or opening your account to a company that is not yours, needs a separate agreement.

Covio staff do not browse customer accounts. Where support requires somebody at Covio to open your screens, that access runs under a grant and every screen opened is written to an access log. Both the grant and the log are part of the data export you can ask for at any time, so you can check what was opened and when.

Covio runs on a single server and is deployed several times a day. It is monitored and backed up nightly, and every deployment takes a database backup before it applies a migration.

Not settled / not in placeCovio does not publish an uptime commitment, a support response time, a recovery time objective or a recovery point objective, because it has not measured any of them over a meaningful period. Any figure in a contract must be one the founder chooses and the operations can meet — not one drafted here.

• The controls that are actually in place →

Either side may end the agreement. When a company leaves, Covio's own lifecycle requires an export to be produced before the account can be terminated: the software will not move a company past the export step without one.

After termination the data enters a retention period, and after that period it is purged. The length of that period is not yet fixed, and Covio says so plainly rather than publishing a number it has not ratified.

• The offboarding lifecycle, step by step →
• What is kept, and for how long →

Covio will tell your owner and administrators before changing these terms in a way that affects you. The current version is always at covio.in/legal, and the date it was last changed is at the top of the page.

Covio drafted this document from its own systems rather than from a template, so what follows are the points where engineering cannot decide and a lawyer must.

1. 1How is acceptance of these terms to be captured, given Covio has no public sign-up and no agreement checkpoint anywhere in the product?
2. 2Which law governs, and which courts or arbitration forum hear a dispute?
3. 3What limitation of liability and indemnity is appropriate for a platform holding a factory's production and compliance records, and what insurance (if any) should stand behind it?
4. 4Should the terms carry a service-level commitment at all at this stage, given nothing is measured yet?
5. 5What notice period should each side give to terminate, and does the customer's right to an export survive non-payment?
6. 6Does anything in these terms need to differ when a company is onboarded through a Covio partner rather than directly?