The Veezoo Analytics Cup is live — Submit by June 7 and win a MacBook Pro

Legal · Archived version

Data Processing Agreement

Version 0.1 – 16.03.2026

Archived version. This is Version 0.1 of the Veezoo Data Processing Agreement, effective 16.03.2026. It is preserved here for reference.Go to current version →

This DPA is structured as follows:

SectionContent
Section A – Key termsThe key variables that apply to the DPA are defined in Section A.
Section B – Legal termsSets out the general legal terms applicable to the processing.
Section C – TOMsThe applicable technical and organizational measures.

Section A – Key terms

Defined termDefinition
Controller(s)The Customer contracting with Veezoo AG
Processor(s)Veezoo AG, Hohlstrasse 511, 8048 Zurich, Switzerland
Contact: privacy@veezoo.com
(together with the Controller(s) the "Parties" and each a "Party")
Processing PurposeProcessing in the context of the provision of Veezoo’s services under Veezoo’s General Terms and Conditions (the "Base Agreement")
Duration of ProcessingOnly as long as necessary for the Processing Purpose
Categories of Data Subjects
  • Consultants and advisors
  • Customers, suppliers and business partners
  • Employees, contractors and freelancers of the Customer
  • Other individuals whose personal data is included in Customer Data
  • Potential clients and leads
  • Website visitors
Categories of Personal Data
  • Identification data (e.g. name, username, user ID)
  • Contact data (email address, phone number, address)
  • Professional information (job title, company, department)
  • Financial or transaction data
  • Account identifiers (customer ID, account number)
  • Online identifiers (IP address, device identifiers)
  • Usage and interaction data relating to the Services
  • Demographic data (e.g. age or date of birth)
  • Any other personal data contained in Customer Data submitted to the Services

The categories of personal data and data subjects depend on the data uploaded by the Customer to the Services.

The Customer shall not upload special categories of personal data under Article 9 GDPR unless explicitly agreed with Veezoo.

Place of storage & processingAt the business address of the Processor and its approved Sub-processors as indicated in this data processing agreement
On-premise auditsNo
Sub-processorsSub-processors are listed in the annex to this Agreement.
Transfer outside of EU/EEA/SwitzerlandOnly allowed to countries where the Processor or an approved Sub-processor is registered

The variables defined in Section A serve as definitions in Section B and section C.

Section B – General terms

1.Purpose and scope

The purpose of this data processing agreement (the "DPA") is to ensure compliance with Article 28(3) and (4) of the EU General Data Protection Regulation ("GDPR") and Article 9 of the Swiss Federal Act on Data Protection ("FADP"), with respect to each law only if and to the extent applicable to the respective processing activity.

This DPA applies with respect to the processing of personal data as specified in Section A.

2.Interpretation

Where this DPA uses the terms defined in the GDPR or the FADP, as applicable, those terms shall have the same meaning as in that law.

This DPA shall be read and interpreted in the light of the provisions of the GDPR and the FADP, as applicable.

These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in the GDPR or the FADP, as applicable, or prejudices the fundamental rights or freedoms of the data subjects.

3.Description of processing operations

The details of the processing operations, and in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the Controller, are specified in Section A.

No AI Training: For clarity, the Processor shall not use Customer Personal Data to train, fine-tune, or otherwise improve any machine-learning or artificial-intelligence model, nor permit any affiliate or Sub-Processor to do so, unless the Processor receives prior written instructions from the Controller.

4.Obligations of the Parties

4.1General

The Processor shall process personal data only on documented instructions from the Controller, unless required to do so by Union, Member States or Swiss law to which the processor is subject. Such instructions are specified in Section A. In this case, the Processor shall inform the Controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the Controller throughout the duration of the processing of personal data. Such instructions shall always be documented.

The Processor shall immediately inform the Controller if instructions given by the Controller, in the opinion of the Processor, infringe applicable Union, Member States or Swiss data protection provisions.

4.2Purpose limitation

The Processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Section A.

4.3Erasure or return of data

Processing by the Processor shall only take place for the duration specified in Section A.

Upon termination of the provision of personal data processing services or termination pursuant to Clause 7, the Processor shall delete all personal data processed on behalf of the Controller and certify to the Controller that it has done so and delete existing copies unless Union, Member States or Swiss law requires storage of the personal data.

4.4Security of processing

The Processor shall implement the technical and organizational measures specified in Section C to ensure the security of the personal data, including protection against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access to that data (personal data breach), in accordance with Article 5, Article 28(3)(c) and Article 32 GDPR and Article 8 FADP. In assessing the appropriate level of security, they shall in particular take due account of the risks involved in the processing, the nature of the personal data and the nature, scope, context and purposes of processing.

In the event of a personal data breach concerning data processed by the Processor, it shall notify the Controller without undue delay and at the latest within 48 hours after having become aware of the breach. Such notification shall contain the details of a contact point where more information concerning the personal data breach can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and data records concerned), its likely consequences and the measures taken or proposed to be taken to mitigate its possible adverse effects. Where, and insofar as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall be provided as it becomes available without undue delay.

The Processor shall cooperate in good faith with and assist the Controller in any way necessary to enable the Controller to notify, where relevant, the competent data protection authority and the affected data subjects, taking into account the nature of processing and the information available to the Processor.

The Processor shall grant access to the data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. The Processor shall ensure that persons authorized to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (special categories of data), the Processor shall apply specific restrictions and/or additional safeguards as reasonably required by the Controller.

4.5Documentation and compliance

The Parties shall be able to demonstrate compliance with this DPA.

The Processor shall deal promptly and properly with all reasonable inquiries from the Controller that relate to the processing under this DPA.

The Processor shall make available to the Controller all information necessary to demonstrate compliance with the obligations set out in this DPA and that are stemming directly from the GDPR or the FADP and at the Controller’s request, allow for and contribute to reviews of data files and documentation or of audits of the processing activities covered by these Clauses, in particular if there are indications of non-compliance.

The Controller may choose to conduct the audit by itself, to mandate, at its own cost, an independent auditor or to rely on an independent audit mandated by the Processor. Where the Processor mandates an audit, it has to bear the costs of the independent auditor. The Controller’s audit, access, and inspection rights under this Clause are limited to the Processor’s records only (including inter-alia the registers of personal data processing activities, the registers of recipients of personal data) and does not apply to Processor’s physical premises. Any audit and request for information shall be limited to information necessary for the purposes of this DPA and shall give due regard to the Processor’s confidentiality obligations and legitimate interest to protect business secrets.

The Processor and Controller shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority on request if and to the extent required by the GDPR or the FADP, as applicable.

4.6Use of Sub-processors

The Processor has the Controller’s general authorization for the engagement of Sub-processors. The list of Sub-processors of the Processor can be found in Section A. The Processor shall inform in text form the Controller of any intended changes to that list through the addition or replacement of Sub-processors at least 30 days in advance, thereby giving the Controller the opportunity to object to such changes prior to the engagement of the concerned Sub-processors. Such objection shall not be unreasonably raised. The Parties shall keep the list up to date.

Where the Processor engages a Sub-processor for carrying out specific processing activities (on behalf of the Controller), it shall do so by way of a contract which imposes on the Sub-processor the same obligations as the ones imposed on the Processor under this DPA. The Processor shall ensure that the Sub-processor complies with the obligations to which the Processor is subject pursuant to this DPA, Article 28(2) to (4) GDPR and Article 9(3) FADP.

The Processor shall provide, at the Controller’s request, a copy of such a Sub-processor agreement and subsequent amendments to the Controller.

The Processor shall remain fully responsible to the Controller for the performance of the Sub-processor’s obligations under its contract with the Processor. The Processor shall notify the Controller of any failure by the Sub-processor to fulfil its obligations under that contract.

4.7International transfers

Any transfer of data to a country outside of the EU/EEA and Switzerland (a "Third Country") or an international organization by the Processor shall be undertaken only if authorized in accordance with Section A and shall take place in compliance with Chapter V of the GDPR and Articles 16 to 18 of the FADP, as applicable.

The Controller agrees that where the Processor engages a Sub-processor in accordance with Clause 4.6 for carrying out specific processing activities on behalf of the Controller in a Third Country and those processing activities involve transfer of personal data within the meaning of the GDPR or the FADP, as applicable, the Processor and the Sub-processor may use standard contractual clauses adopted by the Commission on the basis of Article 46(2) GDPR in order to comply with the requirements of Chapter V of the GDPR, provided the conditions for the use of those clauses are met and provided that an internal assessment concluded that such transfer meets the level of data protection of the GDPR and the FADP.

5.Data subject rights

The Processor shall promptly notify the Controller about any request received directly from the data subject. It shall not respond to that request itself, unless and until it has been authorized to do so by the Controller.

The Processor shall assist the Controller in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights in accordance with Chapter III of the GDPR and Chapter 4 of the FADP, namely:

  • the right to be informed when personal data are collected 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;
  • the notification obligation of 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; and
  • the right to withdraw consent.

The Processor shall assist the Controller in case a data subject has lodged a complaint to the competent supervisory authority that concerns data processed on the basis of this DPA.

In addition to the Processor’s obligation to assist the Controller pursuant to Clause 5, the Processor shall furthermore assist the Controller in ensuring compliance with the following obligations, taking into account the nature of the processing and the information available to the Processor:

  • The obligation to notify a personal data breach to the competent supervisory authority without undue delay after having become aware of it, (unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons), in accordance with Article 33 GDPR and Article 24(1) to (3) FADP;
  • the obligation to communicate without undue delay 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, in accordance with Article 34 GDPR and Article 24(4) FADP;
  • the 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’) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons, in accordance with Article 35 GDPR and Article 22 FADP;
  • the obligation to consult the competent supervisory authority 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 Controller to mitigate the risk, in accordance with Article 36 GDPR and Article 23 FADP.

The Parties shall set out in Section C the appropriate technical and organizational measures by which the Processor is required to assist the Controller in the application of this Clause as well as the scope and the extent of the assistance required.

6.Notification of personal data breaches

In the event of a personal data breach, the Processor shall cooperate in good faith with and assist the Controller in any way necessary for the Controller to comply with its obligations under Articles 33 and 34 of the GDPR and Article 24 of the FADP, as applicable, taking into account the nature of processing and the information available to the Processor.

The Processor shall assist the Controller in notifying the personal data breach to the competent supervisory authority, where relevant. The Processor shall be required to assist in obtaining in particular the following information which, pursuant to Article 33(3) GDPR or Article 24(2) FADP, as applicable, shall be stated in the Controller’s notification:

  • The nature of the personal data 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.

7.Termination

Without prejudice to any provisions of the GDPR or the FADP, as applicable, in the event that the Processor is in breach of its obligations under this DPA, the Controller may instruct the Processor to temporarily suspend the processing of personal data until the latter complies with this DPA or the contract is terminated. The Processor shall promptly inform the Controller in case it is unable to comply with this DPA, for whatever reason.

The Controller may terminate this DPA where:

  • the processing of personal data by the Processor has been temporarily suspended by the Controller pursuant to point (a), Processor’s breach is material, and compliance with this DPA is not restored within a reasonable time and in any event within one month;
  • the Processor is in substantial or persistent breach of this DPA or its obligations under the GDPR or the FADP, as applicable, and such breach cannot be reasonably expected to be remedied;
  • the Processor fails to comply with a binding decision of a competent court or the competent supervisory authority regarding its obligations under this DPA or under the GDPR or the FADP, as applicable.

This DPA shall remain in full force and effect so long as the Base Agreement remains in effect. Any provision of this DPA that expressly or by implication should come into or continue in force on or after termination of the Base Agreement in order to protect personal data shall remain in full force and effect.

8.Liability and indemnity

Each Party’s liability arising out of or related to this DPA shall be subject to the limitations and exclusions of liability set out in the Base Agreement.

9.Miscellaneous

Confidentiality: The Parties agree to keep the terms and existence of this Agreement as well as any information exchanged under this Agreement confidential unless agreed otherwise between the Parties.

Entire agreement: This DPA is the entire agreement, and supersedes all prior agreements, between the Parties relating to the scope of this DPA.

Amendments: All amendments and supplements to this DPA must be made in writing (incl. non-qualified e-signature solutions).

Notices: Any notice ‘in writing’ needs to be delivered with physical mail, any notice ‘in text form’ includes any electronic message, each to the last communicated or available address. If the form is not stated, text form is sufficient.

No assignment: Neither Party may assign any of its rights, obligations or claims under this Agreement unless agreed otherwise.

Severability: If any provision of this DPA (in whole or part) is held to be illegal, invalid or otherwise unenforceable, the other provisions will remain mutatis mutandis in full force and effect.

Governing law & jurisdiction: As per the Base Agreement.

Section C – TOMs

Description of the technical and organizational security measures implemented by the Processor(s):

Technical and Organizational Measures (TOM)

ItemCategoryRequirementAnswer
TOM1.1ConfidentialityAccess Control: Prevention of unauthorized access and system useVeezoo enforces strict access control measures such as multi-factor authentication (MFA) and role-based access control (RBAC). Detailed permission management ensures that only authorized personnel can access, read, modify, or remove data, and session monitoring is used to detect and prevent unauthorized system use.
TOM1.2ConfidentialitySeparation Control: Separated data processing for different purposesData processing within Veezoo is logically separated by purpose at the API and database level, ensuring that data collected for distinct purposes is processed independently and securely. Customer data is assigned unique identifiers to maintain separation and prevent unauthorized access to data across different processes.
TOM1.3ConfidentialityEncryption: Protection of data at rest and in transitVeezoo ensures that all data is encrypted at rest and in transit using industry-standard encryption protocols. Encryption applies to databases, file systems, and all communication channels, preventing unauthorized access, modification, or interception of data during storage and transmission.
TOM1.4ConfidentialityPseudonymization and Data MinimizationVeezoo may apply pseudonymization techniques where necessary to minimize exposure of personal data. Sensitive data fields are replaced with pseudonyms to ensure privacy protection and compliance with data minimization principles.
TOM1.5ConfidentialityData Retention and Deletion PolicyVeezoo retains customer data according to regulatory and contractual requirements. Once the retention period is over, data is securely deleted using cryptographic erasure and other secure methods to ensure that it cannot be recovered. The data lifecycle management policy governs the retention and secure disposal of sensitive information.
TOM1.6ConfidentialityPhysical Security: Protection of data processing locationsVeezoo ensures that physical access to locations where data is processed is restricted to authorized personnel. This includes access control systems, CCTV monitoring, and fire safety protocols.
TOM1.7ConfidentialityData Protection by Design and by DefaultVeezoo integrates data protection principles into the design and implementation of systems and processes. Privacy is considered by default in the development of new features and applications, ensuring compliance with data protection regulations.
TOM2.1IntegrityTransfer Control: Secure transmission of dataVeezoo uses encryption for all data transmission, both internal and external, ensuring that data is protected against unauthorized access, modification, or deletion during transmission.
TOM2.2IntegrityLogging and Monitoring of System Access and ChangesVeezoo maintains comprehensive logs of all system access, data modifications, and critical events. Logs are securely stored, and real-time copying to a system outside the control of system administrators is enforced to prevent manipulation. Logs are regularly reviewed to ensure that only authorized changes have been made and to detect unauthorized activity.
TOM2.3IntegrityIncident Response: Monitoring and handling of security breachesContinuous monitoring tools detect suspicious activity, and an incident response plan is in place to address breaches quickly and effectively. This ensures the integrity of Veezoo’s systems and protects against data loss or corruption. Key personnel are alerted in case of incidents, and protocols are followed to maintain data integrity and security.
TOM2.4IntegritySecure Data Deletion and DisposalVeezoo follows strict secure deletion procedures, using methods such as cryptographic erasure to ensure that data is irrecoverable when no longer needed. The deletion process is logged for audit purposes, and this applies to both data stored locally and in cloud environments.
TOM2.5IntegrityAnti-Malware and Software ManagementVeezoo protects its systems from malware through anti-malware software and stringent software management practices. Authorized software with valid licenses is installed, and regular scans are performed to detect threats. Additionally, firewalls are implemented to separate virtual machines (VMs) and protect internal networks from unauthorized access
TOM2.6IntegrityThird-Party and Supplier ManagementVeezoo requires that third-party suppliers and subprocessors adhere to similar security measures, ensuring the protection of data throughout the supply chain. Data Processing Agreements (DPAs) are established with third-party vendors to formalize their responsibilities in safeguarding data.
TOM3.1AvailabilityBackup and Recovery: Protection against data lossVeezoo performs daily full backups and for some systems even more frequently. All backups are encrypted and redundantly stored across multiple geographic zones to ensure that data is recoverable in case of accidental loss or system failure. These measures protect the availability of customer data.
TOM3.2AvailabilitySystem Hardening and MaintenanceVeezoo applies system hardening standards, such as disabling unnecessary services, regularly applying security patches, and maintaining secure system configurations. This reduces vulnerabilities and ensures that systems remain operational and secure from attacks or misconfigurations.
TOM3.3AvailabilityBusiness Continuity and Disaster RecoveryVeezoo has a comprehensive Business Continuity Plan that ensures operations continue during disruptions. The plan includes regular testing, backup systems, and recovery processes, and ensures that critical systems remain available during disasters. The DevOps and HR teams play a crucial role in ensuring system recovery and business continuity during incidents.
TOM3.4AvailabilityRegular Testing of Business Continuity PlansVeezoo regularly tests its Business Continuity and Disaster Recovery plans by simulating disaster scenarios to ensure preparedness. These tests include both technical and operational recovery plans to minimize downtime and ensure that critical systems remain available during a real incident.
TOM4.1Regular Review and AssessmentData Protection, Incident Response, and Processing ManagementVeezoo regularly conducts security audits, reviews, and incident response drills to ensure compliance with legal, regulatory, and contractual obligations. This process ensures the ongoing effectiveness of Veezoo’s data protection and incident management processes, and continuous improvements are made based on findings from these reviews.
TOM4.3Regular Review and AssessmentEmployee Awareness and TrainingVeezoo conducts regular security training and awareness programs for employees, ensuring that all staff members are familiar with their responsibilities regarding data protection and security. Ongoing education campaigns ensure employees are up-to-date on the latest security practices.

Annex – List of Sub-processors

Pursuant to Clause 4.6 of this DPA, Veezoo will inform Controllers in text form of any intended changes to this list at least 30 days in advance.

CompanyPurposeLocation of personal data
AWSHosting Provider / Infrastructure Services for the Veezoo SaaSFrankfurt, Germany
FivetranReplication of Usage Logs; used to enable Meta Veezoo functionalityFrankfurt, Germany
SlackUsage Logs StreamingEU
Twilio SegmentEvent tracking within VeezooEU West
Twilio SendgridEmail notification servicesEU
AtlassianDefault Git Repository for Knowledge GraphUSA
GoogleInfrastructure Services & Large Language Model servicesEU
OpenAILarge Language Model services (if applicable)USA
AnthropicLarge Language Model services (if applicable)Worldwide

If you have any questions or wish to be notified of changes, please contact us at privacy@veezoo.com.