Data Processing Agreement

(2026-11-04)

How BookSpot processes personal data on behalf of its customers when providing the BookSpot booking system, in line with Article 28 GDPR.

1. Scope

This Data Processing Agreement ("DPA") is entered into between BookSpot AB, reg. no. 559241-7819 ("Processor" and "BookSpot"), and the company that uses the BookSpot booking system ("Controller" and "Client"), together the "Parties". The "Service Agreement" means the agreement governing provision and use of the BookSpot booking system, including the applicable BookSpot Terms & Conditions, order confirmation and any Master Agreement.

To deliver the services under the Service Agreement (the "Services"), the Processor processes personal data on the Controller's behalf. This DPA governs that processing under Applicable Data Protection Law and forms part of the Service Agreement. It becomes effective when the Controller validly accepts the Service Agreement incorporating this DPA, including electronically, without a separate signature. The Parties shall retain evidence of acceptance and the applicable DPA version. This DPA must be effective before the Processor starts processing personal data on the Controller's behalf and supersedes prior data processing terms between the Parties for the same processing.

"GDPR" means Regulation (EU) 2016/679, as amended from time to time (the EU GDPR). "UK GDPR" has the meaning given in section 3(10) of the UK Data Protection Act 2018. "UK Data Protection Law" means the UK GDPR, the Data Protection Act 2018 and applicable UK laws and regulations relating to the protection of personal data. "Applicable Data Protection Law" means the GDPR, applicable Union or Member State law relating to the protection of personal data, and UK Data Protection Law, in each case as amended, supplemented or replaced from time to time and to the extent applicable to the relevant processing under this DPA. Unless otherwise expressly defined, data protection terms have the meanings given in the applicable regime. "Personal Data Breach" has the meaning in Article 4(12) of the GDPR or UK GDPR, as applicable.

Where the UK GDPR applies to the Controller's processing under this DPA, the Parties' contractual obligations concerning that processing also cover the corresponding requirements of the UK GDPR and Data Protection Act 2018. References to the GDPR and its Articles or Chapters in this DPA include the corresponding UK GDPR provisions, as applicable, except references expressly specific to the EU regime, such as EU adequacy decisions and Commission Decision (EU) 2021/914. The EU and UK transfer rules in section 4 apply separately and cumulatively where relevant. References to a supervisory authority include the competent UK supervisory authority where applicable. This clause does not disapply the GDPR where it also applies and does not, by itself, determine the territorial application of either regime to either Party.

2. Instructions

The Processor shall process personal data on the Controller's behalf solely to provide the Services and only on the Controller's documented instructions, including with regard to disclosures and international transfers. Those instructions comprise this DPA, Appendix 1, the Controller's use of the Services and settings within the agreed functionality, and any additional documented instructions agreed between the Parties (the "Instructions"). No ownership rights are transferred by this DPA. The Processor shall not process the personal data for its own purposes under this DPA. Processing outside the Instructions is permitted only where required by Union or Member State law to which the Processor is subject or, in relation to processing subject to the UK GDPR, by applicable UK domestic law to which the Processor is subject. The Processor shall inform the Controller of that legal requirement before processing, unless the relevant law prohibits such information on important grounds of public interest. A UK legal requirement does not itself permit processing or disclosure contrary to concurrently applicable EU data protection requirements, including Chapter V GDPR. The Processor shall promptly inform the Controller of any identified conflict to the extent legally permitted and seek a lawful resolution.

The Controller determines the purposes of processing and is responsible for its lawfulness, the accuracy and minimisation of the data it supplies, necessary notices to data subjects and a lawful basis under Article 6 GDPR and, where relevant, Article 9 or 10 GDPR. It shall ensure that its Instructions are lawful and sufficient and configure access and retention within the functionality available to it. The Processor shall maintain records as required by Article 30(2) GDPR. The Processor shall immediately inform the Controller if, in its opinion, an Instruction infringes Applicable Data Protection Law and may suspend only the affected processing pending lawful clarification, while continuing to protect the data and, where feasible, unaffected Services. This does not transfer the Processor's own statutory obligations to the Controller.

Additional Instructions outside the agreed functionality shall be submitted in writing. The Processor shall promptly explain any legal or technical obstacle and, where appropriate, propose a lawful alternative and a reasonable implementation estimate. Changes to the Services or commercial charges require agreement and shall not delay assistance or other obligations to the extent required by Applicable Data Protection Law. The Controller shall not submit unnecessary personal data or use free-text fields for sensitive information outside the agreed scope.

3. Confidentiality and security

Taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks to natural persons, the Processor shall implement and maintain all measures required by Article 32 GDPR, including the technical and organisational measures in Appendix 1. The Processor shall regularly assess and test the effectiveness of those measures and maintain appropriate confidentiality, integrity, availability and resilience, and the ability to restore availability and access following an incident. The Processor may replace measures with equivalent or stronger measures, provided that the overall level of protection is not reduced; material changes requiring amendment of this DPA are subject to section 8.

The Processor shall take reasonable steps to ensure the reliability of its personnel and its sub-processors' personnel who may access the personal data, and limit such access to persons for whom such access is necessary to provide the Services under the Service Agreement or comply with applicable law.

The Processor shall ensure that all persons authorised to process personal data have committed themselves to confidentiality or are subject to an appropriate statutory obligation of confidentiality. That protection shall continue after their access or engagement ends. Disclosure is permitted only under the Instructions, to authorised sub-processors under section 4, or as required by law in the circumstances permitted under section 2, subject to its notification requirements and the transfer requirements in section 4.

4. Sub-processors and international transfers

The Controller gives general written authorisation to engage the sub-processors listed in Appendix 1 for the activities described there. The Processor shall actively notify the Controller in writing at least thirty (30) days before any proposed addition or replacement takes effect. The notice shall identify the legal entity, its processing activities, relevant data categories, processing locations including support access, and any applicable transfer safeguards. The Controller may object within that period on reasonable, substantiated data protection grounds. The Parties shall seek a commercially and technically reasonable solution in good faith. If no solution is available, either Party may terminate only the affected Services before the proposed sub-processor starts processing the affected data, without an early termination charge, and fees prepaid for the unused period of those Services shall be refunded. The Processor shall not disclose the affected data to the objected-to sub-processor unless the objection is resolved or the Controller authorises it. If no objection is received within the notice period, the change is authorised.

The Processor shall appoint only sub-processors providing sufficient guarantees and shall bind each by a written agreement imposing, in substance, the same data protection obligations as this DPA, including appropriate security, assistance, audit, deletion and onward sub-processing obligations. The Processor shall ensure equivalent protection throughout the sub-processing chain and remains fully liable to the Controller for performance of the sub-processors' obligations. The Processor shall maintain an up-to-date list of the sub-processing chain and make information on identities, activities, locations and safeguards available to the Controller. On request, it shall provide relevant contractual provisions or other evidence sufficient to demonstrate compliance, with necessary redactions to protect confidential information and other persons' data; redactions shall not prevent verification of the relevant data protection obligations. Applicable SCC requirements to provide contractual copies remain unaffected.

For transfers subject to the EU GDPR, the Processor shall not transfer personal data to a country outside the European Economic Area ("EEA") or an international organisation, or permit access amounting to such a transfer, without the Controller's prior documented written authorisation and compliance with Chapter V GDPR. Authorisation of a sub-processor does not itself constitute a Chapter V transfer mechanism. Before an authorised transfer, the Processor shall verify that it is covered by a then-valid and applicable adequacy decision under Article 45 GDPR or implement appropriate safeguards under Article 46 GDPR. Where standard contractual clauses are used, the applicable European Commission clauses, including the appropriate module and completed annexes, shall be entered into; for transfers within the scope of Decision (EU) 2021/914, Module Three applies to processor-to-processor transfers and Module Two to controller-to-processor transfers, as appropriate. Where required for Article 46 transfers, the Processor shall document an assessment of relevant third-country laws and practices, implement effective supplementary measures, and make the relevant assessment available to the Controller subject to appropriate confidentiality protections. The Processor shall monitor material changes affecting the safeguards and suspend the affected transfer if adequate protection cannot be maintained, promptly informing the Controller and seeking a lawful alternative. Neither this DPA nor a foreign authority's request alone constitutes a lawful transfer mechanism.

For transfers subject to UK Data Protection Law, the Processor shall not make or authorise a transfer subject to the UK GDPR's international transfer restrictions to a separate recipient outside the United Kingdom ("UK"), including by remote access or onward transfer through a sub-processor, without the Controller's prior documented written authorisation and compliance with the applicable UK transfer rules. Before the transfer, the Processor shall verify that it is covered by then-valid and applicable UK adequacy regulations or other lawful UK adequacy arrangements or, in their absence, implement appropriate safeguards permitted under UK Data Protection Law. Where contractual safeguards are used, the relevant parties shall enter into a duly completed and legally binding UK-approved International Data Transfer Agreement ("IDTA"), or the applicable EU standard contractual clauses together with the UK International Data Transfer Addendum ("UK Addendum"), as appropriate. EU standard contractual clauses alone do not satisfy this contractual requirement for UK transfers. Any required data protection test or transfer risk assessment shall be completed and documented, and necessary supplementary measures implemented, before the transfer. The Processor shall make relevant assessment information available to the Controller subject to appropriate confidentiality protections, monitor material changes and suspend the affected transfer if lawful protection cannot be maintained, promptly informing the Controller and seeking a lawful alternative.

Where the Controller instructs the Processor to provide the Services to the Controller's UK operations, those documented Instructions constitute authorisation under this section for transfers between the UK and the EEA necessary for that purpose, subject to the applicable EU and UK transfer rules. This does not authorise a new sub-processor or other processing location not approved under this DPA. No IDTA, UK Addendum or EU standard contractual clauses are required solely because a transfer takes place between the UK and the EEA, where the relevant transfer is covered by then-valid and applicable adequacy arrangements under each applicable regime. If both EU and UK transfer rules apply, both must be satisfied. Authorisation under this DPA is not itself a statutory transfer mechanism.

If the Processor receives a request from a public authority for personal data processed under this DPA, it shall, unless prohibited by applicable law, promptly notify the Controller and provide available details. It shall assess the request's legality and scope, seek to lift any notification prohibition where legally possible, challenge the request where there are reasonable grounds to do so and disclose only the minimum legally required data. A third-country order does not by itself displace the Instructions or the requirements of Applicable Data Protection Law, including the applicable EU or UK requirements concerning lawful processing and international transfers. The Processor shall comply with any additional notification and challenge obligations in applicable transfer instruments under this section.

5. Personal data breaches

The Processor shall notify the Controller without undue delay and in any event within forty-eight (48) hours after becoming aware of a Personal Data Breach affecting personal data processed under this DPA. Notification shall not be delayed pending completion of an investigation and shall, to the extent available, describe the nature of the breach, categories and approximate numbers of affected data subjects and records, likely consequences, measures taken or proposed, and a contact point for further information. Information not available initially shall be supplied in phases without undue further delay. The Processor shall document the breach, take appropriate containment and remediation measures, preserve relevant evidence and assist the Controller in complying with Articles 33 and 34 GDPR. The Controller is responsible for deciding on notifications to authorities and data subjects; the Processor shall not notify on the Controller's behalf without instructions unless legally required. A notification is not an admission of liability.

6. Assistance and audits

The Controller is responsible for assessing and responding to data-subject requests under Chapter III GDPR. Taking into account the nature of the processing, the Processor shall assist the Controller by appropriate technical and organisational measures, insofar as possible, in fulfilling those obligations. This includes making available relevant search, access, export, rectification, restriction and deletion functionality and, where the Controller cannot fulfil a request through that functionality, providing assistance concerning data within the Processor's control. The Processor shall inform the Controller without undue delay of any request received and shall not substantively respond except on the Controller's documented instructions or as required by law. Taking into account the nature of the processing and the information available to it, the Processor shall also assist with compliance with Articles 32 to 36 GDPR, including relevant security information, incident documentation, information on processing and safeguards for impact assessments, and assistance with prior consultation. The Parties shall cooperate in good faith to meet applicable statutory deadlines.

The Processor shall make available all information necessary to demonstrate compliance with this DPA and Article 28 GDPR, and shall allow and contribute to audits, including inspections, by the Controller or an independent auditor mandated by it. The Parties shall first consider whether available documentation, relevant independent reports or a remote review provide adequate verification; these do not replace an inspection where necessary. An auditor shall have appropriate expertise, independence and confidentiality obligations. The Processor may object to a direct competitor acting as auditor only on substantiated confidentiality or conflict-of-interest grounds and shall cooperate in promptly identifying an appropriate alternative, without obstructing the Controller's statutory audit rights.

Routine audits shall be on reasonable advance notice, ordinarily no more than once in any twelve-month period, during normal business hours and without unnecessary disruption. Additional audits, shorter notice or different timing shall be permitted where required by a supervisory authority or Applicable Data Protection Law, or reasonably necessary following a Personal Data Breach, a material change affecting compliance, or substantiated indications of non-compliance. Audits shall be limited to relevant processing and subject to appropriate confidentiality and reasonable security requirements, without exposing other customers' personal data or unrelated confidential information; suitable alternative evidence shall be provided where direct access would compromise those protections. These arrangements shall not prevent effective verification or restrict supervisory authorities' powers. Each Party bears its own audit costs, except that the Controller shall bear its appointed auditor's fees.

Ordinary assistance through the Services' standard functionality and provision of existing compliance documentation are included in the agreed service fees. For additional assistance requiring material work beyond that scope, the Processor may charge reasonable, proportionate fees agreed in advance, except to the extent required to remedy the Processor's breach of this DPA or Applicable Data Protection Law. The Processor shall provide an estimate where practicable. Fee discussions or disputes shall not prevent or delay legally required assistance or effective exercise of audit rights.

7. Term, deletion and liability

This DPA takes effect as set out in section 1 and remains in force for as long as the Processor or its sub-processors process personal data on behalf of the Controller, including pending return or deletion. If the Parties renew or replace the Service Agreement for the same Services without agreeing a replacement DPA, this DPA continues to apply and the renewed or replacement agreement is the Service Agreement for these purposes.

When the processing Services end, the Controller may choose return of all personal data followed by deletion of existing copies, or deletion of all personal data and copies. Return shall be in a commonly used, structured, machine-readable format supported by the Services, unless another format is agreed. The procedure and time limits are set out in Appendix 1. The Processor shall ensure that deletion covers data held by its sub-processors and shall confirm completion in writing on request. If Union or Member State law or, in relation to processing subject to the UK GDPR, applicable UK domestic law requires continued storage, the Processor shall, unless legally prohibited, identify the requirement and retention period to the Controller, isolate and protect the retained data, process it only for that legal requirement, and delete it when retention is no longer required. UK-law retention shall not authorise retention contrary to concurrently applicable EU data protection requirements; any identified conflict shall be handled under section 2. This DPA continues to protect all retained data.

Liability towards data subjects is governed by Article 82 GDPR. As between the Parties, the exclusions and limitations of liability in the Service Agreement apply to claims under or in connection with this DPA to the extent permitted by applicable law. Nothing in this DPA restricts data subjects' statutory rights, supervisory authorities' powers, mandatory rights of recourse under Article 82(5) GDPR, or rights and obligations under applicable standard contractual clauses that cannot lawfully be restricted.

8. Changes, law and disputes

The Processor may make editorial or administrative updates to this DPA that do not substantively change its meaning, the scope of processing or either Party's rights or obligations, by giving the Controller written notice.

The Controller authorises the Processor to update the technical and organisational implementation of the Services and the security measures described in Appendix 1, provided that the updates remain within the agreed scope of the Services and the Controller's documented Instructions, do not materially reduce the overall level of protection, and continue to satisfy Applicable Data Protection Law. Such updates do not require separate acceptance. The Processor shall notify the Controller directly of material changes to those measures in reasonable time before implementation. Where an update is urgently necessary to address a security risk or comply with a binding legal requirement, the Processor may implement it immediately and notify the Controller without undue delay. This paragraph does not authorise changes to the purposes of processing, additional categories of personal data or data subjects, or other substantive amendments to this DPA.

For other amendments, the Processor shall notify the Controller directly, ordinarily at least thirty (30) days before the proposed effective date, and provide the revised DPA. Such amendments require the Controller's acceptance, which may be given electronically through a standardised acceptance process. Until acceptance, the existing DPA continues to apply. Changes to sub-processors are governed separately by section 4.

Notices under this section may be sent by email to the Controller's designated contractual contact or through another agreed channel providing a direct notification that the Controller can retain.

If there is a conflict concerning personal data processing, this DPA prevails over the Service Agreement and other service terms, except that the liability allocation incorporated in section 7 continues to apply to the extent lawful. The mandatory provisions of any applicable standard contractual clauses, UK International Data Transfer Agreement or UK Addendum entered into for a relevant transfer prevail over conflicting terms of this DPA or the Service Agreement, including conflicting governing-law or jurisdiction provisions.

Swedish law applies. Disputes between the Parties shall be subject to Swedish courts, with Stockholm District Court as the first instance, without prejudice to data subjects' mandatory rights and remedies under Applicable Data Protection Law, including the GDPR and UK Data Protection Law, the powers of competent EU or UK supervisory authorities, or mandatory jurisdiction provisions of applicable transfer instruments under section 4.

Appendix 1: Instructions

1. Services, purpose, nature and duration of processing

Subject matter: provision of the BookSpot booking system under the Service Agreement. Purpose: to collect and manage the Controller's customer and booking information and deliver booking-related communications as instructed through the Services. Nature and operations: collection, recording, organisation, storage, retrieval, consultation, updating, export, disclosure by transmission to intended recipients and authorised sub-processors, and deletion; hosting, support and troubleshooting, security monitoring, replication, backup and restoration only insofar as necessary to provide and protect the Services on the Controller's behalf. Processing continues for the duration of the Services and, after their end, only for return, deletion or legally required retention under section 7. This description does not authorise additional purposes or integrations outside the agreed Services.

2. Categories of data subjects and personal data

Data subjects: the Controller's customers and, to the extent included by the Controller or such customer in the agreed booking workflow, booking contacts and participants, including children where relevant. The Parties shall document any additional category before the relevant processing begins.

Personal data: first name, surname, telephone number, email address, address, IP address, booking details and booking-form answers supplied by the Controller or its customers. Special categories: health information may occur where the Controller/customer uses booking-form fields for that purpose, such as necessary allergy or accessibility information. Such processing is permitted only within the agreed Services and documented Instructions and subject to the safeguards below and a valid Article 9 condition identified by the Controller.

For health information within the agreed scope, the Processor shall restrict use to the instructed booking purpose, limit access to specifically authorised persons with a demonstrable need, ensure appropriate staff training and confidentiality, maintain access logging and apply the security and retention measures in this Appendix with enhanced protection appropriate to the sensitivity and risk. The Controller shall minimise such fields and specify relevant retention settings. If the available safeguards are insufficient, the Parties shall agree additional safeguards before the relevant processing; the Processor may suspend the affected field or processing pending a lawful solution. This provision does not authorise processing outside the agreed scope.

3. Processing locations and sub-processors

The Processor's own processing location is Sweden. The authorised sub-processors and their currently stated processing locations are listed below. Processing locations include storage, backup, support and administrative access, not only the primary data centre. Any access amounting to a third-country transfer remains subject to section 4. The Processor shall verify the legal entities, actual locations and onward sub-processing chain and maintain accurate information before the relevant processing begins.

• UpCloud, Helsinki, Finland: Data centre and infrastructure. Processed in Germany.

• Mailgun (Sinch Sweden AB), Stockholm, Sweden: Email delivery. Processed in Germany and Belgium.

4. Security measures

• TLS encryption for all traffic, and hosting at UpCloud in Germany with encrypted storage.

• Real-time replication to a standby database that takes over if the primary fails.

• Full backups every 24 hours, kept for seven days, stored separately and tested for restore.

• Personal accounts and need-to-know access for staff. The Controller manages its own users.

• Access logging, and confidentiality commitments for staff and service providers.

• Risk-appropriate access management, periodic review and prompt revocation of access, strong authentication for privileged access, and appropriate measures preventing unauthorised cross-customer access.

These measures are contractual safeguards to be maintained throughout processing, not a representation of any unlisted certification. The Processor shall maintain a documented implementation description, including the scope of privileged authentication, logging and log retention, tenant separation, testing frequency, restoration arrangements and deletion procedures, and make relevant information available for the Controller's Article 32 assessment. Equivalent or stronger replacement measures are governed by section 3.

5. Return or deletion procedure at the end of processing

The Controller determines retention periods for personal data processed on its behalf and shall use available retention and deletion settings or provide documented Instructions. The Processor shall implement those Instructions and shall not independently retain customer booking data for its own purposes. During the term, the Processor shall delete the requested personal data from active systems without undue delay and no later than ten (10) business days after a sufficiently specific authorised request. The backup safeguards below apply; any legally required retention is governed by section 7.

At the end of the Services, the Controller may select return or deletion by written notice, including through the agreed service channel, and may change its choice before completion. Return shall be completed within ten (10) business days after the request or the end of the Services, whichever is later. Following return, active copies shall be deleted within ten (10) business days after the returned data have been made securely available to the Controller. If deletion is selected, active copies shall be deleted within ten (10) business days after the request or the end of the Services, whichever is later. Unless the Controller selects return or gives another lawful Instruction within thirty (30) days after the end of the Services, the Controller instructs the Processor under this DPA to delete active copies within the following ten (10) business days. The Processor shall not delete data earlier than needed to honour a timely return request.

Deletion includes production systems, active replicas, relevant support or export copies and copies held by sub-processors. Residual data in backups shall be protected against ordinary access and further use and deleted or overwritten through the documented seven-day backup retention cycle, no later than seven (7) days after deletion from active systems. If a backup is restored before expiry, the Processor shall reapply the deletion Instructions before restored data are used for ordinary processing. Legally required retention under section 7 is the only exception. The Processor shall document completion and, on request, provide written confirmation covering active systems, backups and sub-processors.