Data processing agreement (DPA)

Section I — Clause 1. Purpose and scope

(a) The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 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).

(b) The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of Regulation (EU) 2018/1725.

(c) These Clauses apply to the processing of personal data as specified in Annex II.

(d) Annexes I to IV are an integral part of the Clauses.

(e) These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(f) These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

Clause 2. Invariability of the Clauses

(a) The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.

(b) This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.

Clause 3. Interpretation

(a) Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, 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 Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.

(c) These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.

Clause 4. Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 5 — Optional. Docking clause

(a) Any entity that is not a Party to these Clauses may, with the agreement of all the Parties, accede to these Clauses at any time as a controller or a processor by completing the Annexes and signing Annex I.

(b) Once the Annexes in (a) are completed and signed, the acceding entity shall be treated as a Party to these Clauses and have the rights and obligations of a controller or a processor, in accordance with its designation in Annex I.

(c) The acceding entity shall have no rights or obligations resulting from these Clauses from the period prior to becoming a Party.

Section II — Obligations of the Parties. Clause 6. Description of processing(s)

The details of the processing operations, 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 Annex II.

Clause 7. Obligations of the Parties — 7.1. 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.

(b) The processor shall immediately inform the controller if, in the processor's opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.

7.2. Purpose limitation

The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.

7.3. Duration of the processing of personal data

Processing by the processor shall only take place for the duration specified in Annex II.

7.4. Security of processing

(a) The processor shall at least implement the technical and organisational measures specified in Annex III 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 of the contract. 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.

7.5. Sensitive data

If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data 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 ("sensitive data"), the processor shall apply specific restrictions and/or additional safeguards.

7.6. Documentation and compliance

(a) The Parties shall be able to demonstrate compliance with these Clauses.

(b) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.

(c) 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 Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. 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.

(d) 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 reasonable notice.

(e) The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.

7.7. Use of sub-processors

(a) OPTION 2: GENERAL WRITTEN AUTHORISATION: The processor has the controller's general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 14 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.

(b) 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 Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(c) 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 secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.

(d) The processor shall remain fully responsible to the controller for the performance of the sub-processor's obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.

(e) The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

7.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 Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.

(b) The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.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 Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.

Clause 8. Assistance to the controller

(a) The processor shall promptly notify the controller of 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.

(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 (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 8(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') where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons; (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 of Regulation (EU) 2016/679.

(d) The Parties shall set out in Annex III the appropriate technical and organisational 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.

Clause 9. 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 of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.

9.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) of Regulation (EU) 2016/679, 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 of Regulation (EU) 2016/679, 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.

9.2 Data breach concerning data processed by the processor. 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 having become aware of the breach. Such notification shall contain, at least: (a) a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned); (b) the details of a contact point where more information concerning the personal data breach can be obtained; (c) its likely consequences and the measures taken or proposed to be taken to address the breach, including 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.

The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller's obligations under Articles 33 and 34 of Regulation (EU) 2016/679.

Section III — Final provisions. Clause 10. Non-compliance with the Clauses and termination

(a) Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, 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 the contract 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 point (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 its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725; (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 Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(c) The processor shall be entitled to terminate the contract 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 7.1 (b), the controller insists on compliance with the instructions.

(d) Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.

Annex I — List of parties

Controller: the organisation registered in domusdesk (an agency, a professional or a private owner), with the name, address and tax identifiers given in its settings; contact person: the person with the OWNER role who accepted these Clauses, at the contact details of their account; data protection officer: where designated, the one the organisation names in its settings. Signature and date of accession: the electronic acceptance domusdesk records (person, date and time, version and SHA-256 digest of this text), of which the organisation can download a copy from its settings.

Processor: Lelio Pellegrini, owner of the domusdesk software (www.domusdesk.com); contact for this agreement: portezuelos.info@gmail.com; the full identification and tax details are given in the terms of service. Signature and date of accession: the publication of this version of the text on the site, with its digest.

Annex II — Description of the processing

Categories of data subjects: the people the organisation records in the software — owners and landlords, tenants and guarantors, buyers and sellers, enquirers and visitors, suppliers and professionals, co-owners and condominium administrators, beneficial owners and representatives of companies — and the organisation's own staff who use it (members, invitees).

Categories of personal data: identification and contact data; tax code, VAT number and billing data; bank details; copies of identity documents and the evidence of anti-money-laundering due diligence (identification, beneficial owner, political exposure, sanctions lists, purpose and nature of the relationship, origin of funds, the risk assessment the organisation records); contracts, mandates, deadlines, payments and commissions; documents and photographs of the properties; communications, enquiries and viewings; access and activity logs.

Sensitive data: the service is not intended to process the special categories of Article 9 or the data of Article 10 GDPR, beyond what anti-money-laundering law requires the organisation to collect (for example the outcome of a sanctions-list check). Safeguards applied: encryption of identity-document data, access limited to authorised roles, a log of every reading of an anti-money-laundering file, limits on export, no use of these data by any artificial-intelligence function.

Nature of the processing: storage, organisation, consultation, computation of deadlines and amounts, retrieval and export, backup, erasure, through cloud software the organisation's staff access with their own credentials.

Purposes for which the data are processed on behalf of the controller: the organisation's management of its own properties, contracts, people, deadlines, documents, works and collections, and the performance of its legal duties, including the due-diligence and record-keeping duties of Italian Legislative Decree 231/2007 where the organisation is an obliged entity. The software collects evidence and flags anomalies; it never decides compliance, never assigns a risk level and never files a report: those remain the organisation's choices and duties.

Duration of the processing: the duration of the subscription, plus the 30-day recovery period after it ends and the rotation of backups (7 days of database history, 35 days of stored file versions). Documented instruction on anti-money-laundering retention: the data and documents the organisation classifies as anti-money-laundering evidence are retained for the number of years the organisation sets in the software for its country (ten years in Italy, Article 31 of Legislative Decree 231/2007), including after the end of the contract, in a separate archive, kept in the encrypted document store and no longer accessible to the organisation's staff, and destroyed when the term ends; the organisation may export them at any time. This is an instruction of the controller under Clause 7.1(a) and the storage required by Member State law under Clause 10(d).

Annex III — Technical and organisational measures

Measures implemented by the processor (described concretely, as the Annex requires; the current technical detail is in the security documentation domusdesk publishes):

1. Separation of each organisation's data enforced by the database (row level security): every read and write happens inside the context of one organisation; no function reads the data of several organisations, except platform administration, limited to subscription data and logged, and the explicit, expiring and logged sharing of one property's file that an organisation grants to another. 2. Encryption: in transit with TLS; at rest in the database and the document store; identity-document data and the answers of verification providers encrypted with AES-256-GCM under a key kept outside the backups and escrowed with more than one person. 3. Documents served only through signed, expiring links; a versioned, deletion-protected store; a copy with a second provider under separate credentials. 4. Database backups with point-in-time recovery; a restore drill before go-live and every quarter, timed; a per-organisation restore procedure, drilled on test data before it is needed. 5. Identification and authorisation: credentials with a hashed password, a second factor, passkeys; expiring sessions; rate limits; the OWNER, MANAGER and AGENT roles checked server-side on every action; bulk export reserved to the OWNER. 6. Event logging: every creation, change, deletion and export recorded with its author and address; every reading of an anti-money-laundering file and every opening of a document scan recorded; a log that cannot be changed, except the redaction of personal details after an erasure, and cannot be deleted, except the anti-money-laundering access records after 24 months. 7. Limited retention: terms per class of data applied by the software (anti-money-laundering evidence for the statutory term the organisation sets; the anti-money-laundering access log 24 months, the other activity-log rows the life of the organisation; notifications 90 days; exports until their link expires); a visible trash and restore. 8. System administrators: a single administrator, designated in writing, with a list available to the authority, a yearly review and, for the application's own systems (the activity log and the platform access log), administrative access logs kept for at least six months, complete and not alterable by the application; the logs that the infrastructure providers keep of administrative access are theirs and are governed by their own terms; for this processing the controller entrusts the processor, under point 3 bis of the Italian Data Protection Authority's measure of 27 November 2008, with the fulfilment of points (d) and (e) of that measure. 9. Secure development: dependencies kept current, automatic checks on every change, additive migrations, verification of security headers and database policies, error reporting to a monitoring service without personal data. 10. Minimisation: no data from anti-money-laundering files, identity documents or biometrics enters any artificial-intelligence function; no biometric data is processed. 11. Portability and erasure: a complete export in open formats available to the OWNER at any time, including during suspension and the recovery period; deletion of the organisation at the end of the recovery period, except the anti-money-laundering archive of Annex II.

Assistance to the controller (Clauses 8 and 9):

(a) Breaches: first notice to every OWNER of the affected organisation within 24 hours of becoming aware, with the contents of Clause 9.2, updates as information becomes available, support in completing the notification to the authority and the communication to data subjects, a final report. (b) Data subjects' rights: every request received forwarded to the OWNER without answering on the merits; tools for consultation, rectification, per-subject export and erasure within the limits of the law, on the organisation's instruction; restriction through the legal archive. (c) Impact assessment: a platform assessment and a data protection impact assessment template for the organisation, with the controller's fields to complete, provided by domusdesk; adoption remains the controller's. (d) Documentation: the security documentation and the records needed to demonstrate compliance with these Clauses, on request; cooperation with audits on reasonable notice.

Annex IV — List of sub-processors

Note: this Annex is completed only in the case of specific authorisation of sub-processors (Clause 7.7(a), Option 1). The Parties chose Option 2, the general written authorisation: the agreed list of sub-processors, with their seat, the activity performed, the place of processing and the transfer mechanism, is the one domusdesk publishes on the sub-processors page of its site (until it is published, the list given in the privacy notice). Every addition or replacement is notified in writing to the organisation's OWNERs at least 14 days in advance, with the information needed to object.