Payroll documents carry names, salaries and bank details. Khaonix is designed so that it reads them, compares them and forgets them, and so that its models never needed them in the first place. This page states what is done with your documents, where, for how long, and what is never done.
Nothing is stored beyond the run it belongs to, and nothing leaves the run except what you download.
The exported file is yours and lives where you put it. Khaonix keeps no copy, no index and no derived data from it.
Two deployment options, same software, same results. The choice follows your security and compliance requirements.
Operated by Khaonix on infrastructure in the European Union. Suited to baselines, pilots and clients whose policies permit processing in the EU under a data processing agreement.
Delivered as a container with the models and controls qualified for you. Documents never leave your network; Khaonix has no access to the running system.
No. The models are trained on documents generated from a specification, in your layouts, before any client document is processed. Client documents are never added to a training set, and the models are not adjusted on them in operation. This is also why Khaonix can be qualified before use: the model that is tested is the model that runs.
In the hosted service, the people you give the key to, through the review page, for as long as the run exists. Khaonix staff do not access client runs. On your own servers, only you.
That a run was created, when, by which key, and what it produced in counts: pairs, outcomes by status, coverage. Not the documents, not the values. The evidence for a run is in the run's own report and goes with the export.
In the hosted service, in the EU, on a dedicated instance. On your own servers, wherever you place the container. In both cases, data is held for the run only.
In the hosted service, the EU infrastructure provider, named in the data processing agreement. No other party is involved in processing. There is no sub-processor in the on-premise deployment.
Each run's report records the complete population, every outcome, the rule applied and the versions of everything involved. It is designed to serve as control evidence under frameworks such as SOC 1 and ISAE 3402; the qualification records for each control are available to clients under NDA.
Khaonix processes personal data on behalf of the client as a processor under the Swiss Data Protection Act and, where applicable, the GDPR. It makes no decisions about individuals: it reports whether two documents agree, and a person decides what follows. Documentation on scope, training data and qualification is kept for each model and control.
A completed security questionnaire and the data processing agreement are available on request. Specific controls not covered here can be discussed before a baseline.
Send them before the baseline. Most are answered on this page; the rest in a short call with the person who built the system.