Skip to content

Terms of Service

Last updated 22 November 2026. Version 2026-11-22.1

1. Parties and scope

1.1 Solvaxis Pty Ltd (ABN 67 703 502 881), trading as DirectHostPay (Solvaxis, we, us or our), supplies the DirectHostPay website and booking administration software (Service). These Terms apply to people who create or operate a Host account (Hosts) and people who use Guest-facing features (Guests), to the extent they have accepted the Terms and the provisions concern their use.

1.2 A Stay Agreement is an agreement for accommodation between an independent Host (or the identified accommodation supplier represented by a Host) and a Guest. A Booking Link is a private link containing the Host's proposed booking terms and payment options. A Payment Provider is Stripe, PayPal, a bank or another provider used for accommodation payments.

1.3 Hosts accept these Terms by ticking a box at signup, including Google signup. We record the time and version on our server. For each booking, Guests tick three separate boxes to accept the Host’s Stay Agreement, the Host’s house rules and these Terms. We record the Terms version with the signed agreement. All boxes start unticked. The Privacy Policy explains how we handle information. It does not waive statutory privacy rights or give blanket marketing consent.

1.4 An individual registering for an organisation warrants that they are authorised to bind it. The Host must be at least 18, provide accurate account information and have legal authority to offer or manage the relevant property.

1.5 No clause limits a non-excludable consumer guarantee, statutory right, privacy obligation or other protection under applicable Australian law.

Back to contents

2. How the Service works

2.1 Hosts license the software for a flat annual subscription. Features may include Host enquiry pages and embedded forms, Host-generated Booking Links, agreements and electronic acceptance records, pricing and payment schedules, calendar imports and exports, receipts, Guest records, email reminders and connections to Host payment accounts.

2.2 A Guest may contact a Host independently or make a non-binding enquiry through the Host’s request page, QR code or website. Only the Host decides whether to offer a stay, sets the dates, price and house rules, and selects a cancellation policy from those available for the property. The Booking Link shows the Host’s offer, including any expiry and other disclosed conditions.

2.3 We do not list Hosts in a public Guest directory, independently select Hosts for Guests, accept enquiries automatically, set accommodation prices, own or manage properties, supply accommodation or guarantee a Host’s performance.

2.4 The supplier named in the Stay Agreement supplies the accommodation. The Host may be the supplier or its authorised representative. Guests pay through accounts the Host connects or nominates. Solvaxis neither receives nor holds accommodation proceeds and charges no booking commission.

2.5 Solvaxis operates the software and its authorised Stripe integrations. On the Host’s connected account, we initiate PaymentIntents, save a card when the Guest chooses, and initiate charges without the Guest present on or after the agreed date, automatically or on the Host’s instruction. We process payment and refund events and send the Host’s confirmed card refund instructions to Stripe (clause 5.6). We do not claim to have no technical involvement in payment administration.

2.6 These factual descriptions do not decide whether a law classifies the Service as a booking service, booking platform, electronic distribution platform or another regulated activity. Solvaxis will comply with obligations that apply to it under the relevant legal definition.

Back to contents

3. The Host's accommodation business

3.1 Each Host is responsible for their legal right to offer the property and for accurate descriptions and the dates they offer, safe premises, access, amenities, lawful maximum occupancy, and all accommodation operations. Hosts must meet the requirements that apply to them, including registration and licensing, fire and building safety, planning and strata restrictions, short-term accommodation codes, levies, taxes and insurance.

3.2 The Host must set lawful prices and house rules and choose the cancellation policy for its stays. Before sending a Booking Link, check the supplier’s full legal name and the stay contact details. A representative must disclose its role and have authority to make the offer. If someone else will receive payment for the supplier, confirm their authority and explain the difference to the Guest before payment. The Service may suggest the Host’s signup name. We rely on the Host’s details without independently verifying the supplier’s identity or the Host’s or payee’s authority. The Host may charge a saved card only as the Stay Agreement permits or the Guest separately agrees, whether through the Service or directly through Stripe. The Host must not use the Service for any other saved-card charge.

3.3 Hosts are responsible for supplying the accommodation as promised, dealing with Guest complaints, refunds, changes or alternative accommodation where legally required, damage claims and lawful Guest removal. Solvaxis does not assume these accommodation obligations by providing a booking administration system.

3.4 Hosts must not present Solvaxis as the property owner, accommodation supplier, guarantor or insurer. Hosts must comply with relevant anti-discrimination, consumer, privacy, direct-marketing and other laws.

3.5 None of these allocations releases Solvaxis from liability for its own actionable conduct or duties legislation imposes directly on Solvaxis.

3.6 The Service may remind Hosts of some State or Territory requirements, such as managing a short-stay levy or showing a registration number. A reminder is general information, not legal advice, and does not mean Solvaxis has checked a Host's compliance or decided who is liable for a levy.

3.7 Hosts must follow the terms of any other site or service where they offer the property, including rules on moving bookings, payments or Guest communications elsewhere and reusing photos, descriptions, reviews or other content. Connecting a calendar or using the Listing Importer gives no permission under those terms. Solvaxis does not check compliance with them.

Back to contents

4. Enquiries, offers, acceptance and payments

4.1 An enquiry does not oblige the Host to offer a stay. A Booking Link can hold dates in the Host’s DirectHostPay calendar before a booking is complete.

4.2 The Host chooses whether to send a Booking Link, specifies the price and terms, and can cancel or replace that link subject to any legal commitment already arising between Host and Guest.

4.3 A Booking Link normally holds dates for 72 hours. A valid card checkout or check may extend the hold. Reporting a PayID or PayPal transfer can leave payment pending without a time limit. Saving a card for later can hold dates in DirectHostPay until payment. Even after acceptance or payment, a hold cannot guarantee that dates remain available elsewhere or that external calendars are up to date.

4.4 The Guest reviews and accepts the Stay Agreement, house rules and these Terms separately (clause 1.3). We keep the signed Stay Agreement and house rules as accepted, the acceptance record and the Terms version. We archive each published Terms version separately. Whether and when the accommodation contract binds the parties depends on their actual offer and acceptance, including earlier independent communications, the payment facts, agreed terms and applicable law. The software status alone does not decide this.

4.5 The Host’s selected cancellation policy fixes the charge day a set number of Sydney calendar days before check-in. The Stay Agreement gives the date. Before that day, a Guest booking by card saves a card and pays nothing upfront. The Service automatically charges the full price on the charge day. On or after that day, a Guest booking by card pays in full when booking. PayID and PayPal payments are always due in full when booking, without saving a card.

Hosts cannot change the schedule or charge day or disable saved cards while accepting cards. A saved card is not charged for the stay before the charge day. A charge may be delayed as the Stay Agreement describes, including if the card is saved on or after the charge day, a cancellation request awaits the Host’s answer, or clause 12.5 applies. No charge may be made later than 30 days after check-out. If it fails, the Guest pays from the Booking Link (clause 6.1). The Service is designed to email the Guest before the scheduled charge. Delivery is not guaranteed.

4.6 Guests should check or provide accurate identity, contact and payment details, protect their private Booking Link and promptly report any material payment discrepancy to the Host. Contact details already entered by the Host are partly hidden and used unless the Guest changes them.

4.7 The Host is responsible for responding to enquiries, communicating confirmed conditions and honouring statutory and contractual rights on cancellation of a link or booking. Only the Host cancels a booking in the Service. Selecting ‘Ask to cancel’ on a Booking Link records the request time and notifies the Host. It does not cancel or refund the booking. While the request is pending, the Guest cannot pay through the link and the Service does not charge the saved card.

Under the available policies, the day the Guest asks through the link determines the refund position. If the Guest asked before the charge day, the Host’s only option in the Service is to cancel. If the Guest asked on or after it, the Host may keep or cancel the booking. If kept, a waiting charge is made on the charge day or afterwards if that day has passed. For a Guest request made outside the link, the day the Host cancels counts. The Host pays any refund (clauses 5.4 to 5.7).

Back to contents

5. Accommodation payment methods, refunds and disputes

5.1 Hosts choose the supported payment methods they offer. Card and supported wallet payments use Stripe Connect Standard direct charges on the Host’s connected account. Stripe processes card details and stores any saved card in that account. Solvaxis keeps card references, brand, last four digits, dates saved and removed, and charge dates, amounts and outcomes. We do not store full card numbers or security codes.

The Service removes the card on full payment, cancellation or link expiry, or 30 days after check-out if money remains unpaid. It retries removal if Stripe is unavailable. If the Service loses access to the relevant Stripe account, it cannot remove the card: it records the card as removed and makes no further charge. The Host must then promptly remove the card in Stripe. A Guest can ask the Host for earlier removal. The Host must remove it promptly and the Guest must then pay any outstanding amount from the Booking Link.

5.2 PayID and PayPal.Me transfers use the Host’s own arrangements. There is no verified PayPal API integration. Guests must use the Host’s payment details. Before confirming receipt, Hosts must check their account. Selecting ‘I've sent the payment’ does not prove funds have cleared.

5.3 Hosts are responsible for payment-provider fees, settlement arrangements, accommodation chargebacks and responding to card/payment disputes, including disputes about charges made to a saved card while the Guest was not present, subject to the relevant provider agreement and law. DirectHostPay does not add a Guest service fee or a per-booking commission.

5.4 The Host chooses each refund amount and must pay any accommodation refund due under the Stay Agreement or law. Cancelling a booking does not itself refund or charge anything. A refund does not change booking status. The Service shows recorded payments and refunds and may flag amounts for the Host to check.

Using the recorded facts, the Service may show what the signed policy provides. If the Host cancelled other than at the Guest’s request, or the Guest asked before the charge day, it may show the Host that the policy gives a full refund and how much has been sent, and tell the Guest that a partial refund does not change what the policy gives. For a request on or after the charge day, it may show the Host that no refund is due under the policy.

The Service does not otherwise calculate entitlement, decide disputes or send refund instructions without the Host’s confirmation. A refund sent or recorded does not decide, reduce or settle the Guest’s entitlement under the Stay Agreement or law. Solvaxis does not owe, pay or fund accommodation refunds. If the Service flags an unapplied payment, including a late, duplicate or incorrect payment, the Host must promptly investigate and return the amount required.

5.5 Solvaxis must provide its software and integrations with legally required care and skill. Solvaxis is not responsible for funding a Host’s accommodation refund merely because the Host used DirectHostPay, including to send a refund instruction. Solvaxis remains liable for loss caused by its own breach where liability applies.

5.6 Card refunds through the Service. For a card payment made through the Service to the Host’s connected Stripe account, the Host may issue one or more full or partial refunds up to the amount paid. A flagged payment that cannot be applied to a booking (clause 5.4) can be refunded through the Service, or recorded under clause 5.7, only for its entire unrefunded balance.

The Host confirms each amount and authorises Solvaxis to instruct Stripe on its connected account and receive status updates for refunds of Service payments, including refunds the Host makes directly in Stripe. Stripe returns funds from the Host’s account to the original card. Solvaxis does not receive, hold or fund them.

Stripe and the card issuer determine whether and when a refund completes. It may be pending, delayed or unsuccessful, including for insufficient available funds in the Host’s Stripe account. An instruction may be irreversible. The Service shows Stripe’s reported status or lack of confirmation. Neither proves the Guest’s entitlement or that the bank has credited the card. If unclear, the Host should check Stripe before retrying or advising the Guest. A failed or insufficient refund leaves the Guest’s entitlement intact. The Host bears any original fees a Payment Provider retains (clause 5.3).

5.7 Refunds outside the Service. The Host itself makes, outside the Service, any refund of a PayID or PayPal payment, or of a card payment the Service cannot refund, including one in a disconnected Stripe account. Where available, the Host may record the amount afterwards. The Guest sees this as the Host’s statement. Recording it moves no money, verifies no receipt and does not establish the Guest’s entitlement.

Back to contents

6. Scheduled charges

6.1 Each Stay Agreement states the amount, payment schedule and cancellation policy that apply to that booking. Saving a card is not payment. The Service makes one automatic charge attempt. If a charge fails, it emails the Guest a payment link and tells the Host. The Host may retry the same amount until 30 days after check-out. A failed charge does not cancel the booking. The Host decides what happens next under the Stay Agreement.

6.2 Solvaxis remains responsible for reasonable care in its own scheduled-charge software.

Back to contents

7. Calendars and taken dates

7.1 Hosts may connect up to five external iCal feeds per property and publish a DirectHostPay calendar link. We read connected feeds periodically before a subscription starts and while it is active, and as described in clause 7.2. When a subscription ends, daily reads stop until renewal. External feeds can be incomplete, delayed, inaccessible or out of date.

7.2 Link creation uses stored calendar data, which may refresh when the Host opens the page. For applicable card and manual payment methods, the Service attempts a fresh check before the Guest pays when booking or saves a card. Checks are subject to timeouts and other limitations. An apparent conflict may prevent the link or payment. If a feed is unreadable, the Service may use the last stored data and tell the Host. Later saved-card charges do not have the same checks.

7.3 Calendars help detect potential conflicts; they do not guarantee zero double bookings, real-time inventory or that an external booking service has synchronised correctly.

7.4 The Host is responsible for checking dates across its booking sources, particularly after connecting a feed, changing dates or receiving a sync warning. The Host must address conflicting commitments and contact affected Guests promptly. Solvaxis remains responsible for the care, skill and accuracy the law requires in providing its calendar tools and integrations.

Back to contents

8. Host subscriptions and pricing

8.1 Stripe ordinarily charges Hosts an automatically renewing annual subscription. The Service shows the price before purchase. Prices may differ for new subscriptions, promotions or future plans, and we may change prices for new subscribers. Before subscribing, Hosts can set up, create and send Booking Links, take stay requests and connect calendars. Before they send a link, the Service explains that Guests can pay through it only while the Host’s subscription is active (clause 12.5).

8.2 The agreed price applies throughout the paid period. A new-customer price change does not change an existing subscription. Before charging more at renewal, we will tell the Host the amount, renewal date and how to stop renewal, and obtain the Host’s agreement. Without agreement, we may keep the existing price or give reasonable notice that the subscription will end when the paid period ends.

8.3 Before payment, the Service discloses automatic renewal. Before each paid renewal, the Service is designed to email the Host the amount, date and how to cancel, timed by the billing provider’s notice. Email delivery is not guaranteed. Hosts can stop renewal through ‘Manage billing’ in their account (Stripe’s billing portal) or by contacting us. This ordinarily prevents the next charge and preserves access until the paid period ends, subject to any different remedy required by law.

8.4 A Host who changes their mind or stops using the Service during a paid period is not entitled to a subscription refund on that basis. This clause preserves any refund or other remedy required by the Australian Consumer Law or other applicable law.

8.5 Promotional access and access codes are subject to their disclosed terms. An access code cannot be used while a paid card subscription is still running (including one cancelled but not yet ended); it can be used once that subscription has ended.

8.6 Material changes to subscription features or pricing will be communicated reasonably in advance. We will not alter a paid period's agreed price retroactively.

8.7 Free access. Hosts can set up and send Booking Links free before subscribing. Promotional or code access lasts for the period disclosed and counts as active during that period (clause 8.5). We may change features available without a subscription. Before taking away a feature a Host uses without one, we will give that Host reasonable notice by email. Clause 1.5 also applies to free access.

Back to contents

9. Host Content, intellectual property and acceptable use

Host Content and Booking Records

9.1 Host Content is material or information entered, uploaded, imported or saved in the Service by or for a Host. It includes property details and names, photos, house rules, the Host’s own agreement and other Guest-facing terms, notes and Guest details the Host enters. Booking Records are the booking, payment, agreement and Guest records in the Host’s account.

9.2 The Host retains ownership of and any rights it has in its Host Content. As between the Host and Solvaxis, Booking Records are the Host’s records. While it has account access, the Host can download available copies, including signed agreements and income summaries. This does not affect Guests’ rights in their personal information or signed terms, or records Solvaxis keeps for its own purposes or by law (clauses 10.5 and 12.3).

9.3 The Host grants Solvaxis a non-exclusive, royalty-free licence to host, store, copy, process, reformat, display and transmit Host Content in Australia and overseas. We may extend the licence to our service providers (clause 11.1). These rights apply only as needed to supply, support and secure the Service, keep records under clauses 10.5 and 12.3, comply with law, or prepare aggregated or de-identified information that identifies neither Host nor Guest. Service use includes displaying content to Guests on Booking Links, receipts, emails and shared-link previews. Reformatting includes stripping location and other hidden photo data.

9.4 The licence ends for an item of Host Content when it is deleted from the Service, except for ordinary backups until they expire, agreements and house rules preserved as signed, records kept under clauses 10.5 and 12.3 or as required by law, and copies already held by others, including received emails and stored link previews.

The Host's responsibility for Host Content

9.5 As between the Host and Solvaxis, the Host alone is responsible for Host Content, including its accuracy, its lawfulness and the Host’s right to use it. Check Listing Importer suggestions before saving them as Host Content. This clause does not make the Host responsible for errors our software introduces after saving. Clause 3.5 applies.

9.6 Each time the Host adds Host Content to the Service, the Host confirms that: (a) the Host owns it, or holds every permission needed (including any commercial licence) to use it in the Service and to grant the licence in clause 9.3; (b) that permission covers use for the Host's own direct bookings and is not limited to the website or booking site where the material was first published; (c) using it as these Terms allow does not infringe any person's copyright, moral rights, trade marks, confidential information or privacy, or breach an agreement the Host has with another person, such as a photographer or a booking site; (d) any person who can be identified in a photo has agreed to its use where the law requires that; and (e) it is not false or misleading.

The Listing Importer and photos

9.7 At the Host’s request, the Listing Importer reads only the public external listing the Host links to and suggests property details. It may follow redirects or make several page requests for that listing. Suggestions are saved only when the Host saves them. Use it only for listings the Host operates or is authorised to manage.

9.8 We copy a listing’s main photo only if the Host ticks ‘I took this photo or have permission to use it’. The box starts unticked. Ticking confirms the Host took the photo or has the copyright owner’s permission to use it for its own direct bookings outside that site. Clause 9.6 applies. A photo on the Host’s listing may belong to a photographer or be licensed only for that site, including where the site arranged the photography. If unsure, leave the box unticked and add a photo you took.

How Solvaxis handles Host Content

9.9 We handle Host Content at the Host’s direction to supply the Service. We do not routinely review, edit or approve it before Guests see it, and we do not check its accuracy, its legality or the Host’s right to use it. The software processes it automatically (such as checking photos, stripping hidden data or generating links). We may look at it for requested support, a complaint, security issue or suspected breach, or as required by law. None of this is a review or approval of Host Content. This does not limit our payment, calendar or notice functions (clauses 2.5, 6.1, 7 and 10.4) or our privacy and security obligations.

Removing content and copyright complaints

9.10 We may remove Host Content or stop displaying it to Guests if we receive an infringement complaint that is not obviously unfounded from or on behalf of an apparent rights holder, reasonably believe the content infringes rights or is unlawful, or are required to act by law, a court or a regulator. We will limit action to the content concerned. Clause 12 governs account restrictions and suspension.

9.11 Where reasonably practicable and appropriate, we will tell the Host about action under clause 9.10 and may invite a response or evidence of rights. We may act without prior notice where reasonably necessary for suspected infringement, unlawful content, a security risk, legal requirement or potential harm. We may restore content where we consider it appropriate. Action under clause 9.10 does not change signed agreements or records we must keep by law.

9.12 To report copyright infringement, email support@directhostpay.com.au with the material, its location, your rights and your contact details. We may give the Host the substance of the complaint so it can respond. Direct accommodation complaints to the Host (clause 15.1).

Solvaxis's software and acceptable use

9.13 Solvaxis retains rights in its own software, branding, service design and documentation. Hosts receive a limited right to use the Service while entitled to access it, not a transfer of ownership.

9.14 Users must not use the Service for fraud, unauthorised accommodation, unlawful discrimination, spam, malicious interference, selling or sharing account access with people who are not acting for the Host (clause 10.7), payment for unrelated transactions, infringement of others' rights or unauthorised access to other users' data.

9.15 Hosts must maintain independent copies of records they are legally required to preserve, and exercise care when downloading or sharing booking and Guest information.

9.16 When a Host cancels a booking and sends a new Booking Link, the old link can no longer be used. A payment already in progress on the old link may still complete, and the Service then flags it for the Host to return (clause 5.4). Hosts must send any new link to the Guest securely.

9.17 Except to the extent the law allows it despite this clause, users must not: (a) copy, decompile, disassemble or reverse engineer the Service's software, or try to obtain its source code; (b) access or collect information from the Service using scrapers, bots or other automated means, other than through features the Service provides for that purpose, such as the DirectHostPay calendar link and the preview shown when a Booking Link is shared; (c) probe, scan or test the Service's security, or get around its sign-in, rate limits or other security measures, without Solvaxis's written permission; or (d) use the Service, or information taken from it, to build or improve a competing product. A person who finds a security weakness is welcome to report it to support@directhostpay.com.au.

Feedback and publicity

9.18 We may use, change and build on feedback for any purpose without payment or attribution. This gives us no additional rights to Host Content or personal information in the feedback. These Terms and the Privacy Policy still apply. We will not publish feedback that identifies its author without their consent.

9.19 We need the Host’s permission to use its name, business or property identity, logo, photos or testimonials in public advertising or promotions. The Host can contact us to withdraw permission for future use. We will take reasonable steps to discontinue that use in material we control. We are not responsible for copies independently retained or distributed outside our control. Privacy, intellectual property and other legal rights are unaffected.

Back to contents

10. Privacy, information security and direct marketing

10.1 Solvaxis handles personal information in accordance with its Privacy Policy and applicable law. Hosts control their own accommodation relationships and are responsible for lawful collection, use, communication and storage of Guest details outside the Service.

10.2 Hosts must not put unnecessary identity documents, sensitive health or medical details or unlawful material in Guest Book notes or other free-text fields.

10.3 A request to stay or a paid booking is not, by itself, consent to unrelated commercial marketing. Hosts must comply with the Spam Act and other relevant requirements for commercial messages and honour withdrawal and unsubscribe requests.

10.4 We send transactional emails to Guests on the Host’s behalf in the property name. Replies go to the Host. Emails include enquiry acknowledgements, link expiry and transfer reminders, confirmations and receipts, saved-card charge notices and failures, notice when the Host keeps a booking after a cancellation request, cancellations and arrival details the Host sets up. Hosts receive booking, security, service and subscription notices. Guests receive come-back reminders only on request, as the Privacy Policy explains.

10.5 Solvaxis and the Host each must keep the records the law requires of it. Reducing Guest access over time does not delete the underlying records. Administrator deletion of a Host account removes its booking, signed agreement and payment records from the app. Hosts should export needed records before the account is deleted. Clause 12.3 explains preservation duties. Provider records and backups have separate retention arrangements.

10.6 Account security. Hosts must keep passwords and sign-in codes private and secure their account email. The Service may email codes for sign-in or before changes to payment details or the sign-in email. Choose ‘Remember this device for 30 days’ only on a device you control. If someone else may have it, use ‘Forget all devices’ or change your password. If you suspect unauthorised use, change your password and promptly email support@directhostpay.com.au.

10.7 A Host may let a person acting for it, such as a co-host, family member or property manager, use its account. The Host is responsible for what that person does in the account as if the Host had done it, and must make sure that person follows these Terms. Solvaxis is not responsible for loss caused by a person the Host let use its account, or by the Host not keeping its sign-in details secure, except to the extent that Solvaxis's own failure to take reasonable care in securing the Service caused or contributed to it.

Back to contents

11. External providers, changes and service interruptions

11.1 The Service relies on third parties including Stripe, banks, PayPal, email, database and hosting services, and connected booking sites. Those services may impose separate terms and may become unavailable. A Payment Provider may review, restrict, suspend or close a Host's account, or hold or delay funds, under its own terms. Solvaxis does not control those decisions.

11.2 Solvaxis will use reasonable care and skill in providing the Service, managing its integrations and implementing security safeguards. Continuous availability and uninterrupted external services cannot be guaranteed.

11.3 We may make reasonable changes for development, maintenance, security, operational or legal reasons. If a change materially reduces features during a paid period, we will give reasonable advance notice where practicable. For urgent security, compliance or service integrity changes, we may act first and notify afterwards where appropriate. We will consider reasonable subscription requests from materially affected Hosts. Statutory remedies remain available. A material amendment to these Terms applies to an affected Host only with its agreement. Publication does not retrospectively change an existing Stay Agreement or extinguish accrued rights.

11.4 Solvaxis does not guarantee a specified number of bookings, accommodation revenue or commercial result from use of the Service.

11.5 Events beyond reasonable control. Neither Solvaxis nor a Host is liable for delay or failure to the extent caused by an event beyond its reasonable control that it could not reasonably prevent or work around. Examples include natural disasters, fire, flood, pandemics, widespread power or telecommunications failures, cyber attacks on a third party or outages of external services under clause 11.1, and government action. This exception does not cover payment obligations or failures caused by our lack of reasonable care, including in choosing, configuring or monitoring external services. The affected party will notify the other where practicable, take reasonable steps to limit the effects and resume performance as soon as practicable. Clauses 1.5 and 13.1 apply.

Back to contents

12. Restrictions, closure and data access

12.1 Solvaxis may restrict new activity, suspend or terminate an account for a serious breach, fraud, security concern, unlawful use, non-payment or a legal requirement, using a response reasonably proportionate to the risk.

12.2 Where reasonably practicable, we will tell the Host about a necessary restriction or suspension under clause 12.1 and its general reason. We may give the Host an opportunity to put things right. We may act immediately where necessary for security, fraud prevention, legal compliance or protection of the Service or its users. We will act reasonably and proportionately, considering existing Guest commitments and legal obligations. Restrictions ordinarily stop new links and stay requests but allow existing bookings to be administered where lawful and technically practicable. A Host unable to access ‘Manage billing’ may contact us to stop renewal. If we materially withdraw paid access, we will stop renewal. Statutory remedies remain available. Subject to preservation duties, we may close an unfinished account that has never had a subscription or booking after 90 days without sign-in and at least seven days’ email notice.

12.3 Requesting closure. Hosts may request closure, subject to outstanding subscription cancellation, exports and applicable legal retention. Unless the Host asks for earlier deletion, we will wait until at least 30 calendar days after we receive the request, using Sydney dates. The Service shows the date so the Host can sign in and download available copies (clause 9.2). For a suspended account, we will consider a reasonable request for another way to obtain copies.

An in-Service request stops automatic renewal. For an emailed request, we stop renewal once we verify it. Otherwise the account stays open as before until deletion. Withdrawing an in-Service request leaves renewal off until the Host turns it on. For in-Service requests, we also wait while a signed or paid stay is upcoming or under way, or a saved card or scheduled charge is still live on the Host’s connected Stripe account.

A preservation hold or legal requirement may delay deletion or require other action. Deletion removes underlying Host and Guest records from the app, including those in clause 10.5. It does not selectively preserve records. Where legally required, we can hold the whole account until the hold is released or preserve the required records separately. We remain responsible for keeping our company financial records for the legally required periods.

Deletion immediately ends any running subscription and disables Booking Links and Guest receipts. We attempt to remove saved cards from the Host’s Stripe account and make no further scheduled charges. The Host must promptly remove any card left in its account (clause 5.1).

12.4 We will consider existing Guest commitments when restricting access under clauses 12.1 and 12.2. Closure does not end the Host’s obligations under Stay Agreements.

12.5 When a subscription is inactive. A subscription is active while paid up, while the billing provider retries renewal, or during free access under clause 8.5. Otherwise, whether the subscription has ended or never started, Guests cannot start payments or save a card through the Service. We do not charge saved cards automatically or on Host instruction, or send pre-charge reminders. Hosts cannot record a payment as received.

The limits in the Stay Agreement and clauses 5.1 and 6.1 keep running. To charge a saved card the Host must reactivate first. On reactivation, a charge that fell due is made if the card is still saved. The Guest may receive no advance email.

The Host can still sign in, create and send links, take stay requests, cancel bookings, refund card payments through the Service, record refunds and use records. Payments remain recorded. Guests retain access to receipts and signed agreements. After a subscription ends, daily calendar reads and requested come-back reminders stop until renewal (clause 7.1). Other automated booking emails may continue. A Guest unable to pay should contact the Host. Subscription status does not change either party’s obligations under the Stay Agreement.

Back to contents

13. Consumer guarantees and liability

13.1 Australian Consumer Law and other laws may confer guarantees and remedies that cannot be excluded, restricted or modified. Nothing in these Terms purports to do so.

13.2 For Host subscription services of a kind not ordinarily acquired for personal, domestic or household use, and only where section 64A of the Australian Consumer Law permits and reliance is fair and reasonable, Solvaxis limits its liability for failure to comply with a consumer guarantee to supplying those services again or paying the cost of having them supplied again.

13.3 The accommodation supplier is responsible for providing the stay, the condition and safety of the property, Host-caused cancellations and any refund, relocation or other remedy the Host owes. Solvaxis is responsible for its own software and conduct and for duties the law places on it.

13.4 Subject to clauses 13.1 and 13.6, each party is responsible for legally recoverable loss to the extent caused by its breach or other actionable conduct. For claims for breach of these Terms, each party is liable only for losses of a kind that it could reasonably have foreseen when the contract was made. Each party must take reasonable steps to reduce any loss for which it claims compensation. These limits do not restrict a remedy or measure of loss available under mandatory law.

13.5 Solvaxis does not assume the Host’s accommodation obligations or cover losses caused solely by the independent acts or omissions of a Host, Guest or external provider. Where Solvaxis’s own breach, negligence or other actionable conduct contributes to a loss, Solvaxis remains responsible to the extent required by law. This includes responsibility for its own work in operating and managing integrations.

13.6 Nothing in these Terms excludes or limits liability for fraud or deliberate misconduct, or any liability, guarantee or remedy that the law does not allow the parties to exclude or limit.

Back to contents

14. Indemnities

14.1 To the extent permitted by law, the Host indemnifies Solvaxis for amounts Solvaxis is legally required to pay a third party and reasonable external defence costs, to the extent the claim is caused by the Host’s negligent or unlawful accommodation operations, material breach of a Stay Agreement or these Terms, or breach of the rights or permissions warranty in clause 9.6 or 9.8.

14.2 The indemnity does not apply to the extent caused or contributed to by Solvaxis's negligence, breach of duty, unlawful conduct, wilful misconduct or other actionable fault, and does not require payment of amounts which law prevents us from shifting to a Host.

14.3 Solvaxis will give the Host reasonable notice of a claim where practicable, provide reasonable cooperation, give the Host a reasonable opportunity to participate in the defence and take reasonable steps to reduce the loss and costs. A delay in notice reduces the Host’s obligation to the extent it materially prejudices the defence.

14.4 Solvaxis will not settle a claim under clause 14.1 in a way that requires the Host to admit fault, pay money or assume another obligation without the Host’s consent, which must not be unreasonably withheld. This indemnity does not permit duplicate recovery.

Back to contents

15. Complaints and governing law

15.1 Email service concerns or privacy requests to support@directhostpay.com.au. Complaints about accommodation delivery, cancellation, property damage and Host refunds should ordinarily be directed to the relevant Host.

15.2 Providing software does not make us a binding arbitrator of accommodation disputes. We will meet any legal duty to assist, disclose records or take regulatory action.

15.3 These Terms are governed by the law of the Australian Capital Territory and applicable Commonwealth law, without restricting any mandatory jurisdiction, venue, tribunal or consumer rights.

15.4 If a provision is invalid, the remainder operates to the extent permitted. A lawful failure to enforce one breach does not waive all future enforcement. These Terms do not displace any accepted Host–Guest Stay Agreement.

15.5 The suburb, state and postcode suggestions Hosts see when entering a property address incorporate or were developed using G-NAF © Geoscape Australia licensed by the Commonwealth of Australia under the Open Geo-coded National Address File (G-NAF) End User Licence Agreement.

15.6 Resolving a dispute with Solvaxis. A Host or Guest may email details of a dispute to support@directhostpay.com.au. The parties are encouraged to try in good faith to resolve it promptly. Either may take steps at any time to protect a claim or time limit or seek a remedy through a court, tribunal, regulator or other available channel.

Back to contents

16. Notices and general terms

16.1 Notices. We email Host notices to the account email address and may also display them in the Service. We email Guest notices to the booking email address. Hosts and Guests give us notice at support@directhostpay.com.au.

16.2 Applicable law, including electronic transactions legislation, governs when notices are given and received. Users must maintain accurate contact details and check their nominated email. If an important email cannot be delivered, we may use another available contact method. We do not undertake individual follow-up for every failed email unless required by law.

16.3 Electronic dealings. Users agree to electronic dealings as permitted by the Electronic Transactions Act 1999 (Cth) and corresponding State and Territory laws. These include checkbox acceptance, electronic notices, receipts and records by email or in the Service, and electronic acceptance of Stay Agreements between Hosts and Guests. An electronic acceptance record is evidence of what happened. It does not by itself decide whether or when a binding contract was formed (clause 4.4).

16.4 Which document applies. These Terms govern use of the Service. The Stay Agreement governs the accommodation relationship between Host and Guest. The Privacy Policy explains how Solvaxis handles personal information. This clause does not affect rights or remedies arising from a representation or commitment for which Solvaxis is responsible under contract or law.

16.5 We may transfer our rights and obligations to a successor that acquires all or substantially all of the business supplying the Service and assumes our continuing contractual obligations. We will give affected Hosts reasonable notice where practicable. Accrued rights and remedies survive and privacy law applies to personal information transferred. A materially disadvantaged Host may terminate its subscription, subject to statutory rights and remedies. Any other transfer by either party requires the other’s consent, which must not be unreasonably withheld.

16.6 Clauses that continue. Clauses 9.3, 9.4, 13, 14, 15 and 16, and any other clause that by its nature is meant to continue (such as clauses 9.2, 10.5 and 12.3 to 12.5), continue after a Host's subscription ends or its account closes, as do rights and obligations that arose before then.

Back to contents