Your files and security
Your files stay yours.
The answers your IT will ask for, in the order they'll ask. Last updated 18 October 2026.
Your files can stay in your office.
Every account is in your name.
Personal data stays on your own machine unless you approve otherwise in writing.
Tested on twenty of your own past jobs before it goes live, and kept working as AI changes.
- A heartbeat, once an hour, going up
- Signed updates, coming down
- The nightly backup, sealed first
- Everything else stays on the box
Where does it run?
On your own machine, in your office.
Not in our cloud, and not in anybody's. Your files, the models and the log stay on that box, on your network. Rather not have a machine? Accounts in your firm's own name work too, with the same log and stop switch. No client machine is installed yet: on install day we prove each answer in front of you.
What leaves the building?
Three things, each one shown to you.
A heartbeat goes up once an hour: the box is alive, its versions and its counts, never a name or a document. Signed updates come down, each checked against our signature first. The nightly backup goes out sealed, to storage in your own country. Your rate cards, records, addresses and passports stay on the box.
What is encrypted?
The whole disk, all the time.
Carry the machine out of your office and nothing on it can be read. No password is typed at start up: the key is sealed in a security chip on the board, and opens only for the same machine with the same startup files. One recovery phrase lives in your own password store.
- The whole disk, encrypted, all the time
- Its key, sealed in the chip on the board
- One recovery phrase, in your own password store
Who can get in?
Your people, us for support, nobody else.
Your people get in on your office network, and on a private network for phones. We get in only for support, over that same network, only the people named in your proposal, and every session is recorded on your box. Nothing is open to the internet.
- Your people, on your own network
- Us, for support only, every session recorded
- Nobody else: no model vendor, no analytics company
What does it write down?
Every step, in a log you own.
What it read, which tool or model ran, what came back and who said yes. The log can only be added to, never changed. It stays on your machine for at least 180 days, as India's CERT-In directions of April 2022 ask, and for a year once the data protection rules apply.
The log, one job
| Time | Step | What | Who said yes |
|---|---|---|---|
| 09:41 | Read | A new customer's enquiry | |
| 09:42 | Priced | From your March rate card | |
| 09:43 | Flagged | A lane under your margin | |
| 09:46 | Sent | The quote, flag marked | Said yes: Priya, sales |
Sample data · Powered by Agentec
Does any model learn from our files?
Only your own, with your written yes.
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. Without the machine, the provider that reads anything is named in writing before we build.
Does anything reach another client?
No. Agentec is its own company.
Nothing you give us reaches IKAN, a relocation company with offices across India where Eashan is chief technology officer, or any of our clients. Your files are never used to build for anyone else.
Which data laws does it meet?
Yours, gone through and written down first.
Most data laws ask who holds your people's data, where, and who else reads it. With the machine, you hold it, in your own country, and no model vendor reads it. We do not give legal advice: what your law asks of you is agreed in writing before anything is built.
| The law | Where | A breach is reported |
|---|---|---|
| DPDP Act and Rules, 2025 | India, from May 2027 | To the Board, no later than 72 hours after learning of it |
| CERT-In directions, April 2022 | India | To CERT-In, six hours from noticing it |
| PDPA | Singapore | To the PDPC, no later than three days after assessing it |
| UK GDPR | United Kingdom | To the ICO, no later than 72 hours after learning of it |
What if something goes wrong?
You hear it from your own system first.
The alert reaches the person you name at once, at any hour, and never waits for a message from us. If we notice first, we tell them what we know as soon as we notice, with every fact your own report needs.
- First
Your system alerts
The person you name, at once, any hour.
- Then
We tell you
What we know, as soon as we notice.
- Your report
It goes in on time
India's CERT-In directions of April 2022 give six hours.
Which certificates do you hold?
Not ISO 27001 or SOC 2, yet.
We say so rather than print a badge. What we can show you now is in the table, each line dated. When a security test by an outside auditor, or the receipts of a client's install day, exist, their dates go on this page.
| What | Today |
|---|---|
| ISO 27001 | Not yet |
| SOC 2 | Not yet |
| A test by an outside auditor | Not yet |
| This page and the trust pack | Dated 18 October 2026 |
| Our own AI policy | In writing, 13 October 2026 |
| Our own machine at work | Checked 22 September 2026 |
What changes for a larger firm?
The same rules, sized to you.
It runs in your own cloud account or data centre, or on two machines with failover. Your people sign in through your own single sign on, with roles for each team. The log goes to your own monitoring too. The recovery time is measured on your system and written into the proposal.
Ask us anything about it.
Send your questions, or your security questionnaire, to the address below.
What stays yours
- Your accountsin your company's name
- Your codeevery line of it
- Personal dataabout your customers and staff, on your own machine unless you approve otherwise in writing
- Plain files and a how-to guideif you stop
Eashan Gupta, founder. You meet him on the first call.