Security

Built with control in mind.

How access, isolation and traceability are handled in the Cenora Laundry Management Platform.

Scope: this page describes design principles of the platform. It is not a certification statement. Cenora does not claim ISO, SOC 2, HIPAA, GDPR or any other compliance certification. Specific controls in a given deployment depend on how that deployment is configured and hosted.

Authentication

Access to the platform requires an authenticated account. Users are identified before any operational data is returned, and sessions are tied to that identity.

Authorization

Authentication establishes who a user is; authorization determines what they can act on. Requests are checked against the permissions attached to the account, so being signed in is not by itself sufficient to reach a given record or action.

Tenant isolation

Each business operates within its own tenant boundary. Records belonging to one business are not addressable from another, and that boundary is applied at the data-access layer rather than only in the interface.

Role-based access

Permissions are granted through roles that reflect operational responsibilities — floor staff, station operators, supervisors, administrators. Branch scoping can further narrow what a role can reach in multi-location businesses.

  • Roles describe operational responsibility rather than individual exceptions.
  • Branch scoping limits visibility to relevant locations.
  • Administrative actions are separated from everyday operational actions.

Auditability

Operational events — stage changes, order updates, handovers — are recorded against the records they affect, so the history of an order can be reviewed rather than reconstructed.

Data integrity

Orders, garments, workflow stages and invoices are stored as related records rather than duplicated across systems, which reduces the chance of two parts of the business disagreeing about the same order.

Infrastructure considerations

Secrets and credentials are held in server-side configuration and are never delivered to the browser. Database access runs through the application layer rather than being exposed directly to clients.

Requires confirmation per deployment: hosting region, backup schedule, encryption-at-rest configuration and retention periods depend on the infrastructure chosen for a given deployment and should be documented before publication.

Security principles

  • Least privilege: accounts receive the access their work requires.
  • Isolation by default: separation between tenants and branches is structural.
  • Traceability: significant operational actions leave a record.
  • No client-side trust: authorization decisions are made server-side.
  • Honest claims: we describe controls that exist rather than certifications we do not hold.