Skip to content
Theatre foyer with staff welcoming visitors to an event

Security

Data security

Organisation isolation, role checks, an operations log and protected sessions. A formal audit remains a separate stage.

Database-level data separation

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

Roles and venues

Cashiers, front-of-house staff, instructors, managers and administrators have separate permissions. Access is determined by their role in the organisation.

Administrator MFA

Administrator accounts require a one-time code. Sessions use HttpOnly cookies.

Immutable records

Sales, refunds, consent and change history are appended to the record. The application cannot overwrite or delete them.

Idempotency and locks

A repeated request cannot create a second payment, ticket or admission. Version conflicts are reported instead of overwriting changes.

Backups and retention

Backups are tested for restoration before each release. Data retention rules are agreed during implementation.

Personal data protection

  • Separate consent for communication channels and profiling
  • Consent history linked to the wording version
  • Children's data limited to enrolment and guardian consent
  • Data exports within the user's permissions
  • Data-retention periods agreed for each implementation
  • Privacy and cookie policies in the portal

Before going live

  • Legal review of terms and the data-processing agreement
  • Data protection impact assessment (DPIA), where required
  • Penetration testing and configuration review
  • Accounting review of sales documents
  • A backup-restoration rehearsal
Audience in front of a concert stage

See how NexaCulture can work for your institution.

Android app