REX42
Try it live Talk to us
Data security

The privacy is structural, not a policy.

A local model removes the question rather than answering it. If the document is read on your own machine, by weights stored on your own disk, there is no transfer to govern, no retention policy to verify, no jurisdiction to argue about, and no breach at a provider that can expose you.

0
Bytes sent outward
0
Third-party processors
Yours
Weights and logs
Air-gap
Runs with no route out
wide image
Why privacy is the whole point

Ask a company why AI is not in their document workflow. The answer is rarely “it doesn’t work”.

It is almost always one of these five, and each one is a legal or contractual obligation rather than a preference.

“Those are our clients’ Emirates IDs and passports.”
Identity documents carry obligations. Sending them to a third-party service abroad may breach the terms under which you were given them.
“That contract has a confidentiality clause.”
Tenancy agreements, supplier contracts and employment offers mostly contain a clause a legal team would read as prohibiting exactly this.
“Those are CVs.”
Candidate data is personal data. The candidate consented to you seeing it, not to it being uploaded to an AI provider.
“Our accounts are nobody else’s business.”
Invoices reveal suppliers, prices, margins and volumes — a competitive map of the business.
“We were told we cannot.”
Banks, healthcare providers, government suppliers and law firms often operate under rules that settle the matter before anyone asks.
A promise versus a property

Policies are real and they matter. They are still promises about data you have already handed over.

The usual answer to these worries is a policy: a commitment not to train on your data, a retention setting, a compliance certificate. Local inference is a different kind of answer.

Policy-based privacy
You verify someone else’s behaviour
The data has left your control. You are auditing a retention setting, a sub-processor list and a jurisdiction — and trusting that all three stay as described for as long as you use the service.
Structural privacy
There is nothing to verify
The document is read on your machine by weights on your disk. No transfer occurred, so there is no retention, no sub-processor, no cross-border question, and no provider breach that can reach you.
No transfer to govern. Data protection obligations around cross-border processing simply do not arise.
No retention policy to verify. The only copy of the document is the one you already had.
No jurisdiction to argue about. Processing happens at the address on your trade licence.
No provider breach that can expose you. There is no provider holding your documents to be breached.
n image
Structural, not contractual

The document never leaves the building, so there is nothing to govern.

No transfer, no retention policy to verify, no jurisdiction to argue about, and no provider breach that can reach you. The privacy is a property of where the computation happens.

How we hold that line in practice

The claim is only as good as the engineering behind it.

No outbound call path
The runtime has no client for any remote inference API. There is nothing to disable, block or firewall — the capability does not exist in the build.
Air-gapped commissioning
Model, runtime and weights install from local media and run with no network route out. We commission with your IT team and leave a signed install manifest.
We never hold your documents
Fine-tuning happens on data you provide under NDA, inside your environment or an isolated enclave you approve. We keep no copy after handover.
Real data, substituted
Training sets are built from real documents with every personal detail replaced, so the model learns layouts and never learns people.
Local, auditable logging
Input hash, model version, latency and output fields — written locally, readable by your SIEM, owned entirely by you.
Paperwork, properly
NDAs, DPAs and UAE-entity contracting through Royex Technologies LLC.
In practice

How the line is held

n image
Install
Air-gapped commissioning
Model, runtime and weights from local media, with no network route out.
n image
Audit
Local, structured logs
Input hash, model version, latency and fields — written locally, owned by you.
n image
Paperwork
Contracted properly
NDAs, DPAs and UAE-entity contracting through Royex Technologies LLC.
Honesty as a security property

A confident, wrong passport number is more dangerous than a blank field.

Our first models invented values when they could not read a document. That is the worst possible failure in business use, so refusal is engineered into the system rather than left to the model’s discretion.

It refuses unclear input. If an image is too poor to read, the response says so instead of producing a plausible value.
It discards what it cannot find. Any value not present in the source text is dropped, not inferred.
Facts come from approved text. Prices, discounts, contact details and company facts are answered from code, never generated.
Output is checked against the source. Every extracted field is verified against the document before it is shown to a user or written to a system.
Keep reading

Bring us your strictest requirement.

If your rules say the data cannot leave the building, that is the case REX42 was built for.

Talk to us See deployment options