Data Processing Agreement

1. Preamble

1. These Contractual Clauses (the Clauses) set out the rights and obligations of the data controller and the data processor, when processing personal data on behalf of the data controller.
2. The Clauses have been designed to ensure the parties' compliance with Article 28(3) of Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data and repealing Directive 95/46/EC (General Data Protection Regulation).
3. In the context of the provision of Tables (tables.so), the data processor will process personal data on behalf of the data controller in accordance with the Clauses.
4. The Clauses shall take priority over any similar provisions contained in other agreements between the parties.
5. Four appendices are attached to the Clauses and form an integral part of the Clauses.
6. Appendix A contains details about the processing of personal data, including the purpose and nature of the processing, type of personal data, categories of data subject and duration of the processing.
7. Appendix B contains the data controller's conditions for the data processor's use of sub-processors and a list of sub-processors authorised by the data controller.
8. Appendix C contains the data controller's instructions with regards to the processing of personal data, the minimum security measures to be implemented by the data processor and how audits of the data processor and any sub-processors are to be performed.
9. Appendix D contains provisions for other activities which are not covered by the Clauses.
10. The Clauses along with appendices shall be retained in writing, including electronically, by both parties.
11. The Clauses shall not exempt the data processor from obligations to which the data processor is subject pursuant to the General Data Protection Regulation (the GDPR) or other legislation.

2. The rights and obligations of the data controller

1. The data controller is responsible for ensuring that the processing of personal data takes place in compliance with the GDPR (see Article 24 GDPR), the applicable EU or Member State data protection provisions and the Clauses.
2. The data controller has the right and obligation to make decisions about the purposes and means of the processing of personal data.
3. The data controller shall be responsible, among other, for ensuring that the processing of personal data, which the data processor is instructed to perform, has a legal basis.

3. The data processor acts according to instructions

1. The data processor shall process personal data only on documented instructions from the data controller, unless required to do so by Union or Member State law to which the processor is subject. Such instructions shall be specified in appendices A and C. Subsequent instructions can also be given by the data controller throughout the duration of the processing of personal data, but such instructions shall always be documented and kept in writing, including electronically, in connection with the Clauses.
2. The data processor shall immediately inform the data controller if instructions given by the data controller, in the opinion of the data processor, contravene the GDPR or the applicable EU or Member State data protection provisions.

4. Confidentiality

1. The data processor shall only grant access to the personal data being processed on behalf of the data controller to persons under the data processor's authority who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality and only on a need to know basis. The list of persons to whom access has been granted shall be kept under periodic review. On the basis of this review, such access to personal data can be withdrawn, if access is no longer necessary, and personal data shall consequently not be accessible anymore to those persons.
2. The data processor shall at the request of the data controller demonstrate that the concerned persons under the data processor's authority are subject to the abovementioned confidentiality.

5. Security of processing

1. Article 32 GDPR stipulates that, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the data controller and data processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.

   The data controller shall evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. Depending on their relevance, the measures may include the following:

   • Pseudonymisation and encryption of personal data;
   • the ability to ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services;
   • the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
   • a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
2. According to Article 32 GDPR, the data processor shall also, independently from the data controller, evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. To this effect, the data controller shall provide the data processor with all information necessary to identify and evaluate such risks.
3. Furthermore, the data processor shall assist the data controller in ensuring compliance with the data controller's obligations pursuant to Articles 32 GDPR, by inter alia providing the data controller with information concerning the technical and organisational measures already implemented by the data processor pursuant to Article 32 GDPR along with all other information necessary for the data controller to comply with the data controller's obligation under Article 32 GDPR.

   If subsequently, in the assessment of the data controller, mitigation of the identified risks require further measures to be implemented by the data processor, than those already implemented by the data processor pursuant to Article 32 GDPR, the data controller shall specify these additional measures to be implemented in Appendix C.

6. Use of sub-processors

1. The data processor shall meet the requirements specified in Article 28(2) and (4) GDPR in order to engage another processor (a sub-processor).
2. The data processor shall therefore not engage another processor (sub-processor) for the fulfilment of the Clauses without the prior general written authorisation of the data controller.
3. The data processor has the data controller's general authorisation for the engagement of sub-processors. The data processor shall inform in writing the data controller of any intended changes concerning the addition or replacement of sub-processors at least 30 days in advance, thereby giving the data controller the opportunity to object to such changes prior to the engagement of the concerned sub-processor(s). Longer time periods of prior notice for specific sub-processing services can be provided in Appendix B. The list of sub-processors already authorised by the data controller can be found in Appendix B.
4. Where the data processor engages a sub-processor for carrying out specific processing activities on behalf of the data controller, the same data protection obligations as set out in the Clauses shall be imposed on that sub-processor by way of a contract or other legal act under EU or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the Clauses and the GDPR. The data processor shall therefore be responsible for requiring that the sub-processor at least complies with the obligations to which the data processor is subject pursuant to the Clauses and the GDPR.
5. A copy of such a sub-processor agreement and subsequent amendments shall, at the data controller's request, be submitted to the data controller, thereby giving the data controller the opportunity to ensure that the same data protection obligations as set out in the Clauses are imposed on the sub-processor. Clauses on business related issues that do not affect the legal data protection content of the sub-processor agreement, shall not require submission to the data controller.
6. If the sub-processor does not fulfil his data protection obligations, the data processor shall remain fully liable to the data controller as regards the fulfilment of the obligations of the sub-processor. This does not affect the rights of the data subjects under the GDPR, in particular those foreseen in Articles 79 and 82 GDPR, against the data controller and the data processor, including the sub-processor.

7. Transfer of data to third countries or international organisations

1. Any transfer of personal data to third countries or international organisations by the data processor shall only occur on the basis of documented instructions from the data controller and shall always take place in compliance with Chapter V GDPR.
2. In case transfers to third countries or international organisations, which the data processor has not been instructed to perform by the data controller, is required under EU or Member State law to which the data processor is subject, the data processor shall inform the data controller of that legal requirement prior to processing unless that law prohibits such information on important grounds of public interest.
3. Without documented instructions from the data controller, the data processor therefore cannot within the framework of the Clauses:
   • transfer personal data to a data controller or a data processor in a third country or in an international organisation;
   • transfer the processing of personal data to a sub-processor in a third country;
   • have the personal data processed by the data processor in a third country.
4. The data controller's instructions regarding the transfer of personal data to a third country including, if applicable, the transfer tool under Chapter V GDPR on which they are based, shall be set out in Appendix C.6.
5. The Clauses shall not be confused with standard data protection clauses within the meaning of Article 46(2)(c) and (d) GDPR, and the Clauses cannot be relied upon by the parties as a transfer tool under Chapter V GDPR.

8. Assistance to the data controller

1. Taking into account the nature of the processing, the data processor shall assist the data controller by appropriate technical and organisational measures, insofar as this is possible, in the fulfilment of the data controller's obligations to respond to requests for exercising the data subject's rights laid down in Chapter III GDPR. This entails that the data processor shall, insofar as this is possible, assist the data controller in the data controller's compliance with:
   • the right to be informed when collecting personal data from the data subject;
   • the right to be informed when personal data have not been obtained from the data subject;
   • the right of access by the data subject;
   • the right to rectification;
   • the right to erasure ("the right to be forgotten");
   • the right to restriction of processing;
   • notification obligation regarding rectification or erasure of personal data or restriction of processing;
   • the right to data portability;
   • the right to object;
   • the right not to be subject to a decision based solely on automated processing, including profiling.
2. In addition to the data processor's obligation to assist the data controller pursuant to Clause 5.3, the data processor shall furthermore, taking into account the nature of the processing and the information available to the data processor, assist the data controller in ensuring compliance with:
   • The data controller's obligation to without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the competent supervisory authority, Datatilsynet (the Danish Data Protection Agency), unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons;
   • the data controller's obligation to without undue delay communicate the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons;
   • the data controller's obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a data protection impact assessment);
   • the data controller's obligation to consult the competent supervisory authority, Datatilsynet (the Danish Data Protection Agency), prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the data controller to mitigate the risk.
3. The parties shall define in Appendix C the appropriate technical and organisational measures by which the data processor is required to assist the data controller as well as the scope and the extent of the assistance required. This applies to the obligations foreseen in Clause 8.1 and 8.2.

9. Notification of personal data breach

1. In case of any personal data breach, the data processor shall, without undue delay after having become aware of it, notify the data controller of the personal data breach.
2. The data processor's notification to the data controller shall, if possible, take place within 24 hours after the data processor has become aware of the personal data breach to enable the data controller to comply with the data controller's obligation to notify the personal data breach to the competent supervisory authority, cf. Article 33 GDPR.
3. In accordance with Clause 8.2.a, the data processor shall assist the data controller in notifying the personal data breach to the competent supervisory authority, meaning that the data processor is required to assist in obtaining the information listed below which, pursuant to Article 33(3) GDPR, shall be stated in the data controller's notification to the competent supervisory authority:
   • The nature of the personal data breach including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
   • the likely consequences of the personal data breach;
   • the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
4. The parties shall define in Appendix C all the elements to be provided by the data processor when assisting the data controller in the notification of a personal data breach to the competent supervisory authority.

10. Erasure and return of data

1. On termination of the provision of personal data processing services, the data processor shall be under obligation to delete all personal data processed on behalf of the data controller and certify to the data controller that it has done so, unless Union or Member State law requires storage of the personal data.

11. Audit and inspection

1. The data processor shall make available to the data controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 and the Clauses and allow for and contribute to audits, including inspections, conducted by the data controller or another auditor mandated by the data controller.
2. Procedures applicable to the data controller's audits, including inspections, of the data processor and sub-processors are specified in appendices C.7 and C.8.
3. The data processor shall be required to provide the supervisory authorities, which pursuant to applicable legislation have access to the data controller's and data processor's facilities, or representatives acting on behalf of such supervisory authorities, with access to the data processor's physical facilities on presentation of appropriate identification.

12. The parties' agreement on other terms

1. The parties may agree other clauses concerning the provision of the personal data processing service specifying e.g. liability, as long as they do not contradict directly or indirectly the Clauses or prejudice the fundamental rights or freedoms of the data subject and the protection afforded by the GDPR.

13. Commencement and termination

1. The Clauses shall become effective on the date of the data controller's acceptance of the Clauses, as set out in Clause 13.5.
2. Both parties shall be entitled to require the Clauses renegotiated if changes to the law or inexpediency of the Clauses should give rise to such renegotiation.
3. The Clauses shall apply for the duration of the provision of personal data processing services. For the duration of the provision of personal data processing services, the Clauses cannot be terminated unless other Clauses governing the provision of personal data processing services have been agreed between the parties.
4. If the provision of personal data processing services is terminated, and the personal data is deleted or returned to the data controller pursuant to Clause 10.1 and Appendix C.4, the Clauses may be terminated by written notice by either party.
5. Acceptance. The data controller accepts these Clauses electronically as part of the data processor's terms when creating and/or using Tables (tables.so). The data processor records and retains documentation of who accepted, as well as the time and version. On behalf of the data processor, the Clauses are entered into by Theoflow ApS.

14. Data controller and data processor contacts

1. The parties may contact each other using the following contact points, and shall be under obligation continuously to inform each other of changes to them.

For the data processor (Theoflow ApS): email privacy@tables.so.

For the data controller (the customer): the contact person identified at sign-up or on the customer's account.

Appendix A: Information about the processing

A.1 Purpose of the processing

The data processor provides a B2B sales and prospecting platform (Tables, tables.so) to the data controller. The processing is carried out for the purpose of enabling the data controller to store, organise and manage contact information and to plan and carry out sales and prospecting activities through the platform.

A.2 Nature of the processing

The processing comprises storage (hosting), organisation, search and display of personal data, enrichment of the data controller's own uploaded lists, synchronisation with the data controller's own connected systems (for example, a CRM that the data controller connects), backup, and technical support.

A.3 Types of personal data

About the data controller's users: name, work email, phone number, job title, company, login details, IP address and usage/log data.

About the contacts the data controller stores and enriches in the platform: name, work email, phone number, job title, company, publicly available profile information, and any notes added by the data controller. Enrichment may add further contact details such as phone number and email.

The processing comprises only ordinary personal data under Article 6 of the GDPR. It does not comprise special categories of personal data (Article 9).

A.4 Categories of data subjects

The data controller's own users/employees and the natural persons (typically business contacts/leads) whose data the data controller stores and processes in the platform.

A.5 Duration of the processing

The processing is not time-limited and lasts until the main agreement/subscription between the parties terminates.

Appendix B: Sub-processors

B.1 Authorised sub-processors

On entry into force of the Clauses, the data controller has authorised the use of the following sub-processors. The final legal name and address of each sub-processor is confirmed against the relevant provider's own data processing agreement.

• Vercel, Inc. (USA): Hosting and operation of the platform's application layer (functions run in the EU and the USA).
• Neon, Inc. (USA): Hosting of the database containing customer data (data stored in the EU, in Frankfurt).
• PostHog, Inc. (USA): Product analytics and usage statistics in the web application (data in the EU, in Frankfurt).
• OpenAI, L.L.C. (USA): AI-based enrichment of the controller's data.
• Anthropic, PBC (USA): AI-based enrichment of the controller's data.
• Contact enrichment, one or more of: Prospeo, Findymail, Coresignal, ContactOut: Look-up and enrichment of contact details (phone, email) on the controller's uploaded data. Country/transfer basis confirmed per provider; a DPA must be in place before use.

The data processor may not, without the data controller's written authorisation, use a sub-processor for a processing activity other than the one described, or use a different sub-processor for that activity.

B.2 Notice for authorisation of sub-processors

The data processor has the data controller's general authorisation to use the sub-processors listed in B.1. The data processor may only add or replace a sub-processor with at least 30 days' prior written notice to the data controller, so that the data controller has the opportunity to object before the change takes effect.

If the data controller has objections to the changes, it shall notify the data processor within 14 days of receipt. The data controller may object only where it has reasonable, specific grounds to do so.

Appendix C: Instructions regarding the processing of personal data

C.1 Subject matter / instruction

The data processor's processing of personal data on behalf of the data controller is carried out by the data processor providing and operating Tables (tables.so), see Appendix A, including storage, organisation, search, display, enrichment of uploaded lists, synchronisation with the data controller's integrations, backup, and technical support.

C.2 Security of processing

The level of security reflects that the processing comprises ordinary, non-sensitive personal data under Article 6 of the GDPR. A standard level of security is therefore established. The data processor implements at least the following measures:

Encryption: Personal data is encrypted in transit (TLS/HTTPS). Data is stored with the data processor's sub-processors (including Neon/AWS and PostHog EU Cloud), which encrypt data at rest.

Access control and confidentiality: Access to personal data is limited to the data processor's employees with a work-related need who are subject to a duty of confidentiality. The list of persons with access is reviewed on an ongoing basis.

Availability and resilience: The data processor backs up customer data (including via Neon's automatic backup) and can restore the availability of and access to personal data in a timely manner in the event of a physical or technical incident.

Logging: Logging takes place at the infrastructure level with the data processor's sub-processors (Vercel, Neon, PostHog), whose log facilities are only accessible after authenticated access. The data processor does not otherwise maintain separate application-level logging of internal access to individual personal data.

Physical security: The processing takes place in cloud environments, where the physical security of data centres is handled by the relevant sub-processors (including AWS).

Remote work: The use of home/remote workplaces takes place via secured connections.

Testing and evaluation: The data processor continuously assesses whether the level of security is appropriate and adjusts the processing accordingly where necessary.

C.3 Assistance to the data controller

The data processor assists the data controller as far as possible in accordance with Clauses 8.1 and 8.2. The data processor forwards without undue delay any requests concerning data subjects' rights to the data controller if these are mistakenly sent to the data processor. Notifications of security breaches and related assistance are directed to privacy@tables.so.

C.4 Retention period / erasure routine

Personal data is retained until the main agreement/subscription terminates. When the data controller deletes its data or closes its account, the personal data is deleted at the data processor, including backups, within 30 days. On termination of the service, the data processor deletes all personal data and confirms the deletion to the data controller, see Clause 10.1, unless EU or national law requires storage.

C.5 Location of processing

The processing takes place with the sub-processors listed in Appendix B. The database and product analytics are hosted in the EU (Frankfurt). The platform's application layer (Vercel) runs in both Frankfurt (EU) and Washington D.C. (USA). Enrichment via AI and contact providers may involve processing in the USA and/or the EU, see Appendix B and C.6.

C.6 Instructions regarding transfer of personal data to third countries

The data controller instructs the data processor that personal data may be transferred to the USA in connection with the use of the US sub-processors listed in Appendix B (including Vercel, OpenAI and Anthropic). The transfer basis is primarily the EU-US Data Privacy Framework (DPF) for those sub-processors that are DPF-certified. For transfers not covered by the DPF, the European Commission's Standard Contractual Clauses (SCCs) under Article 46(2)(c) are used, attached as a separate annex, supplemented by a necessary transfer impact assessment.

C.7 Procedures for the data controller's audits, including inspections

On the data controller's request, the data processor makes available sufficient documentation to enable the data controller to verify and document that the data processor complies with these Clauses and the GDPR. The data controller or a representative may also inspect the facilities and systems used for the processing, upon reasonable prior notice. Any costs incurred by the data controller in connection with such an inspection are borne by the data controller.

C.8 Procedures for audits and inspections of sub-processors

The data processor supervises its sub-processors on the basis of the sub-processor agreements and the documentation (for example, audit reports or equivalent) that the sub-processors make available. Such documentation is provided to the data controller on request for information.

Appendix D: The parties' regulation of other matters

Remuneration for separate assistance: To the extent the data processor assists the data controller with the latter's compliance with the GDPR (see Clause 8) or with assessing the security of processing (see Appendix C.2) beyond what follows from these Clauses, the data processor may charge for time spent at an hourly rate to be agreed between the parties. If a different hourly rate appears in the parties' main agreement, that rate prevails.