ERPONA
AZENRU
Request a demo
Security

What is protected, and how

What follows are existing mechanisms, not promises. Every item corresponds to a working part of the system.

Last updated: 2 September 2026

Access control

Everyone does only their own job

01

Role sets

Screen permissions are grouped into role sets: director, finance, HR, production, retail. The implementer is not lost among dozens of technical groups.

02

Row level

Model-level permission is not enough: rules decide which ROWS are visible - another company's document, for instance, is not.

03

Single sign-on

Login through an OIDC provider with the role assigned automatically. When someone leaves, access is closed in the central directory.

04

Audit trail

The audit trail is a separate financial report: who made an entry and when is visible.

05

Period lock

Nothing posts into a closed period. That prevents accidental edits and keeps reports stable.

06

Retention policy

A document cannot be deleted before its period is over; afterwards it is archived. There is no automatic deletion - an irreversible operation was deliberately left out.

Protecting the data

Backups, encryption, ownership

Backups

  • A nightly automatic copy: the database (SQL) and the file store
  • Save only the database and every document attachment is lost on restore
  • Restores are tested monthly on a test database - an untested backup is not a backup
  • Retention and location of copies are written into the contract

Network and encryption

  • All traffic is HTTPS; HTTP requests are redirected
  • TLS 1.2 and 1.3; certificates renew automatically
  • Exposing the panel to the internet is not required - it can run inside the company network
  • Requests with an unknown host are closed without a response

The data is yours

  • A full copy of the database is available at any time
  • The format is open: a PostgreSQL dump plus the file store
  • Reports export to CSV
  • The system can be kept on your own server

Updates and faults

  • Before a release, a full install and test suite run on an isolated database
  • If the system is down, the browser gets an explanatory page, not a grey error
  • A health check runs as a separate script

⚠ This page describes technical mechanisms. Concrete commitments - response times, where and how long backups are kept, access procedures - are written into the contract and the SLA.

Reporting an issue

Found a security problem?

Write to info@erpona.app. Telling us before making it public gives us time to fix it.