Trust and security
Straight answers to the questions security teams ask before a pilot.
Last updated 13 October 2026
Where does the check run?
In your infrastructure. You run two parts: the proxy in front of your API, and the approval service that sends each approval to the person's phone. Both run in your cloud or your data center.
When the proxy decides on a request, it does not call OmniArx. It checks the signature against the phone keys your approval service enrolled, which stay in your systems.
Where does our data go?
It stays with you. The proxy sends nothing to OmniArx.
- Each decision is written to your own database: the approval, the request it covered, the result and the reason.
- Your approval service keeps the request details and the text the person saw, in your systems.
- The signed approval carries fingerprints of the request and of the screen, not the details themselves.
- You decide how long records are kept. Nothing is deleted until you set a retention period.
What happens if OmniArx is down?
OmniArx is not in the path of a request. The proxy and the approval service run without calling us.
The parts that matter are the ones you run, and they fail closed:
- If your approval service is down, no new approvals can be made.
- If the proxy cannot reach its replay store or its records database, it refuses the request.
- The proxy never lets a request through because it could not check it.
A signed approval expires 60 seconds after it is made and works once.
Plan for the proxy like any other part of your request path. We design high availability, support and upgrades with you in the pilot.
How much delay does the check add?
We have not published a number yet, because we have not measured one we would stand behind. When we do, we will publish the number and the method on this page.
Until then, you can see it on your own traffic. The proxy reports how long each check takes to your monitoring, in a standard metrics format.
How are phone keys set up and protected?
- Set up: the SDK creates a signing key in the phone's secure hardware. The key never leaves the phone. The phone enrolls the key with your approval service and sends the platform's proof about the device. Your server, not the phone, decides what that proof is worth. If that proof cannot be obtained, enrollment is refused, never quietly downgraded. Each route sets the lowest level it accepts.
- Each approval: the person confirms with face or fingerprint right before the phone signs. The device passcode is not accepted, and adding a new fingerprint or face disables the old key.
- The screen: the phone refuses to sign if anything covers the approval. On iPhone it also refuses while the screen is recorded or mirrored.
What has been tested?
Our own test record, as of 1 October 2026:
- 31 of 31 attacks on the signed approval were refused.
- 49 approval scenarios on real Android phones and iPhones: 8 went through, 24 were refused, 5 were observations only, and 11 are not yet run.
Not every result matched what we expected. We show the full record, gaps included, in a live session.
What it does not protect against
- It does not stop prompt injection. It stops an injected change from running without a matching approval.
- It does not decide who is allowed to approve. Your system decides that.
- A phone whose operating system is compromised and hidden from checks is out of scope.
- It does not stop a person who is persuaded or forced to approve.
How can you verify us?
- The approval format is published as individual Internet-Drafts submitted to the IETF.
- The check runs in your own systems, so your team can inspect what it does and what it logs.
- Every refusal has a name in your operator log, so you can see why each request was stopped.
- In a live session, we run the checks and you name the case.
An independent penetration test is underway.
Report a security issue
Email arun@omniarx.ai. We reply to every report.