Is it safe to let AI read our invoices?
It depends entirely on what the vendor does after the reading, and most will not tell you unless asked. On our demo the file is resized in your browser, sent once to be read, and never stored. Reload the page and it is gone. Ask any vendor the five questions below and you will learn more in ten minutes than from any security page.
Last checked 14 August 2026. Prices on this page are ours and current.
What leaves your building, and what does not
A document has to be sent somewhere to be read. There is no honest way around that unless you are running a model on your own hardware, which for a business of ten people is almost never worth it.
So the question is not whether anything leaves. It is what leaves, how long it lives, and who else sees it. On our reader the image is resized in your browser first, which means the enormous original never goes anywhere. What we send is the smallest version that is still readable.
Then the answer comes back and the file is finished with. It is not written to a database, not put in a bucket, not queued for review. Reload the page and there is nothing left, which you can verify yourself in about four seconds.
The five questions
Ask these of everyone, including us.
Do you store the documents, and if so where and for how long. Are they used to train anything. Who at your company can open them, and does anyone need to in order for the product to work. What happens to everything you hold if we stop paying you. And which country are they processed in, because for some businesses that is a legal question rather than a preference.
Vague answers are answers. A vendor who cannot tell you where your supplier invoices sit has not thought about it, which tells you what you needed to know.
Training is the one people forget
The risk most people picture is a breach. The one that actually catches businesses out is quieter: documents fed back into training a model, so your prices and your suppliers become part of something you no longer control.
This is worth asking about in writing rather than over a call, because the answer is usually buried in terms rather than said out loud. Nothing you send our reader trains anything.
The part nobody mentions
The biggest realistic risk to your supplier invoices is not a model provider. It is the shared folder called scans that half the office can open, the WhatsApp group where photos of paperwork get forwarded, and the laptop with no password on the desk by the door.
If you are thinking carefully about this for the first time, automation is a good excuse to fix the rest of it too. Reading documents properly usually means they stop being scattered, which is a security improvement on its own.
Do not take our word for it.
Read a document, then refresh the page. Nothing comes back, because nothing was kept.
- Do you keep our documents?
- Not on the demo. Files are read once and never stored, and reloading the page clears everything. If you want a searchable archive kept, that is a deliberate choice you ask for and it is your data.
- Are our documents used to train a model?
- No.
- Can your staff see our invoices?
- Not on the demo, because nothing is kept for anyone to look at. On a job we build for you, access is something we agree in writing before we start.
- Can it run entirely inside our own systems?
- It can be arranged and it costs considerably more. Tell us why you need it, because sometimes the real requirement is a data location rather than full isolation, and that is much cheaper.
Tell us what you are trying to work out and we will answer it straight, including when the answer is that you do not need us.
Or email hello@ahlelak.com