Security
Careful controls for financial records
Protection in the database, the server, the desktop client and your approval workflow.
Data on your own server
- Your records stay on your server, not in a vendor cloud.
- FYNEXO never sends your business data to us.
- An internet outage does not stop work on your office network.
Company isolation in the database
- PostgreSQL row-level security keeps each company apart.
- If the company context is missing, the database returns zero rows.
Four access levels
- Full, Entry only, View and Reports only, checked by the server on every request.
- Entry only sees what View sees and can enter transactions.
Maker-checker
- By default, the preparer of a voucher, budget or purchase order cannot approve it.
- Approval levels by amount; time-limited delegations.
Sign-in and sessions
- Sessions expire after 12 hours.
- Repeated wrong passwords lock the account for a while.
- Passwords must be at least 8 characters long.
Audit trail
- Changes to accounts, parties and settings record who and when.
- Posted vouchers are corrected by reversal, not deleted.
Least privilege
- The server runs as a Windows service with restricted rights.
- The database owner is not a superuser; the client talks only to the API.
Coming soon
Signed licences
Licences will be signed with Ed25519 and will never send business data. Licensing
We do not claim to be "100% unhackable". We use verifiable controls and fail safe when something unexpected happens. Security questions: [email protected].
Walk your IT team through FYNEXO
FYNEXO support can explain the database isolation and on-premise set-up.