Echo One /

Clinical-platform terms of service

A clear agreement for the work around care.

Terms for organisational use of Echo One. Service access and clinical processing require an accepted order and the applicable agreements.

Last updated · 25 September 2026

01

The agreement at a glance.

  • These service terms apply when incorporated into an order accepted by Echo and an authorised customer representative. Browsing this page or joining the waitlist does not create a paid subscription.
  • Only the agreed features, sites, users, intended uses and service commitments are included. Preview screens do not add contractual promises.
  • Session pricing, payment, renewal and exit conditions must be written into the accepted agreement before charges begin.
  • The customer retains its rights in its information. Processing, providers, retention and export arrangements must be agreed before clinical data is supplied.
  • Clinicians review and decide on clinical outputs. Echo remains responsible for its own contracted obligations and applicable legal duties.
  • Mandatory consumer rights and lawful access to clinical records are preserved.

Using the public website

Browsing, whitepaper downloads, copyright, search indexing and automated collection are covered separately.

Read website terms
02

Parties, acceptance and contract documents.

Visualisation Hub Pty Ltd trading as Echo Health AI supplies the service to the organisation named in an agreed order. An authorised representative must accept the final service terms and order before access begins. Browsing the website or registering interest does not accept a subscription. The final order must identify the service version, sites, permitted users, start date and intended use. Proposed precedence: the data-processing schedule controls privacy conflicts; expressly agreed order variations control commercial conflicts; these terms and the incorporated usage policy govern the remainder.

03

What Echo provides.

Echo will provide the features and implementation services in the accepted order with due care and skill, maintain the agreed security measures and support, and address reported faults under the agreed process. Availability targets, support hours, response priorities, recovery objectives and maintenance arrangements must be stated in the service schedule. Service-level commitments are set out in the agreed service schedule.

04

Customer administration and permitted users.

The customer appoints authorised administrators, keeps user access and professional roles current, protects credentials and ensures users are appropriately trained. Access is limited to the organisation's authorised purposes and contracted scope. The customer must promptly remove access that is no longer needed and notify Echo of suspected compromise. Echo must enforce its own agreed access and isolation controls.

05

Clinical and AI responsibilities.

AI outputs can be incomplete or incorrect. Qualified users must meaningfully review, correct or reject clinical drafts before accepting or sharing them and retain responsibility for their clinical decisions. Echo must maintain the safeguards agreed for those workflows and investigate reported defects. Human review does not excuse a supplier defect or establish regulatory exemption. Features requiring authorisation may only be used within the approved intended use and deployment scope.

06

Patient information, consent and privacy.

The customer must have authority to supply information and arrange the notices and consent required for recording, processing and sharing. Echo may process customer information only for the agreed purposes and documented instructions, subject to applicable law. The data-processing schedule must identify data categories, services and providers, locations, security measures, retention, incident handling, assistance with individual requests and exit arrangements. Neither these terms nor de-identification alone grants a general right to train models on customer data.

07

Session-based fees and usage.

Fees use the session model agreed in the order. The session definition, annual estimate, capacity, practice fees, included services, messaging and other metered charges, implementation costs, GST and currency must be explicit. Rates remain unpublished. Rollover, top-ups, excess use, renewal and payment timing remain open commercial decisions; no fee, penalty or automatic renewal is created by this page. Disputed amounts and any usage discrepancies require a documented review process.

08

Integrations and external services.

The order must identify supported integrations, required third-party subscriptions and each party's configuration responsibilities. Third-party terms must be supplied where they apply. Echo remains responsible for obligations it has accepted, including contracted subcontractor oversight. Changes or outages affecting an integration require assessment, communication and agreed continuity arrangements; the customer should not assume every connection shown in a preview is available.

09

Customer information and intellectual property.

The customer and relevant rights holders retain rights in their information. Echo receives a limited permission to process it to provide the contracted service. Echo and its licensors retain rights in the platform and general materials. Access does not transfer ownership of the software. The agreement must preserve the customer's ability to use and export its records and reviewed outputs, subject to applicable law and third-party rights.

10

Confidentiality.

Each party must protect the other's confidential information, use it only for the agreement and disclose it only to people who need it and are subject to appropriate obligations. Lawfully required disclosure is permitted, with notice where lawful and practicable. Public information, information independently developed and information lawfully received without restriction are excluded. Personal information remains subject to the data-processing obligations.

11

Service changes and evaluation features.

Material changes to contracted functionality, processing or fees require the notice and change process in the final agreement. Changes must not silently expand a permitted clinical purpose or data use. Evaluation features require defined scope, data restrictions, supervision and acceptance criteria. A materially adverse change should have a proportionate remedy or exit route; these terms give neither party an unrestricted right to rewrite the bargain.

12

Security incidents and continuity.

Each party must promptly raise incidents affecting the service or relevant data and cooperate on containment, investigation, recovery and lawful notifications. The final schedule must specify contacts, contractual notification timing, escalation, preservation of evidence and communications responsibilities. Statutory duties apply independently. Notification commitments and processing locations must be confirmed in the deployment schedule; this page does not establish a fixed notification deadline or Australia-only hosting.

13

Suspension and termination.

Restrictions should be necessary and proportionate to a material breach, serious security threat or legal requirement. Give notice and a reasonable opportunity to remedy where practicable, explain the affected scope and restore access when the cause is resolved. The final agreement must set the term, renewal mechanism, cure periods and termination rights for material breach, prolonged failure or insolvency. Continuity of care and lawful record access must be considered before restricting a clinical service.

14

Exit, export and deletion.

The customer must have an agreed process to export records in a documented usable format, including relevant attachments and provenance. The final schedule must set the request window, assistance, any agreed charges, verification of transfer, residual access, legal holds and deletion from active systems and backups. Termination is not authority to destroy records that must be retained. Deletion follows the agreed schedule and applicable record obligations, including any lawful hold.

15

Warranties, remedies and responsibility.

Nothing excludes rights or remedies that cannot lawfully be excluded, including applicable Australian Consumer Law guarantees. Each party remains responsible for its own acts, omissions and obligations. The allocation of liability, any cap, insurance requirements and any narrowly defined indemnities require legal and commercial approval. Clinician review does not remove Echo’s responsibility for its own conduct, and this page imposes no unlimited customer indemnity or blanket exclusion for patient harm.

16

Disputes, notices and governing law.

The parties should first escalate a dispute to authorised representatives and try to resolve it in good faith, while preserving urgent relief and statutory rights. Send legal or privacy enquiries to security@echo-health.ai; formal notice details belong in the order. The accepted agreement must state the governing law and dispute jurisdiction. Victoria, Australia with non-exclusive jurisdiction is the proposed position, subject to mandatory applicable laws and final review.

17

What must be completed before acceptance.

  • Accepted order and intended use, feature scope and deployment assessment.
  • Final session definition, rates, capacity, payment, renewal and exit conditions.
  • Current data-processing annex, provider and location schedule, and retention decisions.
  • Service levels, support, incident-notification commitments and continuity plan.
  • Reviewed liability and remedy provisions, notice addresses and final legal approval.

Platform privacy

The clinical information lifecycle and the questions the final notice must answer.

Read platform privacy

Acceptable use

Practical responsibilities for access, AI review and incident reporting.

Read acceptable use