Data Processing Agreement (DPA)
Annex ./2
DATA PROCESSING AGREEMENT
in accordance with Article 28 of the General Data Protection Regulation ("GDPR")
Preamble
This agreement governs the processing of personal data ("Data") carried out by the Processor on behalf of the Controller, which the Processor obtains from the Controller ("Data Processing").
The regulation of the economic and legal conditions and a precise technical or expert description of the services to be provided by the Processor are not the subject of this agreement. For this purpose, the parties have concluded the agreement between them (the “Main Agreement”). In particular, the Main Agreement means the contract concluded on the basis of Optimuse’s General Terms and Conditions (“T&C”), together with the offer, order or individual agreement. If the Main Agreement is concluded via the OPTIMUSE App, this Agreement shall take effect upon acceptance of the T&C in electronic form (Article 28(9) GDPR); no separate signature shall be required in that case. In this Agreement, “Platform” or “App” means the OPTIMUSE App (app.optimuse.com). The Customer acts as controller and Optimuse acts as processor under the GDPR.
Thus, the parties agree as follows:
1. Purpose and scope
a) The purpose of this Data Processing Agreement ("Clauses") is to ensure compliance with Article 28(3) and (4) GDPR.
b) These Clauses apply to the processing of personal data for the purpose of fulfilling the Main Agreement.
c) Addendums I and II are an integral part of the Clauses.
d) These Clauses are without prejudice to obligations to which the controller is subject by virtue of the GDPR.
2. Interpretation and hierarchy
a) Where these Clauses use the terms defined in the GDPR, those terms shall have the same meaning as in that Regulation.
b) These Clauses shall be read and interpreted in the light of the provisions of the GDPR.
c) These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in the GDPR or in a way that prejudices the fundamental rights or freedoms of the data subjects.
d) In the event of a contradiction between these Clauses and the provisions of the Main Agreement or a related agreement between the Parties, these Clauses shall prevail.
3. OBLIGATIONS OF THE PARTIES
3.1. Description of processing
The processing operations are carried out for the purpose of fulfilling the Main Agreement.
a) Categories of data subjects: Employees, customers, and representatives of the controller who are registered as users or administrators of the OPTIMUSE app (corporate users), as well as individuals whose data is included in building data or asset projects provided by the controller (e.g., contacts, planners, owners, tenants, or users of buildings).
b) Type of personal data: Names and contact information contained in building data or asset projects; energy consumption and operational data, to the extent that they can be attributed to individual usage units and thus to natural persons; the contents of chat histories, knowledge notes, files, and support requests, to the extent that they contain personal data.
c) Place of processing: See Addendum II.
3.2. Instructions
a) The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. 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. These instructions shall always be documented. In any case, the Main Agreement, this agreement, and the use of the app’s features by the controller and its users shall be considered documented instructions.
b) If legal provisions require the processor to process data in a manner other than that provided for in this agreement, the processor shall inform the controller of these legal requirements immediately upon becoming aware of those requirements and shall also disclose the resulting changes. The controller has the right to object to the commencement of processing in writing. An exception to this notification requirement shall only apply if the relevant legal provision prohibits such notification on grounds of an important public interest.
c) The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe on the GDPR or the applicable Union or Member State data protection provisions.
3.3. Purpose limitation
The processor shall process the personal data only for the purpose of fulfilling the Main Agreement, unless it receives further instructions from the controller.
3.4. Duration of the processing of personal data
Processing by the processor shall only take place for the duration of the Main Agreement and for any agreed-upon or legally mandated retention periods.
3.5. Security of processing
a) The processor shall at least implement the technical and organisational measures specified in Addendum I to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data ("personal data breach"). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.
b) The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring the contract.
c) The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality ("confidentiality obligation"). The confidentiality obligation must be documented and the documentation must be presented to the controller upon request. The confidentiality obligation includes data confidentiality in accordance with Section 6 DSG.
3.6. Documentation and compliance
a) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.
b) The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from the GDPR. At the controller’s request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.
c) The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with at least 30 days’ advance notice, during normal business hours, no more than once per calendar year (except where there are concrete indications of a violation), and at the controller’s expense. As a matter of priority, the processor shall provide appropriate evidence, in particular certificates and audit reports from its sub-processors.
3.7. Use of sub-processors
a) The processor has the controller’s general authorisation for the engagement of sub-processors. This applies, in any case, to those listed in Addendum II. The processor shall inform in text form (specifically by email) the controller of any intended changes of that list through the addition or replacement of sub-processors at least 30 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object. The current list of sub-processors is also available at www.optimuse.com/subprocessors. If the controller lodges a justified objection within the prescribed time limit and the processor is unable to provide the services without the relevant subcontractor, or can do so only at disproportionate effort or expense, both parties are entitled to terminate the Main Agreement or the affected portion of the services, subject to a reasonable notice period.
b) For partners (engineering firms and persons authorised under applicable law to issue energy performance certificates) who provide Premium Solutions on behalf of the data processor, the following applies in deviation from subparagraph (a): The designated partner is identified by name when the respective Premium Solution is commissioned in the OPTIMUSE app or in the order confirmation (see Section 8.2 of the T&C). By placing the order, the controller approves the use of this partner as a subcontractor for this Premium Solution. If the controller objects to the designated partner before the service begins, the processor will engage another partner or provide the service itself; if this is not possible, either party may cancel the affected order free of charge.
c) 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, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to the GDPR.
d) At the controller’s request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secrets or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.
e) The processor shall remain liable to the controller for the performance of the sub-processor’s obligations in accordance with the liability provisions of the Main Agreement. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.
3.8. International transfers
a) Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of the GDPR.
b) The controller agrees that where the processor engages a sub-processor in accordance with Clause 3.7 for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of the GDPR, the processor and the sub-processor can ensure compliance with Chapter V of the GDPR by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) GDPR.
3.9. Assistance to the controller
a) The processor shall promptly notify the controller of
1) any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.
2) requests from courts or authorities relating to personal data processed by the processor on behalf of the controller. Before transferring data processed on behalf of the controller to authorities, courts or other third parties, the processor shall coordinate with the controller on how to proceed.
b) The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with Clause 3.9 a) and b), the processor shall comply with the controller’s instructions.
c) In addition to the processor’s obligation to assist the controller pursuant to Clause 3.9 b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:
1) 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").
2) the obligation to consult the competent supervisory authority/ies 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;
3) the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;
4) the obligations in Article 32 GDPR.
5) If the processor is subject to a legal or regulatory claim by data subjects, and the claim, request, complaint or any other legal remedy indicates that the data subject has mistakenly considered the processor to be the controller responsible for the processing carried out, the processor shall immediately inform the controller of this circumstance and the content of the claim.
3.10. Notification of personal data breach
In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 the GDPR, taking into account the nature of processing and the information available to the processor.
3.10.1. Data breach concerning data processed by the controller
In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:
a) in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant (unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);
b) in obtaining the following information which, pursuant to Article 33(3) GDPR, shall be stated in the controller’s notification, and must at least include:
1) 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;
2) the likely consequences of the personal data breach;
3) 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.
Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay;
c) in complying, pursuant to Article 34 GDPR, with 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.
3.10.2. Data breach concerning data processed by the processor
a) In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor has become aware of the breach. Such notification shall contain, at least:
1) a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);
2) the details of a contact point where more information concerning the personal data breach can be obtained;
3) its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.
b) Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
c) The processor will provide, upon request, any additional information the controller needs to fulfill its obligations under Articles 33 and 34 of the GDPR, to the extent that such information is available to the processor.
4. FINAL PROVISIONS
4.1. Non compliance with the Clauses and termination
a) Without prejudice to any provisions of the GDPR, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.
b) The controller shall be entitled to terminate this Data Processing Agreement insofar as it concerns processing of personal data in accordance with these Clauses if:
1) the processing of personal data by the processor has been suspended by the controller pursuant to Clause 4.1 a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;
2) the processor is in substantial or persistent breach of these Clauses or fails to fulfil its obligations under the GDPR;
3) the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to the GDPR.
c) The processor shall be entitled to terminate this Data Processing Agreement insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 3.2 c), the controller insists on compliance with the instructions.
d) Following termination of the Main Agreement, the processor shall, at the choice of the controller, return all personal data processed on behalf of the controller to the controller in a commonly used format or delete it; until such deletion, the controller may retrieve the data using the app’s export function. The data processor shall delete the data, including any existing copies, within 90 days of the termination of the Main Agreement or the deletion of the workspace, and shall certify the deletion upon request unless Union or Member State law requires storage of the personal data. If, following the cancellation of a paid plan tier in accordance with the T&C, the Workspace is continued in the “Starter” plan tier, the Main Agreement shall continue in this respect. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses. Backup copies shall be overwritten as part of the regular rotation no later than 7 days.
4.2. Applicable law, jurisdiction, severability clause
a) Unless otherwise specified in the Main Agreement, this data processing agreement is governed by Austrian law, excluding referral provisions and the UN Convention on Contracts for the International Sale of Goods.
b) Unless another place of jurisdiction is specified in the Main Agreement, the place of jurisdiction shall be the court with local and subject-matter jurisdiction at the registered office of the processor.
c) Unless otherwise agreed in the Main Agreement, invalid or unenforceable clauses shall not affect the validity of the remaining clauses. The parties undertake to agree on a new, valid provision to replace the invalid provision, which comes as close as possible to the meaning and purpose of the invalid provision. The same applies to gaps in this agreement.
Addendum I TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
1. The parties agree on the following technical and organisational security measures to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, as well as the risks for the rights and freedoms of natural persons.
|
Measures of pseudonymisation and encryption of personal data |
Encryption of stored data (AES-256); encrypted data transmission (TLS 1.2 or higher); pseudonymization of personal data where technically feasible. |
|---|---|
|
Measures for ensuring ongoing confidentiality, integrity, availability and resilience of processing systems and services |
Role-Based Access Control (RBAC); multi-factor authentication; redundant system architecture; continuous monitoring and alerting. |
|
Measures for ensuring the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident |
Daily automated backups with a retention period of 7 days. |
|
Processes for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures in order to ensure the security of the processing |
Security tests (penetration tests) conducted by external providers; regular internal reviews of technical and organizational measures and security configurations. |
|
Measures for user identification and authorisation |
A unique user account for each employee; multi-factor authentication; automatic session logout after inactivity; documented password policies; access for external partners exclusively through personalized user accounts on the platform and limited to the assigned asset projects. |
|
Measures for the protection of data during transmission |
All data transfers must use HTTPS with TLS 1.2 or higher; no unencrypted transmission of personal data. |
|
Measures for the protection of data during storage |
Encrypted databases (AES-256); secure key management; storage exclusively in secure cloud environments (AWS regions within the EU; Google Workspace with data at rest stored in Europe) |
|
Measures for ensuring physical security of locations at which personal data are processed |
Use of ISO 27001-certified data centers (AWS regions within the EU; Google Workspace with at-rest data stored in Europe). |
|
Measures for ensuring events logging |
Automatic audit logs for all access events and security-related actions; centralized log management via Datadog; defined retention periods for logs. |
|
Measures for ensuring system configuration, including default configuration |
Regular software updates and prompt installation of security patches; hardening of the cloud systems in use; centralized configuration management. |
|
Measures for internal IT and IT security governance and management |
Data protection training for all employees; non-disclosure agreements (NDAs) with employees and service providers; documented IT security policies. |
|
Measures for certification/assurance of processes and products |
Use of ISO 27001-certified cloud providers (AWS, Google); internal quality assurance processes; compliance with the requirements of certified subcontractors. |
|
Measures for ensuring data minimisation |
Processing only the personal data necessary for the provision of services; no data collection beyond the defined purpose of processing. |
|
Measures for ensuring data quality |
Technical measures to ensure that the processed data is up-to-date and accurate; correction mechanisms upon user request. |
|
Measures for ensuring limited data retention |
Documented data deletion policy with defined retention periods; automated deletion of personal data upon contract termination (within 90 days; backups are overwritten after 7 days). |
|
Measures for ensuring accountability |
Maintenance of a record of processing activities in accordance with Article 30 of the GDPR; internal documentation of all measures and decisions relevant to data protection. |
|
Measures for allowing data portability and ensuring erasure |
Export function for customer data in common formats (CSV/JSON); deletion upon termination of the contract in accordance with the data deletion policy; secure destruction of data storage media by the data center operator (AWS). |
Addendum II LIST OF SUB-PROCESSORS
1. At the time of entry into force of this Data Processing Agreement the controller has authorised or acknowledged the use of the following sub-processors:
|
Jurisdiction |
Name |
Address |
Purpose of processing |
Nature of processing |
Duration of processing |
Technical and organisational measures |
|---|---|---|---|---|---|---|
|
Luxembourg |
Amazon Web Services EMEA SARL |
38 Avenue John F. Kennedy, L-1855 Luxembourg |
Cloud infrastructure, data storage, email delivery (SES), CDN (CloudFront), operation of AI models (Amazon Bedrock, EU regions) |
Storage, AI-processing, and transmission of platform data |
Duration of the Main Agreement |
ISO 27001, ISO 27017, ISO 27018, SOC 2 Type II; AES-256; TLS 1.2 or higher; regions within the EU; legal basis for any access by Amazon Web Services, Inc. (U.S.): EU-U.S. Data Privacy Framework or Standard Contractual Clauses as specified in the AWS Data Processing Addendum |
|
Ireland |
Google Cloud EMEA Limited (Google Workspace / Drive) |
70 Sir John Rogerson’s Quay, Dublin 2, D02 R296, Ireland |
Communication with customers (email) and storage of customer documents (Google Drive) as part of Support and Premium Solutions |
Storage and Transmission of emails, customer documents, and records |
Duration of the Main Agreement |
ISO 27001, SOC 2 Type II; encryption at rest and in transit; storage of data at rest in Europe (Data Region Europe); legal basis for any access by Google LLC (U.S.): EU-U.S. Data Privacy Framework or Standard Contractual Clauses as specified in the Google Cloud Data Processing Addendum |
|
USA |
Datadog, Inc. |
620 8th Avenue, New York, NY 10018, USA (Usage of EU1-Site, Germany) |
Monitoring, Performance Monitoring, and Error Tracking |
Processing log data, metrics, and traces |
Duration of the Main Agreement |
SOC 2 Type II, ISO 27001; Encryption; Data storage on the EU1 site (Germany); Basis for data transfer: EU-U.S. Data Privacy Framework (Datadog, Inc. is certified) |
|
Ireland |
HubSpot Ireland Limited |
1 Sir John Rogerson’s Quay, Dublin 2, D02 HD32, Ireland |
Support ticketing, to the extent that support requests contain customer data |
Storage and processing of support requests |
Duration of the Main Agreement |
ISO 27001, SOC 2 Type II; encryption; hosting in the EU (Frankfurt); basis for data transfer: EU-U.S. Data Privacy Framework (HubSpot, Inc. is certified); supplemented by standard contractual clauses in accordance with the HubSpot DPA |
|
USA |
Okta, Inc. (Auth0) |
100 First Street, San Francisco, CA 94105, USA |
User Account Authentication and Management (Login) |
Processing of users' login and account information (name, email address, IP address, login logs) |
Duration of the Main Agreement |
EU Tenant (storage in the EU); Basis for data transfer: EU-U.S. Data Privacy Framework (Okta, Inc. is certified); supplemented by standard contractual clauses in accordance with the Okta DPA |
|
Registered office of the respective Partner |
Partners as defined in the T&C (engineering firms and persons authorised under applicable law to issue energy performance certificates) |
Mention by name for each Premium Solution upon placement of an order (Clause 3.7 b)) |
Collection and processing of asset data, delivery of Premium Solutions, kick-off meetings and review of results, issuance of energy performance certificates |
Access to commissioned asset projects exclusively through the platform |
Duration of the respective Premium Solution |
Subprocessor agreement, confidentiality agreement, access exclusively through personalized user accounts on the platform |