SECURITY & DATA

Security built into every data record.
Isolation, audit and encryption.

Not yet accepted for production use

Key features: Security

Organizational isolation

PostgreSQL with forced RLS separates organization data. The organization ID comes from the session, not the request header.

MFA for administrators

The administrator confirms login with the TOTP code. Passwords are stored as scrypt hashes.

Hash chain audit

Change history is added and hashed. The app account cannot edit or delete it.

Encrypted key vault

Payment keys are AES-256-GCM encrypted. The master key is stored outside the repository and applications.

Backups with restore test

Backup restoration has been tested in practice.

Encrypted phone memory

The offline queue in the application is encrypted with SQLCipher. The key and session are in a secure system store.

REAL SCREENS

This is what it looks like
in the working version.

  • Users and rolesTeam accounts, roles, access lockout and MFA for admins.
  • Operations dashboardcollections, fleet, notifications and PSZOK on one screen, with access to details.
  • Analytics and reportsReports with the described data source and export of PDF, XLSX, CSV.
Actual product screens: Users and roles. Click on the screen to see the next one.
HOW IT WORKS
  1. 01Login

    The session receives a random token. Only its SHA-256 hash is saved in the database.

  2. 02Permissions

    API checks role and organization on every read and write.

  3. 03Save

    The idempotence key and record version protect against replaying and overwriting someone else's change.

  4. 04Audit

    Each change goes into the history with its author and time.

SECURITY
Organizational Isolation (RLS)

PostgreSQL with forced RLS separates organization data. The application account does not have permission to bypass this policy.

Admin MFA

Administrator logs in with password and TOTP code. Passwords are stored as scrypt hashes.

Secure sessions

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.

Idempotence and versions

The operation key protects against double writes, and the record version against overwriting someone else's change.

Hash chain audit

The history is appended and linked with hashes. The app account cannot change or delete it.

Payment key vault

Stripe, Przelewy24 and Fakturownia keys are AES-256-GCM encrypted on the server. They don't go to the browser or APK.

Backups with restore test

Restoring a database backup has been tested in practice, not just described in a procedure.

Encrypted offline storage

The application's change queue is encrypted with SQLCipher and the key is in a secure system store.

SCOPE IN PILOT VERSION

What works today,
and what requires configuration.

Running on the system
  • RLS isolation, roles and permissions checked by API
  • Admin MFA, scrypt passwords, CSRF and Origin protection
  • Idempotence, version control and hash chain auditing
  • Encrypted payment key vault
  • Backups with restore test
  • Attachment type and size control
Requires your or provider details
  • Independent penetration test
  • GDPR review, data processing agreement and retention policy
  • Antivirus scanning of attachments

Frequently asked questions

Is the platform security certified?

We do not declare ISO certification or audited compliance. The mechanisms described have been pilot tested. Pentest and legal review are conditions of production.

Can company A see company B's data?

No. The organization's isolation is enforced by the database and API. The tests included attempts to read data from another organization.

Does an audit replace a qualified signature?

No. The hash chain makes it difficult to change history undetected, but it is not a qualified signature or an external WORM archive.

What files can be added to the report?

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.

LET'S START WITH YOUR NEEDS

A cleaner city.
A more efficient team.
Let’s talk.

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.

Presentation of real screensScope tailored to processesClear stages and acceptance criteria

Operational contact does not require marketing consent.