Where your documents run, and who can touch them

Per workflow, not per company. For each document type we ask three questions with your compliance owner: may these pages leave your network at all, what does each option cost at your real volume, and what accuracy does the workflow need.

The pilot measures the answers on your own documents. The decision and its reasons are written into the pilot report, so an auditor can see why each workflow runs where it does.

Owned hardware is not always the cheapest answer. At low volume a hosted open-weight model often costs less, and when it does we say so.

In a deployment in your environment, retention is your policy. Documents and output never reach infrastructure we operate, so there is nothing for us to keep or delete.

When a pilot or a managed batch runs on infrastructure we operate, the retention period is a term of the data processing agreement, fixed before the first document arrives. Our default proposal is the shortest one that works: source documents and output are deleted once you confirm delivery, unless you ask us to hold them longer for reprocessing.

Available for every engagement, and signed before any document that contains personal data is shared, pilots included. You remain the data controller; Akora SIA acts as processor and works only on your documented instructions. If your organization has its own DPA template, we work from yours.

For document processing in your environment: none. No third party receives your documents.

If a workflow uses a private cloud provider or a hosted model for exceptions, each provider is named in the DPA before it is used, and you can refuse any of them.

This website is separate from client work. It uses:

• Hostinger: hosts this website
• Ahrefs Web Analytics: cookieless page statistics
• Web3Forms and hCaptcha: deliver and protect the contact form
• Calendly and Google Meet: book and hold the discovery call

What the site itself collects is covered in the privacy policy.

We never train or fine-tune models on customer data. Your documents and the data extracted from them are used to deliver your output and for nothing else.

If an engagement includes adapting a model to your documents, that is agreed in writing first and runs inside your environment.

It is not a geography promise. We do not sell residency in the EU or any other region as a guarantee. The promise is control: the processing runs where you decide, on infrastructure you govern. If your rules require a specific country or region, you pick the servers or the cloud region, and the deployment follows.

Akora SIA, registration number 40203566478, Upes 11, LV-2008, Latvia. Questions about security or data handling go to hola@aekora.com and are answered by a founder.