Website terms

Project engagements

A separate written agreement defines deliverables, acceptance, fees, GST treatment, ownership, third party licences and support. Illustrative workflows demonstrate a concept and do not report customer performance.

Information and availability

Service information may change as a project is scoped. No live service is purchased, activated or provisioned through this preview. These website terms do not exclude rights that cannot lawfully be excluded.

Use service descriptions as a starting point

The service and solution pages explain the kinds of work that can be discussed with Cobnex. They do not determine the scope, price or timing of a particular engagement. A project may require discovery before dependencies and acceptance criteria can be confirmed. Examples describe possible workflows and should not be read as evidence of a named customer result.

Technical resources support evaluation and planning. Their usefulness depends on the system, data and operating conditions in which they are applied. Check an approach against your own requirements before relying on it in production. Where a regulated or specialist decision is involved, obtain advice from the appropriate qualified person.

Agree the commercial and delivery record separately

A written engagement should identify the parties, deliverables, assumptions, exclusions and the process for accepting work. It should also explain how a requested change affects price, timing and responsibilities. These details cannot be established by a general website description or a locally generated project brief.

Ownership of existing materials, newly created work and third party components needs to be addressed in the relevant agreement. So do licences, subscription costs, maintenance and access after handover. A technology mentioned on this website is not automatically included in an engagement and does not imply a formal relationship with its provider.

Understand the contact tools in this review site

The project brief, enquiry and support forms create local documents for review. They do not submit an order, send a message or establish a support response time. Saving a draft stores information in the browser profile. Downloading a document creates a file that you can inspect and share through an agreed channel.

Do not use the support draft as an emergency notification mechanism. An existing customer should use the escalation route in their service agreement for an active incident. Service hours, incident priorities and response commitments need to be agreed for the actual service. They are not created by selecting a priority in a form.

Respect the material and its context

When sharing a resource, retain enough context that the guidance is not presented as a guarantee or an endorsement of a different service. Brand assets should be used consistently with the accompanying guidance. Do not publish confidential information, impersonate another party or use the site to interfere with someone else's systems.

Website information may be corrected or updated as the service descriptions develop. A downloaded copy can become outdated, so check the source page when making a new decision. The terms of a separately agreed engagement take account of that engagement's circumstances. This preview does not replace the need to establish those terms with the relevant parties.