Data Processing Agreement
This is a translation. If the two versions differ, the Greek version prevails.
1. Subject matter
1.1 Incorporation into the Terms. This Data Processing Agreement (the “DPA”) forms part of the Vendor Terms (the “Terms”) and binds the company with the corporate name “Arche Digital P.C.” and the distinctive title “Arche Digital” (hereinafter the “Company” or “FESTI” or “We”), and the Vendor, as these are defined in the Terms. The Vendor accepts the DPA by accepting the Terms.
1.2 Scope. Part A governs the processing carried out by the Company on behalf of the Vendor. Part B governs the data of the Bookings, which each party processes on its own behalf. Part C applies in both cases.
1.3 Definitions. The terms “controller”, “processor”, “data subject”, “processing”, “personal data” and “personal data breach” have the meaning given to them in Regulation (EU) 2016/679 (the “GDPR”). Other capitalised terms have the meaning given to them in the Terms.
1.4 Compliance. Each party complies with the GDPR, Law 4624/2019, Law 3471/2006 and any other provision on the protection of personal data that applies to the processing (“Data Protection Legislation”).
PART A – FESTI AS PROCESSOR
2. Processing
2.1 Vendor Data. The Company processes on behalf of the Vendor, by way of example, the personal data collected or recorded through the Vendor’s website and request form, the Vendor’s private notes, the accounts of the members of its team and data exports and, generally, those set out in the Company’s Privacy Policy (“Vendor Data”). In respect of those data, the Vendor is the controller and the Company the processor.
2.2 Data subjects and data. The processing concerns visitors who submit a request to the Vendor, its Customers and prospective customers, and the members of its team. The data are, by way of example: full name and contact details, details of the event and of the request, messages and the Vendor’s private notes.
2.3 Nature, purpose and duration. The Company collects, hosts, stores, organises, displays to the Vendor, exports and deletes the Vendor Data and sends the related notifications, for the sole purpose of providing the corresponding functions of the Platform to the Vendor. The processing is continuous and lasts for as long as the Terms are in force and until the deletion of the data after their termination.
3. Obligations of the Vendor
3.1 Lawfulness. The Vendor ensures that the processing of the Vendor Data is based on a lawful basis and that the data subjects have been informed. It does not record special categories of data, unless this is necessary for the event and permitted by law.
3.2 Instructions. The Terms, the DPA and the settings that the Vendor selects on the Platform constitute its complete instructions to the Company. Additional instructions require the written agreement of the parties.
3.3 Account. The Vendor is responsible for the security of its credentials, for the access it grants to the members of its team and for the data it exports from the Platform.
4. Obligations of FESTI
4.1 Instructions. The Company processes the Vendor Data only in accordance with the Vendor’s instructions, unless Union or Member State law requires otherwise. In that case, it informs the Vendor before the processing, unless the law prohibits this.
4.2 Confidentiality. Only those who need it for the performance of the Terms and are bound by an obligation of confidentiality have access to the Vendor Data.
4.3 Security. The Company implements technical and organisational measures appropriate to the risk, in particular those set out in Annex 1. The Company may amend the measures, provided that the level of protection is not reduced.
4.4 Breaches. The Company informs the Vendor without undue delay and in any event within forty-eight (48) hours of becoming aware of a breach affecting Vendor Data. The notification describes, to the extent known, the nature of the breach, the categories and approximate number of data subjects and records, the likely consequences and the measures taken or proposed. The Company takes measures without undue delay to contain the breach. The notification does not constitute an admission of liability.
4.5 Requests. If the Company receives a request from a data subject concerning Vendor Data, it forwards the request to the Vendor within five (5) working days and does not respond to it itself. It reasonably assists the Vendor in fulfilling requests that cannot be dealt with using the tools of the Platform, as well as with impact assessments and prior consultation with the supervisory authority. It keeps a record of the processing activities it carries out on behalf of the Vendor.
4.6 Return and deletion. After the termination of the Terms, the Vendor may export the Vendor Data within thirty (30) days. Thereafter, the Company deletes them within ninety (90) days, unless the law requires their retention. Data contained in backup copies are deleted in accordance with their normal cycle, at the latest within two (2) years, and until then are not subject to active processing.
5. Sub-processors
5.1 Authorisation. The Vendor grants the Company a general written authorisation to entrust the processing of Vendor Data to third parties (“Sub-processors”). The list of Sub-processors, with the service and the location of each, is set out in Annex 2.
5.2 Changes. The Company informs the Vendor by email at least thirty (30) days before adding or replacing a Sub-processor. In an urgent case, in particular for reasons of security or continuity of the service, it may replace a Sub-processor immediately and informs the Vendor as soon as possible.
5.3 Objection. The Vendor may raise a reasoned objection on data protection grounds within the notice period. The parties seek a solution in good faith.
5.4 Obligations and liability. The Company enters into a written contract with each Sub-processor containing data protection obligations no less strict than those of the DPA, and is liable to the Vendor for their acts and omissions as for its own.
6. Audits
6.1 Information. The Company makes available to the Vendor, upon request, the information necessary to demonstrate its compliance with this Part.
6.2 Conduct of audits. If the information is not sufficient, the Vendor may conduct an audit once a year, on thirty (30) days’ written notice. This limit does not apply following a breach of Vendor Data or where the audit is requested by a supervisory authority. The audit is carried out by the Vendor or by an independent auditor who is bound by confidentiality and is not a competitor of the Company, during working hours, without disrupting the Company’s operations and without access to the data of other users. The cost is borne by the Vendor, unless the audit reveals a material breach of the DPA by the Company.
PART B – BOOKING DATA
7. Independent controllers
7.1 Booking Data. For Booking Requests and Bookings, the Company transmits to the Vendor the Customer’s name, email, photo and rating, the details of the event and of the Booking, the messages, the special requirements, for contracts the Customer’s address and electronic signature, as well as the amounts and status of payments, cancellations and Credits. The Vendor transmits to the Company its decisions on Booking Requests, messages, contracts, cancellations and reviews of Customers (together “Booking Data”).
7.2 Roles. In respect of Booking Data, the Company and the Vendor are independent controllers and not joint controllers. Each is responsible for its own processing, informs the data subjects through its own privacy policy and implements appropriate security measures.
7.3 Purpose limitation. The Vendor uses Booking Data only for examining the Booking Request, performing the Booking and fulfilling its legal obligations. It does not use them to promote products or services without the Customer’s consent or another lawful basis. It does not sell them or disclose them to third parties, except to its own processors, its advisers and the competent authorities.
7.4 Special requirements. Information about special requirements of the Customer or of the Customer’s guests, such as dietary or accessibility needs, may reveal health data or religious beliefs. It is used only for performing the Booking and is deleted when it is no longer necessary.
7.5 Breaches. Each party informs the other without undue delay and in any event within forty-eight (48) hours of a breach that affects Booking Data and may affect the other party, and cooperates in dealing with it. Each party notifies the supervisory authority and the data subjects in respect of its own processing, where required.
7.6 Data subject requests. Each party responds to the requests concerning its own processing. A request concerning the processing of the other party is forwarded to that party within five (5) working days.
7.7 Retention. Each party retains Booking Data in accordance with its own retention policy and its legal obligations. Termination of the Terms does not affect the data that the Vendor retains as controller.
PART C – COMMON PROVISIONS
8. Transfers outside the EEA
8.1 Safeguards. Neither party transfers Vendor Data or Booking Data outside the EEA except in accordance with Chapter V of the GDPR. Each transfer is based on an adequacy decision of the Commission, including the EU–US Data Privacy Framework for recipients certified under it, or on the standard contractual clauses of Commission Implementing Decision (EU) 2021/914 (“SCCs”), with the supplementary measures required.
8.2 Sub-processors. For transfers of Vendor Data to Sub-processors that are not covered by an adequacy decision, the Company enters into the SCCs with them (Module Three: processor to processor).
8.3 Vendors outside the EEA. If the Vendor is established in a third country without an adequacy decision, the SCCs Module One (controller to controller) for Booking Data and Module Four (processor to controller) for Vendor Data are incorporated into the DPA, with the Company as exporter and the Vendor as importer. In those SCCs, Clause 7 and the optional wording of Clause 11 do not apply; the competent supervisory authority, where applicable, is the Hellenic Data Protection Authority; Greek law applies and the courts of Athens have jurisdiction. Annexes I and II of the SCCs are completed with the description of the processing and the security measures provided for in the DPA.
9. General terms
9.1 Amendments. The DPA is amended by the procedure for amending the Terms. The list of Sub-processors is updated by means of the notification provided for in Part A. Previous versions of the DPA are available on the Platform.
9.2 Liability. The liability of each party under the DPA is subject to the limitations in the Terms. The limitations do not affect the rights of data subjects under Article 82 GDPR or liability for wilful misconduct or gross negligence.
9.3 Precedence. In the event of a conflict, the SCCs, the DPA and the Terms prevail, in that order.
9.4 Duration. The DPA remains in force for as long as the Terms are in force and, after their termination, for as long as the Company processes Vendor Data.
9.5 Invalidity of a term. If a term of the DPA is held invalid, the remaining terms continue to apply.
9.6 Governing law and jurisdiction. The DPA is governed by Greek law. The courts of Athens have exclusive jurisdiction over any dispute.
Annex 1: Technical and organisational security measures
- encryption of communications with the Platform (TLS);
- storage of passwords and keys only in the form of a cryptographic hash;
- recording of IP addresses as a cryptographic hash, where the full address is not required;
- staff access only where necessary, with logging of actions;
- protection of login forms against automated attacks;
- error monitoring without IP addresses or email addresses;
- hosting in data centres within the EU and regular backups.
Annex 2: Sub-processors
| Sub-processor | Service | Location |
|---|---|---|
| Hetzner Online GmbH | Hosting of the Platform | Germany |
| Laravel Holdings Inc. (Laravel Forge) | Server management | United States |
| Cloudflare, Inc. | File storage, content delivery network, bot protection | United States |
| Resend, Inc. (backup: Postmark, ActiveCampaign LLC) | Sending email | United States |
| SMS.to | Sending SMS | United Kingdom |
| AMD Telecom S.A. (Routee) | Sending SMS | Greece |
| Sinch AB | Sending SMS | Sweden |
| Google LLC (Firebase Cloud Messaging) | Push notifications | United States |
| Functional Software, Inc. (Sentry) | Error monitoring | United States |