Database-level data separation
Each institution can see only its own records. PostgreSQL row-level security enforces this boundary, not just the interface.

Security
Organisation isolation, role checks, an operations log and protected sessions. A formal audit remains a separate stage.
Each institution can see only its own records. PostgreSQL row-level security enforces this boundary, not just the interface.
Cashiers, front-of-house staff, instructors, managers and administrators have separate permissions. Access is determined by their role in the organisation.
Administrator accounts require a one-time code. Sessions use HttpOnly cookies.
Sales, refunds, consent and change history are appended to the record. The application cannot overwrite or delete them.
A repeated request cannot create a second payment, ticket or admission. Version conflicts are reported instead of overwriting changes.
Backups are tested for restoration before each release. Data retention rules are agreed during implementation.
