Works from the local installation
- Core SQLite records
- Local user sign-in and permissions
- Application audit records
- Local backup and restore
Loading…
Analytics
Can we measure anonymous page visits? It shows us which pages help people choose Omnix. Nothing personal is sent, and the analytics script loads only if you accept.
Omnix keeps the working business record on the installed computer. This page separates controls implemented in the desktop app from protections supplied by the operating system and services that still need a connection.
Each boundary below names what the implementation does and what it does not cover. No “unbreakable,” “zero-risk,” or blanket encryption claim.
On this device
Core business records are written to omnix.db in the operating system app-data directory. Counter work reads and writes that local database instead of waiting for a website request.
Boundary
The database file is not encrypted by Omnix. Access at rest depends on the Windows account, device access, and any full-disk encryption configured by the owner.
Inside the app
Passwords are stored as Argon2id hashes. The role system includes Owner, Manager, Cashier, and Viewer, with permissions, groups, and branch or module scopes available for finer control.
Boundary
Roles limit actions inside Omnix. They do not replace Windows sign-in, screen locking, or device administration.
Local application record
Omnix records allowed and denied high-risk or critical permission checks with the user, action, permission, outcome, and available entity context.
Boundary
This is an append-only application table, not a tamper-proof external ledger. Someone with administrative access to the database file remains outside that boundary.
Local and optional cloud
Omnix can create local database snapshots, list them, and restore one after taking a safety copy. Optional cloud backup compresses and encrypts a snapshot on the device with AES-256-GCM before upload.
Boundary
Local .db backup files are ordinary database copies and are not encrypted by the local-backup command. Cloud upload and restore require a connection, an activated machine, and the customer-held backup password.
Local check after issue
The desktop app carries a public key and verifies the RSA signature on an Omnix licence payload before reading its modules and device entitlement.
Boundary
Issuing, activating, or synchronising a licence crosses the internet boundary. A signed key helps detect altered licence data; it does not encrypt business records.
Connected operation
The Tauri updater is configured with Omnix release endpoints and an embedded updater public key so update artifacts can be signature-checked by the updater.
Boundary
Checking for and downloading a release requires internet access. Omnix does not describe that process as protection against every compromise, and this page makes no automatic-install or rollback promise.
Bring your device policy, backup routine, staff roles, and connectivity constraints to a demo. For a written security question, email support@omnix.co.ke.