This agreement governs the processing of personal data that Bujt carries out on behalf of a customer. It forms part of the Terms of Service and applies for as long as Bujt processes personal data for that customer.
1.1 This agreement is between the customer identified in the Order (the "Controller") and Enjoy Albania SH.P.K., registered in the Republic of Albania, with registered office at Rruga Andon Zako Çajupi, Tiranë 1000, Albania (the "Processor"). Bujt is a product of this company. Bujt is not itself a registered company.
1.2 It applies where the Processor processes personal data on behalf of the Controller in the course of providing the Platform, and it is concluded in accordance with Article 28(3) of Regulation (EU) 2016/679 (the "GDPR") and with the equivalent provisions of Albanian data protection law.
1.3 Terms used but not defined here have the meaning given in the Terms of Service or, where they are defined there, in the GDPR.
2.1 In respect of reservation data, guest data, and data about owners, staff and suppliers that the Controller records in the Platform, the Controller is the controller and the Processor is a processor.
2.2 In respect of account administration, billing, security logging and the improvement of its own service, the Processor acts as a controller, and its processing is governed by its Privacy Policy rather than by this agreement.
2.3 Each party is responsible for compliance with the obligations that apply to it in its own role.
3.1 The Processor processes personal data only on documented instructions from the Controller. The Terms of Service, this agreement, the configuration the Controller sets in the Platform, and the use the Controller makes of its features, together constitute those instructions.
3.2 The Processor also processes personal data where required to do so by law to which it is subject. In that case it informs the Controller of the requirement before processing, unless the law prohibits that information on important grounds of public interest.
3.3 The Processor informs the Controller without undue delay if, in its opinion, an instruction infringes the GDPR or other applicable data protection law. The Processor may suspend the affected processing until the instruction is confirmed or withdrawn.
3.4 The Processor does not use personal data processed under this agreement to train machine learning models, and it contractually prohibits its sub-processors from doing so.
The Processor ensures that persons authorised to process personal data are bound by an obligation of confidentiality, that access is granted on the basis of least privilege, that it is limited to what each person needs to perform their duties, and that it is withdrawn when the duty ends.
5.1 The Processor implements the technical and organisational measures set out in Annex II, having regard to the state of the art, the cost of implementation, and the nature, scope, context and purposes of processing, as well as the risk to the rights and freedoms of natural persons.
5.2 The Processor may update those measures, provided that the level of protection is not reduced.
6.1 The Controller grants the Processor general authorisation to engage sub-processors. The sub-processors engaged at the date of this agreement are listed in Annex III.
6.2 The Processor gives the Controller at least 30 days notice before adding or replacing a sub-processor, by email to the administrative contact. The Controller may object on reasonable grounds related to data protection within that period. Where the parties cannot agree a solution, the Controller may terminate the affected part of the Order without penalty, and the Processor will refund fees paid for the unexpired part of the Subscription Term attributable to that part.
6.3 The Processor imposes on each sub-processor, by written contract, obligations no less protective than those in this agreement, and it remains fully liable to the Controller for the performance of the sub-processor's obligations.
7.1 Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Controller's obligation to respond to requests to exercise data subject rights.
7.2 Where the Processor receives such a request directly from a data subject, it does not respond to it substantively. It forwards the request to the Controller without undue delay and informs the data subject that it has done so.
7.3 The Processor assists the Controller in ensuring compliance with the obligations in Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to it.
7.4 Assistance is provided at no additional charge where it can be given through the features of the Platform. Where it requires material effort beyond that, the Processor may charge at its then current rates, on notice given before the work begins.
8.1 The Processor notifies the Controller without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting personal data processed under this agreement.
8.2 The notification describes the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a point of contact. Where the information is not all available at once, it is provided in phases without undue further delay.
8.3 The Processor does not notify a supervisory authority or a data subject on behalf of the Controller unless the Controller instructs it to do so in writing.
9.1 Personal data is hosted in the European Union (Frankfurt, Germany).
9.2 Where the Processor transfers personal data to a country that has not been recognised as providing an adequate level of protection, it does so on the basis of the standard contractual clauses adopted by the European Commission, or another mechanism permitted by applicable law, and it applies supplementary measures where the circumstances of the transfer require them.
9.3 The Controller authorises the Processor to conclude standard contractual clauses with sub-processors in its own name, for and on behalf of the Controller, where that is necessary to make a transfer lawful.
10.1 The Processor makes available to the Controller the information necessary to demonstrate compliance with Article 28 of the GDPR.
10.2 The Controller may audit compliance once in any 12 month period, and additionally after a personal data breach affecting its data. An audit is carried out on 30 days written notice, during business hours, without unreasonable disruption, and subject to confidentiality.
10.3 Where the Processor holds a current third-party certification or audit report covering the matters in question, provision of that report satisfies clauses 10.1 and 10.2 unless the Controller can show a specific reason why it does not.
10.4 The Controller bears the cost of an audit it initiates, except where the audit reveals a material breach by the Processor, in which case the Processor bears the reasonable cost.
11.1 On termination of the Order, the Controller may export personal data through the Platform for 30 days.
11.2 At the Controller's choice, the Processor deletes or returns personal data processed under this agreement, and deletes existing copies, within 90 days of termination, unless law requires further storage. In the absence of a choice, the Processor deletes.
11.3 Backups are deleted on the rolling cycle described in the Privacy Policy. Until a backup is overwritten, the data in it is not restored to production and remains protected by the measures in Annex II.
12.1 The limitations of liability in the Terms of Service apply to this agreement, except where applicable data protection law does not permit them.
12.2 In the event of conflict between this agreement and the Terms of Service, this agreement prevails in matters of personal data. In the event of conflict between this agreement and the standard contractual clauses, those clauses prevail.
Subject matter. Provision of the Bujt hospitality management platform under the Order.
Duration. The Subscription Term, followed by the export and deletion periods in clause 11.
Nature and purpose. Collection, recording, organisation, storage, retrieval, consultation, use, disclosure by transmission to booking channels and other services the Controller connects, restriction, erasure and destruction, for the purpose of operating the Controller's accommodation business, including reservations, guest communication, housekeeping, transport, pricing, invoicing and reporting.
Categories of data subject. Guests and members of a booking party; employees and contractors of the Controller, including cleaners and drivers; property owners; contacts at suppliers and partner businesses.
Categories of personal data. Identification and contact details; reservation details, including dates, unit, party size and price; travel details, including flight numbers and arrival times where supplied; correspondence between guest and Controller; work assignments and completion records; invoice data, including any tax identification number required on a fiscal invoice; access and audit records.
Special categories. None are requested by the Platform. Where a data subject volunteers such data in free text, it is processed incidentally as part of the record in which it appears.
Frequency. Continuous for the duration of the Subscription Term.
The Processor engages the following categories of sub-processor. The current list, naming each provider, is supplied to the Controller on request and with the copy of this agreement signed at the start of the Subscription Term. Changes are notified in accordance with clause 6.2.
| Category | Purpose | Place of processing |
|---|---|---|
| Application hosting | Running and delivering the Platform | Frankfurt, Germany, with a content delivery network worldwide |
| Database and storage | Storing reservation, operational and account data | Frankfurt, Germany |
| Channel connectivity | Exchanging availability, rates and reservations with booking channels | Germany |
| Messaging | Delivery and receipt of guest messages on the channels the Controller connects | Ireland, with onward transfers under the provider's own safeguards |
| Machine learning | The operations described in the Privacy Policy | United States |
Where the Controller does not connect a given service, the corresponding sub-processor does not receive personal data of that Controller. Fiscal invoicing and airport transfers are not yet in operation. Before the first invoice is issued, and before the first flight is tracked, those providers will be added and notified in accordance with clause 6.2.