One document for your IT and procurement.

On one machine you own, in your office, if you choose it. Not in our cloud, not in anybody's cloud. The record, the workflow, the documents and the models that read your mail are built to run on that box, on your network. No vendor data centre holds your files, so there is no vendor data centre for your client to audit.

The machine is small: about the size of a thick book, drawing under 200 watts. It needs a cooled room and a small battery, and it is set to come back on by itself after a power cut.

If you would rather not have a machine, the AI agents can run in accounts in your firm's own name instead, with the same log, the same yes and the same stop switch. We tell you plainly what that changes about where your files sit before anything is built.

Where this stands today. No client machine is installed yet. Answers 01 to 04 say how the machine is built to work, and on install day we prove each one in front of you and write the receipt into your log. Our own machine runs our own AI work: six kinds of it were checked on 22 September 2026, and that story is on our work page.

Three things, by design. On install day we show you each one.

A heartbeat, once an hour, going up. It says the box is alive, which versions it runs, how many jobs ran, how many are waiting, how many errors, the disk and the temperature. It carries no name, no document and no line of any job.

Signed updates, on a schedule, coming down. Each one is a sealed package checked against our signature before it is allowed to run, pinned to an exact version. The box is built to run its own health checks after an update and to put itself back on the previous version if they fail.

The nightly backup, going out already sealed. It is encrypted on the box before it leaves, to a bucket in your own country, so the bucket holds bytes nobody can read without your key.

Nothing else leaves on its own. Your rate cards, your records, your customers' addresses, passports and photographs stay on the box.

Messages your AI agents send and receive on WhatsApp, mail or SMS go through those services, as they do today. Your proposal names each one.

The whole disk, all the time. If the machine were carried out of your office, nothing on it could be read.

One catch: an encrypted disk normally needs somebody to type a password when it starts, and a box that waits for a person at three in the morning stays down. So no password is typed. The key is sealed into a small security chip on the machine's own board, and the chip only hands it back when the same machine starts with the same startup files. Lift the disk out and put it in another machine and it opens nothing. One written recovery phrase exists for the day the board itself has to be replaced. It lives in your own password store, never on our side.

On install day we prove both halves in front of you and write both receipts into your log. We pull the power at the wall and watch the box come back on its own. Then we start it once with a tampered startup file and watch it refuse.

Your people, on your office network, and on a private network for phones outside the office. Nothing is exposed to the open internet.

Us, only for support, over that same private network, and only the people named in your proposal. Every support session is recorded on your box, by your box, and the recording is yours. Nothing is ever downloaded from your machine.

Nobody else. Nobody outside the names in your proposal, no model vendor and no analytics company. The models run on your box, so there is no third party reading your mail to answer a question about it.

Every step records what it read, which tool or model ran, what came back, how long it took, and who, if anyone, said yes. That log is append only and it is yours. It is what makes an audit a morning's reading instead of a project.

It is kept for at least 180 days, the period India's CERT-In directions set for a company's logs, on the machine in your own office. It can be kept for longer, and a copy can go to your own monitoring.

No outside model does. Your data trains only your own model, with your written yes, and never anyone else's. A model trained on your files runs on your machine or in your own accounts, and it is yours.

With the machine, the models run on the box itself, so no model vendor reads your files at all. Without the machine, we tell you plainly which provider reads what before anything is built, and it is written down.

No. Agentec is its own company. Nothing you give us reaches IKAN, the firm our founder also works for, or any of our clients, and your files are never used to build for anyone else.

Most data laws start with three questions: who holds your people's data, where, and who else reads it. With the machine, you hold it, in your own office, in your own country, and no model vendor reads it. The nightly backup is sealed before it leaves and goes to a bucket in your own country.

We do not give legal advice. In the session we go through what your own law asks of you, India's DPDP Act, Singapore's PDPA, the UK GDPR or any other, and what is agreed is written down before anything is built.

Your own system alerts your named person at once, at any hour. It never waits for a message from us. India's CERT-In directions give a company six hours from noticing an incident to report it, so the alert reaches you first, from your own system.

If we notice something first, we tell your named person what we know within six hours of noticing, any day, with every fact you need to make your own report to CERT-In in time. Out of our support hours an AI agent that stops stays stopped, and your team works the old way until we are back. What happens when an AI agent gets a job wrong is on what we answer for.

We do not hold ISO 27001 or SOC 2 yet. We say so rather than print a badge.

What we can show you now. This page and the trust pack, in writing and dated. Our own AI policy, in six lines. Our own machine at work, with the six kinds of AI work checked on it on 22 September 2026. The audit that checks every automation on our own machines each night, and the guards that watch them, both on our work page with their dated counts.

What is not there yet. A security test by an outside auditor, and the receipts from a client's install day. When either exists, its date goes on this page.

The same rules, sized to you. For a firm of thousands, the proposal sets each of these out in writing before anything is built.

Where it runs. In your own cloud account or your own data centre, sized to your load, where one machine in one office is too small. Two machines with failover, where you choose machines.

Who gets in. Your people sign in through your own single sign on, with roles for each team, so access follows the joiners and leavers you already manage.

What you can watch. The log goes to your own monitoring as well as staying on the system.

Recovery. The recovery point is the last nightly backup. The recovery time is measured on your system and written into the proposal, never quoted from a brochure.