1 · One machine
Every piece of Covio's customer data is on a single virtual private server rented from Hostinger, running Ubuntu 24.04 and serving covio.in. There is no second region, no replica, no content delivery network in front of the data, and no separate analytics warehouse.
| What | Where it lives |
|---|---|
| Platform data — companies, people, machines, documents metadata, compliance, the Tally reading | PostgreSQL 17, in a Docker volume on that server |
| The legacy Mikiwire workspace | MySQL 8, in a Docker volume on the same server |
| Uploaded files and machine panel photographs | A Docker volume on the same server. Never served as static files — every read is authenticated and ledgered |
| Backups | Encrypted archives on the same server. The fourteen most recent sets |
Not settled / not in placeCovio does not assert a country of storage on this page. The physical location of the server is a fact about the hosting arrangement, and Covio will state it only once it can be evidenced from the provider rather than assumed. A customer who needs it in writing should ask, and Covio will obtain it.
2 · What leaves the machine
Customer data leaves the server in exactly four circumstances, all of them the service doing what it was asked to do.
| Leaves for | What goes | Who receives it |
|---|---|---|
| A WhatsApp message | The destination number and the message content — a sign-in code, a summary with its figures, or a report document fetched once | Twilio |
| An email | The destination address and the message content — an invitation, a password reset, an operational alert | Resend |
| Reading a machine panel photograph | The photograph, where a company uses photo capture and Covio's own reader has not already read it | Anthropic |
| A person using Covio | Whatever that person's screen shows, over TLS, to their own browser or phone | The signed-in person |
Not settled / not in placeCovio has not assessed where each of those providers processes what it receives, and makes no claim about a transfer mechanism. That assessment is one of the open questions below.
3 · What never leaves
- The databases are not reachable from the internet; neither publishes a port.
- Uploaded files are never served as static objects and there is no public URL for one.
- Covio uses no third-party analytics, advertising, tag manager or session-recording script on its own pages.
- Fonts are self-hosted; no font is fetched from a third-party origin, so a page view does not disclose a visitor to anybody but Covio.
- Covio Connect reads a customer's Tally books from the customer's own computer into this server. It sends nothing back to Tally.
4 · A single machine is a single point of failure
Not settled / not in placeEverything on one server means a failure of that server is a failure of everything, and the backups that would rebuild it are on the same machine. Covio is not going to describe this as resilience. The second destination is specified and the upload tooling is ready; it needs an account and a credential that do not yet exist.
What counsel must rule on before this stops being a draft
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.
- 1Must Covio state the country in which the server is located, and must it obtain that in writing from the hosting provider before signing a customer?
- 2Is any customer subject to a data localisation requirement that a single Hostinger VPS would not satisfy?
- 3Sending a WhatsApp number, an email address or a photograph of a factory panel to a provider that may process it outside India — is that permitted, and does it need a transfer mechanism, a customer notice, or specific consent?
- 4Must the residency position change before a customer with statutory record-keeping obligations can be onboarded, given there is no off-host backup?