You should be able to check,
not just take our word.
An employee that reads your books and answers your customers has to be accountable to you. This page is what Delanti actually does, split three ways: the things your employee has no way to do, the things it holds for a person, and the things you can verify yourself. The last section is the one worth reading twice, because it is where we say what these guarantees do not cover.
For the formal detail, your rights, and every outside service that touches your data by name, see the privacy policy.
What it cannot do
Some things are not promises. They are absences.
A promise is only as good as the person making it, and it can be quietly changed on a busy Tuesday. These are different: the ability is not there to switch on.
It cannot change your accounting books
Tally, Zoho Books, QuickBooks, Xero and Business Central are connected for reading only. The employee can ask your books questions and has no way to alter a ledger.
Where the software maker offers a read-only login, which is Zoho Books and Xero, that is the login we hold. Where none exists, which is QuickBooks, Business Central and Tally, our own software enforces the limit instead. With Tally, the small program on your own computer refuses a write instruction before it ever reaches Tally.
It cannot pay anyone
Your employee holds no card details and no bank login, and none of its built-in tools can send money. All it does with money is read your books, match payments that have already arrived, and draft reminders for you to approve.
If you ever ask us to connect it to a system of yours that can move money, that is a separate build you commission, and every action in it still waits for your yes.
It cannot quietly widen its own reach
Every outside system it touches is one you connected, with the access you granted, and you can withdraw any of them at any moment. It cannot add a connection on its own or reach a system nobody gave it.
What waits for you
Anything that commits your business stops at a person.
Ordinary work happens without ceremony. The consequential things queue up with the exact wording, and go nowhere until somebody named approves them.
Anything about money stops for a person
A message that mentions money, a message to someone your business has no record of, and any message going to many people at once are all held for a named admin. You see the full wording before it goes, and the words you approve are the words that get sent.
Automatic reminders you switch on, work inside connected apps like Drive and the calendar, and anything an owner asks for directly in their own chat follow their own separate rules.
You always see who it thinks it is chasing
Before a payment reminder reaches a customer, a person approves it, and the approval screen says whether that customer has been matched to a client on your list, only guessed at, or not matched at all.
The system never records a match as agreed on its own. Only a person can do that.
What your team teaches it waits for an admin
When somebody on your team teaches the employee something in chat, it is saved as a proposal, and an admin approves it in the dashboard before the employee works from it.
A few things do go live without that step, such as the employee’s own notes on each colleague and its research on software you use. Every one of them sits on your knowledge page, where an admin can change or delete it.
Money questions are answered for the right people only
The employee will not pull figures out of your accounting system for anyone except the owner and the people the owner has specifically cleared. That refusal happens in the software, before your accounting system is ever contacted.
It covers the accounting tools. Anything financial sitting in a shared folder or a spreadsheet is still readable by whoever you gave access to that folder.
And it knows when to stay quiet.
Discretion is not a setting you have to remember. These are refusals it makes on its own, every time.
A teammate asks
What was our revenue last month?
That is for the owners. I cannot share the books.
In the team group
Can you post Priya's number here?
I will send it to you in a private message, not the group.
A staff member asks
What is the margin on the Acme deal?
I will check with an owner before sharing any figures.
And it acts exactly as you set it.
Four modes, from observing quietly to working autonomously. A dial for every connection: read only, suggest, or act. Access set per person, privacy per note, hours per week. It learns with your approval: your own corrections apply immediately, and anything your team teaches waits for your OK.
Set once, changed any time, from your dashboard.
Rohan, customer
What do your packages cost?
Drafted the reply. Waiting for your OK.
On probation, everything outward waits for you.
What you can check
Everything it did, in writing, and yours to take.
Supervision that depends on asking us is not supervision. These you can do on your own, today, without telling anyone.
Every action is written down in plain sentences
What it replied, what it looked up, who it chased, what it filed, and what it is holding for you. In your dashboard, in normal language, readable by day or by person. Nothing happens off the books.
You can take its knowledge and leave
The knowledge your employee works from downloads at any time as ordinary text files that open in any editor. No special software, and nothing held in a format only we can read.
Message history, client records, tasks, the activity log and private notes an admin has locked to themselves are not part of that download and stay in the dashboard.
Your data is copied every night, and the copy is tested
We copy your data nightly, encrypt it, then prove the copy works by loading it into a fresh empty database and checking every record came back. A backup that quietly stopped working shows up as a failure the next morning, rather than on the day you need it.
The copy is taken once a day, so a serious failure could cost up to a day of work. Dashboard sign-in accounts are not part of the copy and are re-created by invitation after a restore.
The limits
What these guarantees do not cover.
Every product page states its strengths. This is the part most leave out, and it is the part you should judge us on, because anyone can write the section above.
Hidden instructions can still get through
When the employee reads an outside web page, file or scan, that content is marked as information before it reaches the employee, and known attack phrases are stripped. That lowers the risk and does not remove it: instructions hidden in ordinary language can still slip past. The protection that does not depend on spotting the attack is the one above, that nothing reaches a new contact without a person approving it.
Where your data actually sits
Your records live in a database in Mumbai. The servers that run the software sit outside India, and so do the encrypted nightly copies. The AI model and a handful of other services we name in the privacy policy also handle your data outside India. Everything travels over an encrypted connection, and any passwords or keys you give us are encrypted by us before they are stored.
We are not certified yet, and we will not pretend otherwise
We hold no SOC 2 report and no ISO 27001 certificate today. What we have instead is on this page and in the privacy policy, plus a data-processing agreement your legal team can have on request. When a buyer needs a formal audit we will say where we are, honestly, rather than showing a badge for something that has not happened.
If you keep other people’s books
Built for work that carries a duty of confidence.
If you are a CA firm, an advisory practice or a law office, your clients’ confidentiality is the whole business, and the record above is written to be examined rather than admired.