Organizational isolation
PostgreSQL with forced RLS separates organization data. The organization ID comes from the session, not the request header.
Not yet accepted for production use

PostgreSQL with forced RLS separates organization data. The organization ID comes from the session, not the request header.
The administrator confirms login with the TOTP code. Passwords are stored as scrypt hashes.
Change history is added and hashed. The app account cannot edit or delete it.
Payment keys are AES-256-GCM encrypted. The master key is stored outside the repository and applications.
Backup restoration has been tested in practice.
The offline queue in the application is encrypted with SQLCipher. The key and session are in a secure system store.
The session receives a random token. Only its SHA-256 hash is saved in the database.
API checks role and organization on every read and write.
The idempotence key and record version protect against replaying and overwriting someone else's change.
Each change goes into the history with its author and time.
PostgreSQL with forced RLS separates organization data. The application account does not have permission to bypass this policy.
Administrator logs in with password and TOTP code. Passwords are stored as scrypt hashes.
Session tokens are 256 bits long; only their SHA-256 hashes are stored in the database. Write operations require a valid Origin header and CSRF token.
The operation key protects against double writes, and the record version against overwriting someone else's change.
The history is appended and linked with hashes. The app account cannot change or delete it.
Stripe, Przelewy24 and Fakturownia keys are AES-256-GCM encrypted on the server. They don't go to the browser or APK.
Restoring a database backup has been tested in practice, not just described in a procedure.
The application's change queue is encrypted with SQLCipher and the key is in a secure system store.
We do not declare ISO certification or audited compliance. The mechanisms described have been pilot tested. Pentest and legal review are conditions of production.
No. The organization's isolation is enforced by the database and API. The tests included attempts to read data from another organization.
No. The hash chain makes it difficult to change history undetected, but it is not a qualified signature or an external WORM archive.
JPG, PNG and WebP photos up to 10 MB. The system checks the file type by content and makes it available only to authorized people.
Choose a product and a conversation topic. The request will receive a number and go to the service center; We will respond to the address provided.