Security Architecture
How Hijin safeguards financial data through local isolation, cryptographic verification, and fail-closed validation.
1. Local-First Isolation Standard
The desktop workstation boundary is the fundamental security perimeter. Sensitive accounting files, invoices, and journal entries are kept inside the operating system's local user context. There is no arbitrary user-data upload path.
2. Least Privilege Execution
The Hijin installer and application run entirely under normal user privileges (standard user token) and do not require administrative elevation (UAC admin privileges) for routine operation.
3. Package Integrity & Checksum Verification
Every binary release and neural model package is accompanied by an authoritative SHA-256 cryptographic hash. The desktop application verifies package digests before activating any downloaded component. Tampered or corrupt files are rejected automatically.
4. Cryptographic Licensing & Fail-Closed Verification
Commercial and trial entitlements are signed using asymmetric Ed25519 cryptography. The desktop client validates signature integrity against embedded public verification keys. If local cache tampering, signature corruption, or clock rollback is detected, the license status fails closed.
5. Responsible Security Posture
We make no absolute claims of invulnerability, as all computing systems have security boundaries, as such marketing claims are technically unfounded. We engineer robust, defense-in-depth security controls based on verified architectural boundaries. If you discover a potential vulnerability, please report it via our security disclosure process on GitHub.