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.

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.

1. Scope

This policy covers the public Cenora Technologies website and the Cenora Laundry Management Platform. Where a business uses the platform to serve its own customers, that business determines what operational data it records; Cenora processes it on that business's behalf.

2. Information collected through this website

The website collects information you submit through the enquiry form:

• Name
• Company or business name
• Email address
• Phone number, if you choose to provide it
• Business type and enquiry type
• The content of your message

The website does not run advertising trackers or third-party analytics profiling. It loads a web font stylesheet from Google Fonts and a 3D rendering library from a public CDN; those providers receive the network request required to serve those files.

3. How website information is used

Enquiry details are used to respond to your enquiry and to hold the resulting business correspondence. They are not sold.

4. Data inside the platform

Businesses using the platform record operational data such as customer records, addresses, orders, garments, workflow events, invoices and payment records. That data belongs to the business operating the account and is held within its tenant boundary.

5. Sharing

Operational data is not shared between tenants. Service providers used to host or operate the platform may process data strictly to provide that service.

6. Retention

Enquiry correspondence is retained for as long as needed to handle the enquiry and any resulting relationship. Platform data is retained according to the agreement with the business operating the account.

7. Your choices

You can ask for correspondence you have sent through this website to be corrected or deleted. If you are a customer of a business that uses Cenora, direct requests about your operational records to that business, which controls them.

8. Changes

If this policy changes, the updated version will be published on this page.

1. About these terms

These terms apply to your use of the Cenora Technologies public website. Use of the Cenora Laundry Management Platform itself is governed by the separate agreement between Cenora and the business operating the account.

2. Use of the site

You may browse the site and submit enquiries for legitimate business purposes. You agree not to attempt to disrupt the site, gain unauthorised access, submit malicious content through the enquiry form, or use automated systems to send bulk submissions.

3. Content and intellectual property

The Cenora name, the platform, site copy, interface designs and visual material are the property of Cenora Technologies unless stated otherwise. Nothing here transfers a licence to reuse them.

4. Product information

Interface visuals and figures shown on this site are demonstrations using fictional data, labelled as such. They illustrate the product interface and do not represent any real business's results, and no performance outcome is promised by them.

5. Third-party services

The site loads typography and a 3D rendering library from public content delivery networks. Their availability is outside Cenora's control.

6. Liability

The website is provided for information. To the extent permitted by applicable law, Cenora is not liable for losses arising from reliance on website content.

7. Governing law and entity details