LeoFlex Platform Agreement including Data Processing Agreement
Version LF-2026-11-18 · 18 November 2026
Convenience translation: Only the German text of this agreement is legally binding. This English translation is provided for information only (see section 1.5).
Provider: Erich Nigg, trading as NEO Digital, sole proprietorship, Nordweg 14, 8010 Graz, Austria, VAT ID ATU57275308. LeoFlex is a product of NEO Digital and not a separate legal entity. Contact: support@leoflex.io, phone +43 316 231620. Security reports: security@leoflex.io. General company contact: hallo@neo-digital.at. Member of the Styrian Chamber of Commerce (Wirtschaftskammer Steiermark), UBIT professional group.
Customer: The business designated during onboarding. Company name, address, billing profile, assigned apaleo account and accepting person are documented upon acceptance of the agreement. The agreement applies exclusively to business use.
Part A – Use of the platform
1 Conclusion of the agreement and module orders
1.1 The framework agreement is concluded by express electronic acceptance during onboarding. The accepting person confirms that they are authorised to represent the customer. The agreement and its annexes are available in readable and storable form before acceptance.
1.2 With every module activation, the customer confirms the complete version of the agreement designated at that point, including the data processing agreement and annexes, by means of a mandatory checkbox that is not pre-ticked and contains a link to the agreement. Without confirmation, the module is not activated. An additional DPA dialogue is not required. Actually opening the link or reading the agreement in full is not an additional requirement for acceptance.
1.3 Before activation, the module, plan, account or property reference, price, quantity basis, minimum fee, included usage, possible additional costs as well as the start of the trial and of payment are displayed. These confirmed order details supplement the agreement. A free framework account or the acceptance of all module descriptions does not order any further chargeable services.
1.4 Each acceptance is documented separately with customer, accepting person, module, time, contract version and an unalterable copy of the agreement including annexes. The version in force and the records of acceptance are made electronically accessible to the customer. Earlier acceptances remain traceable.
1.5 Individual agreements take precedence over this agreement. Part B takes precedence for data protection matters. The language of the agreement is German; where a translation is additionally provided, the German text prevails unless otherwise agreed. Deviating customer terms apply only if expressly agreed.
2 Scope of services
2.1 NEO Digital provides LeoFlex as standard software via the internet with a dashboard and API. An account designates the customer's tenant; a property designates an assigned accommodation business. The current modules require a suitable apaleo account and the necessary permissions. apaleo remains the leading property management system.
2.2 This agreement comprises the following separately activatable modules:
| Module | Service |
|---|---|
| Channel Manager | Synchronisation of supported rates, availabilities and booking events via Channex with apaleo, including the necessary mappings and expressly approved payment processes. |
| Guest Registration | Preparation and technical transmission of the required registration data to the selected supported registration service, including status display and error tracking. |
| Smart Locks | Assignment of supported locks as well as creation, modification and revocation of access codes according to the customer's configuration. |
| Automatic Room Assignment | Assignment of reservations to available rooms according to the selected rules and the attributes maintained in the leading system. |
| Messaging | Consolidation and handling of supported e-mail, WhatsApp and OTA communication as well as commissioned translation, transcription, AI drafts, automatic replies and expressly approved actions. OTA messages may technically run via Channex. |
2.3 The confirmed functions and supported integrations of the selected plan are owed. Consulting, migration, individual set-up or development are charged additionally only if commissioned separately. Published roadmaps do not establish a fixed delivery date.
2.4 All customers receive the same agreement with the descriptions of all current modules. Data is processed for the individual customer only to the extent of the activated functions and permitted configurations. Further modules and their data processing are included in the relevant version of the agreement before they are ordered.
3 Trial period, fees and billing
3.1 The initially offered trial period amounts to exactly 30 consecutive periods of 24 hours each from activation, irrespective of the length of the month. Start and end are displayed upon activation. Termination is possible at any time during the trial period. If use ends no later than at the end of the trial, no module usage fee is incurred. A renewed trial upon reactivation or a change of plan exists only if expressly offered.
3.2 Without termination, chargeable use begins after the end of the trial. The first chargeable period up to the end of the same calendar month is billed pro rata in arrears in the billing run of the following month, together with the fee for that following month in advance. Thereafter, the respective calendar months are billed in advance.
3.3 All prices are net plus any statutory VAT. For pro rata monthly fees, the monthly price is divided by the actual number of calendar days of that month and multiplied by the chargeable days of use. Minimum fees are treated pro rata accordingly. Each commenced chargeable calendar day counts in full; the relevant time zone is Europe/Vienna. This also applies to the first day after the exact end of the trial and to the last day of use. The same day is not counted twice. If use ends exactly at 00:00, the newly beginning day does not count. Times within the free trial period remain free of charge. The total amount is rounded to the cent.
3.4 Upon termination, fees billed in advance for the remaining full unused calendar days are credited pro rata by means of an invoice correction. If termination takes place before the relevant invoice has been transmitted, only the chargeable days of use are billed directly. Agreed usage-based fees remain billable according to their actual extent. Any credit balance remaining after set-off against justified claims due is paid out without undue delay upon termination. There is neither a termination fee nor a minimum commitment until the end of the month.
3.5 The billing date is the first of the month. NEO Digital reviews the invoices and transmits them electronically no later than the fifth of the respective calendar month to the address stored in the relevant billing profile. Services billed in arrears and in advance are shown with separate service periods. The invoice amount is due upon transmission. On the day of transmission, the authorised collection is initiated via the payment method stored during onboarding or later in the billing profile. The actual bank posting may take place later. Other individually agreed payment methods remain possible.
3.6 A required payment mandate or payment authorisation is granted separately; acceptance of the agreement alone does not replace it. For SEPA direct debit, the required pre-notification and mandate terms apply, or an expressly agreed permissible shorter pre-notification period. Collections are made in compliance with these requirements.
3.7 The invoicing service is Runple GmbH, Dornbacher Straße 71–73/3/1, 1170 Vienna, Austria, commercial register no. FN 515653p. Required company, billing profile, contact, tax, contract and billing data are transmitted to Runple, in particular recipients, line items, quantities, periods, prices, taxes, amounts and processing status. No hotel guest data is transferred to Runple for this billing. LeoFlex fees are collected via the payment service set up for this purpose, currently generally Stripe. This is separate from guest payments via apaleo Pay and Adyen. Full card numbers and card verification codes are not stored permanently at LeoFlex.
3.8 Price changes for running modules require express agreement. The proposal is communicated at least 30 calendar days in advance by e-mail and in the platform. Silence and mere continued use do not constitute consent. Without consent, the previous price continues to apply until effective termination. Prices for new orders are displayed before they are confirmed. For changes of plan, the pro rata conditions displayed in advance apply without double charging.
3.9 In the event of late payment, the statutory default interest and collection costs apply. An ordinary suspension for non-payment is preceded by a reminder and a grace period of at least 14 calendar days with a notice of the consequences. Justified invoice complaints are examined. Suspensions are limited to the extent necessary; existing access arrangements and legally required access to data must not be unreasonably impaired. In the event of specific misuse or imminent danger, necessary immediate security measures are permitted.
4 Cooperation and automated functions
4.1 The customer ensures lawful source data, the required information towards data subjects, effective permissions and correct configurations. The customer keeps company and contact details up to date, manages its users and API access and protects the means of access under its control.
4.2 Automations only carry out the ordered and approved actions. In particular, the customer determines rules for communication, room assignment, registrations, payments and access. NEO Digital carefully implements the agreed permission, assignment and execution checks. An approval does not release NEO Digital from its own contractual obligations; where automatic sending has been agreed, the customer does not have to check every single message in advance.
4.3 The customer handles displayed errors and exceptions to a reasonable extent and keeps suitable fallback procedures ready for business-critical processes, in particular manual access. NEO Digital provides the agreed status and error messages. The customer remains the contractual partner of its guests, responsible for its registration obligations and the payee of its hotel revenue.
4.4 AI results may be inaccurate. Specific revenues, AI answers that are correct without exception or a specific commercial success are not guaranteed. The agreed protective functions and liability under section 7 remain unaffected. Required notices of AI interaction and options for human takeover are taken into account. Both parties fulfil the statutory AI obligations applicable to their respective roles.
4.5 Full card data, card verification codes and access passwords do not belong in free message or AI fields. Actions that have not been approved and model training for unrelated purposes are not commissioned. Security vulnerabilities can be reported to security@leoflex.io. Security tests must not access third-party data without authorisation or impair operations.
5 Operation, support and defects
5.1 NEO Digital operates the platform with professional care, complies with the agreed protective measures and handles defects for which it is responsible within a reasonable time. A specific availability percentage, a fixed recovery time or a permanently staffed human emergency service is owed only under an express additional agreement.
5.2 Support is provided via Leo chat and support@leoflex.io in German and English. The regular response target is generally one working day; this is not a guaranteed resolution time. Security incidents and significant operational disruptions are prioritised according to their urgency. Plannable significant maintenance is announced with reasonable notice; urgent security measures may be necessary without prior notice.
5.3 The customer reports defects with the information reasonably available to it. NEO Digital investigates the cause and remedies its own defects or offers a reasonable interim solution. Statutory warranty rights, an appropriate price reduction and refunds for paid services that are definitively not provided remain in place. In the event of significant persistent disruptions, statutory termination rights are retained.
5.4 No additional guarantee is assumed for independent services of third parties commissioned directly by the customer. NEO Digital's own selection, integration and information obligations as well as the statutory attribution of service partners remain unaffected. Disruptions caused by third parties or force majeure do not generally eliminate the customer's rights. Both parties cooperate in reasonably limiting the effects.
6 Rights of use, confidentiality and own data processing
6.1 Rights to software, documentation and trademark remain with NEO Digital or the respective rights holders. For the term of the agreement, the customer receives a simple right of use for its confirmed businesses and authorised users. Objectively justified, documented technical limits apply to API calls; material changes to promised interfaces are announced in good time.
6.2 Rights to the customer's own content remain with the customer. NEO Digital only receives the powers required to provide the services. Guest data must not be used for NEO Digital's own advertising, the sale of profiles or general model training. Both parties protect non-public business and operational information of the other party, also after the end of the agreement, for as long as there is a legitimate interest in confidentiality. Lawfully known, public or independently developed information and legally required disclosures are excluded.
6.3 For its own contract administration, billing and statutory records, NEO Digital acts as an independent controller and provides information about this in its privacy notices. Part B applies to the processing of hotel guest data and other commissioned data. Acceptance of the agreement does not replace any required legal basis towards guests or any separately required marketing consent.
7 Liability
7.1 NEO Digital is liable without the following maximum amounts for intent, gross negligence of a particularly serious kind equivalent to intent, injury to life, body and health as well as mandatory product liability and other liability that cannot effectively be limited by law.
7.2 In the event of slight negligence, NEO Digital is liable for the breach of essential contractual obligations up to EUR 5,000 per customer and damage event. Essential obligations are those whose fulfilment makes the agreed service possible in the first place and on whose fulfilment the customer may regularly rely. For other obligations, liability for slight negligence is excluded. In the event of ordinary gross negligence not covered by paragraph 1, the limit is EUR 25,000 per customer and damage event.
7.3 In addition, total liability for claims for damages that can effectively be limited under paragraph 2 amounts to a maximum of EUR 25,000 per customer and contract year across all ordered modules combined. A contract year comprises twelve months from the start of the framework agreement; a final shorter contract year is not reduced pro rata. The relevant year is the year in which damage from the event first occurs. Later consequences do not allocate the same event several times to different contract years. The individual limit of EUR 5,000 continues to apply within the annual limit.
7.4 A damage event comprises effects demonstrably based on the same cause, irrespective of the legal basis of the claim. Independent causes are not combined merely because of their proximity in time. The limits apply per customer, also during a free trial period, and do not form a common liability limit across all customers. The exceptions under paragraph 1 remain unrestricted.
7.5 Lost profit is excluded in the event of slight negligence. Typical direct costs for correcting incorrect bookings or payments, necessary alternative accommodation, alternative access or data recovery are not excluded across the board; the statutory requirements for claims and the applicable maximum amounts apply.
7.6 Mandatory rights of data subjects, in particular under Art. 82 GDPR, and responsibility under Art. 28(4) GDPR remain unaffected. Any internal recourse is governed by mandatory law and otherwise by this agreement. Warranty, remedy of defects, price reduction, refunds and credits are not limited by the limits on damages. The agreement does not establish a general obligation to reimburse fines imposed on others. Statutory rules on contributory negligence, mitigation of damage and limitation remain in place. Any independent guarantee going beyond this requires express agreement.
8 Term and termination
8.1 The framework agreement runs for an indefinite period. The customer can terminate the agreement or individual modules at any time without notice period, also during the trial period, with immediate effect or at a chosen later date. Termination is possible in the dashboard or by e-mail to support@leoflex.io and is confirmed together with its effective date. Billing is governed by section 3.
8.2 NEO Digital can terminate the framework agreement or individual modules with ordinary notice of at least 90 calendar days. Unused prepayments are refunded pro rata. The right of both parties to extraordinary termination for good cause remains in place. In the case of remediable breaches of obligations, a reasonable cure period that has expired without success is generally required.
8.3 Upon termination, the parties arrange the secure completion of ongoing tasks and existing access arrangements. Technical follow-up work does not automatically extend chargeable module use. An expressly requested continuation during a switch of provider is agreed with the fees applicable to it. The mere withdrawal of an interface permission does not replace termination.
9 Data access and switching provider
9.1 The customer can use the existing API in accordance with its documentation and the customer's permissions. For the legally owed return or a switch of provider, NEO Digital additionally provides required existing customer data upon request to support@leoflex.io via a protected transmission channel in a common machine-readable format. A separate export function in the dashboard is not a prerequisite for this.
9.2 The following are provided: existing customer-specific configurations and templates, operational booking and registration header data, task, status and execution data, communication content and associated metadata as well as customer-related access assignments and validity periods. Structured data is provided as JSON or CSV with the required field and mapping information, attachments in their existing file format. Secrets are only handed over via a specially protected channel. Originals stored exclusively in the external mailbox, PMS or portal are to be retrieved via its responsible provider.
9.3 Only internal assets that may lawfully be excluded are excluded: source code, internal program and system components, other tenants' data as well as security secrets not related to the customer. These exclusions must not exclude required customer data and metadata or obstruct the legally owed switch. Functional equivalence of the target system is not promised. Required cooperation as well as known technical limits and dependencies are communicated to the customer before conclusion of the agreement with the service description or API documentation.
9.4 A notice period of at most 30 calendar days applies to a switching request; an earlier termination of a module is not extended by this. NEO Digital supports the switch in good faith and to the extent required by law while maintaining the agreed continuity of service and security. The transition period is generally at most 30 calendar days. If this is technically not feasible, the reasons and an alternative period of at most seven months are communicated within 14 working days of the switching request. An extension at the customer's request provided for by law is made possible.
9.5 After the transition phase, there is a further retrieval period of at least 30 calendar days. Completion, end of the agreement, end of retrieval and subsequent deletion are communicated to the customer. No separate switching fees are charged for owed switching support, standard provision and retrieval. Ordinary usage fees for expressly continued services remain transparently billable; mere data retrieval does not extend all module subscriptions. Additional consulting not owed by law requires a separate order.
10 Changes and final provisions
10.1 The agreement and annexes remain retrievable in LeoFlex. A newly published version does not change existing agreements merely by being published. When a further module is ordered, the complete version displayed for it is accepted in accordance with section 1. If it is also to apply to running services, this effect and material changes are made clear before acceptance.
10.2 Changes to existing main services, additional processing purposes or material contractual rights require express agreement. Corresponding change proposals are communicated at least 30 calendar days in advance. The first voluntary order of a new module does not require an additional waiting period. Section 3 applies to prices, section 15 to sub-processors.
10.3 Bug fixes, security updates and technical improvements are permitted as long as they do not materially worsen the agreed purpose of the service and the level of data protection and do not establish any additional payment obligation. Editorial changes without substantive effect do not require new acceptance. If an existing integration is materially restricted, NEO Digital informs the customer at an early stage about the consequences and reasonable alternatives; in the event of a material impairment, the customer can terminate the affected service without additional termination costs.
10.4 Austrian law applies, excluding the UN Convention on Contracts for the International Sale of Goods. The exclusive place of jurisdiction for both parties is the court with subject-matter jurisdiction in Graz, to the extent permitted. Mandatory law and mandatory jurisdictions remain unaffected. Declarations can be made in text form, in particular by e-mail or a confirmed platform function; stricter statutory form requirements remain in place. The consequences of an invalid provision are governed by the applicable law; a replacement rule that is automatically the most favourable for the provider is not agreed.
Part B – Data processing agreement pursuant to Art. 28 GDPR
11 Subject matter, duration and roles
11.1 The customer commissions NEO Digital as processor with the processing operations described in Annex 1 for the activated modules. This DPA and its annexes form part of the same electronically accepted complete version. If the customer is itself a processor, its commissioning of NEO Digital must be integrated into the lawful chain of instructions.
11.2 The subject matter is the technical support of hotel operations through interfaces, registrations, access management, room assignment and communication. The processing comprises the necessary retrieval, organising, assigning, matching, transmitting, providing, purpose-bound storage, rectification, restriction and erasure. It begins with the commissioning and lasts for the duration of the service, including the necessary return and deletion phases. Protection obligations continue for as long as commissioned data exists.
11.3 The customer determines the permitted purposes and is responsible for legal bases, information to data subjects and instructions. NEO Digital is responsible for performance in accordance with the agreement and for its own statutory obligations. Data must not be used for NEO Digital's own advertising, the sale of guest profiles or general AI model training.
12 Instructions and confidentiality
12.1 NEO Digital processes commissioned data exclusively on the documented instructions of the customer, including lawfully set-up functions and configurations. Instructions can be given in text form or via the platform functions provided for this purpose. New purposes or a material extension of the processing are agreed in advance.
12.2 If NEO Digital considers an instruction to infringe data protection law, it informs the customer without undue delay and may suspend the affected processing until the matter has been clarified. In the case of a mandatory statutory processing obligation, it informs the customer of this obligation in advance, insofar as the law permits.
12.3 Only authorised persons committed to confidentiality are given access, to the extent required. Support access is limited in scope and time. Legally protected data of other customers remains shielded. Confidentiality continues after termination.
12.4 Planned processing of special categories of data under Art. 9 or 10 GDPR requires a separate specific agreement and appropriate protective measures. Sensitive information contained in messages without being requested is limited to what is necessary and deleted or restricted in accordance with lawful instructions.
13 Security
13.1 NEO Digital implements the technical and organisational measures set out in Annex 3 and maintains a level of protection appropriate to the risk pursuant to Art. 32 GDPR. The effectiveness of the measures is reviewed regularly and after material changes.
13.2 Measures may be developed further technically as long as the agreed level of protection is not lowered and the commission is not extended. Material changes are documented and made accessible to the customer. Any required amendment to the agreement is governed by section 10.
14 Assistance and personal data breaches
14.1 NEO Digital assists the customer with appropriate measures and available information with regard to data subject rights and the obligations under Art. 32 to 36 GDPR. Requests concerning commissioned data are forwarded to the customer without undue delay; NEO Digital only decides on its own where it has its own statutory obligation.
14.2 If NEO Digital becomes aware of a breach of the security of commissioned data, it informs the customer without undue delay. A completed root cause analysis is not required for this. As far as available, the nature and scope, affected categories and approximate numbers, contact point, possible consequences as well as measures taken and planned are communicated. Further findings are added without undue delay.
14.3 NEO Digital supports assessment, containment, required notifications and remediation. Responsibility for notifications to authorities and data subjects is governed by law. Official orders concerning commissioned data are communicated to the extent legally permitted.
14.4 Regular assistance under this DPA is included in the agreed fees. Exceptional customer-specific additional services can be commissioned separately in advance. Urgent assistance required by law and the remedying of NEO Digital's own breaches of obligations are not made dependent on additional remuneration.
15 Sub-processors and processing locations
15.1 The customer grants general authorisation for the use, required for the activated functions, of the sub-processors described in Annex 2 and the processing chains designated there. NEO Digital binds its own sub-processors to the required data protection obligations before they are used and remains responsible pursuant to Art. 28(4) GDPR.
15.2 Planned additional or replacement sub-processors for running services are communicated at least 30 calendar days before their use by e-mail and in the platform, stating activity, data, locations and the required transfer basis. Within this period, the customer can object on comprehensible data protection grounds. The parties endeavour to find a reasonable solution; if this does not succeed, the affected service can be terminated without additional termination costs. Unused prepayments are refunded. An urgent change does not cancel the legally required prior information and effective possibility to object.
15.3 An additional service exclusively for a voluntarily newly ordered module can be expressly and individually authorised when that module is ordered. The service and its processing must be described specifically in advance. This does not permit an unnoticed replacement in modules that are already running.
15.4 Platform infrastructure as well as the commissioned AI router and model inference are operated within the EU. AI is used via router.eu.requesty.ai and exclusively approved EU models. A global fallback route is not permitted. If no permitted EU route is available, the relevant call is not executed via a third country.
15.5 This is to be distinguished from the expressly described external payment, communication and lock services. Insofar as their processing or remote access concerns a third country, a valid basis under Chapter V GDPR is required before the transfer, in particular a relevant adequacy decision or appropriate safeguards including the required supplementary measures. The agreed EU commitment for AI remains in place.
15.6 Services commissioned directly by the customer and statutory recipients are treated according to their actual role. NEO Digital remains responsible for its own proper handover. A provider designation alone does not shift any statutory responsibility.
16 Return and deletion
16.1 During the service, the periods set out in Annex 1 apply. After the end of the processing, the customer chooses the return of the existing commissioned data with subsequent deletion of remaining copies, or deletion, insofar as no statutory retention obligation stands in the way. Switching provider and retrieval are additionally governed by section 9.
16.2 Active commissioned data no longer required is deleted without undue delay after return and the end of required retrieval periods, generally no later than 90 calendar days after the end of the service. Longer switching or retrieval periods required by law are observed and communicated to the customer together with their end date. Earlier lawful deletion instructions are taken into account.
16.3 Data that must be retained by law or is required for a specifically justified open matter is kept separate according to purpose, legal basis and duration, with restricted access. A general unlimited retention of guest data is not agreed.
16.4 Backups expire in accordance with Annex 3 and are separated from ordinary access until then. In the event of a justified restoration, deletions and restrictions previously carried out are applied again before renewed regular use. NEO Digital documents deletions and confirms them on request, including remaining backup processes. Merely hiding data does not replace a required final deletion.
17 Evidence and audits
17.1 NEO Digital keeps the required contract, security and implementation records in an orderly manner and protected against unauthorised access within the company, also in electronic form. It provides the information required to demonstrate compliance with Art. 28 GDPR and enables lawful audits by the customer or a suitable auditor. Confidential data of other customers and security secrets are protected without frustrating the required audit.
17.2 Routine audits are announced reasonably in advance and generally limited to once a year. Additional audits remain possible where there is justified cause, statutory requirements or insufficient evidence. The rights of the supervisory authorities remain unaffected. Existing suitable documentation can be used as a priority.
17.3 Regular evidence is provided without additional remuneration. Exceptional customer-specific audit effort requires prior transparent and reasonable agreement. NEO Digital does not charge the customer for its own effort to remedy a material breach for which NEO Digital is responsible. Confidentiality, protection and evidence obligations continue after the end of the agreement insofar as they are still required.
Annex 1 – Description of the commissioned processing and deletion rules
Data subjects and origin of data
Data subjects are guests, bookers, accompanying persons including minors, employees and authorised contact persons of the customer as well as its communication partners. Data originates from apaleo, Channex and connected portals, from the customer and its users as well as from connected communication and access systems. Processing data of different hotel customers into a common guest profile is not commissioned.
Processing per module
| Module | Data, purpose and scope of storage |
|---|---|
| Channel Manager | Processing of the required booking and reservation references, guest display and contact data, language, stay data, rooms, rates, services, amounts and payment status for synchronisation with apaleo. A webhook may initially only transmit references; the required content is then retrieved and forwarded. Operational header data, in particular guest display name, arrival and departure, amount, references and status, as well as necessary import and execution data may remain locally. A complete duplicate of the PMS guest database is not commissioned. |
| Guest Registration | Retrieval and transmission of the names, addresses, nationality, birth, stay and, where applicable, document data as well as details of accompanying persons required for the selected registration process. Complete registration forms are not retained by LeoFlex as a separate registration database. Required header data such as reservation and registration form number, main guest name, arrival and departure, status and proof of transmission remain locally. Retention by the hotel, the registration provider and the statutory recipient is governed by their actual role and the applicable requirements. |
| Smart Locks | Reservation reference for assignment as well as required room, lock and area identifiers, access codes, validity periods and processing status. Guest names, addresses, e-mail addresses and telephone numbers are not transmitted to the lock service. Assignable references remain personal data. Code creation, modification and removal take place in accordance with the approval; required protected code and action data may be held locally. |
| Automatic Room Assignment | Retrieval of the required reservation, stay, occupancy and room attributes from apaleo, rule-based assignment and feedback. No separate complete guest master database; required assignment, status and error records may be stored. |
| Messaging including AI | Required sender, recipient, channel and contact details, messages, media, documents, conversation and reservation assignments as well as delivery and processing status. WhatsApp and OTA content may be stored locally. E-mail originals are generally retrieved from the connected mailbox; local assignments, drafts and sending states are possible. For ordered translation, transcription, image analysis or AI replies, only the required content and the necessary hotel or reservation information are transmitted to the approved EU processing. |
Payment data: Insofar as the secure Channel Manager payment path is activated, required full card data is passed on only briefly from Channex via LeoFlex to apaleo or Adyen for secure payment processing and tokenisation. Full card numbers and card verification codes are not stored permanently in LeoFlex, logs or backups. Masked details, tokens and payment references remain protected. Without this approved path, only masked details and references actually supplied are processed.
AI data: The transmission is limited to the ordered function. General training with commissioned data is not commissioned. Router and model operation are distinguished from local communication data. Insofar as Requesty logs content, this is limited to a maximum of 30 days; necessary technical billing and operating metadata is treated separately from this. No general promise of complete zero retention is given.
Retention during the term of the agreement
| Data | Period and trigger |
|---|---|
| Messages and associated locally stored attachments, transcripts, translations and personal assignments | 180 calendar days from the later of departure and the last substantive message relating to the stay concerned. Without a reservation reference, 180 days from the last substantive message of the matter. In the event of a final cancellation, its completion takes the place of departure. Technical status messages or a new independent stay do not extend the period for old content. |
| Operational booking and registration header data as well as completed functional assignment and transmission records | 180 calendar days from the later of the end of the stay and the completion of required follow-up processing. For cancellations, the final completion of the matter counts. Complete import content no longer required is deleted after secure completion or reduced to the required header data. |
| Ordinary technical operating logs | 14 days from creation. |
| Separate API access logs and AI tool steps | A maximum of 30 days from creation. Unnecessary message content and secrets are not transferred to ordinary logs. |
| Technical AI run states | A maximum of 90 days from completion or last required processing; inactive technical mailbox states a maximum of 90 days from last activity. Interim results required for a shorter time are deleted once their purpose has been achieved. |
| Guest-related access codes | Usable only for the approved access window. Thereafter removal in accordance with the intended procedure. Open errors during removal are tracked until remedied. Code secrets no longer required are deleted; required limited status records follow the 180-day rule. Emergency and housekeeping codes exist only within the approved operational life cycle. |
| Webhook references, technical tasks and protection against duplicate processing | Content data is deleted or minimised after secure completion and required error handling. For minimal personal completion and retry records, at most the period of the associated functional matter applies. Open tasks are only kept for as long as necessary. |
| Data from support access | Copies of guest data are deleted after completion of the required support. Objectively necessary, minimised records follow at most the period of the associated matter; NEO Digital's own business records required by law are treated separately. |
The rules cover the respective local data, file storage, links and derived data. A local deletion does not delete any originals in the external e-mail mailbox or PMS. Earlier lawful deletion instructions as well as required restricted retention for specific legal claims or statutory obligations remain possible; the reason and duration are documented. Section 16 and Annex 3 apply to the end of the agreement and to backups.
Annex 2 – Service providers and recipients
Only the services required for activated functions are used. The general authorisation under section 15 concerns NEO Digital's own sub-processors; services commissioned directly by the customer and statutory recipients retain their actual role. Approving this list does not activate any additional service.
| Service | Activity and data | Agreed scope or role |
|---|---|---|
| IONOS, Germany | Hosting of the platform, databases and required commissioned data; additional in-house backup service. | Production hosting in Berlin. Backup operation within the EU in accordance with Annex 3. |
| netcup GmbH, Karlsruhe, Germany | Supplementary server operation with the components operated there and required commissioned data. | Server operation in Germany or Austria. |
| BunnyWay d.o.o., Dunajska cesta 165, 1000 Ljubljana, Slovenia – bunny.net | File and media storage, required delivery and retrieval metadata; storage of encrypted backup files. | Exclusively EU storage and EU processing; backups without public CDN delivery. |
| Requesty Ltd, 71–75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom | AI router for required content, responses and technical operating metadata. | EU router in Frankfurt; EU model approval without global fallback route. Infrastructure via Amazon Web Services EMEA SARL in Frankfurt. Any required third-country access is subject to section 15(5). |
| Model operation via Requesty: Microsoft Azure AI, AWS Bedrock, Google Vertex AI and Mistral AI SAS, France | Inference of the expressly approved EU models, including ordered speech and image processing; Mistral Voxtral in particular for transcription. | Exclusively EU endpoints and EU inference. Only the model operation actually selected receives the content required for the call. The commitment and information obligations under section 15 apply to the further service chain. |
| Channex.io LTD, Castell Pigyn Lodge, Abergwili, Carmarthen SA31 2JL, United Kingdom | Channel Manager connection: references, required booking content, rates, availabilities and OTA messages. | Integration in accordance with the respective customer and connection agreement; UK processing only on a valid basis under Chapter V GDPR. |
| apaleo GmbH, Sandstraße 3, 80335 Munich, Germany; Adyen N.V., Simon Carmiggeltstraat 6–50, 1011 DJ Amsterdam, Netherlands | Leading PMS and target system; Adyen for guest payments and tokenisation. | Contractually separate systems of the hotel and their service chain. Payment, bank and card network processing is not a general EU-only commitment. |
| feratel media technologies AG, Maria-Theresien-Straße 8, 6020 Innsbruck, Austria | Transmission of required registration and stay data to the selected registration service and the competent registration authority. | In accordance with the customer's specific registration agreement and the statutory competence. |
| Neuhold Datensysteme GmbH, Nordweg 9, 8077 Gössendorf, Austria | Supported registration interface for required registration and stay data. | In accordance with the specific registration agreement and the competent registration authority. |
| Reif Systemtechnik RS, owner Karl-Heinz Reif e.K., Alfons-Maria-Daiminger-Straße 9, 94227 Zwiesel, Germany – WinTOP | Supported registration interface for required registration and stay data. | In accordance with the specific registration agreement and the competent registration authority. |
| Nuki Home Solutions GmbH, Münzgrabenstraße 92/4, 8010 Graz, Austria; Tedee sp. z o.o., Karola Bohdanowicza 21/57, 02-127 Warsaw, Poland | Depending on the selected integration, reservation reference, lock and area identifiers, codes, validity periods and status. | No transmission of guest master data; processing in accordance with the selected lock connection and the respective agreement. |
| Seam Labs, Inc., USA, where selected as lock connection | Technical access to the respective connected lock provider with reference, code, validity and status data. | US service; an effective basis under Chapter V GDPR is required before transfer. The EU commitment for AI does not thereby extend to this service. |
| Connected Microsoft 365 mailbox or IMAP/SMTP mailbox service chosen by the customer; where applicable, Microsoft Azure AI Translator | Required e-mail content, addresses, metadata and commissioned translations. | The mailbox service is determined by the account connected by the customer. NEO Digital's own sub-commissions are subject to section 15. |
| Meta Platforms Ireland Limited or WhatsApp Ireland Limited, Ireland, with the relevant WhatsApp service chain | WhatsApp communication with required phone numbers, content, media and delivery information. | Processing in accordance with the relevant WhatsApp Business agreements; any third-country processing only in accordance with section 15(5). |
| Runple GmbH, Dornbacher Straße 71–73/3/1, 1170 Vienna, Austria | NEO Digital's own invoicing and billing administration with data under section 3(7). | The provider's own contract administration, no general transfer of the hotel guest database. Provider states server hosting in Germany. |
| Stripe as the payment service set up for LeoFlex fees | Authorisation, collection, payment status and required references for NEO Digital's own customer billing. | Processed by the payment service in accordance with its mandate and contract terms; separate from guest payments via Adyen. |
The customer services and connections actually selected result from the order and configuration. NEO Digital documents its own service chain and provides the required information, including relevant further sub-processors, in accordance with sections 15 and 17. A registered office is not to be equated with the physical storage location.
Annex 3 – Technical and organisational measures
The following requirements apply to the operation and the processing of the commissioned data. They are implemented by NEO Digital, regularly reviewed for effectiveness and developed further in line with the risk.
Access and confidentiality
- Separation of customer tenants in data access, background tasks, webhooks and API calls; checking of authorisation for the object concerned.
- Individual user, client, administration and support permissions limited to the required activity. Access no longer required is withdrawn; administrative access is specially protected.
- Support access limited in scope and time, traceable changes and confidentiality commitments of authorised persons.
Transmission and storage
- Encrypted transmission and secured service access in accordance with the state of the art.
- Application-level encryption of secrets and access codes requiring protection as well as of the WhatsApp content and media fields designated for this purpose using AES-GCM. Keys are protected separately from ordinary data access and made accessible only to authorised components.
- Logging limited to what is necessary; no full card numbers, card verification codes or unnecessary message content in ordinary logs. No permanent storage of full card numbers or card verification codes in databases and backups.
- Deletion or effective anonymisation in accordance with Annex 1, including files, caches and derived data. A mere soft-delete flag does not replace a required final deletion.
Backup and restoration
| Requirement | Agreement |
|---|---|
| Backup scope | Platform databases, required files and media as well as configurations necessary for operation. The required key recovery is ensured with separate protection. |
| Backup frequency | One full backup daily and additionally an incremental backup every twelve hours. Backup results and errors are monitored and the required remedial action is initiated. |
| Storage targets | Protected EU storage at bunny.net and additionally the in-house IONOS backup service with EU storage location. Backups are separated from ordinary customer access and protected against unauthorised access and failure of the production system. |
| Encryption | Backups are to be encrypted with AES and a 256-bit key. Backup files for bunny.net are encrypted before transfer and stored without public CDN delivery. The corresponding encryption is to be activated in the IONOS backup service. Keys or recovery secrets are kept separately with access protection. |
| Retention | Ongoing backups a maximum of 14 days. Individual purpose-bound long-term backups a maximum of six calendar months; not every daily backup is automatically kept for six months. Backups no longer required are deleted. |
| Restoration test | Before the first processing in the agreed backup operation and thereafter at least once per calendar month, a meaningful restoration is tested. The test plan takes both backup routes into account. Date, source, scope, result and necessary remedial action are documented. |
| Recovery | NEO Digital maintains a restoration procedure and enables a restoration that is fast in line with the risk. Backup intervals are not a guarantee of a specific maximum data loss or a fixed recovery time. |
Maintenance and incident handling
- Regular risk-based security updates, checking of known vulnerabilities and regulated handling of security reports.
- Documented procedure for data protection and security incidents with assessment, containment, customer information and follow-up of required measures.
- Review of service provider commitments, of the agreed EU regions and of the approved AI routes; no global AI fallback processing.
- Review of the effectiveness of protection, deletion and restoration measures as well as documentation of required improvements.
Components of this version are Part A, Part B and Annexes 1 to 3 as well as the respectively confirmed order details.