What we collect, why, and what you can ask us to do about it.

Who we are

CLAVIS is built and operated by ProServIQ. For anything in this notice — a question, a correction, a request to erase — write to us, and we will answer.

Reading these pages

This website sets no cookies, runs no analytics and loads nothing from anyone else. The typefaces are served from this site, so opening a page here contacts no third party at all. We learn nothing about you by your reading it.

The only request this site makes on your behalf is the one you start by submitting the enquiry form below.

If you write to us

The enquiry form asks for your name, your email address and your message. A function in the same Mumbai region passes exactly those fields to our mailbox and stores nothing, anywhere. You get an emailed receipt that repeats none of your message back to you.

We keep the resulting email for as long as we need it to answer you and to keep a record of what was agreed. Ask us to delete it and we will.

If you use the free trial

The trial needs no account and asks for no identity. You upload documents, CLAVIS computes, and the result is shown to you. No record is stored — not the documents, not the figures, not a taxpayer record of any kind. The server refuses to store on the trial, so nothing you upload there outlives the page.

Two things do happen, and both are worth stating plainly:

• Rate limiting. So one visitor cannot use up the trial for everyone, requests are counted against an anonymised session identifier, or failing that a one-way hash of your network address. The hash cannot be turned back into an address, and it is never stored with anything you uploaded.
• Usage measurement. We record which features ran and the figures the engine computed — how many documents were read, the income and tax computed under each regime, which regime won, and whether the facts were complete enough to assert a figure. These carry no name, no PAN, no email and no network address, and they are not tied back to a person. We use them to see which parts of the product work and which do not.

If you would rather not be measured at all, do not use the trial — the signed-in product does not do this.

If your firm has an account

Here CLAVIS does keep records, because that is the point: a return you can defend is one with evidence behind it.

• Your sign-in identity — your email and login — is held by Logto, our authentication provider. It never sees your tax records.
• Computations are kept as records: what was computed, under which rules and engine version, and what was filed. They are never overwritten. A correction is a new record beside the old one.
• The facts each computation used — the figures, not the person. This snapshot holds no name, PAN or date of birth.
• A record of each document, not the document. Files are read and not kept; what stays is a SHA-256 fingerprint, the type and year, who uploaded it, and the file name with any PAN in it blanked out.
• A working copy, for at most eight hours while a return is being prepared. This is the one record that carries identity, and it is deleted when it expires.
• An audit trail of who saved, filed, exported or assessed erasure on which record.

A client's records are filed under a salted pseudonym derived from their PAN, never under the PAN itself, and screens show a PAN as ABCDE****F. The one place a full record leaves is the ITR-1 export, because the filing portal will not accept a masked PAN — and that export is written to the audit log when it happens.

Why we are allowed to hold it

For an account, because you asked us to: a firm gives us its clients' figures so that CLAVIS can compute and keep the return it was engaged to produce. Where a firm is the one deciding what happens to its clients' data, that firm is the Data Fiduciary and we process on its instructions.

For an enquiry, because you chose to write to us. For the trial, because you chose to use it.

Where it is, and who else touches it

Records are in Google Cloud's asia-south1 region, in Mumbai — Firestore for the records, Cloud Run for the servers that compute them. Google Cloud encrypts data at rest, and every page and request travels over HTTPS.

The services involved are Google Cloud (hosting and storage), Logto (sign-in), and Zoho (the mailbox your enquiry is delivered to). Nothing else. No AI model reads your documents or computes a figure — documents are read by fixed rules, and every figure comes from the law written as data, computed twice by two independent engines.

Error reports, when switched on, have taxpayer data stripped before anything leaves: request bodies, PANs, Aadhaar numbers and tokens are removed, including from our own error messages.

Your rights

Under the Digital Personal Data Protection Act, 2023 you may ask us for a summary of the personal data we hold about you and what we have done with it, ask us to correct or complete anything inaccurate, ask us to erase it where we no longer need it, and nominate someone to exercise these rights if you cannot.

For a client of a firm using CLAVIS, the firm is who to ask first — they hold the engagement. We will help them answer.

To exercise any of this, or to complain about how we have handled your data, write to us. If we cannot resolve it between us, you may complain to the Data Protection Board of India.

How long we keep it

Saved records are kept while your firm uses CLAVIS, because a computation is evidence of what was filed and a firm may need it years later. Working copies expire within eight hours. Trial uploads are never stored at all.

For any client, CLAVIS can state what it holds and what erasure would leave behind — naming any record that must be kept rather than deleting it silently. Deletion on request is carried out by us today; a self-serve control is in build.

Changes

If this notice changes in a way that matters, we will say so on this page and date it. This version is current as of 2026.