Check an archive on your phone before you open it. List and extract only what is safe, into a folder you choose — and get an honest verdict on everything else.
Android · 7 languages · offline · no telemetry · beta
These features are implemented and tested in the current Android build. Mobile is focused on safe inspection and extraction — not deep recovery.
A read-only scan classifies the archive — Safe, Suspicious, Blocked, Encrypted or Unsupported — before any content is opened. You decide with the facts in front of you.
See the entries an archive contains without extracting them, with unsafe paths (traversal, absolute, reserved names) flagged rather than followed.
Extraction is transactional and stays inside the destination you pick — entries that fail a safety or integrity check are not written.
Output is written through Android's Storage Access Framework into the target folder you select. VERAQIS Archiver doesn't roam your storage.
Mobile follows the same rule as the rest of VERAQIS: report the truth, never fake a result.
NOT_AVAILABLE where deep recovery is not present — those
workflows live on the desktop where available.The interface ships in 7 languages, including full right-to-left layout for Arabic.
Translations are reviewed for key parity and placeholder safety; native-speaker polish is ongoing during beta.
The current Android beta scope, stated without over-claiming.
It scans archives before opening, lists entries safely, and extracts safe entries into a folder selected through Android's Storage Access Framework.
No. Mobile is focused on safe inspection and extraction; deeper recovery workflows belong to VERAQIS Recovery where available.
No. Passwords, when supplied, are handled as transient character data and are not stored in models or logs.
Every screen talks to the archive engine through a single, Android-free safety facade — never directly to the low-level engine. This keeps every safety decision in one audited place, and is enforced by an architecture test in the build.
Scan, list, extract, verify, report
and license all flow through the VERAQIS Archiver Facade API (schema v1).
The safety logic is a plain Kotlin/JVM module with no Android dependencies, adapted to the phone at the edges only.
No JNI/NDK and no copied-in engine internals — the mobile app is its own clean implementation of the safety surface.