Channel manager terms
Operational rules for the Guestcord pilot. Published 23 September 2026. Commercial terms require an identified supplier and a separate signed agreement.
Scope and parties
Guestcord currently offers a public browser demo and a private single-operator pilot. It is not a certified Booking.com or Airbnb connectivity partner. These terms explain the pilot; they do not create a paid subscription, promise connectivity or replace the terms of any channel. The registered legal name, address, tax number, commercial price and governing law must be agreed before independent hosts are onboarded.
Channel authorisation
Only the property owner or an authorised manager may connect a property. Each channel requires its own approved partner access, property-level permission and permitted API scopes. A logo or source label in a sample booking is not evidence of a live API connection. A host may revoke permission in the channel and should notify the operator so data and scheduled jobs can be reconciled.
Source of truth and synchronisation
For a live integration, the provider and host must agree which system controls property content, room mapping, rates, inventory, restrictions and reservations. Imports must keep the channel booking ID and modification history; updates need idempotent handling, acknowledgements, retries, conflict alerts and a reconciliation process. iCal only exchanges blocked dates, can be delayed and does not carry full reservation, pricing or message data.
Guest messages and automation
A host is responsible for approving message templates, language, timings and recipient eligibility. Delivery over a channel requires that channel's authorised messaging API and must respect its permitted content and contact rules. A draft or a message stored in the demo is not a sent message. Failed delivery must remain visible for manual action; cancellation and date changes must suppress or reschedule planned messages.
Fees, deposits and invoices
The host must disclose mandatory fees, taxes and deposits in the channel's permitted fields before booking. Airbnb generally prohibits collecting related fees outside its platform unless expressly authorised, and most hosts cannot collect a security deposit. Guestcord cannot make an unauthorised external deposit a condition for revealing check-in details. Payment status must be verified with an authorised payment provider or manually by the host; the demo's payment button simulates this. Invoice previews are drafts until a legally responsible issuer verifies and issues them.
Security and personal data
Credentials must be kept server-side, scoped and rotated. Access should follow least privilege with MFA for staff where required by the channel. Guest links and access codes are confidential and should expire or be revoked after use. The applicable privacy notice and an executed data processing agreement govern host-controlled guest data; channel-origin data may carry different roles and additional platform terms.
Availability, incidents and exit
Neither channel availability nor delivery time is guaranteed in this pilot. The host should monitor conflicts and use the channel's own interface if a feed fails. Incidents affecting channel data must be assessed under applicable channel contracts and privacy law. Export, retention, deletion, support, service levels, liability and termination for a commercial product require a separate signed agreement. Contact: contact@managemalta.com.