Security and reliability
Not marketing promises - principles enforced in server code, not just in the interface.
- 001
Full separation between businesses
Every record in the system is tied to the account that created it. No request can read or change another business's data, at the server level, not just in the interface.
- 002
Documents you cannot change
An issued fiscal document (invoice, receipt, credit note) is digitally signed the moment it's issued and stored as a permanent snapshot. There is no way - not even through support - to edit or delete an issued document.
- 003
Sequential, secure numbering
Document numbers are locked atomically on the server at issue time. An issue that fails midway releases the number back - the sequence never breaks and a number is never burned by mistake.
- 004
Secrets encrypted at rest
Sensitive connection details (like the Tax Authority connection) are encrypted with AES-256-GCM in the database, and never stored or shown in plain text on any admin screen.
- 005
AI that suggests, never writes
Every AI feature - receipt recognition, the "ask your books" assistant, document drafting - produces a suggestion only. No AI code writes directly to a document, expense, or customer message without explicit human approval.
- 006
Retention as the law requires
Fiscal documents are kept for 7 years as Israeli law requires, even if the account is closed - not as internal policy, but as a mechanism that cannot be bypassed.