Privacy by architecture

Data encryption

• AES-256-GCM seals the SQLite database and attachment packs at rest.
• Passphrases are stretched with Argon2id before key derivation.
• License files use cryptographic verification (ECDSA in production builds).

Local storage — no cloud required

• Customer records live in a local database on the Host (or standalone) machine.
• Core CRM features do not upload contacts to Invoxa servers.
• You choose when to export CSV backups — exports are under your control.

Intranet security

• Clients authenticate to the Host with a bearer token.
• Traffic stays on your LAN; internet uplink is not required for sharing.
• Optional IP / CIDR whitelist restricts which peers may connect.

Trusted stack choices

The desktop shell is Tauri 2 with a Rust backend. Memory safety and a small attack surface matter for software that holds customer PII on disk.

Honest limits

Any offline desktop app can be reverse-engineered by a determined attacker. Invoxa hardens licensing and closes free-trial bypasses, but physical access and malware on the endpoint remain outside the product’s control. Protect OS accounts, backups, and passphrases accordingly.

Download trial Backup guidance