Security and privacy
Documents are the most sensitive thing a business hands over. These are properties of the system, not promises about it.
- Your workspace is isolated in the database
- Every table is protected by row-level security keyed to workspace membership, so one customer's rows are not merely hidden from another's screen — they are not returned by the database at all.
- Documents are stored privately
- The document store has no public URLs. A file is reached only through a short-lived signed link issued to someone who is already a member of that workspace.
- Roles, and an audit trail
- Owner, admin, editor and viewer. Corrections, deletions and permission changes are recorded with who did them and when.
- Deleting really deletes
- Removing a document removes its bytes from storage, not just its row from a list.
- KAI does not train on your documents
- Your files are read to produce your results, and for nothing else.
Documents you upload are sent to Google’s Gemini API to be read. Full detail is in the privacy policy, and what you agree to in using KAI is in the terms.
Keep reading
How it works
The three steps, the formats it reads, and why you can check every figure it gives you.
What KAI costs
A credit is a page. The plans in Kwacha, and what is free before you pay anything.
About KAI and Denovo Systems
Who builds this, where we are, and why it was built for Zambian documents first.
Questions
Columns, handwriting, blurred photos, colleagues and payment — answered plainly.
Put your own documents in front of it.
A workspace takes a minute to create and starts with 50 free pages, so you can find out on your own invoices rather than on a promise.