Subprocessor
A provider may act as a subprocessor where it processes relevant personal data on behalf of HotelConnect24 in a processing chain where HotelConnect24 itself acts as a processor.
HotelConnect24 can use specialised third-party providers to support infrastructure, communications, security and other platform functions. This page explains how subprocessors fit into the HotelConnect24 data protection framework and provides a register of relevant providers.
Identify relevant providers, understand their purpose and keep the production register aligned with the services actually in use.
The role depends on what the third party does, whose instructions it follows and whether it processes relevant personal data on behalf of HotelConnect24 within the applicable processing relationship.
A provider may act as a subprocessor where it processes relevant personal data on behalf of HotelConnect24 in a processing chain where HotelConnect24 itself acts as a processor.
Some third parties may determine their own purposes for particular processing activities rather than acting only on HotelConnect24 instructions. Their legal role can therefore differ.
A hotel, OTA, distribution business or technology partner can participate in a connected workflow without necessarily being a HotelConnect24 subprocessor. The relationship depends on the actual data flow.
The register below identifies providers currently known to support HotelConnect24 services that can involve processing of relevant information. The exact processing depends on which service is enabled.
The same provider can have different legal and operational roles depending on the service being used. HotelConnect24 therefore needs to understand what information is processed, why it is processed and under whose instructions.
This is particularly important when HotelConnect24 processes data on behalf of a hotel and then uses another service provider to support that processing.
A technology provider can be headquartered in one country, operate infrastructure in another and use support or corporate systems across multiple jurisdictions.
HotelConnect24 should therefore evaluate relevant international data flows based on the actual service and contractual arrangement rather than relying only on the provider's brand address.
Before a service becomes part of a HotelConnect24 production workflow, its purpose, data access and operational importance should be understood.
HotelConnect24 may add, replace or remove service providers as the platform evolves. The production register should reflect material changes to relevant processing dependencies.
A new provider may be introduced where HotelConnect24 requires a new service, improves the architecture or replaces an existing dependency.
An existing provider's purpose, service region or data-processing scope may change as the HotelConnect24 implementation evolves.
Providers should be removed from the active register when they no longer support the relevant HotelConnect24 processing activity.
HotelConnect24 can connect with hotels, distribution platforms, technology providers and travel businesses that operate under their own independent roles and responsibilities.
A participating hotel is not listed here merely because it exchanges reservation or property information with HotelConnect24.
OTAs, travel marketplaces and distribution businesses can have their own independent relationship with travellers and hotels.
An integrated technology company is not automatically a subprocessor. Its role depends on the actual processing arrangement and data flow.
Infrastructure and integrations can change. A subprocessor page is useful only when it is maintained alongside the actual HotelConnect24 architecture.
HotelConnect24 aims to keep relevant third-party processing visible so hotels and partners can better understand the infrastructure and service providers supporting the platform.