Status: Pre-launch draft for professional review. It is not final contractual wording.
1. Purpose
Queux is intended for authorised kitchen operations, meal-service planning, recordkeeping, training administration, support and related organisation or site management. Users must act within their role, their organisation’s instructions and applicable law.
2. Accounts and access
Users must use their own account, protect authentication factors, keep recovery details current and report suspected compromise promptly. They must not access another organisation or site without explicit authority, probe identifiers, share sessions, bypass role controls or misuse support access.
3. Prohibited technical activity
Users must not introduce malware; disrupt or overload the service; evade rate limits; scrape or automate access outside documented interfaces; reverse engineer where prohibited by law; test vulnerabilities without written authorisation; intercept another user’s traffic; or attempt to defeat file, webhook, payment or tenant-isolation controls.
4. Content and records
Users must not upload content they lack authority to use, unlawful material, malicious files, unnecessary sensitive personal information or misleading records. They must not falsify operational history, impersonate an approver, silently work around amendment controls or represent a draft as approved.
5. Compliance and professional claims
Users must not present Queux completion states, templates, reports or AI-assisted drafts as proof of legal compliance, regulatory approval, nutritional compliance, a recognised qualification, medical advice or professional certification unless an appropriately authorised and qualified person has independently made and documented that determination.
6. Personal information
Users should enter only the minimum information needed for the authorised operational purpose. Child names, diagnoses, complete medical records, family information and full attendance files must not be copied into Queux merely for convenience. Customers remain responsible for permissions, notices and appropriate handling.
7. Integrations and credentials
Users must connect only providers they are authorised to use, follow provider terms, protect credentials and avoid importing fields outside the approved scope. They must not represent a manual or demonstration data source as a live provider synchronisation.
8. Automation and optional AI
Automation must not be used to create abusive traffic, bulk accounts or unauthorised changes. AI-generated material must remain clearly labelled and subject to human review. Users must not ask AI features to invent allergens, nutritional compliance, legal obligations, mandatory limits, expiry dates, medical advice or approvals.
9. Fair use of staff accounts and resources
“Unlimited reasonable staff users” is intended for genuine people supporting the subscribed site. It does not allow account resale, automated account fleets, unrelated organisations, credential pooling or disproportionate use that threatens service stability.
10. Investigation and enforcement
Queux may investigate suspected misuse and take proportionate steps to protect people, tenants and systems, including limiting activity or suspending access where necessary. Notice and restoration processes must be settled in the final terms, subject to urgent security or legal constraints.
11. Reporting concerns
Report suspected misuse or a security issue to support@queux.com.au. Do not include passwords, payment-card details or unnecessary personal information in the report.