Last updated 18 September 2026.
Koloni is an early product run by three people. This page describes exactly what the system does today rather than what a mature privacy programme looks like. We are not SOC 2 certified — Type I is in progress — and we say so on the front page too. If your security function needs something this page does not cover, ask us and you will get a straight answer.
Two things, and nothing else.
| When you create an account | Your email address, first and last name, and a phone number only if you choose to give one — the field is optional and labelled as such. Your password is stored as a hash; we never see it. |
|---|---|
| When you upload a file | The supplier and invoice rows in the CSV you send. Nothing else is read from the file, and we cannot read a column we did not publish in the template. |
We do not buy data about you, and we do not enrich what you give us from third-party sources.
Your uploaded rows are used to run our detection checks and show you the result. That is the whole purpose. We also look at them to understand where the product falls short — that is what being a design partner means, and it is the exchange we are asking for.
We use your email and name to reply to you. If you give a phone number, we may call you instead of emailing. We will not add you to a mailing list you did not ask for.
Your rows live in your own tenant. The database enforces that separation at the row level, not only in application code, so another customer cannot query your data even through a bug in ours. Among ourselves, the three of us named on the front page can see it. Nobody else can.
We do not sell it, and we do not share it with anyone for their own purposes.
On Amazon Web Services in the United States (region us-east-1),
in a managed PostgreSQL database and on an EC2 instance. Traffic is encrypted in
transit. AWS is our only sub-processor: it hosts the service and sends the
emails the product sends you. If you are in the EU or UK, note that this means
your data is processed in the US — say so before you upload and we will tell
you honestly whether we can accommodate you yet.
Two, both strictly necessary: one that keeps you signed in, and one that protects forms against cross-site request forgery. There is no analytics, no advertising pixel and no third-party tracker on this site or in the application — which is also why you are not being asked to dismiss a cookie banner.
Until you ask us to delete it, or until we shut the demo tenant down. We are not holding your invoices as an asset; they are there so the product can show you something.
Email prasanna@aruk.ai and we will delete everything you uploaded, along with your account, and write back to confirm it is done. The written confirmation is the point — a deletion you cannot evidence is not much use to your auditor.
You can also ask us for a copy of what we hold, or for it to be corrected. Same address.
If we change what we collect or who processes it, this page changes and the date at the top moves. We will not quietly widen it.