Terms and Conditions of Service

Versie 2.1 · Van kracht vanaf 2 oktober 2026 · Gepubliceerd op 2 oktober 2026

ConSergio.ai — DevInterface srl Version 2.1 · Last updated: 2 October 2026 · Effective from: 2 October 2026

Language. This English text is a courtesy translation of the Italian original. In the event of any discrepancy or conflict between the two versions, the Italian version shall prevail.

These Terms and Conditions (the “Terms”) govern the use of ConSergio.ai (the “Service”), a SaaS software platform that enables accommodation businesses to offer their guests a digital concierge accessible via QR code — including a service catalogue, request management and an AI-powered conversational assistant — and, depending on the Plan subscribed, to manage their bookings, answer visitors to their website and notify the State Police of their guests.

The Service is provided by DevInterface srl, with registered office at Via Guglielmo Marconi 20, 37012 Bussolengo (VR), Italy, VAT no. 04080300231 (“DevInterface”, the “Provider” or “we”).

By registering for the Service and ticking the relevant acceptance box, the Customer declares that it has read, understood and fully accepted these Terms, the Privacy Policy and the Data Processing Agreement (DPA), which forms an integral part hereof. This version replaces version 1.1, in force since 3 September 2026.

1. Definitions

Customer (or Property Operator): the natural or legal person owning or operating an accommodation business who subscribes to the Service.
Guest: a person staying at the Property who accesses the web app via QR code.
Booker: a person who makes or requests a booking at the Property, whose data is recorded in the Reservations Module.
Visitor: a person who uses the Widget on the Customer’s website.
Staff Users: the natural persons authorised by the Customer to access the management panel, with the roles and permissions assigned by the Customer.
Account: the commercial entity registered to the Customer, to which the subscription and one or more Properties are linked.
Property: the individual accommodation unit configured within the Service, constituting the data isolation boundary.
Customer Content: texts, service descriptions, images, documents, PDFs, FAQs, local information, rates and any other data the Customer uploads or configures within the Service, including content used to feed the AI Assistant and the Widget.
AI Assistant: the conversational component of the Service that responds to Guests based on Customer Content and, where applicable, on configured External sources.
External sources: third-party information services that the Customer may enable, within the limits of its Plan, to enrich the AI Assistant’s responses (currently the search for places and points of interest).
Concierge Module: the set of functions addressed to Guests in their rooms and to their handling by staff, included in all Plans.
Reservations Module: the functions for managing bookings, stays, availability and rates, included only in the “+ Reservations” Plans.
Widget: the component of the Reservations Module that the Customer installs on its own website to answer Visitors and collect their booking requests, included in the Plus + Reservations and Premium + Reservations Plans.
Pre Check-in Function: the function, which the Customer may enable, for collecting, verifying in person and transmitting to the State Police’s Alloggiati Web service the data of the guests staying at the Property.
Plan: the subscription tier taken out — Essential, Plus or Premium, each also available in the ”+ Reservations” variant — with its associated functional and commercial limits set out in the price list in force.

2. Subject matter of the Service

2.1 DevInterface grants the Customer a non-exclusive, non-transferable and non-sublicensable right to use ConSergio.ai in accordance with the Plan subscribed and for the duration of the subscription.

2.2 The Service includes, within the limits of the Plan:

in all Plans (Concierge Module): the Guest-facing web app, accessible without installation or registration via a QR code associated with the room; the catalogue of the Property’s services and informational content; the collection and management of Guest requests; the multilingual AI Assistant; messages, surveys and notifications addressed to Guests; the management of stays and room charges; the management panel for Staff Users; statistics and configuration functions;
in the “+ Reservations” Plans (Reservations Module): the management of bookings, availability and rates; the import of bookings from external calendars in iCal format; the sending of booking confirmations to Bookers; tourist tax reporting; in the Plus + Reservations and Premium + Reservations Plans, the Widget;
in all Plans, if enabled by the Customer (Pre Check-in Function): in-person verification of guests’ data, its transmission to the Alloggiati Web service and the personal link to the online form, which staff may share with the Guest before arrival; sending the link and reminders by e-mail is available only in the “+ Reservations” Plans.

2.3 The Service is provided on a SaaS basis, accessible via browser. DevInterface does not supply hardware, connectivity, QR code printing, installation of the Widget on the Customer’s website or on-site installation services at the Property, unless otherwise agreed in writing.

2.4 The Service is under continuous development. Features announced as planned for future releases do not constitute a contractual obligation and do not affect the fees due for the features available at the time of subscription.

3. Registration, Account and Staff Users

3.1 Registration is reserved for parties acting in the course of their trade, business or profession. The Service is not intended for consumers.

3.2 The Customer undertakes to provide truthful, complete and up-to-date registration data, and is responsible for keeping its own and its Staff Users’ credentials confidential, as well as for all activity carried out through the Account.

3.3 The Customer is solely responsible for creating, managing and revoking Staff Users and for assigning their roles and permissions. The Account owner has all permissions, including the management of billing and the acceptance of contractual documents on the Customer’s behalf. The Property manager has configuration and full statistics permissions for its Property, and can view billing without changing it. The reception role has operational permissions, including the management of the catalogue and of the content feeding the AI Assistant, of bookings and stays, and the regeneration of QR codes. The Customer may restrict a reception User to specific departments: the restriction applies to Guest requests, the related notifications and the Pre Check-in Function. The Customer undertakes to promptly revoke the access of staff who cease working at the Property.

3.4 The Customer undertakes to notify DevInterface without delay of any suspected unauthorised access to the Account.

4. Configuration, QR codes and Customer Content

4.1 The Customer independently configures the Property profile, the service catalogue, informational content, rates and the documents intended for the AI Assistant and the Widget, indicating which content is to be made public on the Widget. The Customer is responsible for the accuracy, currency and lawfulness of such content.

4.2 The Service generates, for each room, a QR code containing a non-sequential identifier. The Customer is responsible for printing, placing and replacing the QR codes at its premises, and for regenerating the token, which reception Users may also do, should it consider that it has been compromised or disclosed outside the context of the room.

4.3 The Customer is responsible for correctly associating rooms, stay periods and any Guest names entered into the Service. The Concierge Module neither requires nor directly collects identifying data from the Guest.

4.4 The Customer independently configures, within the limits of its Plan, the enabling of External sources. The Customer is responsible for the configurations adopted and for the consequences of the third-party information thereby made accessible to its Guests.

5. Relationship with Guests and Bookers and absence of payments within the Service

5.1 The Service does not handle collections or payment transactions charged to Guests or Bookers, in any of its modules. No payment flow is exposed to Guests, Bookers or Visitors, and neither the web app nor the Widget offers checkout or payment data collection functions.

5.2 The prices shown in the catalogue, in the Widget or in booking confirmations are set by the Customer, which is solely responsible for them. Prices in the service catalogue are for information purposes only. The confirmation, provision and charging of services and stays take place outside the Service, according to the methods and terms set by the Customer.

5.3 The contractual relationship concerning hotel services and stays exists solely between the Customer and its Guests or Bookers. DevInterface is not a party to that relationship and accepts no liability for the performance, quality, availability or price of the services offered by the Property.

5.4 The Customer is solely responsible for taking charge of and fulfilling requests forwarded by Guests and Visitors through the Service. The Service transmits and organises requests but does not guarantee that they are read, handled promptly or resolved.

5-bis.1 Bookings and availability. The Customer is responsible for entering, confirming, amending and cancelling bookings, and for the correctness of the availability, room types, rates, restrictions and conditions applied. The Service prevents two confirmed or optioned bookings from being recorded on the same room and nights, and flags in the management panel only, without sending notifications, overlaps with booking requests and with external calendars. Options not confirmed by the stated deadline are cancelled automatically. The decision to confirm or refuse a booking remains with the Customer.

5-bis.2 External calendars. Synchronisation with external calendars takes place periodically, according to the Service’s technical schedule and the availability of the source calendars, and is neither instantaneous nor guaranteed. It imports into the Service the bookings of the external calendars and does not send to those calendars the bookings recorded in the Service: it is the Customer’s responsibility to close availability on the portals using their own tools. An imported booking whose event no longer appears in the source calendar is cancelled automatically. The Customer acknowledges that overlapping bookings may occur between two synchronisations and remains responsible for handling any overbooking and the related dealings with Guests and portals. The Customer is also responsible for complying with the agreements concluded with booking portals, including any rate parity clauses.

5-bis.3 Confirmations to Bookers. Confirmation and receipt e-mails are sent by the Service on the Customer’s behalf: the confirmation when a Staff User orders it to be sent, the receipt of a request made through the Widget automatically. The texts are prepared by the Service and show the booking details and the Property name and contact details configured by the Customer. The Service does not guarantee delivery of the e-mails or that they are read by the recipient.

5-bis.4 Requests from the Widget. A request sent by a Visitor through the Widget is not a confirmed booking and does not commit availability: it is recorded as a request to be assessed, and the Visitor is told that the Property will contact them. Several Visitors may request the same availability. The Customer is responsible for responding to the requests received.

5-bis.5 Installing the Widget. The Customer installs the Widget on its own website and may specify the websites on which the Widget is authorised to run; failing that, the Widget runs on any website into which it is inserted. The booking request form can be enabled only once the Customer has provided the address of its own privacy notice, which it must keep up to date and consistent with the processing carried out through the Widget. If the Customer enables the reading of its own website, it declares that it is entitled to allow its processing and acknowledges that the Widget’s answers may also be based on that text.

5-bis.6 Tourist tax and records. Tourist tax reporting is a calculation aid and does not replace the declarations, forms and payments required by the regulations of the competent municipality, for which the Customer remains solely responsible. Booking records are retained as provided in Article 8.3.

5-ter. Pre Check-in Function and Alloggiati Web

5-ter.1 The obligation to notify the personal details of guests under Article 109 of the Italian Consolidated Law on Public Security (T.U.L.P.S.) remains with the Customer, which is answerable for it to the authority. The Service is a tool supporting compliance and does not perform it autonomously.

5-ter.2 The Customer undertakes to carry out the in-person verification that each Guest matches the corresponding original identity document, as required by the legislation in force, and to record its outcome in the Service. The Service does not allow the data of a Guest to be transmitted without a positive outcome.

5-ter.3 The Customer undertakes not to upload, send or keep through the Service or its channels (including chat and e-mail) copies or images of identity documents.

5-ter.4 The Customer safeguards its Alloggiati Web access credentials, ensures that they are valid and promptly notifies any compromise.

5-ter.5 DevInterface does not guarantee the availability of the Alloggiati Web service, the acceptance of records by the portal or compliance with legal deadlines where the portal or the Service is unavailable. The Customer remains required to make the notification by the alternative means provided, including the file for manual upload made available by the Service. Transmissions whose outcome is uncertain are not repeated automatically and require verification by the Customer’s staff.

5-ter.6 Identity data is erased automatically within the periods set out in the DPA. The Customer must reflect those periods in the notice given to Guests. Once the Function is enabled, the pre check-in form shows Guests a notice prepared by DevInterface and completed with the Property’s details: the Customer must review it before enabling the Function and remains responsible for it as Controller.

6. Plans and fees

6.1 The Service does not include a free trial period. Activation requires subscribing to a Plan and paying the corresponding fee.

6.2 Fees are charged per Property, according to the price list in force at the time of subscription. Each Plan provides for a maximum number of active rooms: the size of the Property determines which Plans can be activated. Prices are exclusive of VAT and any other applicable taxes.

6.3 Billing may be monthly or annual, at the Customer’s choice. Fees are payable in advance and are non-refundable for the period already invoiced, save as provided by mandatory rules.

6.4 Payments are processed through the payment services provider Stripe. No payment instrument data passes through or is stored in DevInterface’s systems: the Customer enters such data exclusively into components hosted by Stripe.

6.5 The Customer may at any time move to a higher Plan, with immediate effect and proportional adjustment. Moving to a lower Plan, or to a Plan without the Reservations Module, entails the application of the limits of the new Plan, and in particular:

the history retention limits referred to in Article 8.2, after a grace period of 30 days;
the limit on active rooms: after a grace period of 7 days, rooms in excess are deactivated automatically, without interrupting stays in progress, and are reactivated automatically on moving to a suitable Plan;
loss of access to the functions not included in the new Plan. Booking records already created remain retained for the period referred to in Article 8.3, but viewing and exporting them from the panel requires the Reservations Module: it is the Customer’s responsibility to export the booking archive before the move. On written request, DevInterface will provide the Customer with a copy even after the move.

6.6 DevInterface may amend the price list by giving the Customer at least 30 days’ notice. The new terms apply from the following renewal; a Customer that does not wish to accept them may withdraw with effect from the end of the current period.

6.7 Invite a friend. The Customer may invite other accommodation businesses using its own referral code. When the invited business has paid its first fee and is still a customer 30 days later, each of the two receives a reward equal to one month of its own fee, applied as a discount on the next invoice. Each Customer may receive no more than 12 rewards in any twelve-month period; a reward that finds no invoice to be applied to within 12 months lapses. DevInterface may cancel a reward not yet used if the referral is abusive or if the fee that generated it has been refunded. The partner programme, addressed to those who refer accommodation businesses on a professional basis, is governed by separate rules.

7. Plan limits and overage

7.1 Each Plan includes a monthly allowance of activities — Guests’ and Visitors’ interactions with the Service, including messages to the assistant, requests and External source searches, each with a weight set out in the price list — and specific conditions for the use of External sources. The allowance is monthly even where billing is annual. The limits are maximum ceilings: the Customer may reduce them but not exceed them.

7.2 The Service also applies technical usage limits per room, per session and per Property, including limits on the consumption of artificial intelligence resources, as an anti-abuse measure. When they are reached the AI Assistant may temporarily suspend its responses, even before the allowance referred to in Article 7.1 has been used up.

7.3 Soft degradation. On reaching approximately 80% of the monthly allowance, the Customer receives a notification, and a second one on reaching 100%. At that point, and save for the overage referred to in Article 7.4, the responses of the AI Assistant and the Widget are suspended until the monthly allowance is renewed and the Guest is invited to contact staff. The catalogue and the sending of requests to staff remain available to Guests in all cases. The Customer expressly acknowledges that such degradation constitutes neither a malfunction nor a breach.

7.4 Overage (Premium Plans). On the Premium and Premium + Reservations Plans only, and only if the Customer has expressly enabled it, once the included monthly allowance has been exceeded additional activities — except those of the Widget, which do not continue beyond the allowance — are billed on a usage basis, in indivisible packages, according to the price list in force. Overage is permitted only on an active subscription in good standing, is accrued over the cycle and charged on the same invoice as the subscription fee, by automatic debit from the registered payment method. No separate invoice is issued.

7.5 Safety cap. Overage does not continue indefinitely: once the maximum number of packages configured by the Customer is reached, the degradation measures referred to in Article 7.3 apply, so that the maximum amount chargeable in the cycle is known in advance. The enabling of overage and the maximum number of packages are set for the whole Account and apply to each Property on a Premium Plan, for each cycle. The Customer is responsible for configuring its own threshold.

7.6 Usage measurement. The authoritative count for billing purposes is the one recorded by the application. DevInterface periodically checks the consistency between the usage recorded and the usage transmitted to the payment services provider, and provides on request the detail of the usage for an invoiced cycle. Any dispute concerning usage must be raised within 30 days of the invoice date.

8. Data retention

8.1 The retention periods for the data processed on the Customer’s behalf are set out, separately for each module, in Article 12 of the DPA.

8.2 Concierge Module. The retention period for conversation and request history is determined by the Plan subscribed and constitutes a maximum ceiling, which the Customer may reduce but not extend. Regardless of the Plan, the erasure of names and revocation of access codes at the end of the stay, and the handling of data subjects’ erasure requests, always remain active.

8.3 Reservations Module. Booking contact details and notes are erased 12 months after the last departure. Booking and tourist tax records are retained for the number of years configured by the Customer, not less than 5, in view of tax obligations; such retention continues even after a move to a Plan without the Reservations Module. Widget conversations are retained for 90 days.

8.4 Pre Check-in Function. Identity data is erased automatically after transmission, cancellation or expiry, within the periods set out in the DPA; Alloggiati Web receipts and transmission logs are retained as long as the records referred to in Article 8.3.

8.5 Beyond the applicable retention window, data is deleted or anonymised; only aggregated information not attributable to identifiable persons continues to feed statistics.

8.6 On a move to a Plan with a shorter retention window, history data exceeding the new window is deleted or anonymised after the grace period referred to in Article 6.5. It is the Customer’s responsibility to export in advance any data it wishes to keep, using the export functions of the panel. Guest conversations and requests cannot be exported.

9. Customer obligations and responsibilities

The Customer undertakes to:

use the Service in compliance with the law and third-party rights;
not upload Content that is unlawful, defamatory, infringing intellectual or industrial property rights, or containing data it is not entitled to use;
ensure the accuracy and currency of Customer Content, with particular regard to information on opening hours, prices, rates, availability, property rules and safety;
provide its Guests, Bookers and Visitors with an adequate privacy notice, acting as Data Controller of their data, and inform them of the automated nature of the AI Assistant and the Widget;
comply with the legal obligations connected with its business — including the notification of guests, the tourist tax, and tax and statistical obligations — for which the Service is merely a supporting tool;
not use the Service for purposes prohibited by the terms of use of third-party providers, in particular OpenAI and Stripe;
not attempt to access data of other Properties, circumvent Plan limits, subject the Service to abnormal or automated loads, or carry out reverse engineering, decompilation or systematic extraction of the platform’s content;
not resell, sublicense or make the Service available to third parties outside its own internal use, unless specifically agreed in writing.

10.1 The Customer acknowledges that responses from the AI Assistant and the Widget are automatically generated by artificial intelligence models based on Customer Content, on the text of its website where enabled and, where applicable, on enabled External sources, and that they may contain errors, inaccuracies or omissions.

10.2 DevInterface does not warrant the accuracy, completeness, currency or fitness for any particular purpose of the responses, nor the quality of automated translations generated by the Service.

10.3 The Customer undertakes not to rely on the AI Assistant or the Widget for information critical to Guests’ health or safety, including by way of example information on allergens, food intolerances, medical prescriptions, emergency or evacuation procedures. Such information must be provided directly by the Property’s staff or through dedicated channels.

10.4 The Customer is required to supervise the operation of the AI Assistant and the Widget, periodically monitor the conversation history and correct any Customer Content that generates inappropriate responses.

10.5 Information from External sources is produced by third parties and transmitted without substantive modification. DevInterface neither verifies nor warrants its accuracy.

10.6 DevInterface adopts reasonable measures to confine the AI Assistant and the Widget to the Property’s informational domain and to counter attempts to manipulate their instructions (prompt injection), without however being able to guarantee their absolute effectiveness.

11. Intellectual property

11.1 The software, the ConSergio.ai trademark, the interface, the Widget code, the documentation and every other component of the Service remain the exclusive property of DevInterface. No rights are transferred to the Customer beyond the licence of use referred to in Article 2.

11.2 Customer Content remains the property of the Customer, which declares that it lawfully holds such content and grants DevInterface a limited, non-exclusive, royalty-free licence, for the term of the contract only and to the extent necessary to provide the Service — including processing, indexing, automated translation, publication through the Widget of the content marked as public, and transmission to the third-party providers listed in the DPA.

11.3 DevInterface may use aggregated and anonymous data deriving from use of the Service, not attributable to the Customer, Guests, Bookers or Visitors, for the purposes of product improvement, internal statistics and benchmarking.

11.4 Unless authorised in writing, neither party may use the other’s trademark or name for promotional purposes. The Widget bears the ConSergio.ai trademark and a statement of its automated nature, which the Customer may neither remove nor conceal, including by means of changes to its own website.

12. Processing of personal data

12.1 In relation to the data of Guests, Bookers and Visitors processed through the Service, the Customer acts as Data Controller and DevInterface as Data Processor, pursuant to Article 28 GDPR. The terms of processing, set out separately for each module, are governed by the DPA, which the Customer accepts together with these Terms.

12.2 In relation to Staff User data processed within the platform, DevInterface acts as Data Processor on behalf of the Customer. In relation to the Customer’s contact and billing data, service communications and the Service’s measurement tools, DevInterface acts as independent Data Controller, as described in the Privacy Policy.

12.3 The Customer acknowledges that the Service uses sub-processors, listed in the DPA, and undertakes to inform its Guests, Bookers and Visitors of what is necessary in its own privacy notice.

12.4 The Customer is responsible for the lawfulness of the data it enters into the Service, including Guest names associated with rooms, booking data and pre check-in data.

13. Service availability and maintenance

13.1 DevInterface adopts reasonable measures to ensure a high level of Service availability, which constitutes a quality objective and not a guaranteed service level backed by penalties, unless otherwise agreed in writing.

13.2 This is without prejudice to interruptions due to scheduled maintenance — normally announced in advance — urgent maintenance, force majeure, cyber attacks or malfunctions of third-party providers, of external calendars or of the Alloggiati Web service.

13.3 If the artificial intelligence provider is unavailable, the Service degrades in a controlled manner: the catalogue, the sending of requests to staff and the functions of the Reservations Module and the Pre Check-in Function that do not depend on it remain available. The forwarding to staff of questions the AI Assistant cannot answer is performed by the Assistant itself, and stops with it.

13.4 DevInterface performs periodic data backups. The Customer is nonetheless encouraged to independently export any data of interest using the export functions available in the panel.

14. Changes to the Service

DevInterface may modify, develop or replace features of the Service for technical, security, regulatory compliance or product-improvement reasons. Where a change involves the removal of a significant feature included in the subscribed Plan, DevInterface shall give reasonable notice; a Customer that does not wish to accept it may withdraw with effect from the date the change takes effect, with a pro-rata refund of the unused portion of the fee.

15. Limitation of liability

15.1 To the extent permitted by law, DevInterface’s aggregate liability to the Customer, on any basis whatsoever, is limited to the fees paid by the Customer in the twelve months preceding the event giving rise to liability.

15.2 DevInterface shall not be liable for indirect damages, loss of data, loss of profit, loss of business opportunities, reputational harm or business interruption.

15.3 DevInterface shall in no event be liable for damages arising from: inaccurate or outdated content, rates or availability entered by the Customer; failure to fulfil, or delay in fulfilling, the requests of Guests, Bookers or Visitors; overbooking or overlapping bookings, including those resulting from external calendar synchronisation times; non-delivery of e-mails sent on the Customer’s behalf; penalties connected with the failure to notify, or late notification of, guests or with tourist tax obligations; reliance on responses of the AI Assistant or the Widget in breach of Article 10; External source configurations adopted by the Customer; disclosure or misuse of QR codes, access credentials or Alloggiati Web credentials.

15.4 The limitations set out in this Article do not apply in cases of wilful misconduct or gross negligence, nor where the law does not permit their exclusion.

15.5 The Customer shall indemnify DevInterface against third-party claims, including those of its Guests, Bookers and Visitors, arising from breach of these Terms or from content and services within the Customer’s own responsibility.

16. Term, withdrawal, suspension and termination

16.1 The contract has a term equal to the subscription period and renews automatically for periods of equal duration, unless notice of cancellation is given before the end of the current period.

16.2 The Customer may withdraw at any time with effect from the end of the period already invoiced, without entitlement to a refund of the amounts paid for that period.

16.3 In the event of non-payment, the Customer has a grace period of 7 days from the first failed charge, during which the Service remains operational. After that period the Property’s subscription is treated as ended under Article 16.5, until payment is brought up to date. DevInterface may definitively terminate the Service in the event of persistent default.

16.4 DevInterface may suspend the Service, with prior notice where possible, in the event of breach of these Terms, of use that compromises the security or stability of the platform, or at the request of the competent authority.

16.5 End of the subscription. When a Property’s subscription ends, through cancellation, non-renewal or expiry of the grace period referred to in Article 16.3, the QR codes and the Widget cease to function for Guests and Visitors, and the Customer is responsible for removing them from its premises and its website. The Account remains accessible to Staff Users in read-only mode, with the existing data and configurations. The end of the subscription does not entail the erasure of data: the retention periods in Article 8 continue to apply, according to the Plan last subscribed, and once they have elapsed the data is deleted or anonymised.

16.6 Reactivation and seasonal suspension. The Customer may reactivate a Property’s ended subscription, and will find content, configurations and QR codes as it left them, except for data erased in the meantime because retention periods have elapsed. A Customer with monthly billing whose Property is open for only part of the year may use this as a seasonal suspension: it cancels the subscription when it closes and reactivates it when it reopens, and no fee is due for the months of suspension. Article 16.5 applies during the suspension.

16.7 Closure of the Account and erasure of data. The Customer may at any time request the closure of the Account by writing to DevInterface. DevInterface may also order it in the event of definitive termination of the Service under Articles 16.3 and 16.4, or for an Account that has had no active subscription for more than 12 months. When the closure is scheduled, the Account is suspended, the active subscriptions of its Properties are cancelled with no further charges, and the Account owner receives a notice stating the date of erasure, which shall be no earlier than 30 days later. Until that date the Customer may export its data or ask for the closure to be cancelled; after that date the data is erased as provided in the DPA, without prejudice to statutory retention obligations. It is the Customer’s responsibility to download, within that period, the archives of the records it is required by law to retain: the booking archive and, if it has used the Pre Check-in Function, the archive of Alloggiati Web receipts and logs. Until the latter has been downloaded, the erasure of the Account remains suspended as provided in the DPA.

17. Changes to these Terms

DevInterface may update these Terms by notifying the Customer. Material changes are notified with at least 30 days’ notice, including by means of a notice in the management panel; continued use of the Service after they take effect constitutes acceptance. A Customer that does not wish to accept material changes may withdraw with effect from the date they take effect.

18. General provisions

18.1 Assignment. The Customer may not assign the contract without DevInterface’s written consent. DevInterface may assign the contract in the context of corporate transactions, giving notice to the Customer.

18.2 Notices. Notices are valid if sent to the e-mail address associated with the Account or, for DevInterface, to the address stated at the beginning of these Terms.

18.3 Confidentiality. Each party undertakes to keep confidential any non-public information of the other party that comes to its knowledge in the performance of the contract.

18.4 Severability. The invalidity of any clause shall not affect the validity of the remaining provisions.

18.5 Entire agreement. These Terms, together with the Privacy Policy, the DPA and the subscribed Plan, constitute the entire agreement between the parties and supersede any prior understanding.

19. Governing law and jurisdiction

These Terms are governed by Italian law. The Court of Verona has exclusive jurisdiction over any dispute.

Digital acceptance

This document is deemed accepted by the Customer when the Account owner ticks the relevant box, during registration for the Service or, for Customers already registered, in the management panel. The user identifier, document version, date and time, IP address and user agent of the acceptance are retained.

Specific approval of clauses

Pursuant to and for the purposes of Articles 1341 and 1342 of the Italian Civil Code, the Customer declares that it specifically approves the following clauses: Art. 5-bis.1 (automatic cancellation of expired options), Art. 5-bis.2 (external calendar synchronisation, automatic cancellation of imported bookings and overbooking), Arts. 5-bis.3 and 5-bis.4 (booking confirmations and requests), Art. 5-bis.6 (tourist tax), Arts. 5-ter.1, 5-ter.5 and 5-ter.6 (guest notification obligations and limitations of the Pre Check-in Function), Art. 6.3 (non-refundability of fees), Art. 6.5 (effects of moving to a lower Plan, including deactivation of rooms in excess), Art. 6.6 (price list amendments), Art. 6.7 (cancellation of “Invite a friend” rewards), Arts. 7.2 and 7.3 (suspension and degradation of the service upon reaching limits), Arts. 7.4 and 7.5 (metered billing and safety cap), Art. 7.6 (usage measurement and dispute deadline), Art. 8.6 (data deletion upon downgrade), Art. 10 (limitations of the AI Assistant and the Widget), Art. 13.1 (absence of guaranteed service levels), Art. 15 (limitation of liability and indemnity), Arts. 16.3 and 16.4 (suspension of the Service), Art. 16.5 (effects of the end of the subscription), Art. 16.7 (closure of the Account and erasure of data), Art. 17 (unilateral changes to the Terms), Art. 18.1 (assignment of the contract), Art. 19 (exclusive jurisdiction).

DevInterface srl — ConSergio.ai Terms and Conditions of Service — Version 2.1