Also available in: Nederlands · Deutsch
Data Processing Agreement Dutchview
Version 2.8, valid from 11.11.2026. This text is identical to the version customers can sign; download the data processing agreement as a PDF to sign.
The customer that purchases Dutchview's services (hereinafter: the controller),
and
Dutchview information technology B.V., with its registered office at Keizerstraat 43, 7411 HE Deventer, the Netherlands, hereinafter referred to as the processor, duly represented herein by Mr R.B. Loenen, director, and Mr M. Otterloo, director,
declare that they have concluded a data processing agreement as referred to in the General Data Protection Regulation (GDPR) between the controller and the processor. Where this data processing agreement uses terms that correspond to definitions in the GDPR, these terms have the meaning of the definitions in the GDPR.
Article 1. Definitions
Where this data processing agreement uses terms that correspond to definitions in Article 4 GDPR, these terms have the meaning of the definitions in the GDPR. This applies in any case to the terms Personal Data, Processing, Controller, Processor, Data Subject and Personal Data Breach (hereinafter: Data Breach).
1.1 Annexes: appendices to this data processing agreement, which form part of this data processing agreement.
1.2 Supervisory Authority: the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP), the independent administrative body appointed by law in the Netherlands as the supervisory authority for the processing of personal data.
Article 2. Commencement and duration
2.1 This data processing agreement takes effect on signature or, if the parties do not sign it separately, on the effective date of the agreement that refers to this data processing agreement, and continues for as long as the processor acts as a processor of personal data in connection with the personal data made available by the controller.
Article 3. Subject of this data processing agreement
3.1 The processor processes the personal data made available by or via the controller exclusively on the instructions of the controller and only insofar as necessary for the performance of the agreement under which the services of Dutchview information technology B.V. are provided.
3.2 The processor shall not process the personal data for any other purpose, unless this is necessary to comply with a legal obligation to which the processor is subject.
3.3 The processor processes the personal data with due care and in accordance with the applicable laws and regulations, including the General Data Protection Regulation (GDPR).
3.4 The processor is entitled to use data that has been anonymised to such an extent that it can no longer be traced to a natural person for statistical analyses, security, capacity planning and the improvement of its services.
Article 4. Obligations of the processor
4.1 The processor processes data on behalf of the controller, in accordance with the controller's instructions.
4.2 The processor has no control over the personal data made available. It does not take decisions on the receipt and use of the data, the provision of the data to third parties or the duration of storage of the data. Control over the personal data provided under this data processing agreement shall never vest in the processor.
4.3 When processing personal data in the context of the activities referred to in Article 3, the processor shall act in accordance with the applicable laws and regulations on the processing of personal data. The processor shall follow all reasonable instructions of the controller, unless legal obligations require otherwise.
4.4 The processor shall at all times, at the first request of the controller, hand over the personal data made available in connection with this data processing agreement.
4.5 The processor shall at all times enable the controller to meet its obligations under the GDPR within the statutory time limits, in particular with regard to the rights of data subjects, such as, but not limited to, a request for access, rectification, completion, erasure or restriction of personal data and the follow-up of an upheld objection.
4.6 The processor shall immediately inform the controller if, in its opinion, an instruction infringes the GDPR or another data protection provision.
4.7 The processor shall assist the controller in carrying out a data protection impact assessment (DPIA) and any prior consultation of the supervisory authority (Articles 35 and 36 GDPR), taking into account the nature of the processing and the information available to the processor.
Article 5. Duty of confidentiality
5.1 Persons employed by or working on behalf of the processor, as well as the processor itself, are obliged to maintain confidentiality with regard to the personal data of which they may take cognisance, except insofar as a provision given by or pursuant to the law requires disclosure. The employees of the processor sign a confidentiality statement to this end.
5.2 If the processor is required by a legal obligation to provide data, the processor shall verify the basis of the request and the identity of the requesting party and shall inform the controller thereof immediately, prior to the provision, unless statutory provisions prohibit this.
Article 6. Obligation to report data breaches and security incidents
6.1 The processor shall inform the controller as soon as possible, but no later than 24 hours after the first discovery, of all (suspected) breaches of security as well as other incidents that must be reported to the supervisory authority or data subject pursuant to legislation, without prejudice to the obligation to undo or limit the consequences of such breaches and incidents as quickly as possible. The processor shall also, at the first request of the controller, provide all information the controller considers necessary to assess the incident. When doing so, the processor shall in any case provide the controller with the information described in Annex 1.
6.2 The processor has a thorough action plan for the handling and settlement of breaches and shall, at the controller's request, give the controller access to the plan. The processor shall inform the controller of material changes to the action plan.
6.3 The processor shall leave notifications to the supervisory authority or authorities and to data subjects to the controller. The processor shall assist the controller at the controller's request and insofar as reasonable.
6.4 The processor shall provide all necessary cooperation in providing, where required and as soon as possible, additional information to the supervisory authority or authorities and/or data subject(s). When doing so, the processor shall in any case provide the controller with the information described in Annex 1.
6.5 The processor shall keep a detailed log of all (suspected) breaches of security, as well as the measures taken following such breaches, containing at least the information referred to in Annex 1, and shall make it available for inspection at the first request of the controller.
Article 7. Security measures and inspection
7.1 The processor is certified for ISO/IEC 27001 and ISO 9001 and maintains an information security management system that is periodically evaluated and improved.
7.2 The processor takes appropriate technical and organisational measures to protect personal data against loss or against any form of unlawful processing.
7.3 These measures ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing.
7.4 The controller may verify compliance with this data processing agreement. The processor shall provide reasonable cooperation to this end by making relevant documentation on its security measures and processes available.
7.5 Any audit by or on behalf of the controller shall take place only after prior written notice and with due regard for reasonable time limits, confidentiality and minimal disruption of the processor's business operations.
7.6 The costs of such an audit are borne by the controller, unless the audit shows that the processor materially fails to comply with this data processing agreement.
Article 8. Engagement of third parties
8.1 The processor may use third parties (sub-processors) in providing its services.
8.2 The processor ensures that written agreements are made with these sub-processors containing at least the same data protection obligations as this data processing agreement.
8.3 The processor remains responsible at all times for the performance of the obligations of these sub-processors.
8.4 The controller may object to the engagement of a new sub-processor if there is a justified reason relating to the protection of personal data.
8.5 The processor informs the controller before engaging a new sub-processor.
8.6 The processor hosts and stores the personal data exclusively within the European Economic Area (EEA). Transfer to, or access from, a country outside the EEA takes place exclusively by the sub-processors on the sub-processor page (Article 8.7), with the appropriate safeguards stated there as referred to in Chapter V of the GDPR, or after prior written consent of the controller.
8.7 The sub-processors engaged by the processor, with their role, the place of processing and the safeguards, are listed on the processor's sub-processor page: www.dutchview.com/subprocessors. By entering into this data processing agreement, the controller gives general authorisation for the engagement of those sub-processors. The processor keeps the page up to date, states the date of the last change and informs the controller in advance of a new or changed sub-processor, after which Article 8.4 applies. On request, the processor provides the list as it applied on the date of signature.
Article 9. Amendment and termination of the data processing agreement
9.1 This data processing agreement can only be amended in writing by means of a proposal approved by both parties.
9.2 Once the cooperation has ended, the processor shall, at the controller's choice, (i) make all of the personal data made available under this data processing agreement, or a part determined by the controller, available to the controller, or (ii) destroy the personal data received from the controller at all locations, in whatever form, and demonstrate this, unless the parties agree otherwise. If necessary, the controller may impose further requirements on the manner in which the data is made available, including requirements on the file format, or on its destruction. These activities must be carried out within 30 days of the end of this data processing agreement and a report will be made of them.
9.3 At the controller's request, the processor makes the personal data referred to in the previous paragraph available in a structured, commonly used and machine-readable format (Excel and PDF), within 30 days of the end of this data processing agreement and without loss of data. The processor then deletes the personal data from the production environment. Backups expire according to the processor's fixed backup schedule (maximum 180 days) and are not restored during that period, except at the controller's request.
9.4 The controller and the processor shall consult each other about amendments to this data processing agreement if a change in legislation or a change in the interpretation of legislation gives rise to this.
9.5 If a party fails to perform an agreed obligation, the other party may give it notice of default, granting the defaulting party a reasonable period to still perform. If performance still does not take place, the defaulting party is in default. Notice of default is not required if a strict deadline applies to the performance, if performance is permanently impossible, or if it must be inferred from a communication or the conduct of the other party that it will fail to perform its obligation.
9.6 The controller is entitled, without prejudice to the provisions of this data processing agreement and the related main agreement and without prejudice to the other provisions of the law, to suspend the performance of this data processing agreement by registered letter, or to dissolve it in whole or in part with immediate effect without judicial intervention, after the controller has established that:
- the processor applies for a (provisional) suspension of payments; or
- the processor files for bankruptcy or is declared bankrupt; or
- the processor's company is dissolved; or
- the processor discontinues its business; or
- there is a substantial change in control over the activities of the processor's company as a result of which the controller cannot reasonably be expected to maintain the data processing agreement; or
- a substantial part of the processor's assets is attached (other than by the controller); or
- the processor demonstrably fails to perform the obligations arising from this data processing agreement and this serious attributable failure has not been remedied within 30 days of a written notice of default to that effect, or one of the other situations referred to in Article 9.5 occurs.
9.7 The processor shall immediately inform the controller if there is a threat of bankruptcy or suspension of payments, so that the controller can decide in good time to reclaim the personal data before bankruptcy is declared.
9.8 The controller is entitled to dissolve this data processing agreement and the main agreement with immediate effect if the processor indicates that it is not (or no longer) able to meet the reliability requirements imposed on the processing of personal data as a result of developments in legislation and/or case law.
9.9 If the data processing agreement is terminated prematurely, Articles 9.2 and 9.3 apply mutatis mutandis.
9.10 Termination or expiry of this data processing agreement does not release the processor from its obligations that are intended to remain in force after termination or expiry, including the obligations arising from Articles 5, 7, 9, 10 and 11.
Article 10. Liability
10.1 If the processor fails to perform its obligations under this data processing agreement, the controller may give it notice of default. However, the processor is in default immediately if performance of the relevant obligation within the agreed period is already permanently impossible for reasons other than force majeure. Notice of default is given in writing, granting the processor a reasonable period to still perform its obligations. If performance does not take place within this period, the processor is in default.
10.2 The processor is liable for damage resulting from an attributable failure to perform this data processing agreement or from an infringement of the GDPR attributable to the processor, in accordance with the allocation of Article 82 GDPR. This liability is limited, per event and per calendar year, to the amount the controller paid for the services in the twelve months preceding the event. This limitation does not apply in the case of intent or deliberate recklessness on the part of the processor.
10.3 The controller indemnifies the processor against damage or loss insofar as the grounds for it are exclusively attributable to the controller.
Article 11. Applicable law
11.1 This data processing agreement and all disputes that may arise from or in connection with it are governed by Dutch law.
11.2 This data processing agreement is a translation of the Dutch version (www.dutchview.com/nl/verwerkersovereenkomst). In the event of a conflict between the versions, the Dutch text prevails.
Signature: this data processing agreement is signed by the controller and the processor, or applies as part of the agreement in which the controller refers to it.
Annex 1: Information to assess incidents
The processor shall provide all information the controller considers necessary to assess the incident. When doing so, the processor shall in any case provide the controller with the following information:
- the (alleged) cause of the breach;
- the (currently known and/or expected) consequences;
- the (proposed) solution;
- contact details for following up the notification;
- the number of persons whose data is involved in the breach (if the exact number is not known: the minimum and maximum number of persons whose data is involved in the breach);
- a description of the group of persons whose data is involved in the breach;
- the type or types of personal data involved in the breach;
- the date on which the breach occurred (if no exact date is known: the period within which the breach occurred);
- the date and time at which the breach became known to the processor or to a third party or subcontractor engaged by it;
- whether the data was encrypted, hashed or otherwise made unintelligible or inaccessible to unauthorised persons;
- the measures already taken to stop the breach and to limit its consequences.
Annex 2: Sub-processors
The current sub-processors are listed on the processor's sub-processor page (Article 8.7).
Annex 3: Nature and purpose of the processing
The data processed is set out below for each product. The product you use applies to you.
Ed Controls (SaaS)
Nature and purpose: management and communication in (construction) projects. The processing is necessary to enable the controller and its users to use the system, including assigning tasks, sharing project information and finding users by e-mail address.
Categories of personal data: identification, contact and authorisation data of users (including name, e-mail address, organisation and project role), the record of who created, changed or completed what and when, the position of a finding on the drawing (no location of persons or devices) and content entered by users such as photos, free text and signatures.
Categories of data subjects: employees of the controller and other users to whom information is provided or tasks are assigned via the system, such as project participants and subcontractors.
Retention period: the controller determines the retention period; as a starting point, up to ten years after completion of the project, after which the data is deleted or handed over to the controller (Article 9).
Location of processing: within the EEA (see Article 8.6).
Flexwhere (SaaS)
Nature and purpose: supporting flexible working, including booking workplaces, meeting rooms and parking spaces and finding colleagues by name or role.
Categories of personal data: identification and authorisation data of employees, location data within the system and reservation data.
Categories of data subjects: employees of the controller.
Retention period: for the duration of the agreement; after it ends, the data is returned on request within 30 days and then deleted from the production environment; backups expire within a maximum of 180 days (Article 9).
Location of processing: within the EEA (see Article 8.6).
