Status: Pre-launch draft for professional legal review. No commercial customer should rely on this draft as the final agreement.
1. About Queux
Queux is a subscription kitchen-operations platform. It organises information used for meal planning, recipe quantities, shopping, daily tasks, operational records, handbooks, training records, handover and reporting.
In these terms, “customer” means the organisation that subscribes to Queux, “site” means a physical meal-service location configured by that customer, and “authorised user” means a person the customer permits to use its workspace.
2. The service boundary
Queux supports operational and recordkeeping processes. It does not certify compliance, replace an approved Food Safety Plan or Program, determine legal obligations without human review, invent mandatory critical limits, issue nationally recognised qualifications, or provide legal, medical or dietetic advice.
The customer remains responsible for deciding which laws, plans, limits, procedures, qualifications and approvals apply to each site and for obtaining appropriate professional advice.
3. Accounts and authority
A person creating a customer account must be authorised to act for the organisation. The customer is responsible for accurate account information, allocating appropriate roles, removing access when no longer needed, and protecting authentication factors.
Accounts must not be shared between people. An authorised user must notify the customer promptly if they suspect unauthorised access.
4. Customer configuration and content
The customer controls its site configuration, uploaded documents, recipes, forms, limits, approvals and operational records. Queux may provide standard templates or draft content as a starting point. The customer must review and approve applicable content before relying on or publishing it.
Published content and finalised submissions may be preserved as immutable history. Corrections can require a new version or amendment with an actor, time and reason rather than an overwrite.
5. Subscription and payment
Pricing, GST treatment, billing interval, included sites, optional services and renewal terms are shown during the commercial order and account setup. The current public launch price is described on the pricing page, but the accepted order should control if it differs.
Payment processing is intended to use a configured payment provider. Queux does not store payment-card details. Rules for failed payment, renewal, cancellation, credits and refunds require confirmation in the final legally reviewed terms.
6. Acceptable use
The customer and its users must follow the Acceptable Use Policy. They must not attempt unauthorised access, bypass tenant boundaries, interfere with service operation, upload malicious content or use Queux to mislead others about compliance or qualifications.
7. Data and privacy
Each party must handle personal information consistently with applicable law and its role. The intended practices are described in the Privacy Policy draft and Data Processing Terms draft.
The customer must only provide personal information it is authorised to use and should minimise identifiable information. Kitchen calculations are designed around aggregate room, meal, dietary and texture counts by default.
8. Integrations and third parties
Provider integrations depend on supported access, documentation, credentials, permission and any applicable agreement. A named provider is not represented as live unless an authorised connector is enabled. Manual entry and CSV workflows may remain available.
Third-party services have their own terms, availability and security responsibilities. The customer is responsible for authorising a connection and for charges imposed directly by a third party unless an accepted order states otherwise.
9. Intellectual property
The customer retains rights in content it supplies. The intended subscription grants the customer a limited right to use Queux during the subscription term. Queux retains rights in the platform, original templates, brand assets and documentation, subject to any identified third-party licences.
The final agreement should specify the licence needed for Queux to host, process, back up and display customer content solely to provide and protect the service.
10. Availability, support and change
Queux may require maintenance, security updates and product changes. Any service-level commitment, support hours, notice period, backup commitment or data-recovery objective must be stated in the accepted order or final agreement rather than inferred from marketing copy.
11. Suspension and termination
The final terms are expected to permit proportionate suspension for material security risk, unlawful use, serious misuse or unresolved non-payment, with notice where reasonably possible. Customer access, export periods, retention and deletion after termination must be settled in the final agreement and data-processing terms.
12. Warranties and liability
Any warranties, consumer guarantees, exclusions, indemnities and liability limits must be drafted and reviewed by qualified Australian counsel. Nothing in final terms should exclude a right or remedy that cannot lawfully be excluded.
No statement in this draft is a promise that software will prevent every error, security event, service interruption, food-safety issue or regulatory breach.
13. Governing law and notices
This draft assumes South Australia and applicable Commonwealth law as the intended governing framework, subject to professional confirmation and any mandatory law. Formal notice methods and the contracting entity must be settled before commercial launch.
14. Contact
Questions about this draft can be sent to support@queux.com.au.